Skill
ArchUnitNET for .NET
Use the open-source free `ArchUnitNET` library for architecture rules in .NET tests.
dotnet skills install archunitnet
MCAF: Non-Functional Requirements
Apply MCAF non-functional-requirements guidance to capture or refine explicit quality attributes such as accessibility, reliability, scalability, maintainability, performance, and compliance. Use when a feature or architecture change needs explicit quality attributes and trade-offs.
Trigger On
- a feature or architecture change needs explicit quality attributes
- a team is using vague words like "fast", "reliable", or "secure" without measurable meaning
- docs, ADRs, and tests are out of sync on quality expectations
Workflow
- Decide which quality attributes materially affect the change.
- Turn vague goals into explicit requirements, constraints, or testable expectations.
- Link NFRs to feature docs, ADRs, and verification when they affect design or rollout.
- Use only the specific reference files that match the active quality attribute.
Deliver
- explicit NFRs for the changed area
- docs or ADRs that describe measurable quality attributes
- better alignment between architecture, testing, and operations
Validate
- each chosen NFR is measurable or at least falsifiable
- the selected attributes are the ones that actually drive design trade-offs
- verification and operational expectations are linked where needed
Load References
- pick only the exact file for the active NFR: accessibility, reliability, performance, scalability, compliance, maintainability, and so on
Related skills
Skill
MCAF: Documentation
Apply MCAF documentation guidance for docs structure, navigation, source-of-truth placement, and writing quality.
dotnet skills install mcaf-documentation
Skill
MCAF: Feature Spec
Apply MCAF feature-spec guidance to create or update a feature spec under `docs/Features/` with business rules, user flows, system behaviour, verification, and Definition of Done.
dotnet skills install mcaf-feature-spec