plugin87/ux-ui-agent-skills

observe

Show whether the agent followed the kit''s rules in recent sessions: pages edited and measured, Stop hook blocks, findings left open.

ソースを見る

使い方

  1. インストールコマンドをコピーし、自分の環境へ導入する前にソースを確認します。
  2. 必要なツール、認証情報、対応環境を原文で確認します。
  3. 入力と成果物を指定し、出力を資料と照合します。
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_MISSING On KIT_MISSING only the skill folders were installed. Say so, point the user at the plugin install or npx ux-ui-agent-skills init, and stop.

Report what the hooks recorded - never a reconstruction from memory.

  1. 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).

  1. Quote the summary lines it prints. If it says no session edited UI, say that

and stop: there is nothing to judge.

  1. 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.

  1. 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.

同じリポジトリから

関連する Skills

すべての Skills
plugin87
コミュニティ

critique

Adversarial design critique of the current work. Render it, look at it, and argue for rejection. Run after the gates are green, never instead of them.

1時間の導入数
1
GitHub Stars
3207
更新日
11月18日
plugin87
コミュニティ

design-qa

Set up or run design QA gates for token + hardcoded-value lint, automated a11y (axe), contrast, visual regression across variants/states/themes/RTL, and the manual a11y checklist. Use when the user wants CI quality gates, to prevent design regressions, or to QA a component/screen before shipping.

1時間の導入数
2
GitHub Stars
3200
更新日
11月18日
plugin87
コミュニティ

redesign

Upgrade an existing website or app to premium quality without breaking functionality. Audit the current design, identify generic/AI tells, then apply taste and system rules surgically. Use when the user wants to improve, modernize, polish, or "make better" an existing UI/codebase.

1時間の導入数
2
GitHub Stars
3200
更新日
11月18日
plugin87
コミュニティ

data-dashboard

Build a dense, data-heavy screen - an analytics console or a trading terminal - with real charts drawn from tokens: candlestick, volume, depth, stacked area, waterfall, scatter, correlation matrix, donut, gauge, sparklines, heatmaps and order books. Use when the request is a dashboard, terminal, monitoring view, data console, or any screen whose job is to show many numbers at once. Covers the layout sequence, the SVG geometry, the accessibility contract per chart type, and the contrast traps tha

1時間の導入数
1
GitHub Stars
3138
更新日
10月27日