Communitygithub.com

ui-design-system

Shows an agent how to art-direct and build "ui design system" so the concrete output is a design-system pass with tokens. The procedure moves through UI design system, 1. Scope the job, 2. Inventory before deciding. Use it when a new assignment calls for this craft.

ui-design-system とは?

ui-design-system is a Claude Code agent skill that shows an agent how to art-direct and build "ui design system" so the concrete output is a design-system pass with tokens. The procedure moves through UI design system, 1. Scope the job, 2. Inventory before deciding. Use it when a new assignment calls for this craft.

対応~Claude Code~Codex CLI~Cursor
npx skills add https://github.com/Hesham-14/skills-g-hub/tree/HEAD/skills/ui-design-system

お気に入りのAIに質問する

このエージェントスキルを事前に読み込んだ状態で新しいチャットを開きます。

ドキュメント

UI design system

A design system here is the project's existing visual language made explicit, consistent and reusable. Extract and improve what is there; create only what is missing; keep the project's framework and styling approach. Do not introduce React, Tailwind, shadcn, a token build tool or any package the project does not already use, unless the user approves that specific addition.

If a skill named here is not installed, apply the intent stated in this file and say which one was missing; never install it.

1. Scope the job

RequestOutput
Extract / documentDESIGN.md or the project's design doc: current tokens, components, rules, known drift
ConsolidateOne source per token and component; call sites migrated within the agreed scope
ExtendNew tokens, a theme, RTL support or a new shared component, fitting the existing system
Slice for a UI changeOnly the tokens/components that change needs; record the rest as drift

Migration of every call site is its own decision: propose it with a count, and change only the files the user's scope includes.

2. Inventory before deciding

Read the real sources: CSS custom properties and theme blocks, Tailwind @theme or config, shared stylesheets, page-level style blocks, component/macro/partial folders, existing design docs and reference screenshots. Count, do not estimate:

  • distinct values per category (colour, font size, spacing, radius, shadow, z-index, breakpoint), with how often each appears and where;
  • hard-coded values that duplicate a token;
  • the same concept implemented under different names or markup;
  • themes defined twice, or tokens missing from one theme.

A grep/rg count over the style sources is enough; keep the command in the report so the count can be rerun.

3. Define or repair the tokens

Follow tokens.md: semantic roles over raw values, a small scale per category derived from values already in use, theme and direction rules, and contrast verified per theme. Every token has one definition site.

4. Define or repair the components

Follow components.md: an inventory of the patterns that exist, a state matrix per component, one implementation per concept in the project's own component model (React component, Jinja macro, CSS class contract), and interaction conventions.

5. Write it down where agents will read it

Record the system in the project's existing design doc, or DESIGN.md at the root when none exists, and point to it from docs/agents/workflow.md or the agent instruction file only with the user's agreement. Keep the doc a map: token names, roles, scales, component list with file locations, rules that are not obvious from the code, and remaining drift with counts. Leave values the code already states to the code.

6. Verify

Token and component changes ripple. Run the project's build and tests, then the visual loop from ui-engineering (references/visual-feedback-loop.md) on every screen that uses a changed token or component, in every theme and direction. Hand the change to ui-guard. Report counts before and after, the screens checked, and what drift remains.

関連スキル