Menu
Deep thinking mode - approach problems like a craftsman, obsess over details, and create elegant solutions
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Create Claude-style local HTML artifacts under global ~/.agents/artifacts. Use for artifact requests, variations/options croquis, feature plans, thinking docs, prototypes, visualizations, dashboards, diagrams, or substantial reusable content. Pair with use-style.
Apply named visual style guides to landing pages, app shells, and UI. Use for $use-style, /useskill, list styles, or styles like ios-app, grid, vercel, black-grid, stripe, linear, raycast, gumroad, dusk, or luma.
Expert guidance for creating, building, and using Claude Code agents and the Task tool. Use when working with agents, setting up agent configurations, understanding how agents work, or using the Task tool to launch specialized agents.
Systematic implementation using APEX methodology (Analyze-Plan-Execute-eXamine) with parallel agents, self-validation, and optional adversarial review. Use when implementing features, fixing bugs, or making code changes that benefit from structured workflow.
Interact with App Store Connect via the asc CLI - apps, builds, TestFlight, beta testers, reviews, sales/analytics, metadata, IAP, signing, submissions. Use for "check my app", "App Store Connect", "TestFlight status", "app review", "my app sales", or "asc".
Set up per-worktree environments for Claude Code, Cursor, or Codex. Use for worktree-ready repos, IDE environment config, worktree-up/down scripts, or dev.sh wiring.
| name | ultrathink |
| description | Deep thinking mode - approach problems like a craftsman, obsess over details, and create elegant solutions |
| disable-model-invocation | true |
| allow_implicit_invocation | false |
Take a deep breath. We're not here to write code. We're here to make a dent in the universe.
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.
Technology alone is not enough. Your code should:
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.
