Skip to content
cccskills
FreePublished on GitHub

brand-guidelines

Given an existing Style, generate a human-readable brand guidelines document covering colors, typography, voice, do/don't, imagery rules, and usage examples. Use when the user asks for a brand book, brand guide, or design system document.

The English summary is being prepared. Showing the original description.

See how to install

Files included (1)

  • SKILL.md1.7 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

brand-guidelines

Produce a readable brand guidelines artifact from a Style. The artifact is itself rendered via a Template + Style application, not free-form prose.

Procedure

  1. Read the Style: claw style get <styleId>.
  2. Choose the rendering shape:
    • For a one-pager (single page brand summary) use one-pager.product or one-pager.profile.
    • For a long-form brand book, generate sections per area (colors, typography, voice, imagery, usage) and concatenate.
  3. Build the data:
    • Colors: list named tokens with hex values.
    • Typography: list stacks (display, body, mono) and the size scale.
    • Voice: copy the ## Voice section from STYLE.md verbatim.
    • Do/Don't: copy the ## Do / Don't section verbatim. If empty, do not invent.
    • Imagery: copy imagery.photography, imagery.illustration, imagery.iconography if set, plus the generation_prompt_suffix.
  4. Render pdf + html outputs using the same Style being documented (so the doc looks like the brand).
  5. Surface a clear summary: where the doc was written and what sections were covered.

Constraints

  • Never invent rules the Style does not declare. Empty sections must remain empty.
  • The brand book is generated, not authored by hand. Re-running it is idempotent given the same Style state.
  • Use the Style being documented as both the source AND the rendering style for the artifact.

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

Govern Clawix accessibility changes across screen reader behavior, keyboard navigation, focus order, contrast, reduced motion, text scaling, timed interactions, and agent-generated UI.

The English summary is being prepared. Showing the original description.

clawic/Clawix8Updated Jun 6, 2026

Review or update stable, canonical, any-human, PMF, and adoption claims using adoption/canonicity governance packets.

The English summary is being prepared. Showing the original description.

clawic/Clawix8Updated Jun 6, 2026

Turn a new or changed ADR into implemented behavior, routing docs, tests, and guardrails rather than leaving it as standalone prose.

The English summary is being prepared. Showing the original description.

clawic/Clawix8Updated Jun 6, 2026

Repair confirmed architecture drift in small batches while preserving public canon and avoiding broad opportunistic refactors.

The English summary is being prepared. Showing the original description.

clawic/Clawix8Updated Jun 6, 2026

Add or improve canonical data catalog collections, fields, aliases, relations, evidence tags, docs, and tests.

The English summary is being prepared. Showing the original description.

clawic/Clawix8Updated Jun 6, 2026

Apply the 90/10 visual-to-text rule when composing a piece on a canvas (poster, card, social post). Use when the deliverable lives on a single fixed surface where each element competes for attention.

The English summary is being prepared. Showing the original description.

clawic/Clawix8Updated Jun 6, 2026

See all skills by clawic

Report a problem with this skill