You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
Automates browser interactions for web testing, form filling, screenshots, and data extraction. Use when the user needs to navigate websites, interact with web pages, fill forms, take screenshots, or extract information from web pages.
Use when completing tasks, implementing major features, or before merging to verify work meets requirements. Structured code review process.
Comprehensive document creation, editing, and analysis with support for tracked changes, comments, formatting preservation, and text extraction. When Claude needs to work with professional documents (.docx files) for: (1) Creating new documents, (2) Modifying or editing content, (3) Working with tracked changes, (4) Adding comments, or any other document tasks
Use when you have a written implementation plan to execute. Load plan, review critically, execute tasks step by step with progress tracking.
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes. Systematic approach to root cause analysis.
Use when you have a spec or requirements for a multi-step task, before touching code. Write bite-sized implementation plans.