Project foundation
Pain point
A development environment can appear to work while its responsibilities are scattered across personal setup, editor defaults, shell history, and undocumented Git behavior. That makes failures difficult to reproduce and forces newcomers to discover the system by trial and error.
The project foundation makes those responsibilities explicit. Read the pages in sequence: each mechanism addresses a remaining source of inconsistency without trying to replace the others.
| Foundation | Pain point it reduces |
|---|---|
| Dev Container | Host operating systems provide different development environments |
| Mise | Tool installation and recurring commands drift between contributors |
| Project entry | Small repository-local setup steps are easily forgotten |
| Agent guidance | Coding agents lack the project's commands, preferences, and safety boundaries |
| EditorConfig | Editors create avoidable formatting and encoding differences |
| Git attributes | Git checkouts and diffs vary across platforms |
| Git ignore | Local state, generated output, and secrets can enter commits |
| Git hooks | Routine checks are forgotten or run inconsistently |
| GitHub Actions | Local checks and publishing depend on one contributor's machine |
| Project documentation | Durable knowledge becomes scattered, duplicated, or difficult to navigate |
| README | New visitors cannot quickly understand or use the project |
| Community files | Contributions arrive without shared intake, evidence, or safety expectations |
| License | Reuse rights remain unclear without an explicit legal grant |
Each page explains the selected solution, current configuration, trade-offs, and adaptation boundary. The corresponding repository file remains the source of truth for exact values.