Project Contract
Create a short project constitution from repository evidence, not generic preferences.
Include only durable rules that should affect most tasks:
- canonical package/build/test tools;
- naming and domain vocabulary;
- architecture and ownership boundaries;
- input validation and data-integrity rules;
- security and secret-handling rules;
- required verification gates;
- rules for preserving user changes and avoiding destructive Git actions.
Keep specialized details in referenced documents or skills instead of expanding every Codex turn. Do not overwrite stronger existing project instructions without explicit evidence that they are stale or contradictory.