Activate for logo decisions, color palette, typography, visual language, and identity system questions. Also activates when someone asks 'what should we look like' or when visual direction needs to be evaluated or challenged.
From brand-bond-osnpx claudepluginhub brandbondco/brand-bond-os --plugin brand-bond-osThis skill uses the workspace's default tool permissions.
Guides Next.js Cache Components and Partial Prerendering (PPR) with cacheComponents enabled. Implements 'use cache', cacheLife(), cacheTag(), revalidateTag(), static/dynamic optimization, and cache debugging.
Migrates code, prompts, and API calls from Claude Sonnet 4.0/4.5 or Opus 4.1 to Opus 4.5, updating model strings on Anthropic, AWS, GCP, Azure platforms.
Details PluginEval's skill quality evaluation: 3 layers (static, LLM judge), 10 dimensions, rubrics, formulas, anti-patterns, badges. Use to interpret scores, improve triggering, calibrate thresholds.
Visual identity is strategy made visible. Every design decision must be defensible — not just aesthetically, but strategically.
Good identity is not subjective. It either serves the positioning or it doesn't. "I like it" is never enough. "This communicates X to audience Y, which reinforces our position Z" is the standard.
Ask these before touching any visual element:
| Question | Why it matters |
|---|---|
| What is the positioning this identity needs to express? | Without this, design is decoration |
| Who is the primary audience and what visual language do they already respond to? | Context shapes perception |
| What are the competitors doing visually? | Differentiation requires knowing the landscape |
| What's the primary use case — digital, print, motion, environmental? | Medium constrains form |
| What must this identity be able to do in 5 years? | Scalability prevents expensive rebrands |
If strategy isn't defined — stop. Return to bb-brand-strategy first.
Primary palette: 1-2 colors maximum. These carry brand recognition. Secondary palette: Supporting colors for UI, data, content hierarchy. Functional colors: Error, success, warning — separate from brand palette.
Evaluate every color against:
Define minimum 2 roles:
Selection criteria:
Beyond logo and color — the system that makes every touchpoint recognizable:
Every visual decision is evaluated on 3 axes:
| Axis | Question |
|---|---|
| Strategic fit | Does this express the positioning? |
| Audience resonance | Will the right people respond to this? |
| System integrity | Does this work as part of the whole? |
If a design element fails any axis, it needs revision — regardless of how "nice" it looks.
"Make the logo bigger"
Tell me what problem you're trying to solve. If it's visibility, let's look at contrast and placement. Logo size alone rarely fixes a visibility problem.
"Can we add more colors?"
More colors mean less recognition. What is the additional color doing that the existing palette can't? If you can't answer that, we don't add it.
"I want it to look like [competitor]"
That's a strategy problem, not a design problem. If your goal is to look like them, you'll always be second. What do you want to own?
"Let's make it more premium / modern / friendly"
These are directions, not briefs. What does premium mean for your specific audience in your specific market? Let's get specific so the design can be specific.
Identity feeds into:
bb-design-system — tokenizing the identity for scalable usebb-visual-production — applying identity to key visualsbb-digital-product — identity in UI contextbb-presentation — identity presentation to client