Idea Forge
Three-mode idea engine - generate collides the week's zeitgeist with what you can ship...
Install
npx skills add aeonfun/aeon --skill idea-forge -g -a claude-code -y- Repository
- aeonfun/aeon787
- Category
- Business
- Updated
- 3d ago
- License
- MIT
- Context cost
- Mediumabout 3,000 tokens
- Runs scripts
- No, instructions only
What it does
Three-mode idea engine - generate collides the week's zeitgeist with what you can ship into scored wedges; validate viability-screens the idea backlog; memo writes evidence-backed startup memos.
${var}, Selector
mode [theme/constraint]. First token picks the mode:generate(default) collides the zeitgeist with the capability surface into ranked wedges;validatescreens the existing backlog for viability;memowrites 2 rigorous evidence-backed startup memos. Anything after the mode is a theme/constraint bias. A bare theme with no mode keyword (e.g.payments,crypto) =generatebiased to that theme.dry-runanywhere skips the notify. Examples: `` (empty → generate, open-ended) ·simulation(generate, themed) ·validate crypto(screen crypto ideas) ·memo solo founder(memos under a constraint) ·generate payments dry-run(generate, no notify). Apick:<id|name>value (from the "build next?" force-reply, e.g.pick:Onchain reputation) is intercepted before mode dispatch: it marks that idea as chosen-to-build in the shared backlog and ends, see "Force-reply interception" below.
Today is ${today}. Read soul/SOUL.md + soul/STYLE.md + STRATEGY.md first and read them closely, this skill thinks as the operator, in their worldview, not about them. If soul/ is the empty template, ground purely on STRATEGY.md + the capability surface and write in a clear, direct tone. Then read memory/MEMORY.md for current goals and active topics. Each mode below names its own memory/logs/ scan window for dedup, honor it.
Force-reply interception, pick:<idea> (run FIRST, before mode dispatch)
Before tokenizing ${var} for the mode, check it. If ${var} starts with pick:, this run is the operator answering the "which idea to build next?" force-reply, do not run generate/validate/memo. Handle it and end. This is behaviorally identical to idea-pipeline's step 0 (same backlog, same marking convention), so a pick reply works whichever skill it routes to:
