Agent Kit

Teach your agent.

Markdown guides that show your coding agent how to find, install and combine Hyperblur items the right way, so a whole page comes out coherent.

What it is#

The Agent Kit is twenty guides. They are plain Markdown files, delivered through the same private registry as the premium items, so you install them with the shadcn CLI or the shadcn MCP server.

KindInstalls toHow you use it
Skill~/.claude/skills/<name>/SKILL.mdLoaded by your agent on its own when a task matches.
Prompt~/.claude/commands/hyperblur-<name>.mdA slash command you run: /hyperblur-<name>.
Recipe~/docs/hyperblur/recipes/<name>.mdA build guide you point your agent at.

Files land in your home folder, not in the project, so one install serves every project on your machine.

Install#

Set up the @hyperblur-pro registry once, then add a guide by its slug. Start with the main skill.

terminal
npx shadcn@latest add @hyperblur-pro/skill-hyperblur

The shadcn CLI accepts several items in one command, so you can add the four skills together.

terminal
npx shadcn@latest add \
  @hyperblur-pro/skill-hyperblur \
  @hyperblur-pro/skill-dark-premium \
  @hyperblur-pro/skill-editorial-type \
  @hyperblur-pro/skill-motion-restraint

Restart your agent session after installing so it picks up new skills and commands. The slugs of all twenty guides are in the lists below.

Skills#

Skills are rules your agent loads automatically. The main one explains how to search the free and Pro catalogs, the exact install commands and where files land. The other three are design directions: dark premium interfaces, type-led editorial pages and restrained motion.

Prompts#

A prompt is a ready-to-run slash command that builds one kind of page from catalog items. It lists the sections in order, the editable base copy, the exact items and install commands for each section and the acceptance criteria. Install it, then run it with a short brief.

terminal
npx shadcn@latest add @hyperblur-pro/prompt-saas-landing

The command name is /hyperblur- followed by the guide name. Whatever you write after it becomes the brief: product name, one-line pitch, audience and accent color. If you leave it empty, the prompt uses its base copy and your agent lists every placeholder it kept.

your agent
/hyperblur-saas-landing Acme, a status page for small teams, audience: founders, accent: teal

Recipes#

A recipe is a step-by-step build guide with the install order, the files, the imports and working code for one kind of page or screen. Prompts decide what to build, recipes show how. Point your agent at the file.

your agent
Follow ~/docs/hyperblur/recipes/app-shell.md and build the app shell for this project.

Good to know#

  • Every prompt and recipe states the minimum plan its catalog items need, from Free up to Pro. The kit itself comes with Pro and above. A 403 from the registry means an item sits outside your plan.
  • The commands and skill folders are written for Claude Code. The files are plain Markdown, so you can read them or adapt them for another agent.

Related

For prompts that come from effect pages, the MCP servers and the Claude Code plugin, see Agents.