Pre-release gate — run the full gate, responsive + render checks, then produce the release checklist (README badge/current/changelog). Use before tagging a release.
インストール方法を見るインストールする前に、エージェントに与えられる指示の中身を確認できます。
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_MISSINGOnKIT_MISSINGonly the skill folders were installed, which is whatnpx skills adddoes. Say so plainly, point the user atnpx ux-ui-agent-skills initor the plugin install, and stop. Do not guess the contents of a file you could not open.
Gate first, then prepare the release. Do nothing destructive without explicit confirmation (no tag, no publish) — this command verifies and drafts only.
Quality gate (must be fully green before continuing):
node ${CLAUDE_SKILL_DIR}/../../../scripts/accuracy_report.mjs — report the real N/N.node ${CLAUDE_SKILL_DIR}/../../../scripts/verify_responsive.mjs examples — no overflow at 280/320/414.python3 ${CLAUDE_SKILL_DIR}/../../../scripts/check_no_emoji.py — UI + taste + instruction surface.
If anything fails, stop and fix; do not proceed to the checklist.Release checklist (per the project release rule):
README.md: version badge, "current" line, and changelog entry.examples/apple-home stays gitignored (local IP).Output a ready-to-review summary: the green N/N line, the proposed version,
and the drafted changelog entry. Wait for the user to approve before any
git tag / publish step.
まだレビューはありません。使ってみた感想をお寄せください。
概要と使いどころ
Audit a UI or design against WCAG 2.2 AA/AAA and ARIA patterns, returning criterion-referenced findings with severity and specific fixes. Use when the user wants an accessibility check, contrast verification, keyboard/screen-reader review, or wants to confirm a component meets POUR.
日本語の概要は準備中です。原文の説明を表示しています。
Apply a visual direction — an archetype (high-end agency, editorial minimal, brutalist, soft-SaaS, dark-tech) or one of 138 named design systems (apple, linear-app, stripe, vercel, notion, material, shadcn, spotify, tesla…) — by resolving it into the token system. Use when the user wants a specific look/vibe/brand feel, or asks to make a design feel premium/expensive/non-generic.
日本語の概要は準備中です。原文の説明を表示しています。
Generate a complete, accessible brand design system from a brief — primitive → semantic → component DTCG tokens (color, type, spacing, radius, shadow, motion), light + dark, plus a single theme.css — verified for WCAG. Use when the user wants a from-scratch brand/design foundation, a new palette + type system, or a themeable token kit for a product.
日本語の概要は準備中です。原文の説明を表示しています。
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.
日本語の概要は準備中です。原文の説明を表示しています。
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 that only appear in dark mode.
日本語の概要は準備中です。原文の説明を表示しています。
Generate production-ready, accessible, token-driven component code for ANY framework — React+Tailwind, Next.js, SwiftUI, Vue, Svelte, Angular, Solid, Web Components/Lit, React Native, Flutter, Jetpack Compose, vanilla CSS, or CSS-in-JS. Use when the user wants working UI code for a component or screen in a specific stack.
日本語の概要は準備中です。原文の説明を表示しています。