mcaf
The `mcaf` skill bootstraps Managed Code Adoption Framework governance into .NET repositories by establishing root and project-local `AGENTS.md` files, organizing repository-native documentation across architecture and operations, and installing aligned governance and implementation skills. Use it when establishing MCAF processes in new or existing .NET projects, defining durable agent workflows, or restructuring how multiple projects coordinate their agent behavior and documentation standards.
git clone --depth 1 https://github.com/managedcode/dotnet-skills /tmp/mcaf && cp -r /tmp/mcaf/catalog/Platform/MCAF/skills/mcaf ~/.claude/skills/mcafSKILL.md
# MCAF Adoption
## Trigger On
- bootstrapping MCAF in a new or existing repository that also contains `.NET` work
- updating root or project-local `AGENTS.md` files to follow a durable repo workflow
- deciding which MCAF governance skills and implementation-focused catalog skills to install together
- organizing repo-native docs for architecture, features, ADRs, testing, development, and operations
## Workflow
1. Start from the canonical bootstrap surface:
- tutorial: `https://mcaf.managed-code.com/tutorial`
- concepts: `https://mcaf.managed-code.com/`
- public MCAF skills: `https://mcaf.managed-code.com/skills`
2. Place root `AGENTS.md` at the repository or solution root.
3. Add project-local `AGENTS.md` only when the solution has multiple projects with genuinely different local rules.
4. Install MCAF governance skills (`mcaf-*`) for process areas and implementation-focused catalog skills for framework work. Check [references/skill-map.md](references/skill-map.md) for overlap before adding duplicate surfaces.
5. Route to the narrowest MCAF skill once the governance concern is clear:
| Concern | Skill |
|---------|-------|
| Delivery workflow and feedback loops | `mcaf-agile-delivery` |
| Developer onboarding and local inner loop | `mcaf-devex` |
| Durable docs structure and source-of-truth placement | `mcaf-documentation` |
| Executable feature behaviour docs | `mcaf-feature-spec` |
| Human review for large AI-generated drops | `mcaf-human-review-planning` |
| ML/AI product delivery process | `mcaf-ml-ai-delivery` |
| Explicit quality attributes and trade-offs | `mcaf-nfr` |
| Branch, merge, and release hygiene | `mcaf-source-control` |
| Design-system, accessibility, front-end direction | `mcaf-ui-ux` |
6. Scaffold repo-native documentation:
```
docs/
├── Architecture.md
├── Features/
├── ADR/
├── Testing/
├── Development/
└── Operations/
```
7. Encode the non-trivial task flow in `AGENTS.md`: `<slug>.brainstorm.md` then `<slug>.plan.md` then implementation and validation.
8. Treat verification as part of done: tests, analyzers, formatters, coverage, and any architecture or security gates the repo configured.
```mermaid
flowchart LR
A["Adopt MCAF"] --> B["Root AGENTS.md"]
B --> C{"Multi-project?"}
C -->|Yes| D["Project-local AGENTS.md"]
C -->|No| E["Root policy only"]
B --> F["Install mcaf-* governance skills"]
B --> G["Install implementation-focused skills"]
D --> H["Document boundaries and commands"]
E --> H
F --> I["Repo-native docs scaffolds"]
G --> J[".NET implementation guidance"]
H --> K["Run full quality pass"]
I --> K
J --> K
```
## Deliver
- repository-ready MCAF adoption with clear root and local `AGENTS.md` responsibilities
- correct split between `mcaf-*` governance and implementation-focused skills
- repo-native docs and verification expectations instead of chat-only instructions
## Validate
- root `AGENTS.md` exists at the repository or solution root
- project-local `AGENTS.md` files exist only where genuinely needed
- repo documents exact build, test, format, analyze, and coverage commands
- durable docs exist for architecture and behavior, not only inline comments
- non-trivial work follows the brainstorm-to-plan flow before implementation
- the full quality pass is part of done, not only a narrow happy-path test run
## References
- [references/adoption.md](references/adoption.md) - canonical MCAF entry points, bootstrap rules, and the local-mirror boundary between governance and implementation skills
- [references/skill-map.md](references/skill-map.md) - MCAF catalog map with overlap-vs-new split for precise routingBuild, debug, modernize, or review ASP.NET Core applications with correct hosting, middleware, security, configuration, logging, and deployment patterns on current .NET. USE FOR: working on ASP.NET Core apps, services, or middleware; changing auth, routing, configuration, hosting, or deployment behavior; deciding between ASP.NET Core sub-stacks. DO NOT USE FOR: unrelated stacks; generic tasks that do not need this specific guidance. INVOKES: inspect the repository context, edit targeted files, and run relevant build, test, lint, or validation commands when changes are made.
Build, upgrade, and operate .NET Aspire 13.3.x application hosts with current CLI, AppHost, ServiceDefaults, integrations, dashboard, testing, and Azure deployment patterns for distributed apps. USE FOR: Aspire.AppHost.Sdk, Aspire.Hosting.*, DistributedApplication.CreateBuilder, WithReference, WaitFor, AddProject, AddRedis, AddPostgres, aspire run, aspire init, aspire. DO NOT USE FOR: unrelated stacks; generic tasks that do not need this specific guidance. INVOKES: inspect the repository context, edit targeted files, and run relevant build, test, lint, or validation commands when changes are made.
Build, review, or migrate Azure Functions in .NET with correct execution model, isolated worker setup, bindings, DI, and Durable Functions patterns. USE FOR: working on Azure Functions in .NET; migrating from the in-process model to the isolated worker model; adding Durable Functions, bindings, or host configuration. DO NOT USE FOR: unrelated stacks; generic tasks that do not need this specific guidance. INVOKES: inspect the repository context, edit targeted files, and run relevant build, test, lint, or validation commands when changes are made.
Build and review Blazor applications across server, WebAssembly, web app, and hybrid scenarios with correct component design, state flow, rendering, and hosting choices. USE FOR: building interactive web UIs with C# instead of JavaScript; choosing between Server, WebAssembly, or Auto render modes; designing component hierarchies and state. DO NOT USE FOR: unrelated stacks; generic tasks that do not need this specific guidance. INVOKES: inspect the repository context, edit targeted files, and run relevant build, test, lint, or validation commands when changes are made.
Maintain or migrate EF6-based applications with realistic guidance on what to keep, what to modernize, and when EF Core is or is not the right next step. USE FOR: EF6 codebases; runtime versus ORM migration decisions; EDMX, code-first, ObjectContext, and legacy data-access review. DO NOT USE FOR: unrelated stacks; generic tasks that do not need this specific guidance. INVOKES: inspect the repository context, edit targeted files, and run relevant build, test, lint, or validation commands when changes are made.
Design, tune, or review EF Core data access with proper modeling, migrations, query translation, performance, and lifetime management for modern .NET applications. USE FOR: DbContext, migrations, model configuration, EF queries, tracking, loading, performance, transactions, and EF6 migration decisions. DO NOT USE FOR: unrelated stacks; generic tasks that do not need this specific guidance. INVOKES: inspect the repository context, edit targeted files, and run relevant build, test, lint, or validation commands when changes are made.
Build, review, or migrate .NET MAUI applications across Android, iOS, macOS, and Windows with correct cross-platform UI, platform integration, and native packaging assumptions. USE FOR: working on cross-platform mobile or desktop UI in .NET MAUI; integrating device capabilities, navigation, or platform-specific code; migrating Xamarin.Forms or aligning. DO NOT USE FOR: unrelated stacks; generic tasks that do not need this specific guidance. INVOKES: inspect the repository context, edit targeted files, and run relevant build, test, lint, or validation commands when changes are made.
Use ML.NET to train, evaluate, or integrate machine-learning models into .NET applications with realistic data preparation, inference, and deployment expectations. USE FOR: ML.NET integration; local model training or retraining; inference pipelines, model loading, evaluation, and deployment review. DO NOT USE FOR: unrelated stacks; generic tasks that do not need this specific guidance. INVOKES: inspect the repository context, edit targeted files, and run relevant build, test, lint, or validation commands when changes are made.