create-rulelisted

# Creating Cursor Rules Create project rules in `.cursor/rules/` to provide persistent context for the AI agent. ## CRITICAL: Check Existing First **Before creating ANY rule, verify:** 1. **Check for existing rules:** ```bash ls -la .cursor/rules/*.mdc 2>/dev/null cat .cursor/rules/*.mdc 2>/dev/null | head -100 ``` 2. **Check for conflicting conventions:** ```bash cat CONTRIBUTING.md .editorconfig .eslintrc* 2>/dev/null | head -50 ``` 3. **Check if similar rule exists:** - Don't duplicate existing rules - Consider extending existing rules instead **Why:** Rules should complement, not conflict with, existing project conventions. ## Gather Requirements Before creating a rule, determine: 1. **Purpose**: What should this rule enforce or teach? 2. **Scope**: Should it always apply, or only for specific files? 3. **File patterns**: If file-specific, which glob patterns? ### Inferring from Context If you have previous conversation context, infer rules from what was discussed. You can create multiple rules if the conversation covers distinct topics or patterns. Don't ask redundant questions if the context already provides the answers. ### Required Questions If the user hasn't specified scope, ask: - "Should this rule always apply, or only when working with specific files?" If they mentioned specific files and haven't provided concrete patterns, ask: - "Which file patterns should this rule apply to?" (e.g., `**/*.ts`, `backend/**/*.py`) It's very important that we get