Skip to content
cccskills
FreePublished on GitHub

brand-to-tokens

Turn a confirmed brand identity into a DTCG tokens.json source of truth — emit CSS vars + Tailwind via design-tokens, export locked brand deck templates.

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

Run score Not tested

See how to install

Files included (4)

  • SKILL.md5.5 KB
  • evals/triggers.json2.4 KB
  • templates/marp-brand-deck.md.example1.3 KB
  • templates/reveal-brand-deck.yaml1.1 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

brand-to-tokens

The brand→token derivation — the first consumer demand that closes the ADR-061 §8 deferral. Takes a confirmed brand-identity constraint set and produces a DTCG tokens.json source of truth, then hands it to the design-tokens toolchain to emit CSS vars + Tailwind. The same tokens.json is the export that pack-ai-image brand-asset generation and the greenfield scaffold seed consume (B → A; contract: brand-token-consumption).

When to use

  • A confirmed brand identity (colour story, type story, spacing) needs to become a maintained token system.
  • A consumer asks to "turn the brand into tokens / CSS variables / a theme."
  • Before pack-ai-image brand-asset generation or a greenfield scaffold needs the tokens.json export.

Procedure

  1. Take the confirmed brand-identity constraint set — colour story (roles + values), type story (heading/body classes), spacing/radius intent. If a consumer brand profile already registers values, those win (brand-source-of-truth).

  2. Author tokens.json on the design-tokens 3-layer DTCG model ($value / $type): brand palette → primitive.color.*; brand roles (primary, accent, surface, destructive) → semantic.color.* referencing the primitives; per-widget needs → component.*. Add dark.semantic.* overrides. Type tokens come from typography-system stage-2 (archetype → pairing-filter), added under the typography section.

  3. Generate CSS vars + Tailwind through the toolchain:

    node <skills-root>/design-tokens/scripts/tokens.mjs generate \
      --config tokens.json -o assets/design-tokens.css
    node <skills-root>/design-tokens/scripts/tokens.mjs generate \
      --config tokens.json --format tailwind
    
  4. Validate — node <skills-root>/design-tokens/scripts/tokens.mjs validate --dir src/ until clean (exit 0 is the evidence); convert hardcoded values to var(--token).

  5. Export the deck templates — emit the locked-variable brand deck templates from templates/ — marp-brand-deck.md.example (copy to .md to use) and reveal-brand-deck.yaml — substituting the brand variables from tokens.json. No render engine is owned (decision 7); the templates feed the user's own deck tool.

  6. Publish tokens.json as the source of truth other surfaces read (pack-ai-image generation, greenfield scaffold) per the consumption contract.

Output format

  1. tokens.json — DTCG 3-layer (primitive → semantic → component) + dark.semantic + typography, every value {$value, $type}.
  2. Generated design-tokens.css + the Tailwind theme.extend snippet.
  3. validate evidence — exit 0, or the token_violation findings handed to polish.
  4. The exported brand deck templates (Marp + reveal) with brand variables locked from the tokens.

Gotcha

  • tokens.json is the single source — never hand-edit the generated CSS or a consumer-side copy. pack-ai-image generation and the greenfield scaffold read this file; a hand-edited downstream copy silently drifts from the brand.
  • Derive, do not invent. Every token traces to a brand-identity decision or the consumer's existing brand; a value with no brand provenance is off-brand (brand-source-of-truth § Iron Law 2 flags it).
  • Deck templates lock brand variables — never inline a raw hex/font in a template; reference the token so the deck stays on-brand when tokens change.

Do NOT

  • Do NOT generate marks or assets here — this skill emits tokens + templates; logo-generation / brand-asset-generation generate the marks from the tokens (B → A, never inverted).
  • Do NOT hand-edit generated CSS — tokens.json is the source.
  • Do NOT let components reference primitives directly — semantic layer between.
  • Do NOT own a slide-render engine — export validated templates only (decision 7).

See also

  • design-canon.md § Colour references — culturally-situated palettes + a11y-contrast grounding when deriving brand colour tokens.
  • brand-identity — supplies the constraint set this skill derives tokens from.
  • design-tokens — the DTCG toolchain that emits CSS/Tailwind from tokens.json.
  • typography-system — brand-aware stage-2 supplies the type tokens.
  • brand-token-consumption — the read contract pack-ai-image and greenfield scaffold consume.
  • brand-source-of-truth § Iron Law 2 — the checklist emitted artifacts are read against this token source of truth.

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

Use when reviewing UI for accessibility — WCAG 2.2 AA, keyboard nav, focus, ARIA, contrast, screen-reader semantics — even on 'is this a11y-OK?' or 'mach das barrierefrei'.

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

event4u-app/agent-config13Updated Oct 24, 2026

Use when defining or auditing the activation event — aha-moment selection, retention correlation, falsifiable definition. Triggers on 'what is our aha moment', 'redefine activation'.

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

event4u-app/agent-config13Updated Oct 24, 2026

Use when capturing an architectural decision — file naming, next ADR number, Status / Context / Decision / Consequences, index regen; fires even without saying 'ADR'.

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

event4u-app/agent-config13Updated Oct 24, 2026

Adversarial critique — devil's advocate, stress-test, honest teardown ('poke holes', 'be brutal', 'was hältst du davon'); explicit request only. Routine code or design review → code-review.

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

event4u-app/agent-config13Updated Oct 24, 2026

Use when reading, creating, or updating agent documentation, module docs, roadmaps, or AGENTS.md. Understands the full .augment/, agents/, and copilot-instructions structure.

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

event4u-app/agent-config13Updated Oct 24, 2026

Use for an adversarial red-team / blue-team / auditor review of an AI agent's CONFIG + behaviour (rules, skills, MCP, hooks, permissions) — attack-chain → defensive-gap list, not a code audit.

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

event4u-app/agent-config13Updated Oct 24, 2026

See all skills by event4u-app

Report a problem with this skill