Give better context
Use project rules, AGENTS.md, and CLAUDE.md
Rules turn repeated corrections into project infrastructure. FireCursor can browse, create, and edit Cursor rules plus AGENTS.md and CLAUDE.md guidance from Android.
Quick answer
The shortest useful version.
Put stable repository facts and operating constraints in the provider-appropriate rule file, keep instructions scoped to their directory, avoid secrets, and verify a new session actually follows them.
Step by step
Do this with confidence.
- 01
Choose the right scope
Use root guidance for repository-wide rules and nested guidance for a specific subtree. Avoid duplicating instructions at every level.
- 02
Write operationally
Name the commands, conventions, safety boundaries, source-of-truth files, and verification expectations an agent can act on.
- 03
Keep providers honest
Use .cursor/rules for Cursor-specific behavior, AGENTS.md for compatible agent scope, and CLAUDE.md for Claude-specific context.
- 04
Test the rule
Start a fresh bounded run and ask the agent to summarize the applicable instructions before it edits.
What belongs in durable guidance
- Build, test, lint, and release commands
- Directory ownership and generated-file boundaries
- Architecture contracts and source-of-truth locations
- Security and destructive-action constraints
- The expected evidence in a final handoff
What does not belong
Do not store credentials, pairing tokens, temporary task details, personal preferences unrelated to the repository, or claims that are no longer true. Rules are powerful because agents may apply them repeatedly.
Treat rule edits like source changes: review the diff and confirm the intended scope.