project-guidelines-example

Project-specific development standards are established by defining architecture, file structure, code patterns, testing requirements, and deployment workflows. This skill enforces critical rules such as immutability, TDD, and input validation to ensure consistency and quality across a production application.

Critical coding rules for development standards include enforcing immutability, Test-Driven Development (TDD), and input validation. These non-negotiable principles ensure code quality and consistency across the application's architecture and deployment workflow.

Testing requirements are set up by specifying pytest for backend testing and React Testing Library for frontend testing. These methodologies enforce TDD practices and ensure robust validation before deployment.

Yes, this project guidelines approach works for onboarding developers by providing a definitive guide to the tech stack, architecture, coding standards, and deployment process. It details common API response formats, frontend calls, and AI integrations.

The best way to document deployment workflows is by including pre-deployment checklists and specific deployment commands within the project guidelines. This ensures all architecture and file structure standards are verified before releasing the production application.

You need to enforce immutability and input validation in your code patterns whenever writing production application logic. These are non-negotiable critical rules applied to API response formats, frontend calls, and AI integrations to prevent edge case failures.