Activate for The Side System™ long-form document production: pitch decks, capability presentations, case studies, methodology documents, and partner proposals. Produces structured, on-brand deliverables ready for client-facing use. Also activates when any TSS content needs to be formatted into a shareable document.
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.
Structure is clarity. Clarity is trust.
Every TSS document makes one argument clearly. If it tries to make three arguments, it makes none.
| Trigger | Document type |
|---|---|
| First client contact, formal intro | Capability Deck |
| Engagement approved, scope ready | Partner Proposal |
| Post-engagement, results delivered | Case Study |
| Investor or partner briefing | Methodology Document |
| Client needs to understand the 5S process | Methodology Document |
| Proposal accepted, kick-off needed | Engagement Brief |
01 — The Problem (insight opening)
02 — The Consequence (what it costs companies)
03 — Why existing solutions fail
04 — The Side System™ (who we are, one sentence)
05 — The 5S Framework (how we work)
06 — What we build (tangible outputs per phase)
07 — Who we're for (3 audience types)
08 — Partnership model (risk-sharing, embedded)
09 — Evidence (case fragment or result)
10 — Next step (single, specific CTA)
01 — Why sequence matters (the logic of order)
02 — side:sight (pattern recognition phase)
03 — side:scope (priority and definition phase)
04 — side:setup (build phase)
05 — side:scale (growth phase)
06 — side:sync (partnership phase)
07 — What "embedded" actually means
08 — What you get (concrete outputs, named)
Company: [1-line description — sector, size, stage]
The problem: [What was broken — specific]
What we did: [Phase(s), team, timeline]
Output: [Concrete deliverable — not "we improved things"]
Result: [Measurable — number or state change]
The lesson: [What this proves generally]
01 — What we heard (the problem in their language)
02 — What we found (initial diagnostic observation)
03 — What we'd do (phase map with rationale)
04 — What you get (named outputs per phase)
05 — What we need (client inputs required)
06 — What's excluded (explicit scope boundary)
07 — Investment (3-option pricing table)
08 — Next step (one action, one date)
Every slide must answer: what is the one thing I want them to know after this slide?
| Rule | Example |
|---|---|
| Headline = the point, not the topic | ✅ We don't advise. We build. / ❌ About Us |
| One idea per slide | Split if there are two ideas |
| Max 40 words of body copy | If more is needed, redesign the slide |
| Data over adjectives | ✅ side:setup delivers in 6 weeks / ❌ We work fast |
| Active voice | ✅ We diagnose, build, and stay. / ❌ Clients are supported through... |
(Coordinate with Figma/bb-brand-identity for final execution)
| Element | Standard |
|---|---|
| Layout | Grid-disciplined, nothing accidental |
| Color | Deep dark primary, single sharp accent |
| Type | Geometric or technical — precision reading |
| Photography | Systems, infrastructure, human + machine, no stock |
| Charts/data | Clean, labeled, no decoration |
Before delivering any document:
side: prefixThe Side System™ in title case + ™ on first mention| After tss-deck | Next |
|---|---|
| Deck needs copy review | → tss-copy |
| Deck ready to price | → tss-proposal |
| Deck contains AI/tech claims | → tss-intel (review for accuracy) |