backend-developer

Implement .NET backend services with EF Core, ABAC, and OpenAPI contracts.

6|Updated Jan 25, 2026
One-click install
npx skills add https://github.com/gajakannan/nebula-crm --skill backend-developer-gajakannan
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: backend-developer
Source: https://github.com/gajakannan/nebula-crm/tree/main/agents/backend-developer
Command: npx skills add https://github.com/gajakannan/nebula-crm --skill backend-developer-gajakannan

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This skill provides a structured blueprint and practical tooling for building a robust .NET backend following Clean Architecture, ensuring scalable APIs, data access, and maintainable domain logic.

Core Features & Use Cases

  • Implements domain, application, infrastructure, and API layers aligned with planning artifacts.
  • Enforces OpenAPI contracts, JSON Schema validation, and ABAC authorization.
  • Integrates with EF Core, audit/timeline events, and testable patterns for rapid delivery.
  • Real-world use: as a backend developer, generate repositories, services, and endpoints per specifications to deliver a production-ready backend.

Quick Start

Refer to the SKILL.md and planning-mds for the exact setup instructions. Use the scaffolding scripts to bootstrap entities and use cases, then run tests with the provided run-tests script.

Frequently Asked Questions about backend-developer

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

FAQPage Schema
How do I implement a .NET backend service using Clean Architecture?

Implement .NET backend services by building domain, application, infrastructure, and API layers aligned with planning artifacts. This enforces OpenAPI contracts, JSON Schema validation, and ABAC authorization to deliver testable, maintainable code.

How do I scaffold EF Core repositories and APIs from planning specifications?

Scaffold EF Core repositories, services, and endpoints per specifications using provided scaffolding scripts to bootstrap entities and use cases. Run the provided test script to verify the generated production-ready backend code.

What is ABAC authorization and how does it work with .NET APIs?

ABAC authorization enforces attribute-based access control within .NET API layers. It operates alongside audit timelines and OpenAPI contracts to secure endpoints and maintain maintainable domain logic across the backend service.

Does this backend implementation approach support EF Core and audit timelines?

Yes, the backend implementation integrates EF Core for data access and audit timeline events. It structures these within the infrastructure layer to ensure testable patterns and rapid delivery of production-ready backend code.

What's the best way to enforce OpenAPI contracts and JSON Schema validation in .NET?

Enforce OpenAPI contracts and JSON Schema validation by applying them across the API layer during Phase C implementation. This ensures the generated .NET backend services remain robust, testable, and strictly aligned with planning specifications.

Do I need architecture artifacts and workflows before building the .NET backend?

Yes, architecture artifacts and workflows are required inputs. The implementation processes these planning-mds specifications to generate domain logic, application services, and infrastructure components that adhere to Clean Architecture.