What problem does it solve? Verifying a visual change requires loading the real site, but starting a duplicate dev server or killing a teammate's session breaks shared work. This Skill defines the rules for finding, reusing, and safely driving the local Astro dev server before any preview, screenshot, or DevTools session. ## Core Features & Use Cases - Server discovery and reuse: Check for a running server with npx astro dev status or a curl probe on port 4321, and reuse it instead of starting a new one. - Safe startup and cleanup: Start your own server on a free port only when none is running, and stop only the processes you started. - Browser selection and boot verification: Use Chrome by default, Firefox for engine-specific issues, and confirm the client actually booted (document.readyState, customElements.get('lenis-scroll')) before trusting a screenshot. - Auth-aware previewing: Localhost bypasses Basic Auth in dev, and protected deployments require an Authorization header via a forwarding proxy rather than URL credentials or the Sanity draft cookie. - Use Case: Before taking a screenshot to confirm a layout fix, you check port 4321, find a teammate's server running, drive it with the Chrome MCP, and verify the page's custom elements upgraded before capturing. ## Quick Start Check whether the Astro dev server is already running on port 4321 and open the page in Chrome to verify my visual change.
