aiup-blazor-dotnet

aiup-blazor-dotnet is the AI Unified Process construction plugin for C#, Blazor, and Entity Framework Core on .NET 10. It turns the entity model and use case specifications produced by aiup-core into EF Core migrations, Vertical Slice features, and tests using bUnit, xUnit, and Playwright.

This plugin is designed to continue from the specifications produced by aiup-core. For the complete AI Unified Process workflow, use it alongside aiup-core and select one stack plugin.

Skills and workflow

Construction
─────────────────────────────────────────────────
/ef-migration  →  /implement  →  /bunit-test
                              ↘  /dotnet-test
                              ↘  /playwright-test

The linked SKILL.md files are the authoritative reference for detailed inputs, outputs, and behavior.

Installation

Tessl

Initialize the project once:

tessl init --agent agents

agents is the vendor-neutral layout; use claude-code, cursor, gemini, codex, copilot, or copilot-vscode for a specific host. Then install the plugins:

tessl install ai-unified-process/aiup-core
tessl install ai-unified-process/aiup-blazor-dotnet

Depending on the configured agent, skills may be exposed as slash commands or invoked by intent, for example "implement UC-001".

Claude Code

/plugin marketplace add ai-unified-process/marketplace
/plugin install aiup-core
/plugin install aiup-blazor-dotnet

See the marketplace installation guides for other agents and manual adoption.

Prerequisites

• aiup-core and reviewed docs/entity_model.md plus docs/use_cases/UC-*.md artifacts.
• A .NET 10 solution or project using Blazor and Entity Framework Core.
• A configured relational database provider and EF Core tooling for migrations.
• Node.js and installed Playwright browsers when browser tests are generated.
• Optional MCP servers configured through rules/mcp-servers.md.

Inputs and generated artifacts

The plugin consumes the core documentation under docs/. It updates EF Core persistence types, creates migration files, implements a feature folder per use case, and places bUnit, backend, and browser tests in the solution's test projects.

Project structure

your-solution/
├── docs/
│   ├── entity_model.md
│   ├── use_cases/UC-*.md
│   └── test_cases/TC-*.md
├── <Application>/
│   ├── Data/                            # DbContext and EF configurations
│   ├── Migrations/                      # /ef-migration
│   └── Features/
│       └── UCXXX_<FeatureName>/         # /implement
├── <Application>.Tests/                 # /bunit-test and /dotnet-test
└── <Application>.Tests.E2E/             # /playwright-test

A feature folder can contain the Blazor page, code-behind, scoped CSS, command or query, handler, and validator. The skills inspect existing project and test conventions before selecting exact names and paths.

Traceability

The test skills mark every test with the use case, scenario, and business rules it verifies, so the AI Unified Process Navigator, AI Unified Studio, and coverage audits can find it. They create a UseCaseAttribute in the test project when it is missing and use it as [UseCase("UC-001", Scenario = "A2: Invalid Postal Code", BusinessRules = ["BR-003"])].

MCP servers

See rules/mcp-servers.md for setup details.

Related documentation

• Getting started
• Workflow and artifacts
• aiup-core

License

Apache-2.0 · © 2025-2026 Carl J. Mosca and the AI Unified Process contributors

See LICENSE and NOTICE. "AI Unified Process" identifies the original methodology; derived works must retain the NOTICE file and must not present themselves as the official AI Unified Process.