What problem does it solve? Coding agents often need to interact with a locally running Angular demo app—filling forms, clicking controls, navigating routes, or reading the current UI state—without launching a separate browser automation stack. This Skill lets the agent operate the tab the developer already has open via the page tool on the @craft-ts/function-registry-mcp server, avoiding Playwright or Chrome DevTools entirely. ## Core Features & Use Cases - Live tab interaction: Fill inputs, click controls, and navigate routes in the already-open ng serve tab using data-craft-name ids, with single round-trip act batches. - State inspection: Read the current page surface at controls detail by default, or dom-styles detail when debugging visual and CSS layout bugs. - Reload and multi-tab handling: Waits through ng serve reloads (reloading → ready), disambiguates multiple ready tabs via registry.clients, and recovers from disconnected client errors. - Use Case: While fixing a login form bug, ask the agent to goto /login-form, fill the email and password fields, click submit, and report the resulting page state—all in the tab you are already watching. ## Quick Start Ask the agent to use the page MCP tool to navigate to the login-form route in the open tab, fill in the email and password fields, click submit, and report the new page state.
