What problem does it solve? Developers working on the Toollab codebase receive requests phrased in French education business vocabulary (cursus, émargement, exonération, reconduction) and must map each term to the correct model, table, endpoint, or screen before writing any code. ## Core Features & Use Cases - Business-to-code mapping tables: Translates terms for school structure, people and roles, enrollment, attendance, year-end decisions, and payments into concrete models like Cursus, ClassSchedule, StudentYearOutcome, and LignePaiement. - Screen-to-route dictionary: Maps user phrases like "la fiche famille" or "mon planning" to application routes such as /family/[id] and /professeur/planning. - Vocabulary traps: Documents pitfalls such as the registar slug spelling, the singular cursus table, and the rule to never display "Telegram" in the UI. - Use Case: A user asks to "ouvrir la saisie des décisions"; the Skill identifies this as toggling school_years.outcomes_open from the /decisions screen, restricted to the director role. ## Quick Start Ask the assistant to explain what the French business term used in your request corresponds to in the Toollab codebase before implementing the change.