Skip to content
cccskills
FreePublished on GitHub

brand

Grounded brand decisions from a curated corpus — archetype, voice, naming, colour psychology, logo-style fit, messaging frameworks, archetype→type mapping. Use to ground brand strategy and identity.

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

See how to install

Files included (11)

  • SKILL.md5.7 KB
  • ATTRIBUTION.md1.7 KB
  • data/archetypes.csv4.1 KB
  • data/color-psychology.csv4.7 KB
  • data/logo-style-fit.csv6.9 KB
  • data/manifest.json4.3 KB
  • data/messaging-frameworks.csv5.1 KB
  • data/naming-patterns.csv6.3 KB
  • data/typography-principles.csv4.3 KB
  • data/voice-tone.csv3.3 KB
  • evals/triggers.json1.7 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

brand

The grounded source for brand decisions — a second instance of the ADR-061 corpus-grounding layer (corpus-grounding), after design-intelligence. Branding is the layer that constrains UI: the corpus grounds brand strategy and identity decisions (archetype, voice, naming, colour, logo style, messaging, archetype→type filter) as a constraint set the human confirms — never the final brand. No forked engine; this plugs into the shared one via a manifest.

Corpus: 7 tabular CSVs under data/ — 12 brand archetypes, a voice-and-tone matrix, naming patterns, color psychology by industry, logo-style ↔ industry fit, messaging frameworks, and typography-principles (archetype → pairing-filter Grounding, the layer that upgrades typography-system stage-2). Provenance: ATTRIBUTION.md; manifest: data/manifest.json.

When to use

  • A brand decision needs grounding: which archetype fits, what voice/tone, how to name, which colour direction, which logo style, which messaging framework, or which type pairing-filter an archetype implies.
  • Before brand-strategy / brand-identity commit to a direction — those skills consult this corpus first.
  • When typography-system needs the brand-aware (archetype → pairing-filter) upgrade — query the typography domain here.

Procedure: consult the brand corpus

  1. Ground or search (paths resolve skill-relative; works from any cwd):

    node <skills-root>/corpus-grounding/scripts/ground.mjs search \
      --manifest <skills-root>/brand/data/manifest.json \
      "<brand brief: sector + intent + audience>" \
      [--domain archetype|voice|naming|color|logo|messaging|typography] \
      [--filter "Archetype Fit=Ruler"] [--json]
    

    <skills-root> is ~/.claude/skills/ for Claude Code installs, src/skills/ inside this repo.

  2. Read confidence + every evidence_gap line before trusting any row — surface them; the human signs off on what the corpus could NOT support.

  3. Propose grounded options (archetype + voice + colour + logo + messaging), each cited per corpus row, with alternatives — the human confirms.

  4. The confirmed selections become the brand token + voice constraint set that brand-to-tokens, brand-source-of-truth § Iron Law 2, and pack-ai-image's brand-asset generation consume.

Output format

  1. Grounded brand candidates per domain (archetype, voice, naming, colour, logo style, messaging, type filter) — each selection cited per corpus row.
  2. The grounded output's confidence label + every evidence_gap line, verbatim.
  3. Alternatives per domain so the human can swap before confirming.

Do NOT

  • Do NOT report a trademark position from the corpus. Trademark Risk in data/naming-patterns.csv rates the PATTERN, not the name on the table. A candidate leaves with a check that was RUN — registry, date, result — or with "not checked". The column alone reads as a clearance nobody performed.
  • Do NOT let the corpus author final brand copy or names — it supplies constraint sets and patterns; final strings are agent-written and human-confirmed.
  • Do NOT fork the engine — plug in via the manifest (ADR-061 §2).
  • Do NOT override the consumer's existing brand tokens / voice profile with corpus rows — consumer brand is the source of truth; the corpus fills gaps (see brand-source-of-truth).
  • Do NOT hide low confidence — the user signs off on the gaps too.

Gotchas

  • Corpus grounds pre-action selection — not mid-task reference and not output validation (brand-source-of-truth § Iron Law 2 owns validation).
  • Keep queries brand-shaped ("luxury law firm rebrand", "playful kids snack brand") — generic words land on the default archetype domain.
  • An empty result is a legitimate outcome — surface the evidence gap and proceed on priors; never widen filters to force a hit.
  • BM25 drops tokens ≤2 chars — pad short queries ("B2B", "AI") with companions.

See also

Policies

  • Provenance: ATTRIBUTION.md — original-authored corpus from public brand frameworks; shared engine attributed in design-intelligence/ATTRIBUTION.md.
  • Refresh: quarterly per the manifest; re-review archetype↔type rows when the font-pairings Reference refreshes.

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 23, 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 23, 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 23, 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 23, 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 23, 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 23, 2026

See all skills by event4u-app

Report a problem with this skill