rule-generating-agent

---

description: This rule is essential for maintaining consistency and quality in rule creation across the codebase. It must be followed whenever: (1) A user requests a new rule to be created, (2) An existing rule needs modification, (3) The user asks to remember certain behaviors or patterns, or (4) Future behavior changes are requested. This rule ensures proper organization, clear documentation, and effective rule application by defining standard formats, naming conventions, and content requirements. It's particularly crucial for maintaining the rule hierarchy, ensuring rules are discoverable by the AI, and preserving the effectiveness of the rule-based system. The rule system is fundamental to project consistency, code quality, and automated assistance effectiveness. globs: alwaysApply: true

Cursor Rules Format

Template Structure for Rules Files

---
description: `Comprehensive description that provides full context and clearly indicates when this rule should be applied. Include key scenarios, impacted areas, and why following this rule is important. While being thorough, remain focused and relevant. The description should be detailed enough that the agent can confidently determine whether to apply the rule in any given situation.`
globs: .cursor/rules/**/*.mdc OR blank
alwaysApply: {true or false}
---

# Rule Title

## Critical Rules

- Concise, bulleted list of actionable rules the agent MUST follow

## Examples

<example>
{valid rule application}
</example>

<example type="invalid">
{invalid rule application}
</example>

Organizational Folders (Create if non existent)

All rules files will be under an organizational folder:

• .cursor/rules/core-rules - rules related to cursor agent behavior or rule generation specifically
• .cursor/rules/my-rules - gitignore in a shared repo, rules specifically for ME only
• .cursor/rules/global-rules - these will be rules that are ALWAYS applied to every chat and cmd/ctrl-k context
• .cursor/rules/testing-rules - rules about testing
• .cursor/rules/tool-rules - rules specific to different tools, such as git, linux commands, direction of usage of MCP tools
• .cursor/rules/ts-rules - typescript language specific rules
• .cursor/rules/py-rules - python specific rules
• .cursor/rules/ui-rules - rules about html, css, react

• create new folders under .cursor/rules/ as needed following similar grouping conventions,
  • for example .cursor/rules/cs-rules if we started using c# in a project