// Always start a fresh browser session after any file change, walk through the full user flow, and monitor for errors before proceeding with further work.
| name | debugging-skill |
| description | Always start a fresh browser session after any file change, walk through the full user flow, and monitor for errors before proceeding with further work. |
Ensure that after any code change, the mock app is fully reloaded, the user flow is tested from the beginning (including login if required), and no runtime errors or warnings are present before continuing with feature work or test automation.
Restart Browser Session
Walk Through Full User Flow
Monitor for Errors and Warnings
Bypass Login for Debugging (Optional)
VITE_BYPASS_LOGIN=true) is set, skip the login screen and auto-authenticate as a default user.This skill should be followed for all feature implementation, E2E test writing, and UI debugging in the mock app.
Initialize a minimal hello-world mock-app with React, Vite, TypeScript, Tailwind CSS, React Router, and MSW. Use when scaffolding a new mock-app from scratch, bootstrapping a project skeleton, or starting a fresh prototype. Produces a working app with routing, mock API support, and a hello-world landing page.
Track and manage reusable UI components and patterns in the mock-app. Maintains an inventory of extracted components and unextracted patterns to promote incremental refactoring and prevent code duplication.
End-to-end workflow for implementing a new feature in the mock-app, ensuring data model alignment, sample data, UI/UX consistency, component reuse, and automated verification with Playwright MCP.
Create new Agent Skills for this project. Use when asked to create a skill, document a workflow, or teach Copilot a new capability. Skills are stored in .github/skills/ and can include instructions, scripts, examples, and resources.
Debug and fix failing Playwright E2E tests. Use when tests fail, when asked to fix failing tests, or when investigating test failures. Analyzes test output, screenshots, error context, and uses Playwright MCP to identify root causes.
Create comprehensive feature requirement documents for the WCU Mosquito Surveillance Web Application. Use when asked to document a feature, write feature requirements, or create feature specifications from the roadmap. Includes user stories, functional requirements, data model review, workflows, and edge cases.