Use for DESIGN.md visual identity contracts; author, scaffold, lint, diff, and export design contracts with the upstream spec and CLI.
インストールする前に、エージェントに与えられる指示の中身を確認できます。
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.mdまだレビューはありません。使ってみた感想をお寄せください。
概要と使いどころ
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
日本語の概要は準備中です。原文の説明を表示しています。
Use when a project has 50+ files, missing context, or explicit $codex-genome request; generates multi-layer project context to reduce hallucination.
日本語の概要は準備中です。原文の説明を表示しています。
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.
日本語の概要は準備中です。原文の説明を表示しています。
Use when code changes may require documentation updates; maps git diff to candidate docs without auto-editing documentation.
日本語の概要は準備中です。原文の説明を表示しています。
Use for documents, reports, memos, guides, academic papers, or formal text that needs clear structure, reliable tone, formatting, and diagrams.
日本語の概要は準備中です。原文の説明を表示しています。
Use when frontend, backend, mobile, data, DevOps, or security work needs domain routing and at most four focused references.
日本語の概要は準備中です。原文の説明を表示しています。