Agent skill
ultrathink-trigger
Auto-escalate reasoning depth for complex problems. Use proactively when encountering architecture, debugging, or unfamiliar code.
Install this agent skill to your Project
npx add-skill https://github.com/aiskillstore/marketplace/tree/main/skills/dmjgilbert/ultrathink-trigger
SKILL.md
Ultrathink Trigger
Automatically invoke maximum reasoning depth for complex problems.
Complexity Indicators
| Signal | Weight | Example |
|---|---|---|
| Files affected > 5 | +2 | Refactoring across modules |
| Unfamiliar language/framework | +3 | First time with codebase |
| Architecture decision | +4 | Choosing patterns |
| 2+ failed fix attempts | +3 | Root cause unclear |
| Multi-domain interaction | +2 | Frontend + Backend + DB |
| Security implications | +3 | Auth, permissions, secrets |
| Performance-critical code | +2 | Hot paths, algorithms |
| Breaking change potential | +3 | API changes, schema migrations |
Threshold
If total weight >= 5: Trigger ultrathink mode
Invocation
Prefix complex analysis with one of:
- "Think harder about this:"
- "ultrathink:"
- "Take your time to deeply analyze:"
These phrases trigger Claude's extended thinking mode for more thorough analysis.
Integration Points
With /fix command
After 2 failed attempts, automatically invoke:
ultrathink: What are all the possible root causes?
What assumptions am I making? What haven't I checked yet?
With /brainstorm command
Auto-triggers when topic complexity >= 5 (or --deep flag). Applied to EVALUATE and SYNTHESIZE phases:
ultrathink: Deeply analyze these options considering trade-offs,
edge cases, maintainability, and long-term implications.
Flags:
--deep- Force ultrathink regardless of complexity--quick- Suppress auto-detect, stay fast
With orchestrator INNOVATE phase
For architecture decisions:
ultrathink: Evaluate these approaches considering
maintainability, performance, security, and complexity.
With sequential-thinking
For multi-step complex analysis:
mcp__sequential_thinking__sequentialthinking({
thought: "ultrathink: [complex problem]",
thoughtNumber: 1,
totalThoughts: 10, // More steps for deep analysis
nextThoughtNeeded: true
})
When to Use Proactively
- Architecture Decisions: Before proposing patterns or structure
- Debugging Deadlock: After 2+ failed fix attempts
- Security Analysis: Any auth, permission, or secret handling
- Performance Optimization: Before optimizing hot paths
- Breaking Changes: Before proposing API/schema changes
- Unfamiliar Code: First encounter with a new codebase area
Example Workflow
1. Encounter complex problem
2. Calculate complexity weight:
- Multi-file change: +2
- Architecture decision: +4
- Total: 6 (>= 5, triggers ultrathink)
3. Invoke: "ultrathink: Design the data flow for..."
4. Extended analysis produces thorough solution
5. Proceed with implementation
Anti-Patterns
- Using ultrathink for simple, well-understood tasks
- Skipping ultrathink for complex problems to "save time"
- Not recalculating complexity when scope changes
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
perigon-backend
Perigon ASP.NET Core + EF Core + Aspire conventions
perigon-agent
Pointers for Copilot/agents to apply Perigon conventions
perigon-angular
Angular 21+ standalone/Material/signal conventions for Perigon WebApp
fastapi-mastery
Comprehensive FastAPI development skill covering REST API creation, routing, request/response handling, validation, authentication, database integration, middleware, and deployment. Use when working with FastAPI projects, building APIs, implementing CRUD operations, setting up authentication/authorization, integrating databases (SQL/NoSQL), adding middleware, handling WebSockets, or deploying FastAPI applications. Triggered by requests involving .py files with FastAPI code, API endpoint creation, Pydantic models, or FastAPI-specific features.
context7-efficient
Token-efficient library documentation fetcher using Context7 MCP with 86.8% token savings through intelligent shell pipeline filtering. Fetches code examples, API references, and best practices for JavaScript, Python, Go, Rust, and other libraries. Use when users ask about library documentation, need code examples, want API usage patterns, are learning a new framework, need syntax reference, or troubleshooting with library-specific information. Triggers include questions like "Show me React hooks", "How do I use Prisma", "What's the Next.js routing syntax", or any request for library/framework documentation.
browser-use
Browser automation using Playwright MCP. Navigate websites, fill forms, click elements, take screenshots, and extract data. Use when tasks require web browsing, form submission, web scraping, UI testing, or any browser interaction.
Didn't find tool you were looking for?