使用方法
- 复制安装命令，在自己的智能体环境安装前先检查源码包。
- 从原始文档核对所需工具、凭据和支持的宿主。
- 说明输入材料与期望交付物，并对照来源检查输出。
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.
