What problem does it solve? Developers modifying family, guardian, or student features in Toollab risk breaking subtle business rules: the polymorphic User/UserRole identity model, the callerCanAccessFamily access gate, enrollment replace semantics, and irreversible deletion behaviors. This Skill consolidates those rules so changes stay consistent with the existing codebase. ## Core Features & Use Cases - Identity model reference: Explains that students are Users with a polymorphic UserRole on a Family, contact data lives in key-value user_infos, and one person can be both guardian and student (requiring deduplication). - Endpoint and gate documentation: Covers FamilyController routes, the reusable callerCanAccessFamily gate, enrollment via StudentClassroomController with the replace pattern, and family deletion with 409 blockers and year-scoped trash. - UI screen specifications: Details the family list, family detail page, and class selection page including gender-based class filtering, capacity gauges, and known bugs to avoid. - Use Case: When asked to add a field to the student edit form, consult this Skill to learn that student data lives in user_infos key-value pairs, that first_name is nullable, and that deleting a student is irreversible. ## Quick Start Ask the AI to modify a family or student feature in Toollab, such as adding a guardian to a family, and it will apply the identity model, gate, and endpoint rules from this Skill.
