菜单
Use when creating or maintaining docs/BRAND.md as the brand-facing source of truth for tone, identity, naming, copy, storytelling, and visual direction.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
Use when a new goal, feature request, migration, or non-trivial change needs focused clarification before PRD, spec, plan, or implementation work begins.
Use when implementing repository changes through the smallest safe path, from direct routine fixes to risk-driven clarification, specs, plans, task coordination, validation, and documentation updates.
Use when a user asks to use OpenArc generally, initialize governance, improve repository continuity, audit governance drift, migrate an existing workspace, or choose which OpenArc skill should handle a request.
Use when producing a lightweight implementation plan before coding, including scope, affected systems, migration, rollback, tests, reuse, and architecture impact.
Use when auditing repository governance read-only, or when explicitly initializing or repairing governance and patching an agent guide without destructive rewrites.
Use when creating or updating OpenArc feature specs with acceptance criteria, compatibility decisions, and technical direction.
| name | brand-governance |
| description | Use when creating or maintaining docs/BRAND.md as the brand-facing source of truth for tone, identity, naming, copy, storytelling, and visual direction. |
Use this skill when a repository needs brand, voice, naming, or communication consistency.
Maintain docs/BRAND.md as the source of truth for product identity and communication.
If the user has not clearly specified brand direction, follow this flow before writing:
docs/PRD.md, docs/DESIGN.md, and docs/assets/brand/*.docs/BRAND.md.Do not merge docs/BRAND.md with docs/DESIGN.md.
BRAND.md explains what the product should feel and sound like.
DESIGN.md explains how the UI should be implemented.
docs/assets/brand/ when logo or identity assets exist.