npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

aimapper

v0.2.9

Published

Universal build tool for managing coding agent rules - Support Claude Code, Cursor, Windsurf, GitHub Copilot, and more

Readme

aimapper

Universal build tool for managing coding agent rules across multiple AI-powered development tools. Support Claude Code, Cursor, Windsurf, GitHub Copilot, Amazon Q, and more.

npm version License: MIT

Installation

npm install -g aimapper

Or use directly with npx:

npx aimapper build  # Uses aimapper package, runs 'aimap build'
# or after global install:
aimap build

Usage

Build rules for default agent (Claude)

aimap build  # Generates CLAUDE.md only

Build for specific agents

aimap build --agents claude,cursor

Clean generated files

aimap clean           # Clean all generated files
aimap clean --all     # Also remove build hash

Configuration

Create .aimap.yml in your project root:

# Source directory for rule files
source: .rules

# Agents to build for
agents:
  - claude
  - cursor
  - copilot
  - amazonq

# Custom output paths (optional)
outputs:
  claude: CUSTOM_CLAUDE.md

Options

Build command

  • -s, --source <dir> - Source directory for rules [default: .rules]
  • -a, --agents <list> - Comma-separated list of agents [default: all]
  • -v, --verbose - Verbose output
  • --dry - Dry run (show what would be built)
  • -c, --config <file> - Path to config file [default: .aimap.yml]

Clean command

  • --all - Remove all generated files including build hash
  • -v, --verbose - Verbose output
  • -c, --config <file> - Path to config file [default: .aimap.yml]

Supported Coding Agents (2025)

| Agent | ID | Output Files | Notes | |-------|-----|--------------|-------| | Universal Agents | agents | AGENTS.md | Combined rules for any agent | | Claude Code | claude | CLAUDE.md | Writes a bullet list of @ references; supports CLAUDE.tempalte.md with @@RULES@@ placeholder | | Cursor IDE | cursor | .cursor/rules/*.mdc | MDC format (v0.52+) | | GitHub Copilot | copilot | .github/instructions/*.instructions.md | Granular instructions | | Amazon Q | amazonq | .amazonq/rules/*.md | 32KB file limit | | Aider | aider | .aider.conf.yml | Updates read array | | Cline | cline | .clinerules/*.md | Individual files | | RooCode | roocode | .roo/rules/*.md | Individual files | | Windsurf | windsurf | .windsurfrules | 6KB hard limit | | JetBrains AI | jetbrains | .aiassistant/rules/*.md | Individual files | | Gemini CLI | gemini | GEMINI.md | Combined rules |

Quick Start

  1. Create a .rules/ directory in your project:
mkdir .rules
  1. Add your coding rules as markdown files:
echo "# Code Style\n\nUse TypeScript" > .rules/01-style.md
echo "# Testing\n\nWrite unit tests" > .rules/02-testing.md
  1. Build rules for your agents:
npx aimapper build --agents claude,cursor,windsurf
# or with global install:
aimap build --agents claude,cursor,windsurf
  1. Your agents will automatically use the generated files!

Example

Project Structure

my-project/
├── .rules/
│   ├── 01-coding-style.md
│   ├── 02-architecture.md
│   └── 03-testing.md
├── .aimap.yml              # Optional config
└── ... (generated files after build)

Generated CLAUDE.md

When building for Claude, the file contains a list of rule references:

- @.rules/01-coding-style.md
- @.rules/02-architecture.md
- @.rules/03-testing.md

If a CLAUDE.tempalte.md file exists in the project root, @@RULES@@ will be replaced with this list in the template content.

Sample Config (.aimap.yml)

# Source directory for rule files
source: .rules

# Agents to build for
agents:
  - claude
  - cursor
  - copilot
  - windsurf

Sample Rule File (.rules/01-coding-style.md)

# Coding Style Guidelines

- Use TypeScript for all new code
- Follow ESLint configuration  
- Write comprehensive tests
- Use meaningful variable names

Development

# Install dependencies
npm install

# Build
npm run build

# Run tests
npm test

# Development with watch mode
npm run test:watch

License

MIT