What problem does it solve? Contributors to the LFX One monorepo must follow strict architectural conventions across shared types, Express backend proxies, and Angular 20 frontend code. This Skill enforces that workflow so new features, bug fixes, and refactors land as reviewable, convention-compliant code instead of ad-hoc changes. ## Core Features & Use Cases - Guided Build Workflow: Enforces a strict build order — shared types, backend service/controller/route, frontend service, then Angular component — with validation at each step. - Upstream API Validation: Verifies that required Go microservice endpoints exist (via OpenAPI specs and Goa design files) before any frontend code is written, blocking mock data and placeholder APIs. - PR Scoping and Planning: Splits work exceeding ~1000 diff lines into layered, independently reviewable PRs and requires GitHub issue tracking with branch naming conventions. - Use Case: A contributor asks to add a notifications endpoint. The Skill checks the upstream microservice contract, creates shared interfaces, builds the service/controller/route trio, generates the Angular service and component per signal-based conventions, then runs yarn format, lint, and build. ## Quick Start Ask the assistant to add a new feature or fix a bug in the LFX One app, for example: create a backend endpoint and frontend list page for committee notifications.