From thinking-frameworks-skills
Generates 5 distinct intuitive framings (everyday analogy, physical metaphor, contrarian take, historical angle, counterfactual) for any technical topic. Call when building explanations that need multiple pedagogical angles.
How this skill is triggered — by the user, by Claude, or both
Slash command
/thinking-frameworks-skills:generate-analogy-setThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
- [The 5 archetypes](#the-5-archetypes)
Related skills: Called by the Intuition Builder agent as step 1. Feeds map-analogy-to-concept, stress-test-analogy, check-analogy-novelty, voice-fitness-check.
Each framing must match one of these archetypes:
propose-counterfactual for depth.)These 5 are fixed. If a topic resists one archetype (rare), the agent produces a weaker version rather than substituting a 6th.
Generate 5 framings for topic T:
- [ ] Step 1: Restate T in one sentence (what the writer is explaining)
- [ ] Step 2: Brainstorm 2-3 candidates per archetype
- [ ] Step 3: Pick the strongest candidate per archetype using the voice-profile analogy-direction priority (biology > organizational > sports; NEVER physics/military)
- Exception: "physical metaphor" archetype explicitly permits physical domain, but even here prefer fluid/biological analogues over mechanical/military ones.
- [ ] Step 4: Write each as one-line framing statement (≤25 words)
- [ ] Step 5: Return the 5 with archetype labels
The voice-profile says biology → AI, organizational → multi-agent, sports → calibration are the writer's characteristic directions. Within each archetype, if a biology-flavored option exists AND is crisp, it wins over an equally crisp mechanical/military option. The writer almost never uses physics/military.
Topic: Attention (in Transformers).
5 framings:
Each framing is ≤1 sentence (some are 2). The mapping, breaks, and novelty checks come from the downstream skills.
npx claudepluginhub lyndonkl/claude --plugin thinking-frameworks-skillsRoutes analogical reasoning to the right sub-skill: boundary-testing, domain-transfer, perspective-shifting, or structure-mapping. Use for finding comparisons, importing solutions, or testing analogies.
Maps source-domain components of an analogy to target technical concept components, flagging unmapped elements and checking relation systematicity. Use after generate-analogy-set.
Forces the user to produce analogies between a new concept and existing knowledge, then stress-tests those connections against code or docs. Use when learning something new or when a concept isn't sticking.