plugin87/ux-ui-agent-skills

scaffold-project

Scaffold a new design-product project that matches the recommended Claude Code layout (the reference structure).

ソースを見る

使い方

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

開始前の確認

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

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

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.

Generate a new design-project skeleton from ${CLAUDE_SKILL_DIR}/../../../templates/product-design/ into a target directory the user names.

The layout to produce (exactly the reference structure):

<target>/
  # CONTEXT CLAUDE LOADS
  CLAUDE.md              the brief Claude reads every session
  CLAUDE.local.md        your personal prefs, gitignored
  .mcp.json              Figma, Notion, Drive connections

  # TEAM TOOLKIT
  .claude/
    rules/               conventions, loaded only when relevant
    skills/              repeatable workflows, off main context
    commands/            your custom slash commands
    settings.json        shared permissions, checked into git

  # YOUR PROJECT
  design-tokens.json     source of truth: color, type, spacing
  src/components/        the real UI Claude reads and edits
  public/images/         real images so prototypes don't break
  reference/             real screens Claude studies for context

The fast path, when the kit is installed or reachable via npx:

npx ux-ui-agent-skills new <target>

That does steps 2 and 3 below in one call (template copied, CLAUDE.local.md un-suffixed, engine areas installed without overwriting the lean brief). Then pick up at step 4. The manual steps are spelled out so the same result can be produced by hand from a clone.

Steps:

  1. Ask for the target directory if not given. Create it if it does not exist.
  2. Copy every file of ${CLAUDE_SKILL_DIR}/../../../templates/product-design/ into it, preserving the tree.

Two rules on the copy:

  • CLAUDE.local.md.template lands as CLAUDE.local.md (the suffix exists

only so the kit's own gitignore cannot swallow the file).

  • .gitkeep stays in .claude/skills/, .claude/commands/,

src/components/, public/images/, and reference/ so the empty folders survive the first commit. The template already ships .gitignore (which ignores CLAUDE.local.md), .mcp.json, .claude/settings.json, and three rules files (components.md, tokens.md, accessibility.md).

  1. Install the engine next to it so the gates the brief references actually run:
   npx ux-ui-agent-skills add tokens components taste accessibility \
       workflows content frameworks design-systems scripts skills

Use add, not init: init also writes the full engine CLAUDE.md over the lean project brief. The project brief stays short by design, and the engine knowledge loads from the copied folders when a task needs it.

  1. Install the render gates' one dependency in the target: npm i -D playwright.

Skipping this is silent: every render gate prints SKIPPED and exits 0.

  1. Fill in the placeholders in CLAUDE.md with the user: product, primary user,

stack, icon set, vocabulary. Leave nothing in angle brackets behind.

  1. Point design-tokens.json at the brand: replace the primitive.brand ramp,

keep the semantic and component tiers, then prove it still passes:

   python3 ${CLAUDE_SKILL_DIR}/../../../scripts/validate_contrast.py
  1. Remind the user to fill reference/ with real screens and public/images/

with real imagery, and to set the MCP env vars (FIGMA_API_KEY, ...) in their own shell. Never write a secret into .mcp.json.

Verify before handing over: the target tree matches the layout above, and

python3 ${CLAUDE_SKILL_DIR}/../../../scripts/validate_template.py

passes against the source template.

タスクに関連する項目

同じリポジトリから

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