本文へ移動
cccskills
無料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.

インストール方法を見る

含まれるファイル(11)

  • SKILL.md5.4 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(原文)

インストールする前に、エージェントに与えられる指示の中身を確認できます。

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):

    ./scripts-run <skills-root>/corpus-grounding/scripts/ground 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-consistency, 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 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-consistency 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.

レビュー

まだレビューはありません。使ってみた感想をお寄せください。

同じリポジトリのスキル

概要と使いどころ

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'.

日本語の概要は準備中です。原文の説明を表示しています。

event4u-app/agent-config112026年10月12日 更新

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

日本語の概要は準備中です。原文の説明を表示しています。

event4u-app/agent-config112026年10月12日 更新

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

日本語の概要は準備中です。原文の説明を表示しています。

event4u-app/agent-config112026年10月12日 更新

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.

日本語の概要は準備中です。原文の説明を表示しています。

event4u-app/agent-config112026年10月12日 更新

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

日本語の概要は準備中です。原文の説明を表示しています。

event4u-app/agent-config112026年10月12日 更新

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.

日本語の概要は準備中です。原文の説明を表示しています。

event4u-app/agent-config112026年10月12日 更新

event4u-app のスキルをすべて見る

このスキルの問題を報告する