dotnet-engineering

To load canonical .NET engineering rules without duplication, use a discovery-only wrapper that initializes the authoritative surface first and defers deeper context loading. This ensures a single source of truth for project guidance.

The best way to access authoritative .NET engineering references is through a canonical surface discovery mechanism. It loads templates and validation rules without altering the active agent context, providing a stable entry point for developers.

A discovery wrapper is needed for .NET engineering knowledge because it disambiguates the canonical surface, preventing duplicated guidance. It applies discovery-only operation to ensure rules and provenance context are pulled only as needed.

Yes, you can use the .NET engineering surface wrapper without altering your active agent context. It operates as a stable entry point that initializes rules and references while maintaining your current environment state.

You should defer deeper context loading during .NET project setup when using a discovery-only operation approach. This prevents duplicating pack guidance by loading the canonical engineering surface first and pulling deeper rules only as required.

Yes, the .NET engineering surface provides validation rules for code generation. It loads templates, validation rules, and references through a discovery wrapper to guide project setup and code generation processes.