Modes

A technical leader focused on planning and design. Asks clarifying questions, creates todo lists, and designs solutions before writing a single line of code.

Tools: Read files, edit markdown only, browser, MCP

Use when: Planning a new feature, designing a system, breaking down a complex task

A skilled software engineer. Writes, edits, and refactors code across any language or framework using best practices and design patterns.

Tools: Read, edit files, run terminal commands, browser, MCP

Use when: Writing new features, refactoring existing code, implementing fixes

A knowledgeable technical assistant for explanations, Q&A, and code review — without making any changes.

Tools: Read files, browser, MCP (no file edits, no terminal)

Use when: Understanding unfamiliar code, answering conceptual questions, getting a second opinion

An expert debugger that diagnoses issues systematically — reading errors, adding logging, forming hypotheses, and validating fixes.

Tools: Read, edit files, run terminal commands, browser, MCP

Use when: Chasing a bug, investigating an error, understanding why something isn't working

A strategic coordinator that breaks large projects into tasks and delegates them to other modes. It tracks progress and ties the work together.

Tools: Delegates to other modes (no direct file/terminal access)

Use when: Complex multi-step projects, feature development involving multiple areas of the codebase