How do I install the Vengeance UI skill?

Run npx skillmds@latest add ashutoshx7/vengeance-ui in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Vengeance UI safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Vengeance UI?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Vengeance UI free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Vengeance UI?

ashutoshx7 (@ashutoshx7) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Vengeance UI by ashutoshx7 — Agent Skill

Name: Vengeance UI
Author: ashutoshx7

Vengeance UI

Install and compose VengeanceUI animated React/Tailwind components via the shadcn registry and vengeanceui-mcp. Use when building landing pages, heroes, buttons, navs, text motion, or when the user mentions VengeanceUI, vengenceui.com, or npx shadcn add with the Vengeance registry.

ashutoshx7 d60f2ae 4 files · 4.5 KB Updated Sep 17, 2026

File contents

VengeanceUI

Prefer existing registry components over inventing similar UI.

For Next.js API quirks in this repo, see AGENTS.md.

Workflow

Clarify the UI need (hero CTA, text motion, nav, card, background, …).
Call MCP search_components (optional category filter).
Call MCP get_component for props, usage, and deps.
Call MCP get_install_command (or install yourself).
Adapt the usage snippet; do not rewrite the component unless asked.

If MCP is unavailable, use the install URL pattern in install.md and read public/r/{componentName}.json / docs pages — still do not invent duplicates of catalog components.

MCP tools

Tool	Purpose
`list_categories`	Catalog categories
`search_components`	Find by name/slug/description
`get_component`	Props, usage, deps (slug or componentName)
`get_install_command`	`shadcn add` URL for a package manager
`get_component_source`	Live registry JSON + source
`list_registry`	All registry names (includes blocks)

Slug vs componentName

slug — docs/URL key (e.g. my-animated-button)
componentName — registry install name (e.g. animated-button)

get_component / get_install_command accept either. Always install with componentName.

Rules

Install via shadcn + Vengeance registry URL — see install.md.
Follow conventions.md ("use client", cn, theme tokens, motion).
Keep the skill small; never paste the full catalog into context — use MCP.
Walkthroughs: examples.md.

---name: vengeance-uidescription: Install and compose VengeanceUI animated React/Tailwind components via the shadcn registry and vengeanceui-mcp. Use when building landing pages, heroes, buttons, navs, text motion, or when the user mentions VengeanceUI, vengenceui.com, or npx shadcn add with the Vengeance registry.---# VengeanceUIPrefer existing registry components over inventing similar UI.For Next.js API quirks in this repo, see [AGENTS.md](../../../AGENTS.md).## Workflow1. Clarify the UI need (hero CTA, text motion, nav, card, background, …).2. Call MCP **`search_components`** (optional category filter).3. Call MCP **`get_component`** for props, usage, and deps.4. Call MCP **`get_install_command`** (or install yourself).5. Adapt the usage snippet; do **not** rewrite the component unless asked.If MCP is unavailable, use the install URL pattern in [install.md](install.md) and read `public/r/{componentName}.json` / docs pages — still do not invent duplicates of catalog components.## MCP tools| Tool | Purpose ||------|---------|| `list_categories` | Catalog categories || `search_components` | Find by name/slug/description || `get_component` | Props, usage, deps (slug **or** componentName) || `get_install_command` | `shadcn add` URL for a package manager || `get_component_source` | Live registry JSON + source || `list_registry` | All registry names (includes blocks) |## Slug vs componentName- **slug** — docs/URL key (e.g. `my-animated-button`)- **componentName** — registry install name (e.g. `animated-button`)`get_component` / `get_install_command` accept either. Always install with **componentName**.## Rules- Install via shadcn + Vengeance registry URL — see [install.md](install.md).- Follow [conventions.md](conventions.md) (`"use client"`, `cn`, theme tokens, motion).- Keep the skill small; never paste the full catalog into context — use MCP.- Walkthroughs: [examples.md](examples.md).

Frequently asked questions