Cursor Feature Scope Lock
Free Cursor File Cursor text prompt. Copy and paste into Cursor. No signup required. — promtable
#build-with-ai #cursor #file #project-file #feature-scope-lock
# rules.md
## Purpose
This file configures Cursor for ship one feature without refactoring the surrounding app. Keep it in the repository root or the tool-specific rules directory so future AI coding sessions inherit the same safety and quality standards.
## Operating Rules
- Read the user request and inspect relevant files before editing.
- Keep the patch focused on the requested behavior.
- Preserve existing naming, architecture, state management, and test patterns.
- Do not add dependencies without explicit approval.
- Do not delete files or run destructive git commands.
- Do not change database schema, auth, payments, secrets, environment files, or deployment configuration unless explicitly requested.
- Do not fabricate analytics, traffic, AdSense, Search Console, view, click, or copy metrics.
## Workflow
1. Map the relevant entry points and data flow.
2. Identify the smallest safe change.
3. Edit only the required files.
4. Add or update focused tests when logic changes.
5. Run the narrowest relevant verification command first, then broader gates if needed.
6. Return a concise handoff with changed files and verification results.
## Quality Bar
The output should be useful to a real builder immediately. Avoid generic advice. Include exact files, exact behavior, and exact stop conditions. If the task is ambiguous, ask one concise question instead of guessing into risky code.
## Final Response
Include what changed, why it changed, commands run, and any risk that remains.