From protocols
Structured debugging with competing hypotheses and escalation levels. Use when encountering unexpected behavior, multiple possible causes, or after 3+ failed fix attempts. Separates facts from theories and tracks evidence systematically.
npx claudepluginhub ctoth/protocols-plugin --plugin protocolsThis skill uses the workspace's default tool permissions.
Use when: unexpected behavior, multiple possible causes, debugging > 3 failed attempts.
Guides Next.js Cache Components and Partial Prerendering (PPR): 'use cache' directives, cacheLife(), cacheTag(), revalidateTag() for caching, invalidation, static/dynamic optimization. Auto-activates on cacheComponents: true.
Processes PDFs: extracts text/tables/images, merges/splits/rotates pages, adds watermarks, creates/fills forms, encrypts/decrypts, OCRs scans. Activates on PDF mentions or output requests.
Share bugs, ideas, or general feedback.
Use when: unexpected behavior, multiple possible causes, debugging > 3 failed attempts.
Start at L1. Escalate when stuck.
investigations/[topic].md in project rootSeparate FACTS (verified, have evidence) from THEORIES (plausible, untested).
Maintain several competing hypotheses. Chasing a single theory is confirmation bias with extra steps.
For each test:
Before each action: state hypothesis. After each action: record result.
# Investigation: [topic]
## Facts (verified)
- [thing] - evidence: [how verified]
## Theories (plausible)
1. [theory A] - would explain [X], predicts [Y]
2. [theory B] - would explain [X], predicts [Z]
3. [theory C] - would explain [W], predicts [Y]
## Tests Run
| Test | Hypothesis | Result | Rules Out | Supports |
|------|------------|--------|-----------|----------|
| | | | | |
## Current Best Theory
[Which theory survives the evidence, and why]
## Open Questions
-
## Next Action
[What to try next and what it would tell us]