
Ideate
Break out of repetitive LLM suggestions when you are stuck on a design or product decision by running structured, category-rotating ideation methods.
Overview
Ideate is a journey-wide agent skill that generates diverse solution candidates by rotating category-spanning ideation methods—usable whenever a solo builder needs fresh options before committing to one design path.
Install
npx skills add https://github.com/athola/claude-night-market --skill ideateWhat is this skill?
- Seven catalogued methods (SCAMPER, SIT, morphological analysis, cross-domain, etc.) tagged with evidence grades
- Method rotation across passes to fight LLM mode collapse instead of volume-only brainstorming
- Reasoning scaffolds per method—structure reasoning during generation, impose schema only when reporting
- Honest evidence grades (weak/mixed) so you pick methods with eyes open
- Ports creativity frameworks to technical problem-solving, not generic word lists
- 7 ideation methods in the catalog
- Reasoning-scaffold design aligned with arXiv 2505.18949
Adoption & trust: 1 installs on skills.sh; 304 GitHub stars; trending (+100% hot-view momentum).
What problem does it solve?
You are stuck on a design or keep getting near-duplicate ideas from the model because it is collapsing to one mental frame.
Who is it for?
Indie builders iterating on product, UX, or technical designs who want structured creativity without forcing every idea into the same template mid-generation.
Skip if: Teams that already have an approved spec and only need execution tasks, or anyone wanting a single fixed brainstorming output format during generation.
When should I use this skill?
Stuck on a design or fighting repetitive LLM output.
What do I get? / Deliverables
You exit with a deliberately varied candidate set produced from rotated methods, ready to compare, narrow, or hand off into planning or spec work.
- Diverse solution candidate set
- Final reported idea set with post-generation structure
Recommended Skills
Journey fit
Useful at every journey phase - explore requirements and options before committing to a direction.
Where it fits
Compare three positioning angles before picking a niche to validate.
Generate structurally different prototype concepts instead of UI skin variants.
Explore decomposition-based options when the same microservice layout keeps reappearing.
Rotate methods to draft distinct launch narrative angles for the same feature.
Break repetitive content-series pitches with cross-domain ideation passes.
How it compares
Use instead of asking the model for “10 more ideas” from one prompt, which usually amplifies mode collapse.
Common Questions / FAQ
Who is ideate for?
Solo and indie builders using Claude Code, Cursor, or similar agents who hit repetitive suggestions while designing features, systems, or product directions.
When should I use ideate?
In Idea when exploring options before validation; in Validate when prototype directions feel samey; in Build when architecture or UX choices stall; anytime LLM output feels like one idea with minor tweaks.
Is ideate safe to install?
It is procedural guidance with no special permissions in the skill text; review the Security Audits panel on this Prism page before installing from the upstream repo.
SKILL.md
READMESKILL.md - Ideate
# Ideation: Diverse Methods With Rotation **Diversity is a selection problem, not a volume problem.** Generating ten ideas from one mental frame yields ten variations of the same idea. The fix is to ideate from different categories of method, then rotate methods across passes so the next round does not repeat the last. This is the documented lever against LLM mode collapse, not a brainstorming ritual. ## The one design rule Structure the reasoning, not the output. "The Price of Format" (arXiv 2505.18949) found that rigid output templates collapse output diversity, while reasoning scaffolds raise it. So each method hands you a reasoning prompt. Do not force the ideas into a fixed schema while generating; impose structure only when reporting the final set. ## Catalog Seven methods that port to technical problem-solving, each tagged with an honest evidence grade (see Sources below): | Method | Category | Evidence | |--------|----------|----------| | SCAMPER | transformation | weak | | SIT task unification | transformation | mixed | | Morphological analysis | decomposition | mixed | | SIT subtraction | decomposition | mixed | | Cross-domain analogy (TRIZ) | analogical | mixed | | Inversion (pre-mortem) | inversion | anecdotal | | Constraint provocation | perturbation | anecdotal | The grades are deliberately conservative. Individual-method evidence is thin; the value is the diverse-selection-plus-rotation pattern, not any single method. For the structured analogical form, use `Skill(tome:triz)`. ## Workflow 1. Pick how many approaches you want (3 to 5 is the useful range). 2. Select methods spanning distinct categories: `select_methods(n)` from `tome.channels.ideation` returns methods from different categories by construction. 3. Apply each method's reasoning prompt to the problem. Generate ideas freely; do not normalize them into a schema yet. 4. On a second pass, rotate: `select_methods(n, exclude=used_ids)` or `rotation_plan(passes, n_per_pass)` so no method repeats until the catalog is exhausted. 5. Score the candidates with `score_idea` (weighted criteria per `Skill(leyline:evaluation-framework)`). Novelty claimed without evidence is capped, so "novel" must be earned, not asserted. 6. Report the final set with rationale and scores. ## Scoring `score_idea(scores, novelty_evidence=False)` applies weighted criteria (novelty 0.25, fit 0.20, feasibility 0.20, simplicity 0.15, reversibility 0.10, impact 0.10) and an anti-inflation rule: a novelty score of 8 or higher without supporting evidence is capped to 7. Pass `novelty_evidence=True` only when you have checked for prior art and found the idea genuinely new. ## Anti-goals - Do not generate many ideas from one method and call it diverse. - Do not impose a rigid output schema during generation; it collapses diversity. - Do not present anecdotal-evidence methods as proven; cite the grade. - Do not import the full 20-method bundle; the catalog is curated on purpose. ## Sources The diversity rationale and method evidence grades draw on: - Verbalized Sampling (arXiv 2510.01171): distributional prompting for 1.6 to 2.1x diversity gains, training-free. - The Price of Format (arXiv 2505.18949): rigid output schemas collapse generation diversity. This is the basis for the reasoning-prompt-not-schema rule above. - Barriers to Diversity in LLM-Generated Ideas (arXiv 2602.20408): chain-of-thought reduces fixation; diverse personas restore collective diversity. - The originality and SCAMPER / morphological-analysis education literature underpins the per-method evidence grades. ## Exit Criteria - [ ] At lea