菜单
Use for DESIGN.md visual identity contracts; author, scaffold, lint, diff, and export design contracts with the upstream spec and CLI.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | codex-design-md |
| description | Use for DESIGN.md visual identity contracts; author, scaffold, lint, diff, and export design contracts with the upstream spec and CLI. |
| load_priority | on-demand |
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-design-system 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-design-system for palettes, typography, layouts, and motion vocabulary.references/spec-essentials.mdreferences/cli-commands.mdreferences/integration-playbook.mdUse for project memory, decisions, handoffs, genome, knowledge index, changelog, and patterns that must persist across sessions.
Use for frontend, backend, mobile, debugging, security, or specialized engineering work that needs focused domain references and strict boundaries.
Use for prototype, MVP, fullstack feature, from-scratch feature, or multi-domain work that needs a SPEC.md before planning or implementation. Do not use for tiny one-file edits.
Use when code changes may require documentation updates; maps git diff to candidate docs without auto-editing documentation.
Use before completion, PR, deploy, handoff, or when verifying code changes. Runs advisory or blocking checks and reports evidence.
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.