Claude Skill

These docs are also packaged as a Claude Skill — a folder of instructions Claude loads when it recognizes you’re working on a Vite.NET integration.

Download the skill (.zip)

Installing it

Claude Code

Unzip the folder into your skills directory — .claude/skills/ inside a project to share it with your team through version control, or ~/.claude/skills/ to have it everywhere:

1. Extract the archive so the skill sits in its own folder:

   unzip vite-dotnet-skill.zip -d ~/.claude/skills/

   On Windows PowerShell:

   Expand-Archive vite-dotnet-skill.zip -DestinationPath $HOME\.claude\skills\

2. Restart Claude Code (or start a new session) so it picks up the new skill.

3. Check it loaded by asking Claude to list its available skills — vite-dotnet should be among them.

Claude apps

In the Claude desktop or web app, open Settings → Capabilities → Skills and upload the .zip as a custom skill. Claude then loads it automatically when a conversation involves Vite.NET.

Note

Uploading custom skills requires an eligible plan and the Skills capability enabled for your account or organization.

It's just markdown

A skill is a folder with a SKILL.md and supporting files. Read it, edit it, or trim it to your project’s conventions.

What’s in the archive

• Directoryvite-dotnet/

  • SKILL.md the overview Claude always reads
  • Directoryreferences/

    • setup.md install walkthrough + per-framework configs
    • plugin-and-manifests.md the Vite plugin and both manifest schemas
    • backend-api.md AddViteIntegration and the tag helpers
    • workflows.md dev, production, multiple SPAs
    • without-npm.md owning the integration without the npm package
    • migrating-from-v0.md the upgrade path
    • troubleshooting.md error messages and their real causes

SKILL.md is the entry point; Claude opens a reference file only when the task calls for it, so the detail costs nothing until it’s needed.

Using it

Once installed, no special invocation is needed — describe the task and Claude applies the skill:

• “Add a Svelte SPA to this Razor Pages project with Vite.NET.”
• “My page shows ‘Vite Dev Server Not Found’ — what’s wrong?”
• “Migrate this project from Vite.NET v0 to the manifest-driven version.”
• “Set up a second SPA at AdminApp and render it on its own page.”

Keeping it current

The skill is generated from this documentation and pinned to the same releases, currently 1.0.0 (NuGet) and 1.0.0 (npm). When you upgrade the packages, download it again so Claude’s instructions match the versions you’re on.