create-datadriven-aspnetcore

Generates ASP.NET Core CRUD pages, controllers, and Minimal API endpoints backed by EF Core.

Updated Sep 22, 2026
One-click install
npx skills add https://github.com/bytecakelake/Nurse-Scheduler --skill create-datadriven-aspnetcore-bytecakelake
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: create-datadriven-aspnetcore
Source: https://github.com/bytecakelake/Nurse-Scheduler/tree/main/.agents/plugins/dotnet-data/skills/create-datadriven-aspnetcore
Command: npx skills add https://github.com/bytecakelake/Nurse-Scheduler --skill create-datadriven-aspnetcore-bytecakelake

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Manually writing repetitive CRUD code for ASP.NET Core applications — Razor Pages, Blazor components, MVC controllers, and Minimal API endpoints — is time-consuming and error-prone, especially when matching existing UI conventions and wiring up Entity Framework Core correctly. ## Core Features & Use Cases - Multi-Framework Scaffolding: Generates Razor Pages, Blazor components, MVC controllers with views, and Minimal API endpoints without relying on CLI scaffolding tools. - EF Core Integration: Creates or reuses DbContext classes, registers providers, and manages the full migration lifecycle (add migration, update database). - Convention Matching: Inspects existing layouts, CSS frameworks (Bootstrap, Tailwind), and coding patterns so generated UI blends into the project. - Use Case: You have a Product model in an ASP.NET Core project and need full CRUD Razor Pages with a new SQLite-backed DbContext, including CRUD for the parent Category entity, plus verified migrations and a clean build. ## Quick Start Ask the agent to scaffold Razor Pages with CRUD for your model in the target project, specifying the model namespace, the .csproj path, the DbContext name, and the database provider to use.

Frequently Asked Questions about create-datadriven-aspnetcore

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

FAQPage Schema
How do I scaffold CRUD Razor Pages with Entity Framework Core?▼

Provide a natural-language request naming the model, its namespace, the project .csproj path, a DbContext name, and the database provider. The workflow generates list, details, create, edit, and delete pages, then creates and applies an EF migration.

How to generate Minimal API endpoints with OpenAPI in ASP.NET Core?▼

Request Minimal API endpoints for your model with OpenAPI support enabled. Each endpoint gets a route group, unique WithName operation ID, tags, descriptions, Produces response metadata, and an executable .http file covering all CRUD requests.

Does this work with Blazor interactive server components?▼

Yes, Blazor CRUD components are supported with specific rules: [SupplyParameterFromForm] properties use = new() to prevent EditForm crashes, and AddInteractiveServerComponents/AddInteractiveServerRenderMode are only added when components actually use InteractiveServer render mode.

Why does my Blazor EditForm crash on initial page load?▼

The crash occurs when [SupplyParameterFromForm] properties are initialized with null! instead of = new(). Initializing with a new instance ensures the EditForm has a valid model during the initial GET request before form submission.

When should I not use code generation for ASP.NET Core scaffolding?▼

Avoid this approach for non-ASP.NET Core projects such as class libraries or console apps, and when CLI-based scaffolding tools are explicitly preferred. It targets web artifacts like pages, views, components, and API endpoints only.