What problem does it solve? New code written for the Toollab project often clashes with the existing codebase style, producing inconsistent naming, unwanted comments, wrong formatting, and English-only validation messages. This Skill ensures any code you write blends into the existing Laravel and Nuxt codebase. ## Core Features & Use Cases - Comment policy enforcement: Near-zero comments allowed, except one-liners explaining non-derivable constraints, with existing "why" comments preserved. - Mixed FR/EN naming rules: Follows the domain's language (French for PaiementService methods, English for ClassroomController) instead of forced harmonization. - Structural conventions: Defines controller/service layering, model property ordering, Vue script-setup organization, file placement, dead-code removal rules, and Pint formatting scoped to touched files only. - Use Case: Before adding a new endpoint to PaiementController, invoke this Skill so the validation messages are in French, the response uses the {status, message, data} format, and no JsonResource is introduced. ## Quick Start Apply the Toollab coding conventions while writing the new PHP controller and Vue page for the payment feature.
