What problem does it solve? Cursor IDE exposes many independent configuration surfaces (rules, skills, hooks, settings, MCP servers, Automations), and choosing the wrong one leads to misplaced files, duplicated guidance, and broken workflows. This Skill acts as a routing layer that tells the agent which surface to use, where files live, and how to drive Cursor from chat. ## Core Features & Use Cases - Configuration Surface Router: Decision tables and flowcharts map user intent to the right surface — project rules (.mdc), user rules, skills, hooks, settings.json, MCP servers, or Automations. - cursor-app-control MCP Operations: Covers workspace switching (move_agent_to_root, move_agent_to_cloned_root), project bootstrapping (create_project), user rule management (cursor_dialog), and Glass UI automation. - Directory Maps and Pitfall Guards: Documents user-level, project-level, and built-in skill stores, plus common mistakes like writing to ~/.cursor/skills-cursor/ or prefilling Automations with local MCP servers. - Use Case: A user asks to make the agent always run a linter before edits in their repo — the Skill routes this to a project hook in .cursor/hooks.json rather than a rule or skill, then defers to the built-in create-hook skill. ## Quick Start Ask the agent where a specific Cursor behavior should be configured, for example: where should I put a rule that makes the agent always use bun instead of npm across all my projects?
