custom-framework-arch

What problem does it solve?

This skill helps teams design and organize a multi-library .NET framework repository with clear package boundaries, consistent layout, and public distribution readiness.

Core Features & Use Cases

• Package taxonomy and boundaries: split into focused packages such as Abstractions (optional) and a main Core or Framework package, with feature modules to follow.
• Standardized repository layout: adopt a consistent src/, test/, samples/, and docs/ structure with one project per package and clear directory ownership.
• API layering and packaging rules: enforce stable public contracts, inward dependencies, and dedicated extensions to support clean consumption.
• Centralized build and packaging configuration: consolidate settings in Directory.Build.props and Directory.Packages.props, and include repository metadata and symbol publishing.
• Governance and documentation: establish quality gates, changelogs, migration notes, and post-change documentation routines.
• Real-world usage: scaffold a multi-library solution for a new framework and prepare it for NuGet publishing with versioning and SourceLink.

Quick Start

Define the target framework name, choose main package naming, and scaffold a multi-library solution layout with consistent package boundaries and packaging rules.