morphological-analysis-triz
Explores solution spaces systematically through morphological analysis (parameter-option matrices) and resolves technical contradictions using TRIZ inventive principles to generate novel, non-obvious solutions. Use when exploring all feasible design alternatives before prototyping, resolving technical contradictions (speed vs precision, strength vs weight, cost vs quality), generating novel product configurations, finding inventive solutions to engineering problems, identifying patent opportunities, or when user mentions morphological analysis, Zwicky box, TRIZ, inventive principles, systematic innovation, or design space exploration.
What this skill does
# Morphological Analysis & TRIZ
## Workflow
Copy this checklist:
```
Morphological Analysis & TRIZ Progress:
- [ ] Step 1: Define problem and objectives
- [ ] Step 2: Choose method (MA, TRIZ, or both)
- [ ] Step 3: Build morphological box (if MA)
- [ ] Step 4: Identify contradictions (if TRIZ)
- [ ] Step 5: Apply TRIZ principles
- [ ] Step 6: Evaluate and select solutions
```
**Step 1: Define problem and objectives**
Clarify problem statement, key objectives, constraints (cost, size, time, materials), and success criteria.
**Step 2: Choose method**
- **Morphological Analysis:** 3-7 clear parameters, each with 2-5 options, goal is comprehensive exploration
- **TRIZ:** Clear contradiction (improving A worsens B), need inventive breakthrough
- **Both:** Complex system with parameters AND contradictions
**Step 3: Build morphological box (if using MA)**
1. Identify 3-7 independent parameters (changing one doesn't force another)
2. List 2-5 distinct options per parameter
3. Create parameter × option matrix
See [resources/template.md](resources/template.md) for structure.
**Step 4: Identify contradictions (if using TRIZ)**
State clearly:
- **Improving parameter:** What to increase?
- **Worsening parameter:** What degrades?
- Look up in TRIZ contradiction matrix
See [resources/template.md](resources/template.md) for 39 TRIZ parameters and contradiction matrix.
**Step 5: Apply TRIZ principles**
1. Review 3-4 principles recommended by matrix
2. Brainstorm applications of each principle
3. Generate solution concepts
4. Combine principles for stronger solutions
See [resources/template.md](resources/template.md) for all 40 principles.
For advanced techniques, see [resources/methodology.md](resources/methodology.md).
**Step 6: Evaluate and select**
**Morphological:** Identify promising combinations, eliminate infeasible, score on objectives, select top 3-5
**TRIZ:** Assess contradiction resolution, check side effects, estimate difficulty, select most promising
Use [resources/evaluators/rubric_morphological_analysis_triz.json](resources/evaluators/rubric_morphological_analysis_triz.json) for quality criteria.
## Common Patterns
### Typical Parameters (Examples)
**Physical Products:** Materials, power source, form factor, control interface, manufacturing method
**Software:** Architecture, data storage, UI, deployment, authentication
**Services:** Delivery channel, pricing model, timing, customization, support level
**Processes:** Automation level, batch size, quality control, scheduling, location
### Common Contradictions
| Improving ↑ | Worsens ↓ | Example TRIZ Principles |
|-------------|-----------|------------------------|
| Speed | Precision | Segmentation, Periodic action |
| Strength | Weight | Anti-weight, Composite materials |
| Reliability | Complexity | Segmentation, Beforehand cushioning |
| Functionality | Ease of use | Segmentation, Universality |
| Capacity | Size | Nesting, Another dimension |
**Full principles list:** See [resources/template.md](resources/template.md) for all 40.
### When to Combine MA + TRIZ
1. Build morphological box → Find promising configurations
2. Identify contradictions in top configurations
3. Apply TRIZ to resolve contradictions
4. Re-evaluate configurations with contradictions resolved
## Guardrails
**Morphological Analysis:**
- **Limit parameters:** 3-7 parameters (too few = incomplete, too many = explosion)
- **Ensure independence:** Changing one parameter shouldn't force changes in another
- **Manageable options:** 2-5 per parameter (practical range)
- **Don't enumerate all:** Focus on promising clusters
**TRIZ:**
- **Verify real contradiction:** Improving A truly worsens B (not just budget limit)
- **Adapt principles:** Use as metaphors, not literal prescriptions
- **Check new contradictions:** Solution may introduce new trade-offs
- **Combine principles:** Often need 2-3 together
**General:**
- Document rationale for parameters/options selected
- Iterate if first pass reveals missing dimensions
- Prototype top concepts - don't just analyze
## Quick Reference
**Resources:**
- `resources/template.md` - Morphological structure, TRIZ contradiction matrix, 40 principles
- `resources/methodology.md` - Advanced TRIZ (trends of evolution, substance-field, ARIZ algorithm)
- `resources/evaluators/rubric_morphological_analysis_triz.json` - Quality criteria
**Output:** `morphological-analysis-triz.md` with problem definition, morphological matrix (if used), contradictions, TRIZ principles applied, solution concepts, evaluation, selected solutions
**Success Criteria:**
- Parameters independent and essential (3-7 with 2-5 options each)
- Contradictions clearly stated (improving/worsening parameters)
- Multiple principles applied per contradiction
- Solutions are novel, feasible, address objectives
- Top 3-5 selected with rationale
- Score ≥ 3.5 on rubric
**Quick Decisions:**
- **Simple configuration?** → Morphological only
- **Clear contradiction?** → TRIZ only
- **Complex with trade-offs?** → Both methods
- **Unsure?** → Start TRIZ to identify contradictions, then build morphological box
**Common Mistakes:**
1. Too many parameters (>7 = explosion)
2. Dependent parameters (choosing A forces B)
3. Vague contradiction ("better vs cheaper" - be specific)
4. Literal TRIZ (principles are metaphors)
5. No evaluation (generate but don't filter)
**Examples:**
**Morphological (Portable Speaker):**
```
Power: Battery | Solar | Hybrid
Size: Pocket | Handheld | Tabletop
Audio: Mono | Stereo | Surround
Material: Plastic | Metal | Fabric
Control: Button | Touch | Voice | App
Result: 3×3×3×4×4 = 432 configs → Evaluate top 10
```
**TRIZ (Electric Vehicle Range):**
```
Contradiction: Increase range → worsens cost (battery expensive)
Principles: #6 (Universality - battery is structure), #35 (Parameter change - new chemistry)
Solution: Structural battery pack + high energy density cells
```
**Combined:**
```
Build morphological box for EV architecture → Top config has range/cost contradiction → Apply TRIZ Universality principle → Structural battery resolves both range and cost
```
---
**For detailed principle explanations, contradiction matrix, advanced techniques (substance-field analysis, ARIZ, trends of evolution), and software/service adaptation, see [resources/template.md](resources/template.md) and [resources/methodology.md](resources/methodology.md).**
Related in Design
contribute
IncludedLocal-only OSS contribution command center. Auto-refreshes the user's in-flight PR and issue state on invoke so conversations start with full context — no need to brief Claude on what's in flight. Helps the user find issues to contribute to on GitHub, builds per-repo dossiers of what each upstream expects (CLA, DCO, branch convention, AI policy, draft-first, review bots, issue templates), runs deterministic gates before any external action so AI-assisted contributions don't reach maintainers as slop. State is markdown-only: candidate files at ~/.contribute-system/candidates/, repo dossiers at ~/.contribute-system/research/, append-only event log at ~/.contribute-system/log.jsonl. No database, no cloud calls. Use when the user asks about their PRs / issues / contributions, wants to find new work to take on, claim an issue, build/refresh a repo's dossier, or draft a Design Issue or PR. Trigger with "/contribute", "what's my PR status", "find a contribution", "claim issue X", "draft a Design Issue for Y", "refresh dossier for Z".
architectural-analysis
IncludedUser-triggered deep architectural analysis of a codebase or scoped subtree across eight modes — information architecture, data flow, integration points, UI surfaces, interaction patterns, data model, control flow, and failure modes. This skill should be used when the user asks to "diagram this codebase," "map the architecture," "show the data flow," "give me an ERD," "trace control flow," "find the integration points," "verify the layout pattern," "audit the UX architecture," or any similar request whose primary deliverable is mermaid diagrams plus cited reports under docs/architecture/. Dispatches haiku/sonnet sub-agents in parallel for per-mode exploration, then verifies every citation mechanically before any node lands in a diagram. Not for one-off prose explanations of code (use code-explanation) or for high-level system design from scratch (use system-design).
mcp
IncludedModel Context Protocol (MCP) server development and tool management. Languages: Python, TypeScript. Capabilities: build MCP servers, integrate external APIs, discover/execute MCP tools, manage multi-server configs, design agent-centric tools. Actions: create, build, integrate, discover, execute, configure MCP servers/tools. Keywords: MCP, Model Context Protocol, MCP server, MCP tool, stdio transport, SSE transport, tool discovery, resource provider, prompt template, external API integration, Gemini CLI MCP, Claude MCP, agent tools, tool execution, server config. Use when: building MCP servers, integrating external APIs as MCP tools, discovering available MCP tools, executing MCP capabilities, configuring multi-server setups, designing tools for AI agents.
react-native-skia
IncludedDesign, build, debug, and optimise high-polish animated graphics in React Native or Expo using @shopify/react-native-skia, Reanimated, and Gesture Handler. Use when the user wants canvas-driven UI, shaders, paths, rich text, image filters, sprite fields, Skottie, video frames, snapshots, web CanvasKit setup, or performance tuning for custom motion-heavy elements such as loaders, hero art, cards, charts, progress indicators, particle systems, or gesture-driven surfaces. Also use when the user asks for fluid, glow, glass, blob, parallax, 60fps/120fps, or GPU-friendly animated effects in React Native, even if they do not explicitly say "Skia". Do not use for ordinary form/layout work with standard views.
plaid
IncludedProduct Led AI Development — guides founders from idea to launched product. Six capabilities: Idea (discover a product idea), Validate (pressure-test the idea against fatal flaws, problem reality, competition, and 2-week MVP feasibility), Plan (vision intake + document generation), Design (translate image references into a design.md spec), Launch (go-to-market strategy), and Build (roadmap execution). Use when someone says "PLAID", "plaid idea", "help me find an idea", "product idea", "idea from my business", "idea from my expertise", "plaid validate", "validate my idea", "pressure-test", "is this idea good", "find fatal flaws", "validate the problem", "plan a product", "define my vision", "generate a PRD", "product strategy", "plaid design", "design from image", "translate image to design", "create design.md", "extract design tokens", "plaid launch", "go-to-market", "launch plan", "GTM strategy", "launch playbook", "plaid build", "build the app", "start building", or "execute the roadmap".
nextjs-framer-motion-animations
IncludedAdds production-safe Motion for React or Framer Motion animations to Next.js apps, including reveal, hover and tap micro-interactions, whileInView, stagger, AnimatePresence, layout and layoutId transitions, reorder, scroll-linked UI, and lightweight route-content transitions. Use when the user asks to add, refactor, or debug Motion or Framer Motion in App Router or Pages Router codebases, especially around server/client boundaries, reduced motion, LazyMotion, bundle size, hydration, or route transitions. Avoid for GSAP-style timelines, WebGL or 3D scenes, heavy scroll storytelling, or CSS-only effects unless Motion is explicitly requested.