Use for DESIGN.md visual identity contracts; author, scaffold, lint, diff, and export design contracts with the upstream spec and CLI.
The English summary is being prepared. Showing the original description.
See how to installReview the instructions the agent will receive before you install.
Load when a project needs a durable design contract, not just one-off styling advice. This skill adds a structured DESIGN.md layer with typed tokens, ordered rationale sections, and validation/export tooling. No upstream source checkout is required for the default workflow.
DESIGN.md, design tokens, Tailwind theme export, DTCG export, or a reusable visual identity contract.$design-md, "create a design contract", "lint DESIGN.md", or "export design tokens".codex-frontend-design when UI work needs both creative direction and a durable source-of-truth file.frontend-specialist is active and the task needs persistent design-system artifacts.DESIGN.md exists, scaffold one first with scripts/design_contract.py scaffold.references/spec-essentials.md to keep tokens and sections inside the canonical format.scripts/design_contract.py lint before relying on the contract.scripts/design_contract.py diff when the contract changes.scripts/design_contract.py export only after lint is clean.DESIGN.md as the durable source of truth for visual identity; do not scatter token decisions across ad-hoc prompts.codex-frontend-design (references/ for OKLCH palettes, typography, layouts, motion) for the visual vocabulary.references/spec-essentials.mdreferences/cli-commands.mdreferences/integration-playbook.mdNo reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Use when implementation is complete, all tests pass, and you need to decide how to integrate the work — guides completion of development work by presenting structured options for merge, PR, or cleanup
The English summary is being prepared. Showing the original description.
Use when a project has 50+ files, missing context, or explicit $codex-genome request; generates multi-layer project context to reduce hallucination.
The English summary is being prepared. Showing the original description.
Use when the task involves reading, creating, or editing `.docx` documents, especially when formatting or layout fidelity matters; prefer `python-docx` plus the bundled `scripts/render_docx.py` for visual checks.
The English summary is being prepared. Showing the original description.
Use when code changes may require documentation updates; maps git diff to candidate docs without auto-editing documentation.
The English summary is being prepared. Showing the original description.
Use for documents, reports, memos, guides, academic papers, or formal text that needs clear structure, reliable tone, formatting, and diagrams.
The English summary is being prepared. Showing the original description.
Use when frontend, backend, mobile, data, DevOps, or security work needs domain routing and at most four focused references.
The English summary is being prepared. Showing the original description.