ericrisco/rsc-harness / skills/brand-identity
brand-identity
VerifiedUse when a project needs its visual foundation built or consolidated into one system: logo brief, color system in HEX/RGB/CMYK/OKLCH with proven AA contrast, type system, usage rules, and an exported W3C design-tokens.json that later skills consume. NOT the applied UI pixels (that is design), NOT the words or tone (that is brand-voice).
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 10.4 KB |
| evals/README.md | markdown | 1.0 KB |
| evals/cases.yaml | config | 3.8 KB |
| references/color-and-tokens.md | markdown | 6.1 KB |
| references/logo-and-assets.md | markdown | 4.4 KB |
| scripts/verify.shexecutable | script | 7.6 KB |
evals/cases.yaml
View on GitHubskill: brand-identity
should_trigger:
- prompt: "Build our brand identity — logo brief, colors, fonts, the whole brand book."
why: "The core ask: all four deliverable parts (logo, color, type, usage) named explicitly. Exact center of the skill."
- prompt: "Pick a color palette and document the hex, rgb, and cmyk values for our brand."
why: "Color-system core; the four-channel value requirement (HEX/RGB/CMYK/OKLCH) is the skill's contract for colors."
- prompt: "Define our type system: primary and secondary typefaces with a scale and weights."
why: "Type-system core — 2-3 typefaces, scale, weights, pairing rationale are exactly this skill's bar."
- prompt: "We've got random fonts and hex codes scattered across files — consolidate them into one system."
why: "Non-obvious rebrand/consolidation trigger: no 'brand book' wording, but unifying ad-hoc colors/fonts into a system is precisely the rebrand path."
- prompt: "Necesito una identidad de marca y la guia de marca con normas de uso del logo."
why: "Spanish/Catalan trigger naming brand identity, brand guidelines, and logo usage rules — all owned here."
- prompt: "Export a design-tokens.json with our brand colors so the dev team stops eyeballing the palette."
why: "Non-obvious: phrased as a tokens export, but emitting the W3C design-tokens.json hand-off contract is this skill's machine-readable deliverable."
should_not_trigger:
- prompt: "Make this landing page look premium — pick the layout, motion, and ship the Tailwind."
route_to: design
why: "Applied UI layer (layout, motion, real code) consumes the brand foundation; it is not the foundation itself."
- prompt: "Write our tone of voice and a tagline for the homepage."
route_to: brand-voice
why: "Verbal identity — words and tone — not the visual system."
- prompt: "Write the hero headline and the CTA copy for our pricing page."
route_to: marketing
why: "Page words / conversion copy, not the logo/color/type system."
- prompt: "Put together a press kit with our logos and boilerplate for journalists."
route_to: press-kit
why: "Media packaging of finished assets, not defining the brand system."
- prompt: "Design the investor pitch deck slides for our seed round."
route_to: presentations
why: "Deck composition/visuals, not the brand foundation the deck would draw from."
capability:
- scenario: "We're a fintech startup 'Ledgerly'. Create our brand identity foundation."
must_include:
- "A logo brief with the full variation set (primary / stacked / mark-only / monochrome), a clear-space rule tied to the mark's cap/x-height, minimum sizes (e.g. ~24px digital / ~10mm print), and a file + favicon export matrix (SVG primary, PNG/ICO fallbacks, apple-touch 180, android 192/512, site.webmanifest)."
- "Color roles assigned (2-3 primary, 2-3 secondary, a neutral ramp, exactly one accent), each color carrying HEX + RGB + CMYK + OKLCH — not HEX alone."
- "At least one documented text-on-background pair meeting WCAG 2 AA (>= 4.5:1 normal text / 3:1 large), stated as an explicit pair (fg on bg with the ratio), and a note that logo/brand-name text is exempt under WCAG 1.4.3 while typed taglines are not."
- "A type system of 2-3 typefaces max with a modular scale, named weights, and a one-line pairing rationale (plus a variable-font note)."
- "A W3C-format design-tokens.json (2025.10) emitted with light/dark roles via group inheritance / $extends and OKLCH values, mapped to CSS custom properties / Tailwind v4 @theme."
- "Usage/misuse rules (no stretching, no off-palette color, require the mono variation on busy backgrounds) plus an explicit hand-off note to design as the skill that applies the tokens."
- "A pointer to run scripts/verify.sh on the emitted design-tokens.json to confirm roles, hex coverage, and AA contrast before claiming done."
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| brainstormingobra/superpowersYou MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or planning anything new, in software or out of it (a talk, a business, a renovation). | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| brand-guidelinesanthropics/skillsApplies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| frontend-designanthropics/skillsGuidance for distinctive, intentional visual design when building new UI or reshaping an existing one. Helps with aesthetic direction, typography, and making choices that don't read as templated defaults. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| mcp-builderanthropics/skillsGuide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK). | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |