What problem does it solve? Maintaining the Academic Events web app requires coordinating Express SSR templates, webpack bundles, class-based UI components, and API envelope handling across four page entries, which is error-prone without a codified map of the architecture and its conventions. ## Core Features & Use Cases - Architecture Guidance: Documents the Express + Mustache SSR routes, webpack entries, client modules, and API integration precedence so changes land in the right files. - Implementation and Review Rules: Enforces DOM data hygiene, component consolidation, CSS split conventions, and Portuguese-facing text consistency when editing home, login, week, or dashboard pages. - Validation Workflow: Pairs Node test suites under web/tests with a browser smoke checklist so interaction changes are verified in a real browser, not just jsdom. - Use Case: When adding a new event filter to the home page, follow the documented steps to update the template, query-state helpers, and API support, then run npm test and verify the filter interaction in a browser session. ## Quick Start Ask the agent to add a category filter to the home page of the Academic Events web app and validate it with the existing test suite and a browser check.