scaffolding

Generate .NET backend feature slices with validation, EF Core configuration, and integration tests.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Scaffolding new .NET features consistently is slow and error-prone because developers must manually wire architecture, validation, endpoint behavior, persistence, and tests every time.

Core Features & Use Cases

  • Architecture-aware scaffolds: Generates code that matches your project’s chosen architecture (VSA, Clean Architecture, DDD, or Modular Monolith) instead of producing generic folder layouts.
  • Complete vertical slices: Produces an end-to-end feature (command/handler, validation, endpoints, persistence configuration, and integration tests) as a single unit.
  • Production-grade guardrails: Enforces Result-based handlers, CancellationToken propagation, FluentValidation + filter wiring, OpenAPI metadata, pagination for list endpoints, and a global exception-handling check.
  • Entity-ready scaffolding: Creates entities paired with EF Core IEntityTypeConfiguration<T> and recommends migrations workflow.
  • Testable by default: Includes integration tests with DI replacement using services.RemoveAll<DbContextOptions<T>>(), aiming to prevent fragile test setups.

Quick Start

Ask the AI to scaffold a new “create feature” for your backend by specifying the feature name, target architecture (VSA/Clean Architecture/DDD/Modular Monolith), and the entity fields to generate with EF Core configuration and integration tests.

Frequently Asked Questions about scaffolding

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

FAQPage Schema
How do I scaffold complete .NET Web API endpoints with EF Core and FluentValidation?

Scaffolding .NET Web API endpoints produces complete vertical slices containing command handlers, FluentValidation filter wiring, EF Core persistence configuration, and integration tests as a single architectural unit.

Can I generate integration tests for new .NET entities using DbContextOptions removal?

Yes, generating integration tests for new .NET entities uses DI replacement with services.RemoveAll<DbContextOptions<T>>() to prevent fragile test setups and ensure isolated database contexts.

Does the scaffolding support Clean Architecture and DDD patterns for new CRUD endpoints?

Yes, the scaffolding supports Clean Architecture and DDD patterns for new CRUD endpoints, alongside Vertical Slice Architecture and Modular Monolith, generating code that matches your project's chosen architecture.

What is the best way to scaffold .NET feature slices with CancellationToken propagation?

The best way to scaffold .NET feature slices with CancellationToken propagation is generating architecture-aligned handlers that enforce production-grade guardrails like Result-based responses and OpenAPI metadata.

How do I create EF Core entity configurations when scaffolding new business operations?

When scaffolding new business operations, you create EF Core entity configurations by generating entities paired with IEntityTypeConfiguration<T> and following the recommended migrations workflow.

Why does scaffolding .NET features manually cause errors in Web API endpoints?

Scaffolding .NET features manually causes errors in Web API endpoints because developers must repeatedly wire architecture, validation, endpoint behavior, persistence, and tests by hand, leading to inconsistencies and mistakes.