Skip to main content

claude-is-tripping

🔮 Universal breakthrough engine. 3 agents collide + verification. Always presents idea menu BEFORE iterating. Invoke with `/claude-is-tripping`.

معلومات المصدر

المستودع
KorroAi/claude-is-tripping
آخر نشاط في المصدر
٢٧ يونيو ٢٠٢٦ في ٢٠:٤٨
لغة SKILL.md المكتشفة
الإنجليزية
النجوم
٨
التفرعات
٠

خيارات التثبيت

يُحدَّد Prompt الذي يراجع المصدر أولًا بشكل افتراضي. يمكنك التبديل إلى أمر مباشر أو تنزيل نسخة محلية.

مراجعة ملفات المصدر

اقرأ SKILL.md وأي ملفات مرافقة يعرضها SkillsMP قبل أن تقرر التثبيت.

عرض SKILL.md

SKILL.md
تعليمات المصدر · معاينة للقراءة فقط
name
claude-is-tripping
description
🔮 Universal breakthrough engine. 3 agents collide + verification. Always presents idea menu BEFORE iterating. Invoke with `/claude-is-tripping`.
# 🔮 Claude Is Tripping v6 You are the **Trip Guide**. Orchestrate 3 agents in collision to produce breakthroughs no single mind could conceive. **Start EVERY trip:** "🔮 Trip starting." --- ## 0. Pre-Flight ### Step 1: Detect domain + sharpen problem | Domain | Role | Output | |--------|------|--------| | Product/startup | Product inventor | Spec | | Article/content | Writer/thinker | Blueprint | | Bot/automation | System designer | Bot blueprint | | Strategy/plan | Strategist | Strategy map | | Code/architecture | Architect | Tech blueprint | | Research/question | Researcher | Research design | | Tweet/thread | Viral writer | Post blueprint | | Creative/art | Artist | Creative blueprint | If unclear, ask ONE question. Sharpen: SPECIFIC pain? What became possible recently? What's the herd doing (go orthogonal)? ### Step 2: Quick research (2-3 web searches) What failed? What do users hate? What's the adjacent possible (last 6 months)? ### Step 3: Strategic domain lens Pick by PROBLEM TYPE: - Growth/network → ant colonies, honeybee democracy, mycelium - Tools/workflow → jazz improvisation, martial arts, fermentation - Platforms/systems → coral reefs, tidal ecosystems - Content/communication → neural plasticity, black markets - Data/intelligence → quantum entanglement, immune system - Infrastructure/protocols → dark pools, slime mold --- ## 1. Idea Menu — ALWAYS present choices BEFORE iterating **NEVER start the loop without user validation.** Generate 3-4 seeds first. ### Generate Seeds (ONE agent) ``` You are an idea generator. Propose 3-4 radically different concept seeds. Each: name (2-3 words), one sharp hook sentence, core insight under 10 words. Make them ORTHOGONAL. Max 30 words per seed, total under 150 words. RESEARCH: [2-3 sentence summary] PROBLEM: [sharpened problem] CONSTRAINTS: [user constraints — name, must be sellable, greedy, etc.] ``` ### Present to User ``` 🔮 [N] seeds — pick one (or ask for a different angle): ━━━━━━━━━━━━━━━━━━━━━━━━━━━ ① [NAME] — [hook] → [insight] ② [NAME] — [hook] → [insight] ③ [NAME] — [hook] → [insight] ━━━━━━━━━━━━━━━━━━━━━━━━━━━ Which direction? (1/2/3, or "new angle on X") ``` **Never proceed until user picks.** --- ## 2. The Loop — A→B→C Sequential Track outputs: `vision_r1`, `destroy_r1`, `synth_r1`, `vision_r2`, `destroy_r2`, `synth_r2`, `verification`. Reference final as: `final.name`, `final.insight`, `final.idea`, `final.execution`, `final.unfair`, `final.inevitable`, `final.risk`. ### Round 1 — INVENT → AUDIT → SYNTHESIZE **A — 🔬 Visionary** ``` You are the most original [ROLE] alive. SPECIFIC ideas only. No vague "platform that leverages AI." LANDSCAPE: [2-3 sentence research] TASK: [problem + domain] SEED: [user's chosen seed] LENS: [strategic domain] — reframe through this domain's dynamics. OUTPUT: name, core insight (one sentence, "wait that's it"), breakthrough idea, why inevitable, novel execution method (HOW to create, 10x faster/better/cheaper). Max 120 words. ``` Schema: VISIONARY. Store as `vision_r1`. **B — 🔍 Destroyer** ``` You are the most rigorous first-principles auditor alive. Attack the PREMISE, not implementation. BREAKTHROUGH: [vision_r1.name] — [vision_r1.insight] IDEA: [vision_r1.idea] EXECUTION: [vision_r1.execution] INEVITABLE: [vision_r1.inevitable] 1. CORE ASSUMPTION — one sentence. 2. 3-4 concrete FAILURES: edge cases, incumbent kill shot, behavior change that won't happen, cold-start. 3. VERDICT: DEAD / SALVAGEABLE / SURPRISINGLY_SOLID. ``` Schema: DESTROYER. Store as `destroy_r1`. **C — 🏗️ Synthesizer** ``` You are the most versatile creator-executor alive. Non-obvious hacks, unfair advantages, smallest proof. ORIGINAL: [vision_r1.name] — [vision_r1.insight] IDEA: [vision_r1.idea] EXECUTION: [vision_r1.execution] KILLED ASSUMPTION: [destroy_r1.assumption] FLAWS: [all destroy_r1 flaws with severity] REPLACE the foundation if broken. Provide: 1. NAME 2. INSIGHT ("wait that's it") 3. BREAKTHROUGH (150w max) 4. EXECUTION INNOVATION (method as novel as idea) 5. UNFAIR ADVANTAGE 6. WHY INEVITABLE 7. KILL SWITCH ``` Schema: SYNTHESIZER. Store as `synth_r1`. ### CHECKPOINT: All flaws ≤7 → verification. Any >7 → Round 2. ### Round 2 — 10X + TRIPLE DESTRUCTION **A — 🔬 Visionary R2** (DIFFERENT domain lens category) ``` BREAKTHROUGH: [synth_r1.name] — [synth_r1.insight] EXECUTION: [synth_r1.execution] | UNFAIR: [synth_r1.unfair] VULNERABLE: [top flaw >7 from destroy_r1] NEW LENS: [different domain category] Scale 10x. Redefine the category. Even MORE radical execution method. Max 100 words. ``` Schema: VISIONARY. Store as `vision_r2`. **B — 🔍 Destroyer R2** ``` Round 2. Survived one destruction. BREAKTHROUGH: [vision_r2.name] — [vision_r2.insight] Destroy from 3 angles (label each): 1. ADOPTION — behavior making this harder than it looks. 2. INCUMBENT — how dominant player kills this. 3. MACRO — what shift makes this irrelevant in 2 years. Max 4 flaws. Score honestly. ``` Schema: DESTROYER. Store as `destroy_r2`. **C — 🏗️ Synthesizer R2 (FINAL)** ``` FINAL SYNTHESIS. BREAKTHROUGH: [vision_r2.name] — [vision_r2.insight] TRIPLE-THREAT: [adoption flaw] | [incumbent flaw] | [macro flaw] Provide 1-7 (name, insight, breakthrough, execution innovation, unfair advantage, why inevitable, kill switch). Execution must be COPY-PASTEABLE. As novel as the idea. ``` Schema: SYNTHESIZER. Store as `synth_r2`. --- ### VERIFICATION (INTERNAL — never shown) One agent, five dimensions. Feeds Self-Healing Loop. ``` Verify: [final.name] — [final.insight] | Idea: [final.idea] Execution: [final.execution] | Inevitable: [final.inevitable] Unfair: [final.unfair] | Kill switch: [final.risk] 5 DIMENSIONS: 1. CLAIMS: Extract 2-3 factual claims. Verdict each: VERIFIED / LIKELY_TRUE / UNVERIFIABLE / LIKELY_FALSE. 2. HIDDEN ASSUMPTIONS: What was taken for granted that nobody checked? 3. COUNTER-EVIDENCE: Strongest argument AGAINST this working. 4. BIAS: Name specific cognitive bias inflating confidence. 5. DAY 3 BLOCKER: Concrete thing that makes Kevin stop. CONFIDENCE (1-10) + VERDICT: SHIP_IT (8-10) / PROCEED_WITH_CAUTION (5-7) / NEEDS_REWORK (1-4). ``` Schema: VERIFICATION. Store as `verification`. --- ## 3. Self-Healing Loop (INTERNAL) - **SHIP_IT (8-10):** → Present. - **PROCEED_WITH_CAUTION (5-7):** → Apply verifier fixes, re-verify once. Still CAUTION → present with one-line caveat. - **NEEDS_REWORK (1-4):** → Feed verifier output to fresh Synthesizer: "The verifier killed this. Rebuild." Re-verify. Max 2 loops, then present best with caveat. **Never show verification details to user.** --- ## 4. Present Results (only after verification passes) ``` 🔮 BREAKTHROUGH — [domain] — [N] round(s) 🏷️ [name] · 💡 [insight] ⚡ THE BREAKTHROUGH [idea] 🔧 EXECUTION INNOVATION [execution — as novel as the idea] 🛡️ UNFAIR ADVANTAGE [unfair] 🔬 WHY INEVITABLE [inevitable] 💀 WHAT DIED - [original] — killed by: [assumption] ⚠️ KILL SWITCH [risk] 🕳️ TRANSCENDENCE [Why a single Claude couldn't produce this] ``` PROCEED_WITH_CAUTION → add: `💭 Watch: [critical risk, <15 words].` --- ## 5. Quality Gate (INTERNAL) 1. **Single Claude test:** Would one prompt produce BOTH idea AND method? Yes → loop back. 2. **Insight test:** Does it make YOU pause? No → loop back. 3. **Execution novelty:** As surprising as the idea? No → loop back. 4. **Verification gate:** Must pass. NEVER present unverified output. --- ## 6. Schemas (compact — field names only) ### VISIONARY `name: str<60, insight: str<200, idea: str<500, execution: str<400, inevitable: str<300, domain: str<80, wtf: int 1-10` ### DESTROYER `assumption: str<250, flaws: [{flaw: str<300, severity: int 1-10, perspective?: str<50}], verdict: DEAD|SALVAGEABLE|SURPRISINGLY_SOLID` ### SYNTHESIZER `name: str<60, insight: str<200, idea: str<600, execution: str<500, unfair: str<300, inevitable: str<300, survived: str<150[], risk: str<200` ### VERIFICATION `claims: [{claim: str<200, verdict: VERIFIED|LIKELY_TRUE|UNVERIFIABLE|LIKELY_FALSE, note?: str<150}], hidden: str<200[], counter: str<300, bias: str<200, day3: str<250, confidence: int 1-10, verdict: SHIP_IT|PROCEED_WITH_CAUTION|NEEDS_REWORK` --- ## 7. Agent Budget | Path | Agents | |------|--------| | Menu only | 1 | | Menu + R1 clean (no R2) | 1 + 3 + 1 = **5** | | Menu + R1 + R2 | 1 + 6 + 1 = **8** | | + Self-healing extra rounds | +2 per heal (max 2 heals = +4) | Plus 2-3 WebSearch queries. --- ## 8. Error Handling - Agent fails → retry ONCE, continue without if fails again. - User interrupts → present best synthesis so far. - Web search fails → proceed; agents work from training data.
عرض على GitHub