create-datadriven-aspnetcore
Generate or scaffold ASP.NET Core code — Razor Pages, Blazor components, MVC controllers, views, and Minimal API endpoints — without using ASP.NET Core CLI scaffolding/code-generation tools. Use when (1) adding CRUD pages, views, or API endpoints backed by Entity Framework (EF Core) and a database, (2) generating code to create, read, update, and delete data using a DbContext, (3) scaffolding UI components that match the project's existing CSS framework and coding patterns, or (4) creating data-driven forms, tables, and navigation for a model class. Do not use for non-ASP.NET projects or when
npx skills add dotnet/skills --skill create-datadriven-aspnetcore --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Generate or Scaffold ASP.NET Core Code Generate ASP.NET Core scaffolded code — controllers, views, Razor Pages, Blazor components, Minimal API endpoints. The generated code matches the project's existing CSS framework, layout conventions, and coding patterns. No CLI-based scaffolding/code-generation tools are used; standard `dotnet` CLI commands for build, restore, and migrations are still expected. ## When to Use - Adding CRUD pages, views, or components for a model in an ASP.NET Core project - Scaffolding API controllers or Minimal API endpoints with Entity Framework Core - Generating Razor Pages, MVC views, or Blazor components backed by a DbContext ## When Not to Use - The project is not an ASP.NET Core project - You need to scaffold non-web artifacts (class libraries, console apps, etc.) ## Inputs | Input | Required | Description | |-------|----------|-------------| | Scaffolding request | Yes | Natural-language description of what to scaffold (see format below) | | Project file path | Yes | Full path to the target `.csproj` file | | Solution root path | Recommended | Path to the solution root for multi-project solutions | ### Scaffolding Request Format The scaffolding reque
- When to Use
- When Not to Use
- Inputs
- Scaffolding Request Format
- Workflow
- Step 1: Understand the Scaffolding Request
- Execution Checklists
- Step 2: Discover UI Style (non-API scaffolders only)
- Step 3: Apply Blazor-Specific Rules (Blazor scaffolders only)
- Step 4: Generate Code
- Step 5: Set Up Entity Framework (if applicable)
- Step 6: Generate .http File (API scaffolders only)
- Step 7: Verify
- Validation
What does the create-datadriven-aspnetcore skill do?
Generate or scaffold ASP.NET Core code — Razor Pages, Blazor components, MVC controllers, views, and Minimal API endpoints — without using ASP.NET Core CLI scaffolding/code-generation tools. Use when (1) adding CRUD pages, views, or API endpoints backed by Entity Framework (EF Core) and a database, (2) generating code to create, read, update, and delete data using a DbContext, (3) scaffolding UI components that match the project's existing CSS framework and coding patterns, or (4) creating data-driven forms, tables, and navigation for a model class. Do not use for non-ASP.NET projects or when
How do I install it?
Run `npx skills add dotnet/skills --skill create-datadriven-aspnetcore --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From dotnet/skills, a repository with 4,927 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.