foundation: Skill for Cursor

Create Rule

Create a new rule file with _rules suffix and automatically create symlink in .cursor/rules/.

SUBMODULE MODE: If a submodule name is provided (e.g., /create-rule foundation), create the rule in that submodule. If no submodule name is provided, create in the main repository's docs/ directory.

Command

create-rule [submodule_name]

Inputs

• submodule_name (optional string): Submodule name to create rule in (e.g., "foundation"). If omitted, creates rule in main repository's docs/ directory.

Workflow Overview

If submodule name provided:

1. Verify submodule exists
2. Determine submodule rule location
3. Prompt user for rule details
4. Create rule file in submodule
5. Run setup script to create symlink (if applicable)
6. Exit after submodule rule creation

If no submodule name provided (default - repo mode):

1. Prompt user for rule details
2. Create rule file in docs/{location}/{name}_rules.md
3. Include standard Agent Instructions template
4. Run setup script to create symlink
5. Verify symlink created

Tasks

Step 1: Determine Scope

If submodule name provided:

1. Verify submodule exists:

   if ! git submodule status <submodule_name> >/dev/null 2>&1; then
     echo "❌ Submodule not found: <submodule_name>"
     exit 1
   fi
   

2. Determine submodule rule location:

   • For foundation submodule: foundation/agent_instructions/cursor_rules/
   • For other submodules: Check for standard rule directories or prompt user

3. Set context for submodule rule creation

If no submodule name provided:

• Set context for main repository rule creation in docs/ directory

Step 2: Prompt User for Rule Details

Repository mode prompts:

1. Rule file name (without _rules.md suffix)

   • Example: "entity_resolution" will become "entity_resolution_rules.md"
   • Validate: alphanumeric with underscores only

2. Location in docs/ directory

   • Options: conventions, foundation, subsystems, architecture, developer, etc.
   • Validate: directory must exist or ask to create