What problem does it solve? Cursor IDE integration involves several distinct surfaces with subtle, easy-to-break details: the Cursor 1.7+ hooks.json schema differs from Claude Code and Codex, .cursor/rules/.mdc files have four activation modes controlled by frontmatter, MCP server registration requires correct mcp.json entries, and the first-party extension has its own build and contribution model. This Skill consolidates authoritative guidance for all of these so changes to the Cursor surface stay correct, idempotent, and consistent. ## Core Features & Use Cases - Cursor hooks lifecycle wiring: Documents the six lifecycle events (sessionStart, beforeSubmitPrompt, preToolUse, postToolUse, afterAgentResponse, stop/sessionEnd), the Cursor-specific hooks.json shape, and the idempotent, Windows-safe merge logic in install-cursor.ts. - Rule file authoring: Explains .cursor/rules/.mdc frontmatter (description, globs, alwaysApply), the four activation modes, glob syntax, and anti-patterns such as overusing alwaysApply or reintroducing .cursorrules. - MCP and extension integration: Covers registering the Hivemind stdio MCP server in project or global mcp.json, plus the extension's manifest contributions, webpack build, and activation flow. - Use Case: When asked to add a new Cursor hook or fix a rule that is not firing, load this Skill to check the exact hooks.json entry shape and the rule's activation-mode frontmatter before editing. ## Quick Start Ask the agent to wire the Cursor hooks for Hivemind or to author a new .cursor/rules/*.mdc rule file, and it will consult the matching guide before making changes.
