plugin87/ux-ui-agent-skills

governance

Govern how the design system evolves — SemVer for tokens/components, the contribution workflow, deprecation policy, and change communication.

ソースを見る

使い方

  1. インストールコマンドをコピーし、自分の環境へ導入する前にソースを確認します。
  2. 必要なツール、認証情報、対応環境を原文で確認します。
  3. 入力と成果物を指定し、出力を資料と照合します。
npx skills add https://github.com/plugin87/ux-ui-agent-skills --skill governance

開始前の確認

  • 導入にはモデル契約、API枠、ファイルへのアクセス許可は含まれません。
  • スター数や導入数は活動の指標であり、独立した品質・安全性試験ではありません。
リポジトリの原文

見出し、例、コード、表、リンク、参照画像を含む原文を表示しています。

Skill: Governance

Step 0 — is the kit here? This skill reads files from the kit. Check once: ls ${CLAUDE_SKILL_DIR}/../../../tokens >/dev/null 2>&1 && echo KIT_OK || echo KIT_MISSING On KIT_MISSING only the skill folders were installed, which is what npx skills add does. Say so plainly, point the user at npx ux-ui-agent-skills init or the plugin install, and stop. Do not guess the contents of a file you could not open.

Keep the system consistent as it grows. Apply versioning, contribution, and deprecation rules.

Steps

  1. Read ${CLAUDE_SKILL_DIR}/../../../workflows/governance.md (SemVer table, contribution workflow, deprecation policy, change comms).
  2. Classify the change: major (breaking — renamed/removed token or prop, changed anatomy/default), minor (additive — new token/component/variant/optional prop), patch (fix — contrast/bug/doc/value tweak in tolerance).
  3. For a new component/token: confirm it serves a real, repeated need (≥ 2 places) before promoting product → candidate → core. Design it to the full quality bar (.claude/rules/components.md → Component Quality Bar).
  4. For a deprecation: mark with reason + replacement + removal version; keep working ≥ 1 minor cycle; provide a migration map (${CLAUDE_SKILL_DIR}/../../../design-systems/crosswalk.md style); remove only in a major.
  5. Wire any new file into CLAUDE.md (File Reference Map + relevant table/router) and add a changelog entry.

Verification (definition of done)

  • Change has a SemVer level and a changelog entry.
  • Removals have a deprecation window, a replacement, and a migration table.
  • New spec meets the 8-state + a11y + token-mapping bar and is reachable via the router.
  • python3 ${CLAUDE_SKILL_DIR}/../../../scripts/validate_tokens.py passes; contrast re-checked if colors changed.

タスクに関連する項目

同じリポジトリから

関連する 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日