backend-standards

Define backend standards for API design, database migrations, and query optimization.

1|Updated Mar 7, 2026
One-click install
npx skills add https://github.com/george-popescu/bee-dev --skill backend-standards
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: backend-standards
Source: https://github.com/george-popescu/bee-dev/tree/main/plugins/bee/skills/standards/backend
Command: npx skills add https://github.com/george-popescu/bee-dev --skill backend-standards

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill provides a comprehensive, framework-agnostic set of best practices for backend development, ensuring consistency, maintainability, and robustness across different technologies.

Core Features & Use Cases

  • API Design: Enforces RESTful conventions, consistent status codes, and standardized error responses.
  • Database Management: Dictates best practices for timestamps, foreign keys, indexing, and naming conventions.
  • Migrations: Outlines requirements for reversible, focused, and zero-downtime database migrations.
  • Query Optimization: Guides on preventing N+1 queries, effective caching, and efficient query writing.
  • Use Case: A new backend developer joins a team using multiple frameworks. This Skill serves as their primary guide to understand and implement the team's established backend quality standards, regardless of the specific framework in use.

Quick Start

Review the API design principles for creating a new RESTful endpoint.

Frequently Asked Questions about backend-standards

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
What are the universal standards for RESTful API design and HTTP status codes?

Universal backend standards enforce RESTful conventions, consistent HTTP status codes, and standardized error responses to ensure maintainable API design across diverse technology stacks.

How do I write reversible and zero-downtime database migrations?

Database migration strategies must be focused, reversible, and capable of achieving zero-downtime to maintain database integrity and ensure consistent schema management without service disruption.

What is the best way to prevent N+1 query problems in backend development?

Preventing N+1 query problems involves applying efficient query patterns like eager loading and implementing effective caching to optimize database performance and reduce redundant query execution.

Can I apply these backend development standards to any framework?

Yes, these backend development standards are framework-agnostic, providing universal best practices for API design, database integrity, and query optimization that apply across diverse technology stacks.

What database schema management rules should I follow for indexing and soft deletes?

Database schema management rules dictate best practices for timestamps, foreign keys, indexing, naming conventions, UUIDs, and soft deletes to maintain strict database integrity and consistency.