STD-DEV-001: Engineering Workflow

1. Context

To ensure a consistent, "No-Mess" development process across the team.

2. The Standard (The Floor)

• [MUST] Architectural Alignment: Read archive/STD-ARC-004_Application_Boundaries.md to understand where code belongs.
• [MUST] Naming Conventions:
• Components: PascalCase (PropertyTable.tsx)
• Hooks: camelCase with use prefix (useAuth.ts)
• Utilities: kebab-case (date-utils.ts)
• [MUST] Atomic Commits: One change per commit. Message format: feat(domain): description (STND-XX).
• [MUST] Ghost Branching: Use ghost/[TASK_ID]-[slug] for non-trivial tasks. Delete after merge.
• [MUST] Pre-Flight: CI (Lint, TSC, Test) must pass before merging.

3. Best Practices (The Path)

• [SHOULD] Monorepo Hygiene: Respect boundaries. apps/platform = UI. packages/modules = Logic.
• [SHOULD] Review Protocol: Use Typora for high-fidelity reviews of architecture docs.

4. Version History

Version	Date	Author	Change
1.0	2026-01-25	AI	Extracted from Engineering Handbook
1.1	2026-02-10	Antigravity	Resolved Merge Conflicts & Cleanup