| name | code-and-design-version-control |
| description | Use when managing code + design in git. Git is the source of truth for code; design files reference git commits.
|
Code and Design Version Control
Code and design files belong in git. Commit messages reference design decisions. Track design system evolution alongside code.
What lives in git
Code:
- All source files (.html, .css, .js, .tsx)
- Static assets (smaller than ~10MB)
- Config files (wrangler.toml, package.json)
- Documentation
Design references:
- Brand tokens (CSS variables)
- Figma links in README
- Decision records (DESIGN_DECISIONS.md)
- Brand guidelines (brand-guidelines.md)
What doesn't live in git
- Large image assets (>10MB) — use git-lfs or external storage
- Source design files (Figma, Sketch) — keep in design tool
- Generated builds (dist/) — gitignore
- node_modules — gitignore
- Secrets — .env.example with placeholders
Commit message discipline
Format: <type>(<scope>): <subject>
- feat(hero): add staggered text reveal
- fix(button): align hover state with token
- design(palette): adjust accent to #e85d2c
- refactor(tokens): consolidate type tokens
Make design decisions traceable via git log.
Where this fits in the X3 empire
Source-control practice across X3 repositories.