before-backend-dev

To ensure backend code follows project coding standards, review the repository's engineering guidelines and required patterns for database, error handling, logging, and type safety before writing any code. This prevents inconsistent implementations and avoidable rework.

The best way to start backend feature development safely is to read the relevant guideline documents, specifically targeting database work, error handling, logging, and type safety requirements, to align with established coding standards for maintainability.

Your backend implementation requires reading documentation first to enforce mandatory guideline review, ensuring the task starts from the repository's required engineering guidelines rather than ad-hoc coding, which reduces inconsistent implementations.

Yes, you need to read specific guideline files for database and error handling tasks. The process guides you to consult targeted guideline documents based on the domain you are working in, alongside logging and type safety requirements.

You should not skip the guidelines-first approach for backend development when working on workflows that touch databases, error handling, logging, and type safety, as ignoring established patterns leads to avoidable rework and inconsistent implementations.