Design Dna Skill
Designdesign-dna-skillDesign Dna Skill is an Agent Skill for design published in the majiayu000/claude-skill-registry repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.
Skill describing how to interpret, enforce, and evolve design-dna.json across projects. Used by design-system-architect, builders, and gate agents.
How to use this skill
Bring this guide into your coding agent with a prompt tailored to the tool you use.
- Open your project in Codex.
- Copy and paste the prompt below.
- Review files and risks before approving any action.
Inspect the Agent Skill at https://github.com/majiayu000/claude-skill-registry/blob/HEAD/skills/data/design-dna-skill/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/design-dna-skill, but wait for my approval before writing files or running scripts.
Copying this prompt does not install or run the skill. Review third-party files before use.
Design-DNA Skill – Tokens & Patterns
This skill provides shared understanding of design-dna for all lanes.
It is used by:
design-system-architect- Implementation agents (e.g.
nextjs-builder,expo-builder) when applying tokens - Gate agents (
nextjs-standards-enforcer, design QA) when checking usage
Core Concepts
design-dna.jsonencodes:- Color palette + semantic roles,
- Typography scale and roles,
- Spacing grid,
- Named patterns (cards, layouts, shells, etc.).
- It is the law for UI work: where tokens exist, ad-hoc values are forbidden.
Usage Pattern
-
When reading design-dna:
- Identify available roles for:
- Colors (primary, secondary, accent, surface, etc.),
- Typography (display, heading, body, caption),
- Spacing (base grid, section spacing, gaps),
- Patterns (hero, card grid, dashboard shell, etc.).
- Note any documented minimums or constraints (e.g., minimum font size).
- Identify available roles for:
-
When applying tokens in implementation:
- Map design-dna roles to the project's styling tools:
- CSS variables,
- Utility classes,
- Component variants.
- Avoid creating new arbitrary values when tokens already cover the need.
- Map design-dna roles to the project's styling tools:
-
When enforcing tokens in gates:
- Treat:
- Inline styles and raw hex values as hard violations when tokens exist,
- Spacing and typography outside the defined scales as violations,
- Overuse/misuse of accent colors as design-dna violations if documented.
- Treat:
This skill ensures all agents reason about design-dna in a consistent way and know when to consult project design documentation for deeper schema and examples.