What problem does it solve? Maintaining a consistent Express 5 JSON API requires enforcing a stable response envelope, correct HTTP status codes, bearer-token auth, and MySQL-backed model patterns across every route change, which is error-prone without codified guidance. ## Core Features & Use Cases - Route Implementation Guidance: Codified patterns for auth, users, and events route groups, including validation rules, status codes (201, 400, 401, 404, 409), and try/catch plus next(error) orchestration. - Response Contract Enforcement: Standard success and error envelopes via sendSuccess/sendCreated helpers and CustomError with centralized error middleware. - Domain Model Rules: User and Event model conventions such as bcrypt hashing, email normalization, UUID generation, category fallback, and moderation state handling. - Use Case: When adding a new endpoint like event moderation, follow the documented auth middleware, validation, and side-effect patterns (e-mail, Google Calendar) so the route stays resilient and covered by Jest unit tests. ## Quick Start Ask the agent to add a new authenticated endpoint to the events router following the api-development skill conventions.
