What problem does it solve? Changing domain models in an Express and MySQL codebase risks breaking API contracts, password security, and serialization logic. This Skill documents the exact structure, defaults, and safe-change rules for the User and Event models so edits stay consistent across the codebase. ## Core Features & Use Cases - Model Reference: Documents User fields (bcrypt password hashing, role normalization, lowercase email) and Event fields (defaults for category, location, and createdAt). - Filtering Semantics: Explains how listEvents applies date ranges, case-insensitive category matching, and multi-field search through the Mysql driver. - Safe Change Guidelines: Provides a checklist for adding fields across constructor, toJSON, serialize, normalize, schema, and route validation. - Use Case: When adding a new field like event capacity, follow the checklist to update the model, serialization, SQL schema, and API validation without breaking existing contracts. ## Quick Start Ask the assistant to add a new field to the Event model and update all affected serialization, schema, and validation surfaces.