design-system-implementation
/design-system-implementation
Implement or refine reusable design tokens and interface components that follow an existing product direction. Use when establishing tokens, component APIs, variants, states, or cross-screen consistency.
- Author
- helx0071 ↗
- Repository
- skillsmo ↗
- Licence
- MIT
- Last repository change
- 12.11.2026
Assessment and security
- Files in this package
- 3
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 12.11.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Implement or refine reusable design tokens and interface components that follow an existing product direction. Use when establishing tokens, component APIs, variants, states, or cross-screen consistency.
Original author description
Implement or refine reusable design tokens and interface components that follow an existing product direction. Use when establishing tokens, component APIs, variants, states, or cross-screen consistency.
How it works
- Goal
- Workflow
- Decision rules
- Boundaries
- Completion standard
- Further reading
SKILL.md preview
--- name: design-system-implementation description: "Implement or refine reusable design tokens and interface components that follow an existing product direction. Use when establishing tokens, component APIs, variants, states, or cross-screen consistency." --- # Design-system implementation ## Goal Turn the product's visual and interaction rules into accessible, composable interface primitives. ## Workflow 1. Inspect the existing design source of truth, framework, styling conventions, component library, and representative screens. 2. Identify repeated decisions in color, typography, spacing, borders, elevation, motion, and interaction states; distinguish actual patterns from one-off visuals. 3. Define semantic tokens and a small set of component contracts with clear variants, defaults, responsive behavior, and states. 4. Implement incrementally, replacing repeated values without breaking existing pages; preserve explicit exceptions with a reason. 5. Review keyboard, focus, contrast, reduced motion, responsive behavior, theming, and usage examples across representative components. ## Decision rules - Extend existing tokens and components before adding a competing visual system. - Prefer semantic tokens over raw values in shared components. - Keep component APIs small; add a variant only when real screens need distinct behavior. ## Boundaries - Do not overwrite an existing brand or design source without user direction. - Do not claim a system is consistent because a single demo screen uses the new tokens. ## Completion standard Return the requested artifact or findings with enough evidence for a reviewer to understand what changed, what was checked, and what remains uncertain. Distinguish observed facts, inferred risks, and unverified assumptions. Keep the scope tied to the user's request. ## Further reading - [Field guide](references/field-guide.md) — use for task-specific review questions and edge cases. - [Source and rights notes](references/source-notes.md) — use when maintaining this package or reviewing its provenance.
Files in this package (3)
- SKILL.md 2 KB
- references/field-guide.md 1 KB
- references/source-notes.md 3 KB
Versions
The database has no other skills named design-system-implementation.
Database snapshot: 13.11.2026 · package version 01a8f6b6bcdd (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100design-build
Implement or refine frontend visual design, CSS, layout, typography, color tokens, and component states. Use when creating or styling an interface. - 100design-systems
Use when building or maintaining a component library and design tokens. Covers token architecture, component API design, variants and states, documentation, and governing adoption across a codebase. Trigger on "build a component library", "we have six different button… - 100frontend-design
UI component design principles, visual hierarchy, spacing, typography for Next.js apps. Use when building or reviewing React/Next.js components, setting up design tokens, or establishing visual consistency. - 90briefbound-design-system
Use when a frontend task primarily concerns cross-component design tokens, semantic theming, component APIs, variants and states, shared primitives, Storybook or library governance, Figma-to-code consistency, or a staged design-system migration; do not use for a single page,… - 100dh-build-design-system
Use when someone wants a design system built from the UI an app already ships, or one phase of it, such as \"extract tokens from the app\", \"add states to our Button\", \"replace the hardcoded colors with tokens\" or \"start a design system\". Moving screens onto an existing… - 90design-spec-review
Review a component or screen against its spec (variants, states, accessibility, tokens). Distinct from review-hard (general risk) and repo-consistency-sweep (pattern matching). Activates when a slice's Scope touches a design-system component with no cited design-spec-review…