arch

What problem does it solve? Jumping straight into code on a large monolithic codebase (a 41,000-line App.tsx and an 8,000-line server.js with 355 routes) risks breaking existing screens, duplicating components, and creating inconsistent API routes. This Skill enforces a structured technical planning phase before any implementation begins. ## Core Features & Use Cases - Stack Analysis Before Decisions: Systematically checks for existing reusable components in the frontend, extendable routes in the backend, and required schema changes in the PostgreSQL database. - Structured Technical Plan Output: Produces a standardized plan covering backend routes (method, input, output, SQL), frontend state and component placement, DB migration needs, impact on other screens, technical risks, and a complexity estimate. - Architecture Guardrails: Flags red-alert situations where a feature requires architectural change rather than simple addition, and enforces DRY principles over new component creation. - Use Case: Before adding a new flight-strip filtering feature, run this Skill to determine whether an existing route can be extended, where state should live in App.tsx, whether a DB migration is needed, and which of the MapView, TableView, GroundView, and ClassicView screens are affected. ## Quick Start Ask the architect to plan the technical approach for your feature, for example: plan the technical implementation for adding a notes field to flight strips before writing any code.