dotnet

Implement ASP.NET Core backend services with controllers, validation, and persistence.

Updated Apr 14, 2026
One-click install
npx skills add https://github.com/christopherclemmons/startupkit --skill dotnet-christopherclemmons
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dotnet
Source: https://github.com/christopherclemmons/startupkit/tree/main/skills/dotnet
Command: npx skills add https://github.com/christopherclemmons/startupkit --skill dotnet-christopherclemmons

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill addresses the challenge of delivering reliable, maintainable ASP.NET Core backend services and APIs that align with business requirements, follow established architecture, and are safe to operate in production environments.

Core Features & Use Cases

  • Production-ready API implementation: Design thin controllers, robust service layers, and clear DTO contracts for HTTP APIs.
  • Validation and error handling: Enforce input validation, consistent error responses, and centralized exception handling.
  • Integration and maintainability: Apply constructor injection, async I/O, logging, and clear data access boundaries to keep code testable and extensible.
  • Use Case: Implement a leads API that validates requests, normalizes emails, tags records with environment/business context, and persists leads to a database while exposing stable endpoints for frontend consumption.

Quick Start

Use the dotnet agent to implement an ASP.NET Core controller that validates input, delegates to a service, enforces authorization, and returns consistent HTTP responses.

Frequently Asked Questions about dotnet

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

FAQPage Schema
How do I build production-ready ASP.NET Core APIs with thin controllers and service layers?

Build production-ready ASP.NET Core APIs by designing thin controllers that delegate business logic to service layers, enforce input validation, and return consistent HTTP status codes for safe cloud deployment.

What is the best way to handle input validation and error responses in a .NET backend service?

Handle input validation and errors in a .NET backend by enforcing request validation and implementing centralized exception handling. This approach guarantees consistent error responses and measurable logging across your ASP.NET Core API endpoints.

How do I design request and response DTOs for an ASP.NET Core API?

Design request and response DTOs for ASP.NET Core APIs by establishing clear data transfer object boundaries that separate HTTP contracts from service layers, ensuring consistent status codes and stable frontend integration.

Does this approach to .NET API development support async I/O and database integration?

Yes, this .NET API development approach fully supports async I/O and database integration, applying clear data access boundaries and constructor injection to maintain testable, extensible backend services for cloud deployment.

When should I use constructor injection in an ASP.NET Core API service?

Use constructor injection in ASP.NET Core APIs whenever you need to maintain clear data access boundaries and testable service layers. It satisfies requirements for maintainable layering and keeps your backend services extensible for cloud deployment.