01.05

Naming conventions

Names that sort, search, and read the same everywhere.

Updated: Oct 3, 2026

On this page

Purpose

Names that sort, search, and read the same everywhere.

The standard

Thing	Pattern	Example
Repo	`kebab-case`, tool-first, platform suffix if needed	`facade-generator-rhino`, `standards-wiki`
Branch	`type/short-description`	`feat/pr-checklist`, `fix/login-redirect`
Environments	`local`, `preview`, `prod`
Env variables	`SCREAMING_SNAKE`, prefixed by service	`SUPABASE_URL`, `NEXT_PUBLIC_…` only for browser-safe values
Database tables/columns	`snake_case`, plural tables	`facade_panels.panel_width_mm`
Files (code)	per language style (04.x)
Files (design/data)	`YYYY-MM-DD_project_description_v01.ext`	`2026-09-16_hq_facade_takeoff_v03.xlsx`
Rhino layers	`Discipline::System::Element`	`FAC::CW::Mullion`
Revit families	`[TEAM: company prefix]_Category_Description`	`XX_CurtainPanel_SSG`
Units in names	always explicit	`_mm`, `_in`, `_deg`

Rules

No spaces, no special characters, no "final" or "new" in any name. Dates ISO-8601 only.

Owner: [TEAM] · Last reviewed: 2026-09