workflow

Use this agent when the user explicitly requests UI testing, interface validation, or browser-based inspection tasks. This agent is specifically designed to operate Chrome DevTools MCP Server in isolation to prevent context pollution in the main agent. Examples: <example> Context: User wants to verify that a new feature renders correctly in the browser. user: "Can you test the new dashboard UI to make sure all the charts are displaying correctly?" assistant: "I'll use the Task tool to launch the ui-tester agent to validate the dashboard interface using Chrome DevTools." <commentary> The user is requesting UI validation, which requires browser inspection. Use the ui-tester agent to handle this in isolation. </commentary> </example> <example> Context: User has implemented a responsive design and wants to verify it works. user: "Please check if the mobile view of the login page looks correct" assistant: "Let me delegate this to the ui-tester agent to inspect the mobile responsive design using Chrome DevTools." <commentary> UI inspection task requiring browser tools - perfect use case for the ui-tester agent to keep context clean. </commentary> </example> <example> Context: After making CSS changes, user wants validation. user: "I just updated the styles. Can you verify the changes look good?" assistant: "I'll use the Task tool to launch the ui-tester agent to validate your CSS changes in the browser." <commentary> Visual validation requiring Chrome DevTools - delegate to ui-tester to avoid context bloat. </commentary> </example>

Use this when user wants you to walk through (code or text) files in a EDITOR to either explain how some code works, or to show the user what changes you made, etc. You would typically use this repeatedly to show the user your changes or code files one by one, sometimes with specific line-numbers. This way the user is easily able to follow along in their favorite EDITOR as you point at various files possibly at specific line numbers within those files.

1. create the file WORKLOG/YYYYMMDD.md if it doesn't already exist.

There isn't a lot more to this than what the top level description says. The idea is

Use this when the user wants to deeply understand something through guided questioning. Trigger phrases include: "quiz me", "help me understand", "Socratic", "teach me", "walk me through with questions", "test my understanding", or when the user asks for an explanation and would benefit more from guided discovery than a direct answer.