AI Assistant Skill

What it provides

blazorbit-user.skill is a zip archive following the public Anthropic Skill format (a SKILL.md at the root with optional references/ and scripts/ folders). It teaches an agent how to:

• Pick the right component for a task (buttons, inputs, dialogs, data-grid, …).
• Use the canonical parameter names, types, and presets — no hallucinated APIs.
• Apply the BlazOrbit theming pipeline (--palette-*, --bob-*, --bob-inline-*).
• Register variants, wire forms with EditContext, and use the modal/toast services correctly.
• Honor accessibility rules baked into every component.

The bundle is regenerated against each release, so its component catalog stays in lock-step with the published library — no drift between the agent's mental model and the actual API surface.

Download

The skill bundle is attached to every BlazOrbit GitHub release/preview. Download the file matching version and keep it next to your agent configuration.

Download blazorbit-user.skill ↗

curl -L -o blazorbit-user.skill https://github.com/BlazOrbit/BlazOrbit/releases/latest/download/blazorbit-user.skill

Invoke-WebRequest -Uri https://github.com/BlazOrbit/BlazOrbit/releases/latest/download/blazorbit-user.skill -OutFile blazorbit-user.skill

Install per agent

Claude Code

Claude Code reads skills from ~/.claude/skills/ on macOS/Linux or %USERPROFILE%\.claude\skills\ on Windows. Extract the bundle into a folder named after the skill:

# Linux / macOS
mkdir -p ~/.claude/skills/blazorbit-user
unzip -o blazorbit-user.skill -d ~/.claude/skills/blazorbit-user

# Windows (PowerShell)
$dir = Join-Path $HOME '.claude\skills\blazorbit-user'
New-Item -ItemType Directory -Force -Path $dir | Out-Null
Expand-Archive -Path blazorbit-user.skill -DestinationPath $dir -Force

Restart Claude Code and confirm the skill is loaded with /skills. Trigger it by mentioning a BlazOrbit component in any prompt.

Kimi (Moonshot)

Kimi consumes the same skill format. Upload the file through the "Skills" tab in the Kimi web UI, or drop the extracted folder under the Kimi configuration directory documented at kimi.moonshot.cn/docs.

OpenCode

OpenCode loads skills from its skills/ workspace folder. Extract the bundle and reference the directory in your OpenCode configuration (opencode.json):

mkdir -p ./skills/blazorbit-user
unzip -o blazorbit-user.skill -d ./skills/blazorbit-user

# In opencode.json:
# {
#   "skills": { "path": "./skills" }
# }

Generic loader

Any agent that can ingest the public Anthropic Skill format works. The contract is:

• The archive root contains SKILL.md with YAML frontmatter (name, description).
• Side files live under references/ (read on demand) and scripts/ (executed on request).
• The agent loads the skill when its description matches the user's request.

Extract the archive somewhere your agent scans for skills, then point its loader at that directory.

mkdir blazorbit-user
unzip blazorbit-user.skill -d blazorbit-user
# Now point your agent's skill loader at the blazorbit-user/ directory.

Verify the agent loaded it

Drop this prompt into a fresh chat. A correctly-loaded skill answers with the canonical parameter names, not the agent's training-set guesses:

What parameter does BOBButton expose to render a leading icon?

Expected answer mentions LeadingIcon of type IconKey?, and points to BOBIconKeys.MaterialIconsOutlined.

Update

Every BlazOrbit release publishes a fresh skill bundle. Re-download and overwrite the extracted folder; no migration needed.

curl -L -o blazorbit-user.skill \
  https://github.com/BlazOrbit/BlazOrbit/releases/latest/download/blazorbit-user.skill

# Then re-extract over the existing folder (Claude Code example):
unzip -o blazorbit-user.skill -d ~/.claude/skills/blazorbit-user

For contributors — build locally

The skill is generated by reflecting over the BlazOrbit assemblies, so it stays accurate without manual upkeep. Run the regenerator after building the library:

dotnet build BlazOrbit.slnx -c Debug
./.agents/skills/blazorbit-user/scripts/regenerate-skill.ps1 -Configuration Debug -SkipBuild

Then zip the resulting .agents/skills/blazorbit-user/ folder (excluding scripts/*.ps1 and scripts/*.cs) to produce a custom .skill file. The package-skill CI workflow does this automatically on every release.