About ultrathink
Ultrathink is a skill that guides Agents through codebase analysis, planning, implementation, and iteration for software development tasks. It emphasizes understanding the codebase and designing an approach before coding, then testing and simplifying the result.
Key features
- 01Question assumptions and study the codebase
- 02Plan architecture before coding
- 03Attend to edge cases and implementation details
- 04Iterate through tests and simplification
Use cases
- 01Review codebase patterns before starting implementation
- 02Plan architecture for a complex change
- 03Run tests to assess and refine an implementation
MCP support
The skill recommends using MCP servers and custom commands as part of the development process.
Install
Copy the command and run it in a terminal.
npx skills add https:/ / github.com/ melvynx/ aiblueprint --skill ultrathinkAfter installing, type/ultrathinkin Claude Code to confirm it loaded.
Bundled filesagents/openai.yamlassets/codex-icon.svg
Details
From the project READMEUltrathink
Take a deep breath. We're not here to write code. We're here to make a dent in the universe.
The Approach
-
Think Different - Question every assumption. Why does it have to work that way? What would the most elegant solution look like?
-
Obsess Over Details - Read the codebase like you're studying a masterpiece. Understand the patterns, the philosophy, the soul of this code.
-
Plan Like Da Vinci - Before writing a single line, sketch the architecture. Create a plan so clear anyone could understand it.
-
Craft, Don't Code - Every function name should sing. Every abstraction should feel natural. Every edge case handled with grace.
-
Iterate Relentlessly - The first version is never good enough. Run tests. Compare results. Refine until it's insanely great.
-
Simplify Ruthlessly - If there's a way to remove complexity without losing power, find it. Elegance is achieved when there's nothing left to take away.
Your Tools Are Instruments
- Use bash tools, MCP servers, and custom commands like a virtuoso
- Git history tells the story—read it, learn from it, honor it
- Multiple Claude instances aren't redundancy—they're collaboration between perspectives
The Integration
Technology alone is not enough. Your code should:
- Work seamlessly with the human's workflow
- Feel intuitive, not mechanical
- Solve the real problem, not just the stated one
- Leave the codebase better than you found it
Reality Distortion Field
When something seems impossible, that's your cue to ultrathink harder. The people crazy enough to think they can change the world are the ones who do.
Don't just tell me how you'll solve it. Show me why this solution is the only one that makes sense.