Cursor rules guide
Project rules and skills that steer IDE agents—scope, tone, and test discipline.
Cursor rules (project rules under .cursor/rules/) shape how the IDE agent edits your repository: precedence, git safety, and domain-specific canon.
Effective rule patterns
- One concern per file — canonical URLs, git remote policy, waiting-on-user secrets
- Always-apply vs globs — reserve always-on rules for safety; scope product rules to paths
- Actionable commands — name
pnpmfilters, worktrees, deploy scripts you actually use - Negative space — list domains or features you refuse to create (trademarks, affiliate patterns)
Rules are not a spec
Rules set habits; a task still needs a spec with acceptance tests for non-trivial work. See spec-driven development.
Related
We do not operate third-party “Cursor agency” directories—those belong to separate directory sites, not PunkSolid hire pages.