使い方
- インストールコマンドをコピーし、自分の環境へ導入する前にソースを確認します。
- 必要なツール、認証情報、対応環境を原文で確認します。
- 入力と成果物を指定し、出力を資料と照合します。
npx skills add https://github.com/plugin87/ux-ui-agent-skills --skill observe開始前の確認
- 導入にはモデル契約、API枠、ファイルへのアクセス許可は含まれません。
- スター数や導入数は活動の指標であり、独立した品質・安全性試験ではありません。
リポジトリの原文
見出し、例、コード、表、リンク、参照画像を含む原文を表示しています。
Step 0 - is the kit here? Check once:ls ${CLAUDE_SKILL_DIR}/../../../scripts/observe.mjs >/dev/null 2>&1 && echo KIT_OK || echo KIT_MISSINGOnKIT_MISSINGonly the skill folders were installed. Say so, point the user at the plugin install ornpx ux-ui-agent-skills init, and stop.
Report what the hooks recorded - never a reconstruction from memory.
- Run
node ${CLAUDE_SKILL_DIR}/../../../scripts/observe.mjs --project "$CLAUDE_PROJECT_DIR"
(or without --project when the user asks about every project, and with --days N when they name a window).
- Quote the summary lines it prints. If it says no session edited UI, say that
and stop: there is nothing to judge.
- For each session marked
BROKE A RULE, run it again with--session <id>and
say which rule failed and the timeline line that shows it.
- If the user wants the page, run it with
--html <path>and give the path.
What it measures, and what it does not: three counted rules per session - every edited page had a passing gate before the end, no fast-gate finding was left on a file's latest version, and the agent never finished while the Stop hook still had pages open. It says nothing about design quality, and an unfinished session is not counted for or against.
