Use when synthesizing information from multiple sources (literature review, stakeholder feedback, research findings, data from different systems), creating or evaluating analogies for explanation or problem-solving (cross-domain transfer, "X is like Y", structural mapping), combining conflicting viewpoints into unified framework, identifying patterns across disparate sources, finding creative solutions by transferring principles from one domain to another, testing whether analogies hold (surface vs deep similarities), or when user mentions "synthesize", "combine sources", "analogy", "like", "similar to", "transfer from", "integrate findings", "what's it analogous to".
Synthesizes multiple sources (research, feedback, data) into unified insights and creates structural analogies to explain complex concepts or transfer solutions across domains. Use when user mentions "synthesize," "analogy," "like," or needs to combine conflicting viewpoints, identify patterns, or explain unfamiliar topics using familiar domains.
/plugin marketplace add lyndonkl/claude/plugin install lyndonkl-thinking-frameworks-skills@lyndonkl/claudeThis skill inherits all available tools. When active, it can use any tool Claude has access to.
resources/evaluators/rubric_synthesis_and_analogy.jsonresources/methodology.mdresources/template.mdSynthesize information from multiple sources into coherent insights and use analogical reasoning to transfer knowledge across domains, explain complex concepts, and find creative solutions.
Information Synthesis:
Analogical Reasoning:
Combined Synthesis + Analogy:
Synthesis: Combining information from multiple sources into unified, coherent whole that reveals patterns, resolves conflicts, and generates new insights beyond individual sources.
Analogy: Structural mapping between domains where relationships in source domain (familiar) illuminate relationships in target domain (unfamiliar). Good analogies preserve deep structure, not just surface features.
Example - Synthesis: Synthesizing 15 customer interviews + 5 surveys + support ticket analysis → "Customers struggle with onboarding (87% mention), specifically Step 3 configuration (65% abandon here), because terminology is domain-specific (42% request glossary). Three user types emerge: novices (need hand-holding), intermediates (need examples), experts (need speed)."
Example - Analogy: "Microservices architecture is like a city of specialized shops vs monolithic architecture like a department store. City: each shop (service) independent, can renovate without closing whole city, but must coordinate deliveries (APIs). Department store: everything under one roof (codebase), easier coordination, but renovating one section disrupts whole store. Trade-off: flexibility vs simplicity."
Copy this checklist and track your progress:
Synthesis & Analogy Progress:
- [ ] Step 1: Clarify goal and gather sources/domains
- [ ] Step 2: Choose approach (synthesis, analogy, or both)
- [ ] Step 3: Apply synthesis or analogy techniques
- [ ] Step 4: Test quality and validity
- [ ] Step 5: Refine and deliver insights
Step 1: Clarify goal
For synthesis: What sources? What question are we answering? What conflicts need resolving? For analogy: What's source domain (familiar)? What's target domain (explaining)? What's goal (explain, solve, ideate)? See Common Patterns for typical goals.
Step 2: Choose approach
Synthesis only → Use Synthesis Techniques. Analogy only → Use Analogy Techniques. Both → Start with synthesis to find patterns, then use analogy to explain or transfer. For straightforward cases → Use resources/template.md. For complex multi-domain synthesis → Study resources/methodology.md.
Step 3: Apply techniques
For synthesis: Identify themes across sources, note agreements/disagreements, resolve conflicts via higher-level framework, extract patterns. For analogy: Map structure from source to target (what corresponds to what?), identify shared relationships (not surface features), test mapping validity. See Synthesis Techniques and Analogy Techniques.
Step 4: Test quality
Self-assess using resources/evaluators/rubric_synthesis_and_analogy.json. Synthesis checks: captures all sources? resolves conflicts? identifies patterns? adds insight? Analogy checks: structure preserved? deep not surface? limitations acknowledged? helps understanding? Minimum standard: Score ≥3.5 average.
Step 5: Refine and deliver
Create synthesis-and-analogy.md with: synthesis summary (themes, agreements, conflicts, patterns, new insights) OR analogy explanation (source domain, target domain, mapping table, what transfers, limitations), supporting evidence from sources, actionable implications.
Thematic Synthesis (identify recurring themes):
Conflict Resolution Synthesis (reconcile disagreements):
Pattern Identification (find cross-cutting insights):
Example: Synthesizing 10 postmortems → Pattern: 80% of incidents involve config change + lack of rollback plan. Outliers: 2 incidents hardware failure. Meta-insight: Need config change review process + automatic rollback capability.
Structural Mapping Theory:
Surface vs Deep Analogies:
Example - Surface: "Brain is like computer (both process information)" - too vague, doesn't help Example - Deep: "Brain neurons are like computer transistors: neurons fire/don't fire (binary), connect in networks, learning = strengthening connections (weights). BUT neurons are analog/probabilistic, computer precise/deterministic" - preserves structure, acknowledges limits
Analogy Quality Tests:
Pattern 1: Literature Review Synthesis
Pattern 2: Multi-Stakeholder Synthesis
Pattern 3: Explanatory Analogy
Pattern 4: Cross-Domain Problem-Solving
Pattern 5: Creative Ideation via Analogy
Synthesis Quality:
Analogy Quality:
Avoid:
Inputs Required:
For synthesis:
For analogy:
Techniques to Use:
Synthesis:
Analogy:
Outputs Produced:
synthesis-and-analogy.md with:
Resources:
Minimum Quality Standard:
Creating algorithmic art using p5.js with seeded randomness and interactive parameter exploration. Use this when users request creating art using code, generative art, algorithmic art, flow fields, or particle systems. Create original algorithmic art rather than copying existing artists' work to avoid copyright violations.
Applies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply.
Create beautiful visual art in .png and .pdf documents using design philosophy. You should use this skill when the user asks to create a poster, piece of art, design, or other static piece. Create original visual designs, never copying existing artists' work to avoid copyright violations.