본문으로 건너뛰기
cccskills
무료GitHub에 공개

feature-visibility-surface

A live demo or admin page shipped with every feature whose results the user would otherwise not see. Use when adding a backend endpoint or feature with no UI to see it, when output only shows in logs, the DB, or an agent run, or when the user asks 'how do I test this'.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

설치 방법 보기

포함된 파일(1)

  • SKILL.md2.9 KB

SKILL.md(원문)

설치하기 전에 에이전트에게 전달되는 지시 내용을 확인할 수 있습니다.

Ship a visibility surface with every feature (frontend recipe)

A feature the user can't open and watch work is a feature you'll both burn turns guessing about. Build the page in the SAME change — it's the next file, not a ticket.

Demo page or admin page?

  • No privileges to view → demo: (dev)/demos/<name>/page.dev.tsx (auth shell) or (public-demos)/demos/public/<name>/page.tsx (no auth). Auto-listed at /demos. Use the new-route-scaffold skill to place it.
  • Needs privileged / cross-user / admin data or actions → admin: (admin)/administration/<name>/page.tsx (super-admin gated at the layout; lower with an in-page selectIsAdmin seam if org-admins should reach it later).

Prefer the lower bar (demo) when unsure.

The recipe (self-contained features/<name>/)

  • Read the live backend, never hardcode the URL. Resolve the base from selectResolvedBaseUrl (apiConfigSlice) — the same value every backend call uses, so the admin server toggle routes it. Runtime-guard the JSON (untrusted). For authed POST/execute calls use the canonical backend client (lib/api/backend-client.ts → createAuthenticatedClient), not a hand-rolled fetch.
  • Make it a test bench, not just a viewer. A few Select/inputs to drive the feature; show the REAL result (and, for actions, the receipt). Reuse existing renderers — e.g. the features/matrx-envelope block renderer for live reference chips — never fork one.
  • Real states + real-time. Component-library loading/empty/error states (never plain "Loading…"), a manual Refresh + light polling so it mirrors the live server with no redeploy.
  • Standards. Semantic tokens only, Lucide icons, no emojis, dense + scannable for an admin surface (see ui-dense / data-dense-panels). No new barrels; import from source.

Reuse, never fork

Base URL resolver, backend client, component library, admin gate, envelope renderer — all exist. If you're writing a second fetch layer or a second renderer, stop.

Worked example (copy its shape)

features/directive-catalog/ → /administration/directive-catalog: a live grid of every capability (read from GET /directives/catalog) + a dropdown builder that runs one and shows the receipt (POST /directives/execute). That's the bar.

Done means

The page opens, reads the live backend, shows the real output, lets the user trigger/test the meaningful path, is reachable (feature admin map / /demos index), and you told the user the exact URL + what they'll see in your turn summary.

리뷰

아직 리뷰가 없습니다. 사용해 본 소감을 남겨 주세요.

댓글

로그인 없이 쓸 수 있습니다. 사용 후기, 질문, 작동하지 않은 환경 등을 편하게 남겨 주세요.

아직 댓글이 없습니다. 첫 댓글을 남겨 보세요.

보내면 바로 공개됩니다. 이메일 주소나 전화번호 같은 개인 정보는 쓰지 마세요. URL은 2개까지입니다.

0 / 1,000자

이 양식은 reCAPTCHA로 보호되며 Google 개인정보처리방침 및 서비스 약관이 적용됩니다.

같은 저장소의 스킬

Admin debug system wiring for the floating AdminIndicator's live debug data and Copy Full Context. Use when adding debug visibility to a route or feature, wiring useDebugContext or the debug panel, capturing console errors, or enabling the copy-context workflow for a page.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

armanisadeghi/ai-matrx32026년 10월 19일 업데이트

Compact two-icon Copy / Copy-for-AI controls (components/agent-copy). Use when adding copy buttons to a row, card, list, or record; merging duplicate Copy/JSON/AI controls; continuing the copy rollout; or writing a Copy-for-AI payload. NOT for markdown content actions (use rich-document-actions).

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

armanisadeghi/ai-matrx32026년 10월 19일 업데이트

Disclosing a surface's existing fixed AI jobs in the shell's top Agents menu. Use when a page, panel, overlay, or window already runs a mandate behind a button, assist, automatic action, or mode; when the agent-disclosure guard names a file; or during a surface check.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

armanisadeghi/ai-matrx32026년 10월 19일 업데이트

The watch-fix-rerun method for making an existing platform agent or automated process efficient and correct: baseline its ledger, run one unit yourself, fix the class behind every wasted call, rerun, record. Use when asked to improve, optimize, watch, or 'make efficient' an agent, a sandbox session, a sync job, or any recurring automated process.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

armanisadeghi/ai-matrx32026년 10월 19일 업데이트

Redux state for agent execution and firing agent shortcuts. Use when editing features/agents/redux/, building agent UI, creating a conversation, touching assembleRequest or NDJSON stream state, wiring agent-state selectors, adding a per-conversation capability, or triggering a shortcut from a button, menu, or code (useShortcutTrigger, launchAgentExecution).

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

armanisadeghi/ai-matrx32026년 10월 19일 업데이트

The provision for a call site: the exhaustive menu of values that place in the code can realistically produce. Use before creating or fixing a mandate or agent that reasons about more than its own input, when deciding whether an agent can answer at all with what it is sent, or when its output 'looks right' but nobody checked it could be. NOT for building the agent (use create-agent).

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

armanisadeghi/ai-matrx32026년 10월 19일 업데이트

armanisadeghi의 스킬 모두 보기

이 스킬의 문제 신고