Codebelt
v0.9.0

.NET Segregated Assets

Preserve familiar static-file authoring while separating deployed asset delivery from the business application.

.NET Engineering 0 installs ASP.NET Core web apps Docker Compose .NET 10 SDK or later PowerShell 7+
Open on Skills.sh View source

Overview

.NET Segregated Assets moves application-owned static delivery out of an ASP.NET Core deployment without moving authoring out of wwwroot. The web application stops shipping those files, and a separate codebeltnet/web-cdn-origin:2.0.0 container serves the published asset set from /cdnroot.

The skill keeps asset ownership explicit. Application CSS, scripts, branding, and media remain App assets; reusable frameworks, fonts, and design-system packages remain shared CDN assets. Razor declares that ownership, while configuration selects the application, local origin, or deployed host.

Concepts

  • Authoring and delivery stay separate: developers keep the normal wwwroot workflow while deployment uses a dedicated static origin.
  • App and CDN ownership: application-specific files and shared packages use distinct URL and configuration paths.
  • Existing abstractions win: the migration reuses Cuemon App/CDN TagHelpers or a suitable project abstraction instead of adding a competing URL layer.
  • Deterministic topology checks: publish exclusion, Static Web Assets, container placement, Compose wiring, and artifact-first image inputs are verified rather than inferred from configuration.

Installation

npx skills add https://github.com/codebeltnet/agentic --skill dotnet-segregated-assets

Usage guidance

Use this skill when an ASP.NET Core application should stop serving or shipping its own deployed static files, or when an existing App/CDN setup needs to be reconciled with a segregated asset origin. It inspects the application first, classifies App versus shared CDN references, and preserves framework and generated Static Web Assets.

The local workflow keeps the ordinary project profile intact and adds an opt-in Docker Compose topology for the application and asset origin. Production uses the same published application artifact and a dedicated asset image. Existing Cuemon package versions are resolved from NuGet during the current plan rather than copied from examples.