Automate backend API design and service governance for safe deployments.
npx skills add https://github.com/GuicedEE/ai-rules --skill senior-backend-guicedee
Please help me install this Agent Skill. Skill: senior-backend Source: https://github.com/GuicedEE/ai-rules/tree/main/skills/.curated/senior-backend Command: npx skills add https://github.com/GuicedEE/ai-rules --skill senior-backend-guicedee
Backend teams often struggle with inconsistent API contracts, unclear ownership, and risky migrations that degrade reliability and observability. This Skill provides a structured approach to design, document, and govern backend systems with a focus on API contracts, authentication/authorization, error handling, performance, migrations, and operational safety.
Define a contract first for a new API and its events, including inputs, outputs, errors, and idempotency, then outline data ownership, migrations, rollback, and monitoring requirements for a safe deployment.
High-intent search queries and answers about installing and using this skill.
To design robust backend API contracts, first define inputs, outputs, errors, and idempotency for your API and its events. Then outline data ownership, migration plans, rollback strategies, and monitoring requirements to ensure safe deployments across teams.
The best way to structure database migrations is to use scaffolded templates for migration plans and rollback strategies alongside deployment safety gates. This enforces clear data ownership and operational safety across your environments.
Implement authentication, authorization, and observability by applying structured backend design guidance from day one. Define security controls and integrate monitoring hooks to guarantee reliable and observable system operations.
Yes, this backend governance approach works for complex data models by enforcing requirements for data modeling, error handling, and performance considerations. It provides structured guidance to maintain reliability as system complexity scales.
You need to formalize API idempotency and error handling when planning a new microservice to prevent inconsistent API contracts and risky deployments. Defining these elements early mitigates reliability degradation across teams.
Your backend deployments lack observability and clear ownership due to inconsistent API contracts and missing operational safety gates. Applying structured service governance resolves this by enforcing monitoring integration and data ownership across teams.
HechaoYannetGenerate a master architecture document from GDDs, ADRs, and governance constraints.
korwlik23Plan production deployments with rollback steps and verification commands.
pluginagentmarketplaceContainerize ASP.NET Core apps with Docker and deploy to Azure, AWS, or GCP.
jshsakuraDefine service boundaries and API contracts for microservices architectures.
