monorepo-agent-setup

To synchronize agent configurations in a monorepo, you mirror rules, agents, and hook wiring between the .cursor and .claude directories using a standardized sync policy for project-wide instructions and path-scoped rules.

Keeping .cursor and .claude rules consistent requires applying a strict sync policy that mirrors configuration files and rule sets, ensuring project instructions and subagent definitions remain identical across both environments.

Adding a path-scoped rule for a package involves placing the instruction file in the correct taxonomy layer and mirroring it in both .cursor/rules and .claude/rules directories with the appropriate frontmatter applied.

Yes, the monorepo configuration sync approach explicitly supports MCP server definitions, alongside rules, agents, and hook wiring, to ensure automated development workflows remain consistent across Cursor and Claude environments.

Agent instructions diverge when there is no standardized policy to mirror rules and hook wiring between .cursor and .claude directories, leading to fragmented project-wide instructions and inconsistent path-scoped rules across environments.

You need to synchronize agent configuration files when maintaining automated development workflows in a monorepo, ensuring that taxonomy placement, subagents, and project-wide instructions remain consistent across both Cursor and Claude environments.