plugins/tome/skills/ideate/SKILL.md
Generate diverse solution candidates with category-spanning ideation methods and rotation. Use when stuck on a design or fighting repetitive LLM output.
npx skillsauth add athola/claude-night-market ideateInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
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.
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.
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).
select_methods(n) from tome.channels.ideation returns methods
from different categories by construction.select_methods(n, exclude=used_ids) or
rotation_plan(passes, n_per_pass) so no method repeats until the
catalog is exhausted.score_idea (weighted criteria per
Skill(leyline:evaluation-framework)). Novelty claimed without
evidence is capped, so "novel" must be earned, not asserted.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.
The diversity rationale and method evidence grades draw on:
>= 3 categories from list_categories()).exclude or rotation_plan so no
method repeated before the catalog was exhausted.score_idea, with
any uncapped novelty backed by an explicit prior-art check.tools
--- name: validate-pr description: Use when you need a diff-derived test plan for a PR: reads the diff, groups changes by area, runs targeted verifications, and proves revert-tests are genuine guards, not dead assertions. alwaysApply: false category: validation tags: - pr - validation - test-plan - diff - revert-test - evidence tools: [] usage_patterns: - diff-derived-test-plan - revert-test-quality-check - evidence-capture complexity: intermediate model_hint: standard estimated_tokens: 650
development
Contract for the project decision journal (tradeoffs and lessons-learned logs). Use when recording a decision, tradeoff, or lesson, or building a consumer hook.
development
Ramps implementation ambition a notch only after the prior increment is understood. Use when building a feature you must understand, not just ship.
testing
Verifies a package exists before install, defending against hallucination and slopsquatting. Use when adding, recommending, or installing a package.