scaffolding

Generate .NET feature scaffolds with validation, OpenAPI metadata, and integration tests.

224|87|Updated Dec 15, 2018
One-click install
npx skills add https://github.com/Resgrid/Core --skill scaffolding-resgrid
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: scaffolding
Source: https://github.com/Resgrid/Core/tree/main/.opencode/skills/scaffolding
Command: npx skills add https://github.com/Resgrid/Core --skill scaffolding-resgrid

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill solves the problem of repeatedly writing incomplete .NET feature code that misses architectural conventions, validation, error handling, and test coverage.

Core Features & Use Cases

It generates end-to-end .NET 10 scaffolding guidance for building features as vertical slices, clean architecture layers, DDD aggregates, and modular-monolith modules. It ensures scaffolds include the project’s required result/HTTP mapping pattern, FluentValidation wiring, OpenAPI metadata, pagination on list endpoints, a global exception handler check, and integration tests using WebApplicationFactory with Testcontainers. It also supports entity scaffolding by pairing domain entities with EF Core IEntityTypeConfiguration and migration steps, reducing schema drift and inconsistent data annotations.

Quick Start

Use the scaffolding skill to scaffold a new endpoint-driven feature with validation, OpenAPI metadata, and an integration test in the architecture pattern your project uses.

Frequently Asked Questions about scaffolding

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

FAQPage Schema
How do I scaffold .NET vertical slice features with EF Core and integration tests?

Scaffolding .NET vertical slice features generates complete entity pairs with EF Core IEntityTypeConfiguration, migration steps, and WebApplicationFactory integration tests. This ensures schema drift prevention, reliable API behavior verification, and consistent data annotations across newly generated modules.

What is the best way to add new API endpoints with FluentValidation and OpenAPI metadata in .NET 10?

Adding API endpoints with FluentValidation and OpenAPI metadata is automated through architecture-aware scaffolding. It enforces ValidationFilter wiring, applies typed Result<T> HTTP mapping, propagates CancellationToken, and adds bounded pagination to list endpoints.

Does this scaffolding approach work with modular monolith and DDD patterns?

Scaffolding works with modular monolith and DDD patterns by generating architecture-aware vertical slices and DDD aggregates. It adapts to clean architecture layers, ensuring mandatory conventions like global exception handler verification and DI-safe Testcontainers test setup are satisfied.

Why do my .NET feature scaffolds miss architectural conventions and test coverage?

Feature scaffolds miss conventions when written manually without enforcing patterns. Automated scaffolding applies mandatory rules including Result<T> handling, FluentValidation wiring, appsettings connection string checks, and OpenAPI metadata to produce complete, convention-compliant code.

Can I generate Testcontainers integration tests for .NET modular monolith modules?

Generating Testcontainers integration tests for modular monolith modules is supported through DI-safe test setup. It uses WebApplicationFactory to verify API behavior, including global exception handler checks and appsettings connection string validation.