backend-rules

Backend API route implementation requires strict input validation, secret protection, and authorization enforcement. These secure backend rules ensure server-side tasks align with repository boundaries and reduce risks across route handlers and middleware.

To ensure database queries and authentication logic are tested, you must enforce comprehensive test coverage across all server-side tasks. This backend rules skill requires validating business logic and noting when storage-layer follow-up like RLS policy work is needed.

Yes, this backend rules guidance applies directly to middleware and infrastructure configuration. It provides operating rules for server-side tasks including route handlers, business logic, and infrastructure setup to keep changes secure and testable.

The best way to handle authorization and RLS policy handoff is to enforce authorization checks in business logic and document required storage-layer follow-up. This backend rules approach requires explicit notes when RLS policy work or API contract changes are needed.

Input validation and secret protection are required for server-side tasks to reduce backend risks and maintain security guardrails. Enforcing these secure backend rules prevents unauthorized access and ensures changes align with repository boundaries.

Yes, you can use backend-rules for reviewing API contract changes and business logic. It guides secure backend implementation and review by requiring comprehensive test coverage and flagging when frontend or storage-layer follow-up is necessary.