ViteHub coding-agent skill
The public ViteHub skill helps coding agents build complete applications from current documentation and the application's installed package contract.
It keeps one compact proof loop in SKILL.md, then loads only the project-shape, feature, authority, host, or recovery references that match the task.
Install the skill
Run the skills CLI from your project:
npx skills add https://vitehub.dev
The CLI discovers the published vitehub skill and installs it for the supported coding agents you select.
Run npx skills list to inspect installed project skills.
Follow one proof loop
The skill orients in the current project, routes the smallest matching reference set, validates every planned import and option against installed exports and types, builds a coherent file set, and proves every requested behavior through its real runtime path.
The bundled references teach reusable composition rather than copying the API reference. They cover project shapes, preview contracts, Server Primitives, framework composition, Agent Definitions and Drivers, Workspaces and Sources, Channels and Triggers, Capabilities, orchestration, Boxes and hosts, proof and recovery, and public project patterns.
Links inside a reference are selection menus. The agent opens the smallest live raw page for the current behavior instead of loading the full reference library or documentation set.
Ask for an outcome
The skill activates from normal ViteHub requests. State the result you want and include any host or runtime constraint.
| Task | Example prompt |
|---|---|
| Server primitive | Add ViteHub KV to this route and prove that a value survives a restart. |
| Agent | Create a provider-backed review Agent with repository context and invoke it locally. |
| Host boundary | Build this ViteHub application for Cloudflare and inspect its Provider Output. |
The skill selects one primary product lane, reads only matching references and the smallest live docs pages, checks installed exports and types, and reports the proof for each requested behavior. When documentation and an installed version differ, the installed contract controls the implementation and the agent reports the mismatch.
Keep instruction sources distinct
ViteHub uses several instruction sources for different actors. Keeping them separate prevents repository guidance from leaking into runtime Agent behavior.
| Source | Audience | Purpose |
|---|---|---|
| Public ViteHub skill | Coding agents building a ViteHub application | Routes project patterns through live docs, installed contracts, explicit authority, and runtime proof. |
Repository AGENTS.md | Coding agents contributing to a repository | Defines local development rules and project boundaries. |
| Agent Driver Instructions | Agents that run inside an application | Defines model-facing runtime behavior. |
Agent-local skills/ | Provider-backed Agent Invocations | Automatically installs Skills owned by a folder Agent Definition. |
skills() Capability | ViteHub Agent Invocations | Makes Workspace-backed or external Source Skills available to the Agent. |
Agent-local Skills require a folder Definition. Place them beside server/agents/<name>/agent.ts under server/agents/<name>/skills/<skill>/SKILL.md. A flat Definition such as server/agents/review.ts cannot own a sibling Skill tree; move it to server/agents/review/agent.ts when it needs colocated Skills.
Use the docs fallback
When a coding environment cannot install skills, start from llms.txt and load one raw Markdown page.
Keep the page URL with the supplied context so the agent can report which contract it followed.