before-backend-dev

To enforce backend coding standards before implementation, you must read the specific guideline files for database work, error handling, logging, and type safety. This ensures your new feature aligns with architecture and quality requirements prior to writing any backend code.

Before writing database and error handling code, review the backend guidelines located in the .trellis/spec/backend/ directory, specifically database-guidelines.md and error-handling.md. These files outline the mandatory practices for compliant backend development.

Reading documentation before coding a new backend feature prevents misaligned tasks and skipped standards caused by inconsistent pre-implementation guidance. It satisfies planning requirements and ensures architecture and quality standards are followed.

To create a pre-implementation plan for backend development, open the index.md file in the .trellis/spec/backend/ directory along with the relevant logging and type safety guidelines. Formulate your task plan from these documents before writing any backend code.

Yes, this pre-implementation check applies specifically to logging and type safety tasks, alongside database work and error handling. It ensures you satisfy documentation review and planning requirements prior to starting compliant backend coding.