Apply the naming standards
Name a new identifier, file, repo, or branch the way an AI-native org 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 an AI-native org 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.
Units
- 01Introduction4 min
- 02The naming rules7 min
- 03Keywords and codenames7 min
- 04Knowledge check4 min
- 05Summary3 min
Related
- Design and version an API Shape a clean, consistent API against a clear API design standard - resources, standard methods, typed errors, cursor pagination, idempotency - then version and deprecate it under a versioning policy so no consumer is ever broken without consent.
- Read the pipeline that ships your change Follow a change from a pull request through the canonical CI stage set to a gated production deploy - the ordered gates a pipeline runs, why CI is the real gate, and how the deployment model promotes one signed artifact dev to staging to prod.
- Commits and versioning Write Conventional Commits whose type, scope, and breaking marker drive Semantic Versioning; see how release-please turns merged commits into a human-approved Release-PR, changelog, and tag; and how the trunk-based, protected-main model gates every release.