跳到正文
cccskills
免费在 GitHub 公开

codex-design-md

Use for DESIGN.md visual identity contracts; author, scaffold, lint, diff, and export design contracts with the upstream spec and CLI.

中文简介正在准备中。当前显示原文说明。

查看安装方法

包含的文件(8)

  • SKILL.md2.0 KB
  • agents/openai.yaml276 B
  • assets/design-md-template.md3.3 KB
  • references/cli-commands.md3.0 KB
  • references/integration-playbook.md2.1 KB
  • references/spec-essentials.md2.7 KB
  • scripts/design_context.py7.2 KB
  • scripts/design_contract.py29.8 KB

SKILL.md(原文)

安装前可以查看交给 AI 代理的指令内容。

TL;DR

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.

Activation

  1. Activate when the user mentions DESIGN.md, design tokens, Tailwind theme export, DTCG export, or a reusable visual identity contract.
  2. Activate on $design-md, "create a design contract", "lint DESIGN.md", or "export design tokens".
  3. Load alongside codex-frontend-design when UI work needs both creative direction and a durable source-of-truth file.
  4. Auto-load when frontend-specialist is active and the task needs persistent design-system artifacts.

Decision Flow

  1. If no DESIGN.md exists, scaffold one first with scripts/design_contract.py scaffold.
  2. Use references/spec-essentials.md to keep tokens and sections inside the canonical format.
  3. Validate with scripts/design_contract.py lint before relying on the contract.
  4. Compare revisions with scripts/design_contract.py diff when the contract changes.
  5. Export to Tailwind or DTCG with scripts/design_contract.py export only after lint is clean.

Rules

  • Treat DESIGN.md as the durable source of truth for visual identity; do not scatter token decisions across ad-hoc prompts.
  • Keep the file canonical: YAML tokens first, then markdown sections in spec order.
  • Use exact token values. Do not write vague prose where a token should exist.
  • Pair this skill with codex-frontend-design (references/ for OKLCH palettes, typography, layouts, motion) for the visual vocabulary.
  • Prefer validation and diff evidence over aesthetic claims.

Reference Files

  • references/spec-essentials.md
  • references/cli-commands.md
  • references/integration-playbook.md

评价

还没有评价。欢迎分享你的使用感受。

评论

无需登录即可发表。欢迎分享使用感受、提问,或说明在哪些环境下无法运行。

还没有评论。来写第一条吧。

提交后会立即公开。请勿填写邮箱、电话等个人信息。URL 最多 2 个。

0 / 1000 字

此表单受 reCAPTCHA 保护,适用 Google 的隐私权政策和服务条款。

同一仓库的技能

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

中文简介正在准备中。当前显示原文说明。

Bang-isme/CodexAI---Skills102026年10月5日 更新

Use when a project has 50+ files, missing context, or explicit $codex-genome request; generates multi-layer project context to reduce hallucination.

中文简介正在准备中。当前显示原文说明。

Bang-isme/CodexAI---Skills102026年10月5日 更新

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.

中文简介正在准备中。当前显示原文说明。

Bang-isme/CodexAI---Skills102026年10月5日 更新

Use when code changes may require documentation updates; maps git diff to candidate docs without auto-editing documentation.

中文简介正在准备中。当前显示原文说明。

Bang-isme/CodexAI---Skills102026年10月5日 更新

Use for documents, reports, memos, guides, academic papers, or formal text that needs clear structure, reliable tone, formatting, and diagrams.

中文简介正在准备中。当前显示原文说明。

Bang-isme/CodexAI---Skills102026年10月5日 更新

Use when frontend, backend, mobile, data, DevOps, or security work needs domain routing and at most four focused references.

中文简介正在准备中。当前显示原文说明。

Bang-isme/CodexAI---Skills102026年10月5日 更新

查看 Bang-isme 的全部技能

报告此技能的问题