What Cursor Consumes
Pluxx builds the Cursor target intodist/cursor/. Cursor consumes:
.cursor-plugin/plugin.jsonskills/commands/agents/rules/whenplatforms.cursor.rulesis configuredhooks/hooks.jsonmcp.jsonAGENTS.md
.cursor-plugin/plugin.json. Pluxx wires plugin-native rules, hooks, skills, commands, agents, and MCP config from that root.
Build And Install
~/.cursor/plugins/local/<plugin>
--trust or confirm the trust prompt during install.
Agent-Driven Refinement
Build and install are deterministic. Cursor only does model work when you explicitly run an agent pass:- iterative instruction cleanup
- taxonomy review
- host-specific scaffold review
Cursor-Specific Caveats
- Headless Pluxx runs target the official Cursor CLI binary
agent. Older installs that only exposecursor-agentare still supported as a fallback. - Real Cursor CLI runs require Cursor auth. Use your normal Cursor CLI login flow or provide
CURSOR_API_KEYfor scripted runs. - Use the Cursor app to verify plugin presence, installed skills, and commands. Cursor CLI is the runner surface for Pluxx agent passes, not the strongest plugin-discovery proof surface.
- Cursor plugin hooks live inside
hooks/hooks.jsonin the plugin bundle. Project hooks in.cursor/hooks.jsonare a separate surface and are not auto-installed by Pluxx. - Cursor subagents under
.cursor/agentsor~/.cursor/agentsare also separate from the plugin bundle. Pluxx installs pluginagents/, not project-level subagents.