본문으로 건너뛰기
cccskills
무료GitHub에 공개

universe-of-thoughts

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.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

실행 점수 미검증

설치 방법 보기

포함된 파일(1)

  • SKILL.md8.9 KB

SKILL.md(원문)

설치하기 전에 에이전트에게 전달되는 지시 내용을 확인할 수 있습니다.

Universe of Thoughts (UoT)

Creative reasoning framework based on Margaret Boden's cognitive science theory of creativity. Implements three paradigms that build sequentially: Combinational → Exploratory → Transformative.

When to Use

Use UoT when ANY of the following are true:

  • Problem has ambiguous or undefined goals
  • Solution space is vast and open-ended
  • No single "correct" answer exists
  • Conventional approaches have failed or are known to be suboptimal
  • Task requires genuine innovation, not optimization
  • Domain involves strategy, design, research direction, or policy

When NOT to Use

Do not use UoT for:

  • Well-defined problems with verifiable solutions
  • Mathematical or logical puzzles (use Chain-of-Thought)
  • Tasks requiring convergent reasoning toward a known answer
  • Optimization within fixed constraints
  • Fact retrieval or factual accuracy tasks (use Chain-of-Verification)

Paradigm Selection

ParadigmConditionOutput
CombinationalFamiliar elements exist but need fresh combinationsNovel hybrids from cross-domain synthesis
ExploratoryCurrent solution space feels exhaustedExpanded boundaries, adjacent possibilities
TransformativeConstraints themselves block progressRedefined rules, radical departures

For maximum creativity, run all three sequentially. Each builds on the previous.


Phase 0: Problem Decomposition

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]

Paradigm 1: Combinational (C-UoT)

Goal: Generate novel combinations of existing ideas by connecting previously unrelated concepts.

C1: Domain Mapping

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]

C2: Concept Extraction

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]

C3: Cross-Domain Synthesis

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]

C4: Output

Produce 3-5 combinational solutions ranked by feasibility and novelty.


Paradigm 2: Exploratory (E-UoT)

Goal: Discover new possibilities by probing the boundaries of the current solution space.

E1: Map Current Space

CURRENT SOLUTION SPACE:
├── Known Approaches: [Existing solutions]
├── Common Patterns: [What they share]
├── Boundaries: [Where exploration stops]
└── Implicit Limits: [Unstated constraints on exploration]

E2: Boundary Probing

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?

E3: Novel Thought Generation

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]

E4: Output

Produce 3-5 exploratory solutions that extend beyond current boundaries while respecting immutable constraints.


Paradigm 3: Transformative (T-UoT)

Goal: Alter fundamental rules or constraints to enable radically new solutions.

T1: Constraint Archaeology

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]

T2: Rule Transformation

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]

T3: Radical Solution Generation

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]

T4: Output

Produce 2-3 transformative solutions with explicit rule changes and implementation paths.


Integration: Full Pipeline

When running all three paradigms:

  1. Execute C-UoT → Select top 2 solutions
  2. Execute E-UoT starting from C-UoT outputs → Select top 2 solutions
  3. Execute T-UoT starting from E-UoT outputs → Select top 2 solutions
  4. Produce tiered portfolio:
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]

Evaluation Criteria

Assess all solutions on the dimensions below:

DimensionQuestionScale
FeasibilityDoes it violate immutable constraints?Pass/Fail
UtilityHow effectively does it solve the problem?1-10
NoveltyHow different from existing approaches?1-10

Solutions must pass feasibility. Rank passing solutions by (Utility × Novelty).


Example: Single-Lane Bridge Traffic

Problem: Minimize vehicle delay on a single-lane bridge. No new bridges permitted.

Combinational

Source DomainConceptApplication
Air traffic controlScheduled slotsTime-slot reservations for vehicles
Packet switchingDynamic routingPriority-based direction changes
Tidal systemsPeriodic reversalTime-based directional flow

Exploratory

BoundaryProbeSolution
Vehicles are independentWhat if they communicated?Convoy formation, platooning
Bridge is passiveWhat if it signaled?Smart bridge with dynamic indicators
Optimize for fairnessWhat if throughput mattered more?Batch processing by direction

Transformative

ConstraintTypeTransformationSolution
Single laneConventionVirtual lanesMotorcycle/bicycle parallel path
VehiclesAssumptionMove people, not carsPedestrian/bike priority + parking
BridgeAssumptionChallenge "crossing"Cable car, ferry, tunnel

References

  • Suzuki & Banaei-Kashani (2025). "Universe of Thoughts: Enabling Creative Reasoning with Large Language Models." arXiv:2511.20471
  • Boden, M. A. (2004, 2007, 2009). Computational creativity theory

리뷰

아직 리뷰가 없습니다. 사용해 본 소감을 남겨 주세요.

댓글

로그인 없이 쓸 수 있습니다. 사용 후기, 질문, 작동하지 않은 환경 등을 편하게 남겨 주세요.

아직 댓글이 없습니다. 첫 댓글을 남겨 보세요.

보내면 바로 공개됩니다. 이메일 주소나 전화번호 같은 개인 정보는 쓰지 마세요. URL은 2개까지입니다.

0 / 1,000자

이 양식은 reCAPTCHA로 보호되며 Google 개인정보처리방침 및 서비스 약관이 적용됩니다.

같은 저장소의 스킬

Add automated documentation updater to any Claude skill. Creates a Python sync script that downloads upstream docs, processes markdown for AI consumption, and maintains local cache with configurable refresh. Collects template variables, then delegates implementation through 5-phase workflow. Use when adding auto-updating reference documentation to plugins or skills.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Jamie-BitFlight/claude_skills672026년 10월 20일 업데이트

SAM-style feature initiation workflow — discovery through codebase analysis, architecture spec, task decomposition, validation, and context manifest. Use when a user asks to add a feature, plan a feature, or convert an idea into an executable SAM plan.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Jamie-BitFlight/claude_skills672026년 10월 20일 업데이트

Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, or automating any browser task. Triggers include requests to "open a website", "fill out a form", "click a button", "take a screenshot", "scrape data from a page", "test this web app", "login to a site", "automate browser actions", or any task requiring programmatic web interaction.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Jamie-BitFlight/claude_skills672026년 10월 20일 업데이트

Browser automation for AI agents using the agent-browser CLI and Playwright. Use when navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, logging into sites, or automating any browser task. Triggers on "open a website", "fill out a form", "click a button", "scrape data", "test this web app", "automate browser actions", or any programmatic web interaction request.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Jamie-BitFlight/claude_skills672026년 10월 20일 업데이트

Runs the description-drift experiment — spawns all Claude Code agents simultaneously to collect self-reported capabilities, then compares them against static frontmatter descriptions to reveal how reliable orchestrator routing based on descriptions actually is. Use when measuring description drift across the agent fleet, re-running the capability collection experiment, analyzing a specific agent's self-reported capabilities, or auditing whether frontmatter descriptions accurately reflect agent behavior.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Jamie-BitFlight/claude_skills672026년 10월 20일 업데이트

Create or adapt Claude Code agent definitions. Use when creating an agent, changing subagent configuration, selecting agent scope, or designing a specialized delegation role.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Jamie-BitFlight/claude_skills672026년 10월 20일 업데이트

Jamie-BitFlight의 스킬 모두 보기

이 스킬의 문제 신고