Map Analogy to Concept
Produces an explicit component-by-component mapping from the analogy's source domain to the target technical concept. Rejects vague analogies by forcing each source element to map to a specific target element, and flags unmapped elements as voice-breaking ("it's like a brain" is rejected because "brain" is unmapped). Use after generate-analogy-set, for each of the 5 framings. Trigger keywords — map, component mapping, source target, explicit mapping, what does the X correspond to.
Install
/plugin marketplace add lyndonkl/claudeThe repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.
npx skills add lyndonkl/claude --skill map-analogy-to-conceptgit clone --depth 1 https://github.com/lyndonkl/claude.git /tmp/claude
mkdir -p ~/.claude/skills
cp -r /tmp/claude/skills/map-analogy-to-concept ~/.claude/skills/map-analogy-to-conceptPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Map Analogy to Concept ## Table of Contents - [Workflow](#workflow) - [Mapping schema](#mapping-schema) - [Worked example](#worked-example) - [Guardrails](#guardrails) **Related skills:** Called by the Intuition Builder per framing, after `generate-analogy-set` and before `stress-test-analogy`. Gentner's structure-mapping theory is the theoretical spine: good analogies map **relations**, not just objects. ## Workflow ``` For one framing (source → target): - [ ] Step 1: Enumerate the source domain's key components (entities + relations) - [ ] Step 2: For each source component, propose the target component it maps to - [ ] Step 3: Check systematicity — do the relations carry across, or only objects? - [ ] Step 4: Flag any source component that maps to nothing concrete (vague mapping = reject) - [ ] Step 5: Return the mapping table ``` ### Step 3: Systematicity check A strong analogy preserves the **pattern of relations**, not just object-level similarity. Example: - Weak: "a neural network is like a brain" — both have "neurons", but the relation "neurons fire" doesn't carry over in a useful way. - Strong: "V/D/J gene recombination in B cells maps to multi-agent diversity" — the relation "small vocabulary generates exponential combinatorial space" carries. If the framing only matches on objects (nouns), reject or downgrade. ### Step 4: Unmapped flagging
Details
- Skill name
map-analogy-to-concept- Repository
- lyndonkl/claude
- Path
skills/map-analogy-to-concept/SKILL.md- Repo updated
- 1 September 2026
FAQ
What does the Map Analogy to Concept skill do?
Produces an explicit component-by-component mapping from the analogy's source domain to the target technical concept. Rejects vague analogies by forcing each source element to map to a specific target element, and flags unmapped elements as voice-breaking ("it's like a brain" is rejected because "brain" is unmapped). Use after generate-analogy-set, for each of the 5 framings. Trigger keywords — map, component mapping, source target, explicit mapping, what does the X correspond to.
How do I install the Map Analogy to Concept skill?
Claude Code plugin: /plugin marketplace add lyndonkl/claude. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Map Analogy to Concept popular?
It lives in lyndonkl/claude, which has 200 GitHub stars and 25 forks.
Related skills
Abstraction Concrete Examples
200lyndonkl/claude
Builds structured abstraction ladders that translate high-level principles into concrete, actionable examples across 3-5 levels. Bridges communication gaps, reveals hidden assumptions, and tests whether abstract ideas work in practice. Use when explaining concepts at different expertise levels, moving between abstract principles and concrete implementation, identifying edge cases by testing ideas against scenarios, designing layered documentation, decomposing complex problems into actionable steps, or bridging strategy-execution gaps.
Academic Letter Architect
200lyndonkl/claude
Guides the creation of evidence-based academic recommendation letters, reference letters, and award nominations that combine concrete examples, meaningful comparisons, and genuine enthusiasm. Use when writing recommendation letters for students, postdocs, or colleagues, or when user mentions recommendation letter, reference, nomination, letter of support, endorsement, or needs help with strong advocacy and comparative statements.
Adr Architecture
200lyndonkl/claude
Documents significant architectural and technical decisions with full context, alternatives considered, trade-offs analyzed, and consequences understood. Creates a decision trail that helps teams understand why decisions were made. Use when choosing between technology options, making infrastructure decisions, establishing standards, migrating systems, or when user mentions ADR, architecture decision, technical decision record, or decision documentation.
Paper Cluster By Theme
200lyndonkl/claude
Groups a set of kept papers into 2-5 thematic clusters before synthesis, using abstract semantics + matched-keyword overlap. Names each cluster with a short noun phrase that describes what the cluster argues, not just the topic. Surfaces an "outliers" bucket for single-paper themes that don't fit. Domain-neutral - usable for any literature-scan workflow. Use after relevance filtering and before writing the synthesis report. Trigger keywords - cluster papers, group by theme, thematic clusters, paper themes, organize papers.
Improve Animations
100adriannoes/awesome-agentic-ai
Survey a codebase's animation and motion code as a senior motion advisor, then produce a prioritized audit and self-contained implementation plans for other agents (or cheaper models) to execute. Read-only on source code — it plans improvements, it does not apply them. Use when the user asks to "improve the animations", "audit the motion", "make this app feel better", or wants a roadmap of animation fixes rather than a review of a single diff.
Propose Counterfactual
200lyndonkl/claude
Produces the counterfactual framing in an Intuition Builder 5-set — "what if this component were not here?" Reveals the function of a technical element by subtracting it and observing what breaks. Uses Pearl's causal ladder (counterfactual = level 3) as the theoretical spine. Use as the 5th archetype slot of generate-analogy-set, or invoked standalone when the writer wants to build intuition for why a specific element exists. Trigger keywords — counterfactual, what if not, remove, subtract, reveal function, why does this exist.
Browse the most popular Claude skills, all frontend & design skills, or write your own with the skills generator.