aspnet-backend

Standardize ASP.NET Core Web API backend development with Controller-Service-DB workflows.

Updated Mar 13, 2026
One-click install
npx skills add https://github.com/thinh082/GammarBE --skill aspnet-backend
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: aspnet-backend
Source: https://github.com/thinh082/GammarBE/tree/main/GammarBE
Command: npx skills add https://github.com/thinh082/GammarBE --skill aspnet-backend

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It solves the inconsistency and quality issues that happen when building or modifying ASP.NET Core Web API code without a unified backend workflow, leading to fragile endpoints, weak validation, and error-prone database updates.

Core Features & Use Cases

  • Consistent backend architecture: Guides creation or modification of Controllers and Services that match the project’s conventions and wiring approach (DI, async patterns).
  • Operational robustness: Enforces validation, careful exception handling, and transaction usage for multi-step database workflows.
  • Database and query correctness: Promotes safe and efficient Entity Framework Core patterns like async/await, AsNoTracking for read queries, and AnyAsync for existence checks.
  • Use Case: When you need to add a new feature such as “create an entity”, “update user profile”, or “add an API endpoint with business logic”, use this skill to generate code that fits the project’s expected structure and response format.

Quick Start

Activate this skill when you want to add a new ASP.NET Core endpoint and implement the related business logic in a service with validation and proper transaction handling.

Frequently Asked Questions about aspnet-backend

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

FAQPage Schema
How do I structure a new ASP.NET Core Web API endpoint with proper separation of concerns?

Structure your ASP.NET Core Web API endpoints by separating logic across Controllers, Services, and Entity Framework database operations. This approach enforces dependency injection wiring, async patterns, and a consistent YAML-specified response contract for reliable API workflows.

What is the best way to handle transactional database updates in an ASP.NET Core service layer?

Handle transactional database updates in your service layer by defining explicit transaction boundaries for multi-step workflows. Combine this with safe Entity Framework Core patterns like async/await and AnyAsync for existence checks to ensure robust and error-free data modifications.

How does AsNoTracking improve Entity Framework Core query performance in Web API read operations?

AsNoTracking improves Entity Framework Core query performance by preventing change tracking for read-only operations. Apply this pattern alongside async/await in your service layer to optimize database queries and maintain efficient resource usage across your Web API endpoints.

Can I enforce a standardized API response format when adding new controllers and business logic?

You can enforce a standardized API response format by applying a YAML-specified response contract. This contract standardizes the code, message, and data shape across all newly created or modified controllers and services, ensuring API consistency and operational robustness.

Why should I use AnyAsync for existence checks instead of FirstOrDefault in Entity Framework Core?

Use AnyAsync for existence checks in Entity Framework Core to generate efficient SQL EXISTS queries instead of retrieving entire entities. This async pattern minimizes database overhead and fits the required safe query standards for robust ASP.NET Core Web API backend development.