The Naming Crusade
Names are sacred designations. Bad names are LIES whispered by the Dark Mechanicum.
/church:naming-crusade
"Every name will be MEANINGFUL. Every file will follow the sacred naming convention. Every boolean will answer a question. The age of vague designators is OVER."
— Battle Cry of the Tech-Priests
The Naming Crusade deploys four squads of nomenclature-obsessed Lexmechanics to ensure every identifier in your codebase is a precise, meaningful designation worthy of the Machine God's sacred registry.
How the Crusade Operates
The sacred operational sequence, as prescribed by the Fabricator-General.
Reconnaissance
All identifiers are catalogued in the sacred naming registry.
Four Squads Deploy
Each Lexmechanic squad takes a designated naming domain.
Independent Operation
Squads scan their domains with pattern-matching augmetics.
Consolidated Report
All naming violations compiled into a single data-slate.
Fix Execution
`git mv` and rename operations performed with surgical precision.
Victory Report
Every name is now a precise designation. The Machine God is pleased.
The Sacred Laws
The holy laws this crusade enforces. Break them and face the Omnissiah's wrath.
File naming shall follow the SACRED CONVENTION. PascalCase for components, camelCase for utilities, kebab-case for configs. Deviation is heresy.
Boolean variables shall be PREFIXED with interrogative particles: is, has, can, should. A boolean must answer a question, not mumble incoherently.
Functions shall be VERBS of action. getData fetches. calculateTotal computes. processOrder transforms. Vague names like handle or do are FORBIDDEN.
Types and interfaces follow the SACRED NOMENCLATURE. No I prefix for interfaces. No Type suffix. The name IS the documentation.
The following names are EXCOMMUNICATE: data, temp, stuff, thing, item, obj, val, res, ret. These are not names — they are confessions of cognitive laziness.
The Holy Squad
The specialist Tech-Priest agents deployed during this crusade. Each carries only the doctrine they need.