Coding agents
Coding agents such as Cursor work best when they know how your project is built. void init gives them that context when it creates a project.
On this pageSee what void init adds for coding agents · Install the SDK skills so an agent can read the right docs · Keep agent instructions in AGENTS.md up to date
Set up agent support
Now you will run void init. It sets up coding agents as part of project setup.
npx void initExample output: void init asks a few setup questions, then writes the project files.
New projects get a short AGENTS.md. It explains the SDK and where to find its docs.
In an existing project, the SDK asks before it creates, appends to or updates AGENTS.md. Your instructions outside the SDK section stay as they are. If you decline, the file does not change. CI and non-interactive runs never change instructions in an existing project.
Bundled docs
The full Markdown docs ship in node_modules/void/docs/. Agents can read them directly, even without a skill. Point them to these files first:
guide/quickstart.mdfor setup.reference/cli.mdfor commands.
Agent skills
Skills point your agent to the commands and docs it needs for a task. They link to the installed void package. The guidance always matches the SDK version your app uses.
The SDK ships two skills:
void: commands and docs for app development.migrate-vite-cloudflare-to-void: migration skill for converting existing@cloudflare/vite-pluginapps to the SDK.
void init links the skills when it finds a supported agent's configuration. For example, Claude Code uses .claude/skills/ and Codex uses .agents/skills/.
Globally installed skills fall back to the docs in their own SDK package when there is no local install. If no agent is found, the instructions still point to the bundled docs.
