What problem does it solve? Building a complete web frontend involves many disconnected decisions — stack choice, design tokens, accessible components, data layer, and testing — that are easy to do inconsistently or out of order. This Skill orchestrates the entire frontend web workflow against an existing backend REST contract, enforcing deterministic gates at each stage so nothing ships unvalidated. ## Core Features & Use Cases - Deterministic pipeline: Runs discovery, mockup-first design, stack decision (ADR), design tokens, accessible components, typed data layer, and real Playwright + axe tests in a fixed order with pass/fail gates. - Boundary-aware routing: Recognizes when a request belongs elsewhere — full-system builds go to spec-projeto-completo, backend features to spec-springboot-crud-feature, and isolated steps to web-component or design-tokens-gen. - Quality enforcement: Iterates with a review committee until a score of at least 9, then closes with a readiness audit and an evidence-based final report. - Use Case: Given a Spring Boot REST API for an enrollment dashboard, use this Skill to drive the frontend from requirements through approved mockups, Tailwind v4 tokens, accessible components, a Zod-validated data layer, and Playwright + axe test reports. ## Quick Start Use spec-frontend-web to build the complete web frontend for this feature, consuming the existing backend REST API, from requirements to tested screens.
