Vector Vesper Docs
Build motion that belongs in the product.
Vector Vesper is a library of editable motion components, a runtime that decides when motion runs and at what quality, and tools that help people and coding agents use both correctly.
1. Initialize your project and add a component:
npx vectorvesper init
npx vectorvesper add scroll-highlighter2. Import the component directly into your React tree:
import { ScrollHighlighter } from "@/components/vv/scroll-highlighter";
export default function Hero() {
return <ScrollHighlighter text="Vector Vesper motion toolkit" />;
}Tools and workflows
Components are only useful when they fit the rest of the page. The CLI and MCP server make that workflow repeatable—from adding source to writing your own on the runtime and checking what came out.
CLI Reference
npx vectorvesperInitialize a project, add owned component source, and keep installed components current.
MCP Server
Agent IntegrationBuild components of your own on the runtime: which primitive fits, how to wire it, and a review of what your agent wrote.
Runtime Diagnostics
DevToolsInspect subscriber cost, frame pressure, and quality shedding before changing performance code.
How to use these docs
Get started
Install the CLI and add your first component to a Next.js or Vite project.
Learn the runtime
Understand the shared frame loop, input layer, and performance budget behind live motion.
Browse components
Find free and Pro components, inspect their requirements, and install their source into your project.
Use the guides
Set up your framework, Tailwind, accessibility, theming, and maintenance workflow.
Browse the CLI reference
Look up each command for installing, inspecting, updating, and removing components.
Using a coding agent?
Run npx vectorvesper init to add the shared-runtime rule to your project. Connect MCP when the agent is building something of your own: it plans the motion, hands over the runtime contracts, and reviews the file before it ships.