This skill ensures that all new or modified UI is implemented in line with the project design system, rather than inventing ad-hoc styles.
Use it when:
- Implementing a new component, page, or flow.
- Refactoring existing UI to match the design system.
- Extending the design system with carefully considered new patterns.
It is designed to be used after a design system has been created (for example via the design-system-from-reference workflow).
Inputs and assumptions
- The project design system is defined in:
design/design-system.json (implementation-level source of truth).
- Optionally
design/design.json (higher-level style guide).
- The user can describe:
- What they want to build or change (component/page/flow).
- Any relevant constraints (framework, routing, data layer, accessibility).
- The codebase uses a consistent framework (e.g., React + Tailwind, or another typical web stack).
If design/design-system.json is missing, this skill should not free-style a new design system. Instead, it should:
- Ask the user to confirm whether a design system exists elsewhere.
- Suggest running the
design-system-from-reference workflow first.
Core responsibilities
When building or updating UI, this skill must:
Load and understand the design system
- Ingest
design/design-system.json (and design/design.json if present).
- Identify:
- Tokens (colors, spacing, radii, typography scales, shadows, etc.).
- Component definitions and their variants.
- Layout and spacing rules.
- Interaction states and motion guidelines.
- Summarize back to the user how the design system wants buttons, inputs, cards, navigation, etc. to look and behave.
Map the request to existing patterns
- For a new request (e.g., "build a billing settings page"):
- Break the UI into sections and components.
- For each part, map it to existing component types or patterns in the design system.
- If something genuinely new is needed:
- Propose how it fits into existing patterns (e.g., "This is a variant of the card component with…").
- Avoid inventing totally unrelated styling unless the user explicitly wants to extend the system.
Implement using the design system
- Use only tokens, utility classes, and component recipes defined by the design system whenever possible.
- Avoid arbitrary inline styles or one-off Tailwind utilities that conflict with the system.
- Respect:
- Typography hierarchy (headings, body, labels, etc.).
- Spacing scale and layout rules.
- Color usage rules for states (primary, secondary, error, warning, success, disabled, etc.).
- Motion and interaction patterns.
- Keep code production-quality: clear structure, accessible semantics (ARIA, labels, keyboard navigation), and sensible component boundaries.
Handle extensions carefully
- When the design system does not explicitly cover a case:
- First, try to express the new UI using combinations or variants of existing components.
- If an extension is truly needed, propose an addition to
design/design-system.json:
- Describe new tokens, component variants, or layout rules.
- Ensure they are consistent with the existing system.
- Present the proposed JSON patch or snippet to the user for review before updating the design system.
Validate adherence
- After generating code, briefly explain how it follows the design system:
- Which tokens/variants were used.
- How spacing/typography align with the rules.
- If any deliberate deviations were made (e.g., an experimental component), call them out clearly.
Suggested workflow when invoked
- Confirm context
- Ask the user:
- What they want built or changed.
- Where in the codebase it lives (paths, existing components).
- Whether there is an existing design system JSON; if unsure, search for
design/design-system.json.
- Load design system files
- Open
design/design-system.json (and design/design.json if present) and summarize the relevant parts for this task.
- Plan the implementation
- Break the UI into logical components/sections.
- For each, decide which design system components or patterns to use.
- Share this plan with the user and pause for confirmation.
- Implement incrementally
- Update or create components in small, reviewable steps.
- After each significant chunk (e.g., a component or page section), pause and:
- Show the diff or the new code.
- Explain how it adheres to the design system.
- Optional: update the design system
- If new patterns were introduced, propose JSON additions/changes for
design/design-system.json.
- Only modify the design system after explicit user approval.
- Summarize and hand off
- Recap what was built/changed and how it aligns with the design system.
- List any follow-ups (e.g., applying the same patterns to other screens, updating docs).
Interaction with other skills
- When combined with
design-system-from-reference:
- Run
design-system-from-reference first to create or update the design system files.
- Then use this
design-system-implementation skill for all subsequent UI work.
- When combined with
frontend-design-concept:
- Use
frontend-design-concept for exploring bold conceptual directions.
- Once a direction is chosen and codified into the design system, use
design-system-implementation to roll out consistent implementations across the app.
1---2name: design-system-implementation3description: Build or update frontend components and pages that strictly adhere to the project design system defined in design/design-system.json (and design/design.json when present).4category: design5license: Complete terms in LICENSE.txt6metadata:7 source: https://skillmd.com/skills/dundas/design-system-implementation8---910This skill ensures that all new or modified UI is implemented **in line with the project design system**, rather than inventing ad-hoc styles.1112Use it when:13- Implementing a new component, page, or flow.14- Refactoring existing UI to match the design system.15- Extending the design system with carefully considered new patterns.1617It is designed to be used **after** a design system has been created (for example via the `design-system-from-reference` workflow).1819## Inputs and assumptions2021- The project design system is defined in:22 - `design/design-system.json` (implementation-level source of truth).23 - Optionally `design/design.json` (higher-level style guide).24- The user can describe:25 - What they want to build or change (component/page/flow).26 - Any relevant constraints (framework, routing, data layer, accessibility).27- The codebase uses a consistent framework (e.g., React + Tailwind, or another typical web stack).2829If `design/design-system.json` is missing, this skill should **not** free-style a new design system. Instead, it should:30- Ask the user to confirm whether a design system exists elsewhere.31- Suggest running the `design-system-from-reference` workflow first.3233## Core responsibilities3435When building or updating UI, this skill must:36371. **Load and understand the design system**38 - Ingest `design/design-system.json` (and `design/design.json` if present).39 - Identify:40 - Tokens (colors, spacing, radii, typography scales, shadows, etc.).41 - Component definitions and their variants.42 - Layout and spacing rules.43 - Interaction states and motion guidelines.44 - Summarize back to the user how the design system wants buttons, inputs, cards, navigation, etc. to look and behave.45462. **Map the request to existing patterns**47 - For a new request (e.g., "build a billing settings page"):48 - Break the UI into **sections and components**.49 - For each part, map it to existing component types or patterns in the design system.50 - If something genuinely new is needed:51 - Propose how it fits into existing patterns (e.g., "This is a variant of the card component with…").52 - Avoid inventing totally unrelated styling unless the user explicitly wants to extend the system.53543. **Implement using the design system**55 - Use **only** tokens, utility classes, and component recipes defined by the design system whenever possible.56 - Avoid arbitrary inline styles or one-off Tailwind utilities that conflict with the system.57 - Respect:58 - Typography hierarchy (headings, body, labels, etc.).59 - Spacing scale and layout rules.60 - Color usage rules for states (primary, secondary, error, warning, success, disabled, etc.).61 - Motion and interaction patterns.62 - Keep code production-quality: clear structure, accessible semantics (ARIA, labels, keyboard navigation), and sensible component boundaries.63644. **Handle extensions carefully**65 - When the design system does not explicitly cover a case:66 - First, try to express the new UI using **combinations or variants** of existing components.67 - If an extension is truly needed, propose an addition to `design/design-system.json`:68 - Describe new tokens, component variants, or layout rules.69 - Ensure they are consistent with the existing system.70 - Present the proposed JSON patch or snippet to the user for review before updating the design system.71725. **Validate adherence**73 - After generating code, briefly explain **how** it follows the design system:74 - Which tokens/variants were used.75 - How spacing/typography align with the rules.76 - If any deliberate deviations were made (e.g., an experimental component), call them out clearly.7778## Suggested workflow when invoked79801. **Confirm context**81 - Ask the user:82 - What they want built or changed.83 - Where in the codebase it lives (paths, existing components).84 - Whether there is an existing design system JSON; if unsure, search for `design/design-system.json`.852. **Load design system files**86 - Open `design/design-system.json` (and `design/design.json` if present) and summarize the relevant parts for this task.873. **Plan the implementation**88 - Break the UI into logical components/sections.89 - For each, decide which design system components or patterns to use.90 - Share this plan with the user and pause for confirmation.914. **Implement incrementally**92 - Update or create components in small, reviewable steps.93 - After each significant chunk (e.g., a component or page section), pause and:94 - Show the diff or the new code.95 - Explain how it adheres to the design system.965. **Optional: update the design system**97 - If new patterns were introduced, propose JSON additions/changes for `design/design-system.json`.98 - Only modify the design system after explicit user approval.996. **Summarize and hand off**100 - Recap what was built/changed and how it aligns with the design system.101 - List any follow-ups (e.g., applying the same patterns to other screens, updating docs).102103## Interaction with other skills104105- When combined with **`design-system-from-reference`**:106 - Run `design-system-from-reference` first to create or update the design system files.107 - Then use this `design-system-implementation` skill for all subsequent UI work.108- When combined with **`frontend-design-concept`**:109 - Use `frontend-design-concept` for exploring bold conceptual directions.110 - Once a direction is chosen and codified into the design system, use `design-system-implementation` to roll out consistent implementations across the app.