morphological-analysis-triz
について
このスキルは、形態分析とTRIZ手法を用いて体系的に革新を実現し、技術的矛盾を解決し、包括的な設計空間を探求します。パラメータの組み合わせを分析することで、新しい製品構成の生成、創造的エンジニアリングソリューションの特定、特許取得の機会発見を支援します。速度と精度のようなトレードオフに直面した場合や、ユーザーがツィッキーボックス、TRIZ原則、設計空間探索に言及した際にご利用ください。
クイックインストール
Claude Code
推奨/plugin add https://github.com/lyndonkl/claudegit clone https://github.com/lyndonkl/claude.git ~/.claude/skills/morphological-analysis-trizこのコマンドをClaude Codeにコピー&ペーストしてスキルをインストールします
ドキュメント
Morphological Analysis & TRIZ
Table of Contents
Purpose
Systematically explore solution spaces through morphological analysis (parameter-option matrices) and resolve technical contradictions using TRIZ inventive principles to generate novel, non-obvious solutions.
When to Use
Systematic Exploration:
- Explore all feasible configurations before committing
- Generate comprehensive set of design alternatives
- Create product line variations across parameters
- Document complete solution space
Innovation & Invention:
- Find novel, non-obvious solutions
- Generate patentable innovations
- Discover synergies between features
- Break out of conventional thinking
Resolving Contradictions:
- Improve one parameter without worsening another
- Solve "impossible" trade-offs (faster AND cheaper)
- Apply proven inventive principles
- Resolve conflicts between requirements
Engineering & Design:
- Design new products/systems from scratch
- Optimize existing designs systematically
- Configure complex systems with many parameters
What Is It
Two complementary methods:
Morphological Analysis: Decompose problem into parameters, identify options for each, systematically combine to explore solution space.
Parameters: Power (3 options) × Size (4 options) × Material (3 options) = 36 configurations
TRIZ: Resolve contradictions using 40 inventive principles. Example: "Improve speed → worsens precision" solved by Principle #1 (Segmentation): fast rough pass + slow precision pass.
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)
- Identify 3-7 independent parameters (changing one doesn't force another)
- List 2-5 distinct options per parameter
- Create parameter × option matrix
See 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 for 39 TRIZ parameters and contradiction matrix.
Step 5: Apply TRIZ principles
- Review 3-4 principles recommended by matrix
- Brainstorm applications of each principle
- Generate solution concepts
- Combine principles for stronger solutions
See resources/template.md for all 40 principles.
For advanced techniques, see 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 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 for all 40.
When to Combine MA + TRIZ
- Build morphological box → Find promising configurations
- Identify contradictions in top configurations
- Apply TRIZ to resolve contradictions
- 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 principlesresources/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:
- Too many parameters (>7 = explosion)
- Dependent parameters (choosing A forces B)
- Vague contradiction ("better vs cheaper" - be specific)
- Literal TRIZ (principles are metaphors)
- 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 and resources/methodology.md.
GitHub リポジトリ
関連スキル
content-collections
メタThis skill provides a production-tested setup for Content Collections, a TypeScript-first tool that transforms Markdown/MDX files into type-safe data collections with Zod validation. Use it when building blogs, documentation sites, or content-heavy Vite + React applications to ensure type safety and automatic content validation. It covers everything from Vite plugin configuration and MDX compilation to deployment optimization and schema validation.
creating-opencode-plugins
メタThis skill provides the structure and API specifications for creating OpenCode plugins that hook into 25+ event types like commands, files, and LSP operations. It offers implementation patterns for JavaScript/TypeScript modules that intercept and extend the AI assistant's lifecycle. Use it when you need to build event-driven plugins for monitoring, custom handling, or extending OpenCode's capabilities.
polymarket
メタThis skill enables developers to build applications with the Polymarket prediction markets platform, including API integration for trading and market data. It also provides real-time data streaming via WebSocket to monitor live trades and market activity. Use it for implementing trading strategies or creating tools that process live market updates.
cloudflare-turnstile
メタThis skill provides comprehensive guidance for implementing Cloudflare Turnstile as a CAPTCHA-alternative bot protection system. It covers integration for forms, login pages, API endpoints, and frameworks like React/Next.js/Hono, while handling invisible challenges that maintain user experience. Use it when migrating from reCAPTCHA, debugging error codes, or implementing token validation and E2E tests.
