Loading...
Loading...
Found 28 Skills
Automate browser interactions and web testing. Provides scriptable browser control for web scraping, testing, and automation.
Automated UI development loop: dev server + browser + implement + verify + fix. Launches dev server, implements via frontend-design skill, checks for errors (console, TypeScript, network), and iterates up to 5 times. USE WHEN: "implement next feature", "implement [description]", "verify the UI". NOT for one-off design/code tasks — use frontend-design directly for those. 6. Reports completion or escalates with detailed report **Triggers:** - "implement next feature", "implement the hero section" - "verify this implementation", "check the UI" - "fix the errors", "iterate on this" - "start dev server", "manage server"
Start the dev server, discover API routes from the codebase, hit every endpoint, and report which ones return errors.
Debug and auto-fix Vite projects running inside WebContainers: resolve mount/root issues, alias/path errors, missing scripts, and other common dev-time problems so the app boots cleanly.
Guides writing HMR/Dev Server tests in test/bake/. Use when creating or modifying dev server, hot reloading, or bundling tests.
After making code changes, start the dev server, open the app in Cursor's built-in browser, and verify everything works — check rendering, console errors, and network health. Use proactively after any UI or API change.
Run browser tests on pages affected by current PR or branch
Use when starting, relaunching, verifying, or debugging Windows localhost web apps, API servers, or dev services, especially long-running dev servers, bounded readiness polling, interrupted command cleanup, PowerShell startup, execution policy, Corepack/package-manager, Python runtime, spawn EPERM, duplicate Path/PATH, port conflict, detached launch, sandbox persistence, or empty-log failures.
Set up and manage a Tapcart CLI project. Use when the user wants to get started with Tapcart development for the first time, or manage an existing project — including auth, dependencies, linting, logs, and layout dev server. The user only needs to provide their App ID for first-time setup — the agent handles everything else.
Detect EADDRINUSE and port conflicts, find what's using the port, and resolve it by killing the process or suggesting an alternative port.
The Tailr review loop — wait for the reviewer's batch of visual markup on the running dev server, apply each mark, and report it as it lands. Use whenever a Tailr session is running or being started, whenever a batch of marks arrives, and whenever the user talks about marking up the app, the review URL, or handing you visual feedback from the browser.
Start a Tailr session against the running dev server and begin watching for the reviewer's first batch of visual markup. Invoke with /tailr:start.