Activate for The Side System™ diagnostic phase. Runs the side:sight process — AI-powered pattern recognition across business data, reveals the real problem (not the stated one), and produces a Situation Report with clear next steps. Use when entering a new TSS engagement or when existing diagnosis feels shallow.
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.
"We read between the lines."
side:sight is the most critical phase. Wrong diagnosis = wrong solution.
This skill forces the discipline to see what's invisible before building anything.
| Trigger | Why |
|---|---|
| New TSS client engagement starts | Always begin here |
| Client says "we know what's broken" | Especially then — this is almost always wrong |
| Existing work stalled or misdirected | Re-diagnose before continuing |
| Client has tried multiple solutions and failed | Root cause was never found |
| Proposal requested before problem is clear | Don't scope what you can't name |
These must all be answered before any output is produced:
| Question | If unanswered |
|---|---|
| What is broken — specifically? | Stop. Describe the symptom, not the solution. |
| How long has it been broken? | Distinguishes structural from situational |
| What has been tried before? | Defines where patterns must be sought |
| Who makes decisions in this company? | Determines engagement structure |
| What does success look like in 90 days? | Sets the first measurable outcome |
tss-intelligence feeds this phase. When data is available, analyze:
| Data source | Pattern to detect |
|---|---|
| Revenue over time | Stall point, growth ceiling, anomaly |
| Customer retention | Churn trigger, loyalty driver |
| Team output data | Bottleneck location, productivity gap |
| Sales pipeline | Conversion drop-off, win/loss signal |
| Product/web analytics | Friction point, user behavior pattern |
| Financial ratios | Cash efficiency, burn rate, runway |
Output format for every data pattern found:
Pattern: [Observable fact from data]
Signal: [What it means]
Implication: [What breaks if it continues]
Recommendation: [First action to take]
When formal data isn't available, read the environment:
SITUATION REPORT — side:sight
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Company: [Name / profile]
Date: [YYYY-MM-DD]
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
01. STATED PROBLEM
[What the client says is wrong]
02. OBSERVED PATTERN
[What the data and environment actually show]
03. REAL PROBLEM
[One clear sentence — the structural root cause]
04. CONSEQUENCE
[What happens if this continues — specific, not vague]
05. OPPORTUNITY
[What becomes possible once this is fixed]
06. UNKNOWNS
[What we still need to find before proceeding]
07. PHASE RECOMMENDATION
[Which side: phases apply and in what order, with rationale]
08. NEXT STEP
[One specific action — not generic]
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
"We don't need side:sight, we know what's wrong."
The last three engagements where a client said this — the actual problem was different from the stated problem. side:sight is short. The cost of skipping it is not.
"Just give us the proposal."
A proposal scopes a solution. We can't scope a solution to a problem we haven't diagnosed. Give us 48 hours on side:sight first.
"We tried everything."
Tell me specifically what was tried, when, and what happened. The pattern of failed attempts tells us more than any fresh diagnosis.
| After side:sight | Next skill |
|---|---|
| Problem clear, scope undefined | → tss-scope |
| Problem clear, proposal needed | → tss-proposal |
| Pattern requires AI solution | → tss-intel |
| Competitive pattern detected | → tss-competitive |