One big .cursorrules file for your whole monorepo is why Cursor Agent Mode silently ignores your rules. Here is the scoped .mdc migration that fixes it.
Your .cursorrules file is not broken. It is just being applied to the wrong problem.
Most developers write one big .cursorrules file and put it at the root of their monorepo. One file. Every rule. Every stack. Every service — frontend, backend, infra, scripts, tests — all governed by the same blob of instructions.
Then they switch to Cursor Agent Mode and discover the rules are being ignored.
Not partially ignored. Silently, completely ignored.
Here is why.
If Cursor rules aren't working, you're not alone. You wrote .cursor/rules (or a legacy .cursorrules...
Your .cursorrules file is probably not working the way you think it is. Not because Cursor is broken...
Most Cursor rules I see online are wish lists. "Write clean code." "Follow best practices." "Be...
You did the responsible thing. You added a rules file for your AI tool, .cursorrules or CLAUDE.md or...
Cursor is fast. But left unchecked, it expands PRs. Here are the three .mdc rules I use to keep that...
Agent Skills are the open standard (agentskills.io) for packaging team-specific instructions that any...
