create-blazor-project
Create a new ASP.NET Core web application or web site using Blazor. USE FOR: creating a new Blazor web app, scaffolding a new web project, starting a new web site, choosing render modes (Static SSR, Interactive Server, Interactive WebAssembly, Auto), running dotnet new blazor with the right options, setting up initial project structure. DO NOT USE FOR: adding features to existing projects, changing how an existing app renders, or component authoring (use author-component).
npx skills add dotnet/skills --skill create-blazor-project --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.
# Create a Blazor Web App ## Before You Start — Gather Requirements If the user's request doesn't make the following clear, ask before scaffolding: 1. **What does the app do?** List the main screens/features (e.g., "product catalog with search and shopping cart"). 2. **What kind of interactivity is needed?** Displaying data and forms? Real-time updates? Offline support? Rich drag-and-drop UI? 3. **Deployment environment?** Internet-facing? Intranet? Mobile users on slow connections? 4. **Authentication needed?** Anonymous? Individual accounts? Organizational (Azure AD)? ## Pick the Right Interactivity Level Blazor render modes are a progression scale. Start at the simplest level that satisfies the requirements and only move up when there's a concrete reason. ``` Static SSR ──→ SSR + Enhanced Nav ──→ Interactive Server ──→ Interactive WebAssembly simplest most complex ``` ### Decision Rules | If the app needs... | Use | Why | |---|---|---| | Display data, simple forms, links between pages | **Static SSR** (`-int None`) | No JS runtime, no circuit, no WebAssembly download. Forms work via HTML POST. Enhanced navigation makes it feel snappy. | | Everything above + a few components with
- Before You Start — Gather Requirements
- Pick the Right Interactivity Level
- Decision Rules
- Auto Mode Constraints
- Don'ts
- Scaffold the Project
- Static SSR Only (display data + simple forms)
- Interactive Server, Per-Page (recommended default)
- Interactive Server, Global
- Interactive WebAssembly, Per-Page
- Interactive WebAssembly, Global
- Interactive Auto, Per-Page
- Interactive Auto, Global
- With Authentication
dotnet new blazor -o {AppName} -int None
dotnet new blazor -o {AppName} -int Server
dotnet new blazor -o {AppName} -int Server -ai
dotnet new blazor -o {AppName} -int WebAssembly
dotnet new blazor -o {AppName} -int WebAssembly -ai
dotnet new blazor -o {AppName} -int Auto
dotnet new blazor -o {AppName} -int Auto -ai
dotnet new blazor -o {AppName} -int Server -au IndividualWhat does the create-blazor-project skill do?
Create a new ASP.NET Core web application or web site using Blazor. USE FOR: creating a new Blazor web app, scaffolding a new web project, starting a new web site, choosing render modes (Static SSR, Interactive Server, Interactive WebAssembly, Auto), running dotnet new blazor with the right options, setting up initial project structure. DO NOT USE FOR: adding features to existing projects, changing how an existing app renders, or component authoring (use author-component).
How do I install it?
Run `npx skills add dotnet/skills --skill create-blazor-project --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.