Creative reasoning framework for ill-defined problems where conventional solutions are suboptimal. Use when the problem has ambiguous goals, vast solution space, no single correct answer, or requires innovation. Implements three paradigms — combinational (novel combinations of familiar ideas), exploratory (expand solution space boundaries), transformative (alter fundamental constraints). Do not use for well-defined problems, mathematical puzzles, or tasks requiring convergent reasoning.
62
78%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
Passed
No findings from the security scan
Fix and improve this skill with Tessl
tessl review fix ./.claude/skills/universe-of-thoughts/SKILL.mdCreative reasoning framework based on Margaret Boden's cognitive science theory of creativity. Implements three paradigms that build sequentially: Combinational → Exploratory → Transformative.
Use UoT when ANY of the following are true:
Do not use UoT for:
| Paradigm | Condition | Output |
|---|---|---|
| Combinational | Familiar elements exist but need fresh combinations | Novel hybrids from cross-domain synthesis |
| Exploratory | Current solution space feels exhausted | Expanded boundaries, adjacent possibilities |
| Transformative | Constraints themselves block progress | Redefined rules, radical departures |
For maximum creativity, run all three sequentially. Each builds on the previous.
Before selecting a paradigm, decompose the problem:
PROBLEM ANALYSIS:
├── Core Challenge: [What fundamentally needs solving]
├── Explicit Constraints: [Stated rules and limits]
├── Implicit Assumptions: [Unstated rules being assumed]
├── Current Domain: [Primary field this belongs to]
├── Adjacent Domains: [Related fields that might offer insight]
└── Success Criteria: [How to recognize a creative solution]Goal: Generate novel combinations of existing ideas by connecting previously unrelated concepts.
Identify 3-5 domains analogous to the problem domain:
HOME DOMAIN: [Problem's primary field]
ANALOGOUS DOMAINS:
├── [Domain A] - [Why analogous]
├── [Domain B] - [Why analogous]
├── [Domain C] - [Why analogous]
└── [Domain D] - [Why analogous]For each analogous domain:
DOMAIN: [Name]
├── Key Mechanisms: [How it works]
├── Solved Problems: [What challenges it addresses]
└── Transferable Elements: [What could apply to target problem]Generate combinations systematically:
COMBINATION: [Domain A concept] + [Domain B concept]
├── Mechanism: [How they work together]
├── Application: [How this addresses the problem]
└── Assessment: [Feasibility and novelty]Produce 3-5 combinational solutions ranked by feasibility and novelty.
Goal: Discover new possibilities by probing the boundaries of the current solution space.
CURRENT SOLUTION SPACE:
├── Known Approaches: [Existing solutions]
├── Common Patterns: [What they share]
├── Boundaries: [Where exploration stops]
└── Implicit Limits: [Unstated constraints on exploration]For each boundary:
BOUNDARY: [Description]
├── What defines this limit?
├── What lies immediately beyond?
├── Is this boundary real or assumed?
└── What solution exists at/past the edge?NEW THOUGHT:
├── Description: [The new idea]
├── Relationship to Existing: [How it connects to known solutions]
├── Space Extension: [How it expands possibilities]
└── Integration Potential: [Can it combine with existing solutions]Produce 3-5 exploratory solutions that extend beyond current boundaries while respecting immutable constraints.
Goal: Alter fundamental rules or constraints to enable radically new solutions.
For each constraint:
CONSTRAINT: [Statement]
├── Origin: [Why this rule exists]
├── Type:
│ ├── Physical law → Immutable
│ ├── Regulatory → Potentially changeable
│ ├── Convention → Questionable
│ └── Assumption → Likely unnecessary
├── Removal Impact: [What happens without it]
└── Transformation Potential: [How it could be modified]For constraints marked questionable or unnecessary:
TRANSFORMATION:
├── Original Rule: [The constraint]
├── Transformation Type: [Inversion | Relaxation | Substitution | Elimination]
├── New Rule: [The modified version]
└── New Possibilities: [What becomes possible]TRANSFORMATIVE SOLUTION:
├── Rule Changes Required: [What must be different]
├── Mechanism: [How it works in the new space]
├── Implementation Path: [How to get from current state to new state]
├── Risk Assessment: [What could go wrong]
└── Reward Assessment: [Potential upside]Produce 2-3 transformative solutions with explicit rule changes and implementation paths.
When running all three paradigms:
SOLUTION PORTFOLIO:
├── Tier 1 (Low risk, moderate novelty): [Combinational solutions]
├── Tier 2 (Medium risk, high novelty): [Exploratory solutions]
└── Tier 3 (High risk, breakthrough potential): [Transformative solutions]Assess all solutions on the dimensions below:
| Dimension | Question | Scale |
|---|---|---|
| Feasibility | Does it violate immutable constraints? | Pass/Fail |
| Utility | How effectively does it solve the problem? | 1-10 |
| Novelty | How different from existing approaches? | 1-10 |
Solutions must pass feasibility. Rank passing solutions by (Utility × Novelty).
Problem: Minimize vehicle delay on a single-lane bridge. No new bridges permitted.
| Source Domain | Concept | Application |
|---|---|---|
| Air traffic control | Scheduled slots | Time-slot reservations for vehicles |
| Packet switching | Dynamic routing | Priority-based direction changes |
| Tidal systems | Periodic reversal | Time-based directional flow |
| Boundary | Probe | Solution |
|---|---|---|
| Vehicles are independent | What if they communicated? | Convoy formation, platooning |
| Bridge is passive | What if it signaled? | Smart bridge with dynamic indicators |
| Optimize for fairness | What if throughput mattered more? | Batch processing by direction |
| Constraint | Type | Transformation | Solution |
|---|---|---|---|
| Single lane | Convention | Virtual lanes | Motorcycle/bicycle parallel path |
| Vehicles | Assumption | Move people, not cars | Pedestrian/bike priority + parking |
| Bridge | Assumption | Challenge "crossing" | Cable car, ferry, tunnel |
Jamie-BitFlight/claude_skills
a5218b3
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.