AI Rules

Supercharge Claude Code with framework-specific rules, skills, and best practices.

AI Rules installs curated configuration boilerplates that teach Claude Code your stack's conventions, patterns, and guardrails. Stop explaining the same things over and over — let Claude understand your architecture from the start.

Why Use This?

Quick Start

# Interactive setup (recommended)
npx @malamute/ai-rules init

# Or specify your stack directly
npx @malamute/ai-rules init angular nestjs

That's it. Claude Code now understands your stack.

Installation

# Global install
npm install -g @malamute/ai-rules

# Or use with npx (no install needed)
npx @malamute/ai-rules <command>

Supported Technologies

Commands

ai-rules init [tech...]     # Install configs (interactive if no tech)
ai-rules add <tech>         # Add technology to existing installation
ai-rules update             # Update to latest rules
ai-rules status             # Show installation info
ai-rules list               # List available technologies

Options

By default, init installs everything (skills + shared rules). Use --minimal to skip extras.

What Gets Installed

your-project/
├── CLAUDE.md                    # Your project-specific info (not touched)
└── .claude/
    ├── settings.json            # Allowed/denied commands
    ├── rules/                   # Framework-specific patterns
    │   ├── nextjs/
    │   │   ├── core.md          # Stack, architecture, conventions
    │   │   ├── components.md
    │   │   └── ...
    │   ├── conventions/         # Shared conventions
    │   │   └── core.md
    │   └── security/
    └── skills/                  # Optional workflows
        ├── learning/
        ├── review/
        └── debug/

Note: Your project's CLAUDE.md is never modified. Use it for project-specific context (business domain, team conventions, etc.).

Rules

Context-aware rules that activate based on file paths:

---
paths:
  - '**/*.component.ts'
---

# Angular Component Rules

- Use `ChangeDetectionStrategy.OnPush`
- Use `input()`, `output()`, not decorators
- Template in separate `.html` file

Skills

Interactive workflows invoked with /skill-name:

Shared Rules

Cross-framework rules included with --with-rules:

Examples

Fullstack Setup

# Angular frontend + NestJS backend
ai-rules init angular nestjs

# Next.js frontend + FastAPI backend
ai-rules init nextjs fastapi

# Add a technology to existing installation
ai-rules add nestjs

# Minimal install (no skills/shared rules)
ai-rules init angular --minimal

Preview Before Installing

ai-rules init angular --dry-run

Output:

DRY RUN - No files will be modified

ℹ Would install to: /your/project

ℹ Would install angular...
○   settings.json (create)
○   rules/angular/ (9 files)

Summary:
  10 file(s) would be created
  0 file(s) would be modified

Update Configs

# Check current version
ai-rules status

# Preview updates
ai-rules update --dry-run

# Apply updates (auto-backup enabled)
ai-rules update

Technology Conventions

How It Works

1. Rules are loaded by Claude Code based on file paths you're editing
2. rules/core.md with alwaysApply: true provides framework conventions
3. Skills are invoked on-demand with /skill-name
4. Settings define what commands Claude can run

Your project's CLAUDE.md stays clean for project-specific context, while framework conventions live in rules.

Contributing

# Clone and install
git clone https://github.com/malamute/ai-rules.git
cd ai-rules
npm install

# Run tests
npm test

# Add a new technology
mkdir -p configs/your-tech/rules
# Add rules/core.md and other rules

Adding a Technology

1. Create configs/[tech]/rules/core.md with framework conventions
2. Add rules in configs/[tech]/rules/
3. Add configs/[tech]/settings.json for permissions
4. Add tests
5. Submit a PR

See CONTRIBUTING.md for details on skills structure.

License

MIT © Mehdi Chaabi