What problem does it solve? Evolving the Toollab API database schema is risky: choosing the wrong Eloquent trait breaks multi-tenant scoping, a missing onDelete policy silently blocks deletions in MariaDB, and a NOT NULL column added without backfill corrupts existing data. This Skill encodes the project's exact conventions so every model or migration change is safe and consistent. ## Core Features & Use Cases - Trait decision tree: Determines when to apply BelongsToSchool, BelongsToSchoolYear, and TrackChangesTrait, with the matching columns each trait requires. - Migration conventions: Enforces anonymous-class migrations, explicit cascadeOnDelete/restrictOnDelete/nullOnDelete policies, defensive down() methods, and named composite unique indexes. - Safe NOT NULL rollout: Provides the three-step pattern (nullable column, raw SQL backfill, guard check before locking) plus known pitfalls like the polymorphic user_roles table and N+1 $appends accessors. - Use Case: You need to add a school_year_id column to an existing table with production data. The Skill walks you through the nullable-add, query-builder backfill, orphan guard, and verification commands before you deploy. ## Quick Start Ask the assistant to add a new Eloquent model or modify a migration column in the Toollab API following the project conventions.