HANDBOOK / ENGINEERING
Code that can be maintained
Prefer clear boundaries, small changes, and evidence of correct behavior.
Application structure
Use server components for public reading and small client components for interaction. Keep validation and data access separate from rendering. Use normalized relationships and explicit publication boundaries.
Contribution quality
Use strict TypeScript, semantic HTML, readable names, and meaningful tests around behavior or security boundaries. Explain limitations. Avoid unnecessary services, dependencies, and client JavaScript.
GitHub integration
Link repositories, issues, and pull requests to the institutional context. GitHub owns source control and code review. Automated synchronization is an extension point and must validate signatures, use minimal scopes, and process deliveries idempotently.