javfonsecaj avatar

javfonsecaj

Community

@cfonseca23

5Followers
|
57Public Repos
|
1Published Skills

Skill for migrating Three.js integrations in Blazor WebAssembly to other .NET projects, preserving JS bridge, Razor pages, and GitHub Pages deployment.

Skills Distribution
DomainDeveloper To...Blazor WebAssembly.. (40%)Three.js 3D Integr.. (30%).NET Project Migra.. (20%)GitHub Pages Deplo.. (10%)

Agent Skills by javfonsecaj

Showing 1 vetted skills indexed across 1 GitHub repositories.

Frequently Asked Questions About javfonsecaj

FAQPage Schema
What tasks can I accomplish with the blazor-threejs-migration skill?

You can reconstruct or migrate a Three.js integration embedded in Blazor WebAssembly into another .NET project, even without access to the original source code. It preserves local vendoring, the JS bridge, the Razor page, cleanup steps, and consistent deployment to GitHub Pages.

Who is the blazor-threejs-migration skill designed for?

It targets .NET developers and front-end engineers working with Blazor WebAssembly who need to port Three.js 3D visualizations between projects, particularly when the destination project lacks access to the original codebase.

How does the migration and deployment process work?

The skill rebuilds the Three.js integration inside the target .NET project, maintaining local vendoring of libraries, the JavaScript interop bridge, and the Razor page. It then handles cleanup and produces a consistent deployment to GitHub Pages.

What license does the blazor-threejs-migration skill use and what does it cost?

The skill is released under the MIT license, making it free to use, modify, and redistribute in both personal and commercial projects. There is no cost associated with adopting it.

What prerequisites are needed to use this skill?

You need a Blazor WebAssembly environment within the .NET ecosystem and a target .NET project. The skill works even when the destination project has no access to the original source code, and deployment targets GitHub Pages.