Ship 30 idea types
An idea type (Ship 30 calls them "proven approaches" or containers) is the shape a piece takes: the same topic written as 5 mistakes reads differently from the same topic written as 1 story. A headline names one topic plus one type, with a number when the type is countable.
The /ideas skill and its Jev classifier (~/.claude/skills/ideas/jev_judge.py) read the table below as the closed set of types. Add rows here and both pick them up. One row per type; the Type cell must stay a short single name.
Blocker (2026-10-11)
Ship 30 names 30 types. The vault has 13. The full list is in the masterclass "How To Generate Endless Writing Ideas". Capturing it failed on 2026-10-11 after 2 login tries: Skool showed "Request failed. Please try again." right after "Log in with a code", and no code email was sent. The shared Playwright browser that logged in on 2026-10-05 was in use by another session. The other 17 types are not guessed here. To finish: log in to Skool (email code), open the masterclass, add the missing rows in our own words, and set status: complete.
Types
| Type | Definition (our words) | Countable |
|---|---|---|
| Tips | Small, standalone pieces of advice the reader can apply right away. | yes |
| Skills | Abilities the reader should build, and why each one matters. | yes |
| Tools | Specific products, templates or resources, and what each is good for. | yes |
| Steps | An ordered sequence that gets the reader from start to a named result. | yes |
| Habits | Repeated behaviors that compound, framed as what to do every day or week. | yes |
| Stories | A first-person narrative with a turning point the reader can learn from. | no |
| Lessons | Takeaways the writer earned from experience, stated as principles. | yes |
| Mistakes | Errors the writer made or sees often, each with the fix. | yes |
| Frameworks | A named mental model or structure the reader can reuse to decide or build. | no |
| Data Points | Numbers or findings, each with what it means for the reader. | yes |
| Questions | Questions the reader should ask (of themselves, a vendor, a team) and why. | yes |
| Examples | Concrete cases that show an idea in practice, one per point. | yes |
| Reasons | The arguments for a claim or a choice, each one a separate why. | yes |