本文へ移動
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.

レビュー

まだレビューはありません。使ってみた感想をお寄せください。

同じリポジトリのスキル

概要と使いどころ

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月12日 更新

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月12日 更新

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月12日 更新

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月12日 更新

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月12日 更新

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月12日 更新

armanisadeghi のスキルをすべて見る

このスキルの問題を報告する