Apply the naming standards
Name a new identifier, file, repo, or branch the way the estate does - keyword-first, no redundant prefix, cased by role - and tell a functional keyword apart from a product codename, so your first artifact passes the naming gate by default.
Units5
Duration25 min
Levelintermediate
By the end of this module, you'll be able to:
- Explain the cross-cutting naming principles the estate applies everywhere - keyword-first, no redundant prefix, casing by role, immutable IDs with mutable facts in metadata - and that naming is machine-enforced, not reviewer goodwill.
- Name a repo, a code identifier, a file, and a branch correctly by following the canonical naming standard rather than paraphrasing it from memory.
- Separate a functional keyword from a product codename, and know when a codename is allowed and when a primitive is codename-exempt.
- Follow the naming standard and the codename standard to the owning rule for any detail you need.
Prerequisites
- Basic familiarity with Git and the command line.
- Completion of "Apply the AGENTS floor" is recommended.