Add Rule Command

--help Handler

If the user passes --help as an argument, display this help and stop:

/coconut-rules:add-rule - Add Rule with Smart Placement

DESCRIPTION
  Add or update a rule with intelligent placement. Critical rules
  go in CLAUDE.md, domain-specific rules go in context files.

USAGE
  /coconut-rules:add-rule [rule description]
  /coconut-rules:add-rule --help

ARGUMENTS
  [rule description]   The rule to add. If omitted, prompts for input.

PLACEMENT LOGIC
  Critical → CLAUDE.md:
  - Security fundamentals (secrets, auth, input sanitization)
  - Git workflow (branching, commits)
  - Universal conventions (80%+ of tasks)
  - Safety-critical "never do" rules

  Context → .claude/rules/[domain].md:
  - Language-specific (Python, TypeScript)
  - Framework-specific (React, FastAPI)
  - Tool-specific (Docker, Terraform)
  - Patterns with examples

EXAMPLES
  # Security rule → goes to CLAUDE.md
  /coconut-rules:add-rule "Never log passwords or sensitive data"

  # Python pattern → goes to .claude/rules/python.md
  /coconut-rules:add-rule "Use Pydantic models for API validation"

  # New domain → creates .claude/rules/terraform.md
  /coconut-rules:add-rule "Use Terraform modules for reusable infra"

CONTEXT DOMAINS
  python.md      - Python, FastAPI, Pydantic
  typescript.md  - TypeScript, React, Next.js
  docker.md      - Docker, containers
  security.md    - Detailed auth patterns
  database.md    - SQL, migrations
  [custom].md    - Any custom domain

Add or update a rule with intelligent placement based on rule characteristics.

Placement Decision

Critical Rules → CLAUDE.md

Rules that go directly in CLAUDE.md:

• Security fundamentals (secrets, auth bypass, input sanitization)
• Git workflow (branching, commits)
• Universal conventions that apply to 80%+ of tasks
• Safety-critical "never do" rules

Context Rules → .claude/rules/[domain].md

Rules that go in context files:

• Language-specific (Python, TypeScript, Go)
• Framework-specific (React, FastAPI, Next.js)
• Tool-specific (Docker, Terraform)
• Detailed patterns with examples

Workflow

1. Analyze the rule provided by the user
2. Determine placement:
   • Is it security/safety-critical? → CLAUDE.md
   • Does it apply universally (80%+ tasks)? → CLAUDE.md
   • Is it domain-specific? → Context file
3. Identify context domain (if context file):
   • python.md - Python, FastAPI, Pydantic
   • typescript.md - TypeScript, React, Next.js
   • docker.md - Docker, containers
   • security.md - Detailed auth patterns
   • database.md - SQL, migrations
   • [custom].md - User-specified domain
4. Create or update the appropriate file in .claude/rules/
5. Update CLAUDE.md context table if adding new context file

Instructions

Step 1: Get Rule Content

If provided in arguments, use that. Otherwise ask:

• What rule would you like to add?
• What behavior should this enforce?

Step 2: Analyze and Classify

Ask yourself:

1. Is this a "never do" security rule? → Critical
2. Does this apply regardless of file type/technology? → Critical
3. Is this specific to a language/framework/tool? → Context
4. Would this need examples to understand? → Context

Step 3: Check Current Structure

# Check existing structure
ls -la .claude/ 2>/dev/null || echo "No .claude directory"
ls -la .claude/rules/ 2>/dev/null || echo "No coconut rules directory"

Use Glob to find existing context files:

• Pattern: .claude/rules/*.md

Step 4a: Add Critical Rule to CLAUDE.md

If placing in CLAUDE.md:

1. Read current CLAUDE.md
2. Find or create ## Critical Rules section
3. Add rule as bullet point under appropriate subsection:
   • ### Security - Security rules
   • ### Git Workflow - Git/version control rules
   • ### Conventions - General coding conventions

Keep it brief - no examples, just actionable statements.

Step 4b: Add Context Rule to Context File

If placing in context file:

1. Create .claude/rules/ if needed
2. Create or update .claude/rules/[domain].md
3. Use this structure:

# [Domain] Context

Rules for [domain] development in this project.

## Key Patterns

- [The rule being added]

## Examples

### Recommended
​```[language]
// Good example
​```

### Avoid
​```[language]
// What to avoid
​```

Step 5: Update Context Table in CLAUDE.md

If adding a new context file, update the context table in CLAUDE.md:

## Context (Read When Relevant)

| Working On | Read |
|------------|------|
| Python/FastAPI | `.claude/rules/python.md` |
| [New domain] | `.claude/rules/[new].md` |  ← Add this row

Examples

Example 1: Security Rule (Critical)

User: /add-rule Never log sensitive user data or passwords

Classification: Critical (security, universal)

Action: Add to CLAUDE.md under ### Security

## Critical Rules

### Security
- Never commit secrets, API keys, or credentials
- Never log sensitive user data or passwords  ← Added

Example 2: Python Pattern (Context)

User: /add-rule Always use Pydantic models for API request/response validation

Classification: Context (Python/FastAPI specific)

Action: Add to .claude/rules/python.md

# Python Context

## Key Patterns

- Always use Pydantic models for API request/response validation

## Examples

### Recommended
​```python
from pydantic import BaseModel

class UserCreate(BaseModel):
    email: str
    password: str
​```

Example 3: New Domain

User: /add-rule Use Terraform modules for reusable infrastructure

Classification: Context (Terraform/IaC specific)

Action:

1. Create .claude/rules/terraform.md
2. Add context table entry to CLAUDE.md

Tips

• When in doubt, prefer context file over CLAUDE.md (less always-on load)
• Group related rules in same context file in .claude/rules/
• Keep CLAUDE.md critical rules under 20 lines total
• Use clear trigger keywords in context table for discoverability