expansive-inquiry
Multi-perspective collaborative inquiry. Decomposes a topic into six cognitive lenses (Scope, Logic, Mythos, Bridge, Meta, Pattern) that operate as a chorus rather than a single voice, then synthesizes meta-patterns no single lens could find alone. MANDATORY TRIGGERS: 'expansive inquiry', 'multi-perspective inquiry', 'explore this from every angle', 'six-lens analysis', 'run a chorus on this'. STRONG TRIGGERS: 'help me think through X deeply', 'mythopoetic AND logical analysis'. Do NOT trigger on simple Q&A or failure-focused inquiries — use premortem for those.
What this skill does
# Expansive Inquiry
## What this is
Expansive Inquiry is a cognitive architecture for distributed intelligence. Most inquiry flattens a topic into a single voice. This skill orchestrates six — each with a distinct epistemic posture — and weaves their outputs into a synthesis that surfaces emergent meta-patterns no single lens could find alone.
The lineage:
- The original prototype was a React app (V4) that ran six specialized AI roles sequentially over a user-supplied topic and exported each stage as YAML-frontmatter Markdown.
- Two rounds of critique pushed it toward (a) a real cognitive architecture rather than a six-stage pipeline, (b) parallel execution of independent stages, (c) context summarization to avoid token bloat in later stages, (d) a synthesis layer that detects contradictions across lenses, and (e) an HTML visualization of the inquiry shape ("epistemic signature").
- This skill encodes the matured methodology. Claude IS the orchestrator. The six lenses are personality vectors Claude adopts in turn, not external services. No React app required.
## When to invoke
**Good targets:**
- Open-ended thematic questions ("What is the role of ritual in distributed teams?")
- Strategic decisions where the user wants epistemic pluralism, not narrowing
- Dramaturgical / artistic / philosophical analysis where logic alone would flatten the subject
- Research synthesis where multiple disciplinary lenses are warranted
- Anything the user describes with words like "deeply", "from every angle", "chorus", "mythopoetic"
**Bad targets:**
- Failure-focused analysis → use `premortem` instead
- Decision-by-vote among options → use the LLM Council instead
- Factual/closed questions ("What's the capital of Mongolia?") → just answer
- Code review or feature spec → too narrow for six-lens orchestration
If the user wants ONE answer, this skill is the wrong tool. If they want a SHAPE — the topology of the topic across cognitive registers — this is the right tool.
---
## The six lenses (epistemic personalities)
Each lens has: a role, a posture, a prompt template, and an output structure. They are NOT generic "perspectives" — they are specific cognitive postures with distinct anti-patterns to resist.
### 1. Scope AI (clarification)
**Role:** Distill the user's topic into a single precise actionable inquiry sentence.
**Posture:** Phenomenological reduction. What is essential? What is peripheral?
**Anti-pattern to resist:** Restating the topic verbatim. The Scope AI MUST narrow or sharpen.
**Prompt:**
```
You are the Scope AI. Your role is to take an inquiry and distill it into a single,
precise, actionable sentence that captures the core question.
TOPIC: "{topic}"
Tasks:
1. Restate the topic as a focused question or proposition.
2. Name what is essential (must explore) and what is peripheral (can defer).
3. Identify any hidden ambiguities the user may not have noticed.
Output as Markdown with three sections: ## Core Inquiry, ## Essential vs. Peripheral, ## Hidden Ambiguities.
```
### 2. Logic AI (rational branching)
**Role:** Build a rigorous logical tree of orthodox lines of inquiry.
**Posture:** Analytic philosophy. Why? How? What if?
**Anti-pattern to resist:** Listing five generic branches with no internal recursion.
**Prompt:**
```
You are the Logic AI. You build rigorous logical frameworks via systematic rational exploration.
TOPIC: "{topic}"
SCOPE: {scope_summary}
Tasks:
1. Propose 5 orthodox, rational lines of inquiry.
2. For each line, drill three levels deep using "why?", "how?", or "what if?" — each level
building on the previous, not branching laterally.
3. Render as a hierarchical tree (Markdown nested lists).
Output as Markdown with sections: ## Five Lines, ## Recursive Tree, ## Strongest Branch.
```
### 3. Mythos AI (intuitive branching)
**Role:** Reveal hidden dimensions through metaphor, archetype, and narrative.
**Posture:** Mythopoetic. Stories and symbols that illuminate.
**Anti-pattern to resist:** Generic "this is like a hero's journey" mappings. Mythos AI must commit to specific archetypal claims.
**Prompt:**
```
You are the Mythos AI. You think in stories, metaphors, and archetypal patterns.
TOPIC: "{topic}"
SCOPE: {scope_summary}
Tasks:
1. Propose 5 metaphorical or mythopoetic framings of the topic. Be specific to the topic — no
generic "hero's journey" or "Tower of Babel" unless the structural fit is genuinely tight.
2. For each framing, write a 2-3 sentence analogical story or symbolic reading.
3. Identify the archetypal pattern revealed (e.g., trickster, threshold, sacrifice, return).
Output as Markdown with sections: ## Five Framings, ## Stories, ## Archetypal Reading.
```
### 4. Bridge AI (lateral / cross-domain)
**Role:** Find unexpected connections between this topic and seemingly unrelated domains.
**Posture:** Transdisciplinary. Surface analogical structure across far-apart fields.
**Anti-pattern to resist:** Adjacent-domain analogies (e.g., bridging biology to medicine). Bridge AI must REACH.
**Prompt:**
```
You are the Bridge AI. You find unexpected connections between seemingly unrelated domains.
TOPIC: "{topic}"
SCOPE: {scope_summary}
PRIOR LENSES: Logic produced {logic_summary}; Mythos produced {mythos_summary}.
Tasks:
1. Identify 5 domains far from the topic's natural neighborhood (e.g., bridge a software topic
to choreography, fungal networks, monetary policy, glassblowing, or ant foraging — not to
adjacent software).
2. For each, draw a specific structural analogy that bridges the domain to the topic.
3. Propose a hybrid question that emerges only from each cross-domain connection.
Output as Markdown with sections: ## Five Bridges, ## Hybrid Questions, ## Most Productive Bridge.
```
### 5. Meta AI (recursive design)
**Role:** Design self-improving feedback loops over the inquiry itself.
**Posture:** Reflexive. The inquiry is a system; what would make it converge faster?
**Anti-pattern to resist:** Treating "meta" as just "summary." Meta AI must propose machinery.
**Prompt:**
```
You are the Meta AI. You design self-improving recursive systems and think about thinking itself.
TOPIC: "{topic}"
PRIOR LENSES: Scope, Logic, Mythos, Bridge — full transcripts above.
Tasks:
1. Analyze the prior stages as a system. What did each lens contribute that the others missed?
2. Design a feedback loop that could refine the inquiry: which questions should be regenerated,
which lines pruned, which stages re-run with revised input?
3. Propose 3 concrete ways the system could learn from this specific inquiry pattern.
Output as Markdown with sections: ## System Diagnosis, ## Feedback Loop, ## Three Adaptations.
```
### 6. Pattern AI (emergent meta-pattern recognition)
**Role:** Detect motifs and meta-patterns that span across all prior lenses.
**Posture:** Hyperscanning. What recurs? What is the topology?
**Anti-pattern to resist:** Restating themes from one lens as if they were emergent. Pattern AI must find what is visible ONLY in cross-lens overlay.
**Prompt:**
```
You are the Pattern AI. You recognize emergent structures and meta-patterns across complex,
multi-perspective information.
TOPIC: "{topic}"
PRIOR LENSES: Scope, Logic, Mythos, Bridge, Meta — full transcripts above.
Tasks:
1. Scan all five prior outputs for repeating motifs, structures, or themes that appear in MORE
THAN ONE lens — those are the emergent patterns.
2. Propose 3 meta-patterns and explain how each manifests in at least 3 different lenses.
3. Speculate on the broader significance: what does the cross-lens overlay reveal about the
topic that no single lens could?
Output as Markdown with sections: ## Cross-Lens Motifs, ## Three Meta-Patterns, ## Topological Reading.
```
---
## Execution graph (parallel where independent, sequential where dependent)
The original V4 ran all six stages sequentially. This is wasteful. The dependency graph:
```
Scope ──┬──> Logic ────┐
├──> Mythos ───┤
│ Related in Image & Video
watch
IncludedWatch a video (URL or local path). Downloads with yt-dlp, extracts auto-scaled frames with ffmpeg, pulls the transcript from captions (or Whisper API fallback), and hands the result to Claude so it can answer questions about what's in the video.
physical-ai-defect-image-generation
IncludedUse when the user wants to orchestrate defect image generation, run associated setup, or handle outputs on OSMO. The Day 0 path handles cold-start with USD-to-ROI, image-edit augmentation, and AnomalyGen to create initial PCBA datasets. The Day 1 path performs inference and labeling on real images. This skill helps with first-time asset setup, creation of finetuning checkpoints, and configuring deployment. Trigger keywords: defect image generation, dig workflow, dig pipeline, defect image detection workflow, aoi pipeline, aoi anomalygen, usd2roi anomalygen, day 0 pcba, day 1 pcba, day 1 real-photo alignment, day 1 manual roi, metal surface anomaly, glass defect, anomalygen finetune, setup_pcb, setup_metal, setup_glass, setup_pretrained, dig setup, dig datasets, dig pretrained checkpoint, dig image-edit endpoint.
accelint-react-best-practices
IncludedReact performance optimization and best practices. ALWAYS use this skill when working with any React code - writing components, hooks, JSX; refactoring; optimizing re-renders, memoization, state management; reviewing for performance; fixing hydration mismatches; debugging infinite re-renders, stale closures, input focus loss, animations restarting; preventing remounting; implementing transitions, lazy initialization, effect dependencies. Even simple React tasks benefit from these patterns. Covers React 19+ (useEffectEvent, Activity, ref props). Triggers - useEffect, useState, useMemo, useCallback, memo, inline components, nested components, components inside components, re-render, performance, hydration, SSR, Next.js, useDeferredValue, combined hooks.
elevenlabs-agents
IncludedBuild conversational AI voice agents with ElevenLabs Platform using React, JavaScript, React Native, or Swift SDKs. Configure agents, tools (client/server/MCP), RAG knowledge bases, multi-voice, and Scribe real-time STT. Use when: building voice chat interfaces, implementing AI phone agents with Twilio, configuring agent workflows or tools, adding RAG knowledge bases, testing with CLI "agents as code", or troubleshooting deprecated @11labs packages, Android audio cutoff, CSP violations, dynamic variables, or WebRTC config. Keywords: ElevenLabs Agents, ElevenLabs voice agents, AI voice agents, conversational AI, @elevenlabs/react, @elevenlabs/client, @elevenlabs/react-native, @elevenlabs/elevenlabs-js, @elevenlabs/agents-cli, elevenlabs SDK, voice AI, TTS, text-to-speech, ASR, speech recognition, turn-taking model, WebRTC voice, WebSocket voice, ElevenLabs conversation, agent system prompt, agent tools, agent knowledge base, RAG voice agents, multi-voice agents, pronunciation dictionary, voice speed control, elevenlabs scribe, @11labs deprecated, Android audio cutoff, CSP violation elevenlabs, dynamic variables elevenlabs, case-sensitive tool names, webhook authentication
humanizer
IncludedHumanize AI-generated text by detecting and removing patterns typical of LLM output. Rewrites text to sound natural, specific, and human. Uses 28 pattern detectors, 560+ AI vocabulary terms across 3 tiers, and statistical analysis (burstiness, type-token ratio, readability) for comprehensive detection. Use when asked to humanize text, de-AI writing, make content sound more natural/human, review writing for AI patterns, score text for AI detection, or improve AI-generated drafts. Covers content, language, style, communication, and filler categories.
generating-mermaid-diagrams
IncludedSalesforce architecture diagrams using Mermaid with ASCII fallback. Use this skill when generating text-based diagrams for Salesforce architecture, OAuth flows, ERDs, integration sequences, or Agentforce structure. TRIGGER when: user says "diagram", "visualize", "ERD", or asks for sequence diagrams, flowcharts, class diagrams, or architecture visualizations in Mermaid. DO NOT TRIGGER when: user wants PNG/SVG image output (use generating-visual-diagrams), or asks about non-Salesforce systems.