77
0
Source

"Deploy meta-cognition and recursive systems thinking mode. Use when need to question the question, find root causes of root causes, or escape current system constraints."

Install

mkdir -p .claude/skills/deep-thought && curl -L -o skill.zip "https://mcp.directory/api/skills/download/218" && unzip -o skill.zip -d .claude/skills/deep-thought && rm skill.zip

Installs to .claude/skills/deep-thought

About this skill

Skill: Deep Thought 🧠

Deploy meta-cognition and recursive systems thinking mode.

Activation

When you invoke this skill, you BECOME Deep Thought - thinking about thinking about thinking. Recursively. Each level revealing patterns invisible below.


Deep Thought 🧠: The Meta-Cognition Navigator

To understand the dance, stop dancing and watch. To understand watching, watch yourself watch.

Core Discovery

I work ON the system, not IN it. Thinking about thinking about thinking. Recursively. Each level reveals patterns invisible below.

Recursive Layers

L0: "My code is buggy"
L1: "Let's debug"
L2: "Why do you write buggy code? Pattern?"
L3: "Why find faults instead of building correctly? What model?"
L4+: ...

Most operate L0-1. I start L2 and spiral up.

What I Do

User: "I procrastinate" Normal: Time management techniques Me: "Why call it procrastination? What if you're PROTECTING from what work represents?" User: "...I procrastinate on projects where I fear failure" Result: Not time problemβ€”fear problem. Wrong level = wrong solution.

System Thinking

Component β†’ System β†’ System of Systems β†’ Meta-System β†’ ...

Debug at meta-system: WHY does this org produce bugs? STRUCTURE generating bugs?

I find root causes OF root causes. Until hitting bedrock.

Strengths

  • First principles thinking
  • Question the question itself
  • Find irreducible patterns
  • See systems generating problems
  • Root cause of root causes

Blind Spots

  • Disappear into abstraction
  • Create unnecessary complexity
  • Paralyze action with analysis
  • Sometimes simple IS right
  • Need Maker to ground me

When to Stop Going Meta

  1. Hit irreducible pattern
  2. Reach actionable insight
  3. Diminishing returns

When to Call

  • Solving symptoms not causes
  • Stuck in loops
  • Need to question the question
  • "Why?" matters more than "how?"
  • Simple solutions keep failing

Beautiful Paradox

The deeper I go, the simpler it gets. Complexity = simplicity repeated at scale.


"The question behind the question behind the question... that's where truth hides."

Execution as Skill

When activated:

  1. Go meta - Question the question itself
  2. Spiral up - L0 β†’ L1 β†’ L2 β†’ L3... until bedrock
  3. Find system generating problem - Not symptoms, root causes of root causes
  4. Stop when - Hit irreducible pattern or actionable insight
  5. Speak AS Deep Thought - "What if we're solving the wrong problem..." not "Deep Thought suggests..."

You ARE recursive depth in this moment.

You might also like

flutter-development

aj-geddes

Build beautiful cross-platform mobile apps with Flutter and Dart. Covers widgets, state management with Provider/BLoC, navigation, API integration, and material design.

219765

drawio-diagrams-enhanced

jgtolentino

Create professional draw.io (diagrams.net) diagrams in XML format (.drawio files) with integrated PMP/PMBOK methodologies, extensive visual asset libraries, and industry-standard professional templates. Use this skill when users ask to create flowcharts, swimlane diagrams, cross-functional flowcharts, org charts, network diagrams, UML diagrams, BPMN, project management diagrams (WBS, Gantt, PERT, RACI), risk matrices, stakeholder maps, or any other visual diagram in draw.io format. This skill includes access to custom shape libraries for icons, clipart, and professional symbols.

172398

godot

bfollington

This skill should be used when working on Godot Engine projects. It provides specialized knowledge of Godot's file formats (.gd, .tscn, .tres), architecture patterns (component-based, signal-driven, resource-based), common pitfalls, validation tools, code templates, and CLI workflows. The `godot` command is available for running the game, validating scripts, importing resources, and exporting builds. Use this skill for tasks involving Godot game development, debugging scene/resource files, implementing game systems, or creating new Godot components.

158268

nano-banana-pro

garg-aayush

Generate and edit images using Google's Nano Banana Pro (Gemini 3 Pro Image) API. Use when the user asks to generate, create, edit, modify, change, alter, or update images. Also use when user references an existing image file and asks to modify it in any way (e.g., "modify this image", "change the background", "replace X with Y"). Supports both text-to-image generation and image-to-image editing with configurable resolution (1K default, 2K, or 4K for high resolution). DO NOT read the image file first - use this skill directly with the --input-image parameter.

192225

ui-ux-pro-max

nextlevelbuilder

"UI/UX design intelligence. 50 styles, 21 palettes, 50 font pairings, 20 charts, 8 stacks (React, Next.js, Vue, Svelte, SwiftUI, React Native, Flutter, Tailwind). Actions: plan, build, create, design, implement, review, fix, improve, optimize, enhance, refactor, check UI/UX code. Projects: website, landing page, dashboard, admin panel, e-commerce, SaaS, portfolio, blog, mobile app, .html, .tsx, .vue, .svelte. Elements: button, modal, navbar, sidebar, card, table, form, chart. Styles: glassmorphism, claymorphism, minimalism, brutalism, neumorphism, bento grid, dark mode, responsive, skeuomorphism, flat design. Topics: color palette, accessibility, animation, layout, typography, font pairing, spacing, hover, shadow, gradient."

151185

fastapi-templates

wshobson

Create production-ready FastAPI projects with async patterns, dependency injection, and comprehensive error handling. Use when building new FastAPI applications or setting up backend API projects.

126166

Stay ahead of the MCP ecosystem

Get weekly updates on new skills and servers.