사용 방법
- 설치 명령을 복사하고 자신의 에이전트 환경에 설치하기 전에 소스 패키지를 확인하세요.
- 필요한 도구, 인증 정보, 지원 환경은 원본 문서에서 확인하세요.
- 입력과 원하는 산출물을 설명하고 출처와 결과를 대조하세요.
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.

