Backend Architecture Enforcer

What it does

The backend-architecture-enforcer skill ensures that generated code adheres to a specified backend architecture. It validates the structure and components of the code against predefined architectural rules, promoting consistency and maintainability. This includes enforcing specific directory structures, module dependencies, and API design patterns within the generated code.

When to use it

• Standardizing microservice development: Enforce consistent architectural patterns across multiple microservices being built by an AI agent.
• Generating backend APIs: Ensure newly created REST or GraphQL APIs follow established architectural guidelines for your organization.
• Automating boilerplate code generation: Guarantee that generated project scaffolding adheres to the required architecture, saving developers time and reducing errors.
• Refactoring legacy codebases: Guide an AI agent in restructuring existing code to align with a modern backend architecture.

Key capabilities

• Architecture validation
• Code structure enforcement
• Module dependency management
• API design pattern adherence

Example prompts

• "Generate a new microservice for user authentication, ensuring it follows the layered architecture defined in architecture.json."
• "Refactor this existing Python code to adhere to the MVC architectural pattern."
• “Create a REST API endpoint for retrieving product details, enforcing the established API design guidelines.”

Tips & gotchas

The skill requires an architecture definition file (e.g., architecture.json) that outlines the expected backend structure and rules. Without this configuration, the enforcement will not function correctly.