What problem does it solve? Moving a Three.js 3D integration into a new or empty Blazor WebAssembly project is error-prone: CDN dependencies break offline requirements, JS interop cleanup is often skipped, and GitHub Pages deployment fails without base href and SPA routing fixes. This Skill provides a proven workflow to rebuild or migrate that integration even when the original source code is unavailable. ## Core Features & Use Cases - Automated Three.js Vendoring: Adds an MSBuild target to the .csproj that installs Three.js via npm and copies the module and addons into wwwroot/lib/three during Build and Publish. - JS Bridge and Razor Page Generation: Creates a three-bridge.js ESM module with initThree, updateConfig, and disposeThree lifecycle functions, plus Razor pages that import it via Navigation.BaseUri and dispose resources with IAsyncDisposable. - GitHub Pages Deployment: Replicates a workflow with Node setup, dotnet publish, base href rewriting, 404.html for SPA routing, and .nojekyll. - Use Case: You want to reproduce a 3D text page from an old Blazor repo in a fresh .NET 10 project with fully offline assets. The Skill generates the csproj target, bridge module, Razor page, and workflow from scratch, then validates the build and vendored files. ## Quick Start Ask the AI to migrate the Three.js 3D page into a new Blazor WebAssembly project with offline vendoring and GitHub Pages deployment.