What problem does it solve? Generating a DIVA business entity requires dozens of consistent names (files, instances, variables, constants) derived from a domain, entity, and SQL table. Computing them by hand is error-prone and can cause compiler collisions between RecordSql and Record identifiers. This Skill deterministically computes the full token set and validates its coherence before any code generation. ## Core Features & Use Cases - Token computation: From the triplet (domain, entity, SQL table), produces a JSON set of naming tokens covering files (.dhsq, .dhsp, .dhsf), instances (RS_, ChkData), defines, and module names. - Coherence validation: A validator checks PascalCase rules, DB prefix consistency, empty fields, and the RecordSql/Record non-collision rule (V01-V09), returning a structured error/warning report. - Collision handling: Detects case-insensitive collisions between NomVue and the SQL table and supports a --nom-vue override to resolve them. - Use Case: Before generating a Retail entity FamRglt backed by table RtlFamRglt, run the compute script to obtain tokens like fichier_rsql=rtlrsfamrglt.dhsq and RS_instance=RS_FamRgltRtl, then pipe the output into the validator to confirm zero errors. ## Quick Start Ask the AI to compute the naming tokens for a DIVA entity by providing the domain, entity name, RecordSQL name, key field, and description, then validate the resulting token set.
