菜单
Use when packaging an approved identity into a client-facing guide with logo, colour, typography, spacing, imagery, voice, and application rules. Unlike brand-visual-identity, this documents settled decisions rather than creating the identity.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Use when a game for children or learners needs age-appropriate comprehension, scaffolding, learning-feedback separation, privacy/safety, stopping cues, guardian/teacher needs, accessible play, or non-exploitative engagement. Use onboarding-and-first-run-design for ordinary apps.
Use when a game needs visual pillars, shape language, colour scripting, character/world readability, cultural motif governance, 2D/3D cohesion, VFX hierarchy, an asset bible, style scalability, performance-aware art, or engine handoff. Use illustration-style-and-systems for non-game illustration sets.
Use when tuning a game action through anticipation, response, impact, timing, animation, VFX, audio-visual coordination, camera, hit-stop, particles, haptics, reduced-motion, sensory alternatives, or intensity settings. Use micro-interactions-and-feedback for ordinary UI controls.
Use when designing game HUDs, menus, maps, inventory, dialogue, tutorials, pause/settings, save/load, failure/success, controller focus, touch, couch-distance, or diegetic interfaces. Use ordinary app UI skills for non-game task flows.
Use when a game needs its player fantasy and interaction loop routed into HUD, art direction, feedback, camera, input, accessibility, testing, and engine handoff. Use ordinary app UI skills for non-game software and the four game specialists for focused craft.
Use when designing or auditing an interactive UI for WCAG 2.2 AA, keyboard and focus behaviour, accessible names, screen readers, target size, reflow, authentication, or reduced motion. Use inclusive-and-assistive-design for needs beyond the compliance floor.
| name | brand-style-guide |
| description | Use when packaging an approved identity into a client-facing guide with logo, colour, typography, spacing, imagery, voice, and application rules. Unlike brand-visual-identity, this documents settled decisions rather than creating the identity. |
| metadata | {"portable":true,"category":"02-color-brand-and-visual-identity","compatible_with":["claude-code","codex"]} |
Acknowledgement: Shared by Peter Bamuhigire, techguypeter.com, +256 784 464178.
docs/brand-style-guide.md) once brand strategy and the design system already exist — the premium hand-off deliverable.color-system-and-palette first.logo-and-wordmark-design, and the broader mark/identity system is brand-visual-identity.voice-tone-and-content-style-guide.font-selection-and-pairing before specimen-ing them here.| Input | Supplied by | Required? | Why |
|---|---|---|---|
| Approved identity-system specification | Brand-visual-identity | yes | Supplies settled rules |
| Production assets and licence records | Brand owner/production | yes | Enables lawful delivery |
| Audience, formats, and maintenance owner | Delivery brief | yes | Shapes usable guidance |
| Output | Consumer | Evidence / acceptance |
|---|---|---|
| Client-facing style guide | Client, partners, and producers | Required sections use approved examples |
| Asset and licence index | Client asset custodian | Source, format, owner, and restrictions recorded |
| Guide QA record | Delivery owner | Links, values, specimens, accessibility, and exports verified |
| Condition | Decision | Wrong-choice failure |
|---|---|---|
| Decision is approved and stable | Document with do/don't examples | Rule remains open to interpretation |
| Decision is missing or contradictory | Stop and return to identity owner | Guide invents policy |
| Guide serves non-designers | Prefer concise rules and production examples | Attractive document remains unusable |
| Editable and fixed delivery are needed | Supply source plus verified PDF | Client cannot maintain or view faithfully |
Read and document generation are required. Editing applies only to the authorised guide and delivery copies. Do not change master identity rules, redistribute restricted files, or publish without approval.
If required evidence or tooling is unavailable, use the scoped fallback below and mark the result unverified. Without final assets or approvals, create a marked draft with an open-decisions register. Without rendering, supply source content and mark visual QA blocked; never call it final.
doctrine/design-doctrine.md — the Mission and Anti-Slop Charter; the style guide must record deliberate, stated choices, not defaults.doctrine/references/ai-slop-banned-fonts.md and doctrine/references/font-groups-and-usage.md — verify the typography specimen names an approved, non-banned face before it ships to the client.doctrine/references/pairing-principles.md, doctrine/references/type-scale-and-spacing.md — typography pairing and the spacing/type scale the specimen documents.02-color-brand-and-visual-identity/color-system-and-palette (palette card hexes + WCAG), 02-color-brand-and-visual-identity/brand-visual-identity, 01-typography-and-fonts/font-selection-and-pairing.references/legacy-guidance.md and references/style-guide-template.md for the deliverable structure; read only the files under references/ that match the task.examples/mini-style-guide-worked.md — a worked compact brand style-guide deliverable for a
sample roaster (Köya): logo usage, colour palette (hex + OKLCH + roles), an approved Fraunces +
Public Sans typography specimen with scale, spacing system, photography note, and a do/don't.
Use it as the calibration target for specificity and the stated-choice discipline.SKILL.md as the portable execution layer for both Claude Code and Codex.