Activate for website strategy, mobile app decisions, UX architecture, content structure, and digital experience questions. Also activates when a digital product feels unclear, overbuilt, or disconnected from brand strategy.
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.
A website or app is not a brochure or a feature list. It's the brand's most interactive touchpoint — and the one most likely to contradict everything strategy promised.
Digital product decisions are brand decisions. Every UX choice communicates something. Prioritize clarity of experience over completeness of features.
| Question | If unclear... |
|---|---|
| What is the primary job of this digital product? | Everything else is secondary |
| Who is the user and what are they trying to accomplish? | Can't design for an undefined user |
| What does success look like — in behavior, not metrics? | Metrics follow behavior |
| Is the brand identity system ready? | UI built before identity = rework |
The most common digital product mistake: building before the purpose is clear.
Before wireframes, define:
Primary message → Above fold, immediately clear
Supporting evidence → Below fold, earned by primary message
Call to action → Specific, not generic ("Get started" is generic)
Secondary content → Never competing with primary
"Add more features"
What problem does each feature solve? Features without user problems are technical debt and cognitive load. Let's audit what's there before adding.
"Make the homepage do everything"
A homepage that does everything does nothing. What is the one job of this page? Design for that job first.
"We need it to look impressive"
Impressive to whom, and measuring what? An impressive homepage that confuses users has failed. What impression specifically needs to be created?
"Can we just copy [competitor's] structure?"
Their structure was built for their strategy and audience. Yours might be different. Let's validate the structure against your goals before copying it.
| Decision type | Tool |
|---|---|
| Component and UI system | bb-dp-figma |
| Web build and CMS | bb-dp-framer |
| Mobile native patterns | bb-dp-mobile |
| Advanced prototype | bb-dp-protopie |
| Interactive animation | bb-dp-rive |
| 3D web experience | bb-dp-spline |
| Code generation | bb-dp-cursor-antigravity |
Digital product connects with:
bb-brand-identity — source of visual systembb-design-system — tokens for UIbb-copywriter — UX copy and contentbb-presentation — presenting digital strategy to client