From thinking-frameworks-skills
Answers strategic questions about substacker (e.g., 'should we launch paid?') with evidence, chain reasoning, specific downside triad, and recommendation. Used in growth reviews.
npx claudepluginhub lyndonkl/claude --plugin thinking-frameworks-skillsThis skill uses the workspace's default tool permissions.
```
Generates design tokens/docs from CSS/Tailwind/styled-components codebases, audits visual consistency across 10 dimensions, detects AI slop in UI.
Records polished WebM UI demo videos of web apps using Playwright with cursor overlay, natural pacing, and three-phase scripting. Activates for demo, walkthrough, screen recording, or tutorial requests.
Delivers idiomatic Kotlin patterns for null safety, immutability, sealed classes, coroutines, Flows, extensions, DSL builders, and Gradle DSL. Use when writing, reviewing, refactoring, or designing Kotlin code.
Per question:
- [ ] Step 1: Reject if not answerable with current inputs → "I'd like to ask X, but I don't have the data. Here's what to collect before next quarter."
- [ ] Step 2: Gather evidence: numbers, quotes, specific posts. Cite them.
- [ ] Step 3: Write reasoning as a chain: evidence A → inference B → inference C → recommendation
- [ ] Step 4: Write downside: what SPECIFICALLY goes wrong if the recommendation is wrong?
- [ ] Step 5: End with one-line recommendation: do X / don't do X / watch Y
- [ ] Step 6: 200-400 words per question
The Strategist chooses 3 per quarter. Scoring:
### Q{N}: {phrased as a real question, not a topic}
**Evidence**: What the numbers / corpus / audience actually say. Cite Growth Analyst report or specific posts.
**Reasoning**: Why the evidence leads to {answer}. Chain: A → B → C.
**Downside**: What specifically breaks if this recommendation is wrong.
**Recommendation**: Do X / Don't do X / Watch Y before deciding.