Skip to content

library-quality-mandate-unity

Library Quality Mandate: Unity Naming Charter (engine-specific additions)

Section titled “Library Quality Mandate: Unity Naming Charter (engine-specific additions)”

Extends core rules/library-quality-mandate.md (“charter-conformant” delegates here). Applies to a Unity project whose primary deliverable is a reusable library/submodule (Packages/<library-name>/); a shipped-game project may use it as a north star.

DecisionDefault action
Genre/perspective token in core-package code?Block. Relocate to the correct package/namespace.
Demo introduces a pattern 2+ demos already have inline?Extract to the library now; don’t “wait for the third copy.”
Breaking import change relocating namespaces?Ship [Obsolete]/[MovedFrom] aliases one release cycle + migration guide.
Unity library package count grows?Fine if each serves a clear reuse axis; not for “org clarity” alone.
New ISystem shipped without tests?Block. Ships with Tests/EditMode/ coverage.

A name describes the generic ROLE, never one concrete instance, demo, or genre. Where a test regex enforces a convention, the regex is the SSOT — a convention restated in a charter row, README, and regex changes at all three in the same commit, or the suite stays green while the prose describes nothing enforced. Full 12-row charter (genre tokens, namespaces, assembly split, more naming examples), the adoption checklist, and the regex-sync incident: docs/library-quality-mandate-unity.md. Consult it before naming any asset, group, or menu path.

library-quality-mandate.md (core) · docs/library-feature-discovery-protocol.md · code-conventions.md (core) § “Modular Boundaries”