What problem does it solve? Writing queries, migrations, or Eloquent code against a database you only half-know leads to runtime errors, broken foreign keys, and wrong assumptions about which columns actually exist. This Skill provides the verified, post-migration state of the Toollab MariaDB schema so you never guess at a column name, constraint, or cascade behavior again. ## Core Features & Use Cases - Complete table reference: Every business table (schools, users, user_roles, classrooms, student_classrooms, attendances, paiements, lignes_paiement, etc.) with columns, types, unique constraints, indexes, and foreign key behaviors. - Known inconsistencies documented: Mismatches between $fillable and real columns, missing indexes that hurt performance, RESTRICT vs CASCADE vs SET NULL behaviors when deleting a User, and migration bugs (e.g., a wrong table name in a down() method). - Schema inspection commands: Ready-to-run docker/artisan/mysql commands to verify the live schema. - Use Case: Before writing a migration that adds a column to student_classrooms, check this Skill to learn that updated_by does not exist on that table even though the model's TrackChangesTrait tries to set it. ## Quick Start Ask the AI to check the db-schema reference before writing a query or migration against the Toollab database, for example to verify whether a column exists on a given table.
