What problem does it solve? It provides a reusable, stack-agnostic role core for frontend development work, enforcing a consistent pipeline (analysis, tests, implementation, review, testing, documentation) so frontend tasks follow the same quality contract across projects without duplicating role definitions. ## Core Features & Use Cases - Fixed development pipeline: analysis with codebase grep, mandatory tests, implementation, /reviewer loop (up to 5 iterations), /testing, /techwriter, and a structured final report. - Clear responsibility boundaries: defines what a frontend agent may change (UI, pages, forms, API clients, frontend docs) and what it must never touch (backend code, database, migrations, deployment). - Stack-agnostic principles: server as source of truth, no business calculations on the client, fallback values for API fields, dictionary-based labels, accessibility, and mandatory tests for every new component, hook, or page. - Use Case: A project wrapper skill references this core so that any frontend task (e.g., adding a new settings page) automatically follows the same review, testing, and reporting workflow regardless of framework. ## Quick Start Reference this core from a project wrapper skill and ask the agent to implement a frontend task such as adding a new form page with tests.
