project-guidelines-example

Standardize FastAPI and Next.js project architecture by applying a repeatable blueprint that defines repository file structures, coding patterns, and service interactions. This enforces consistency, making codebases predictable as teams scale and new features are added.

Testing patterns for FastAPI and Next.js should follow TDD with prescribed pytest patterns for the backend and React Testing Library coverage expectations for the frontend. The approach requires meeting specific coverage targets to ensure predictable software delivery.

Structure Claude API tool-calling outputs by following explicit implementation patterns that define reference API response shapes and frontend data fetching. This ensures structured outputs remain consistent across AI service interactions within the standardized architecture.

Yes, the project guidelines template requires predictable CI/CD practices and includes a specific deployment workflow. It provides a pre-deployment checklist, deployment commands, and required environment variable documentation to standardize delivery.

Core rules for error handling and environment variables require explicit immutability and thorough environment-variable documentation. Following these mandatory rules ensures stable architecture and prevents configuration errors during deployment.

Yes, you can use these project guidelines for a new repository without an existing layout by aligning its structure, coding patterns, test approach, and deployment steps to the provided template for immediate architectural consistency.