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

rulesforge

v1.0.0

Published

Analyze any codebase and generate optimized AI coding rules for Claude Code, Cursor, Copilot, and more

Readme

RulesForge

Analyze any codebase and generate optimized AI coding rules for Claude Code, Cursor, Copilot, and more.

Your AI coding assistant is only as good as its context. RulesForge scans your project — frameworks, conventions, patterns, dependencies — and generates tailored rules files that make AI understand your codebase.

One command. Four output formats. Zero configuration.

Quick Start

npx rulesforge

That's it. RulesForge scans your project and generates:

| File | Tool | Purpose | |------|------|---------| | CLAUDE.md | Claude Code | Project context, conventions, and rules | | .cursorrules | Cursor | AI code generation guidelines | | AGENTS.md | Multi-agent tools | Agent task patterns and file ownership | | .github/copilot-instructions.md | GitHub Copilot | Code completion context |

What It Detects

Frameworks: React, Next.js, Remix, Astro, Vue, Nuxt, Svelte, Express, Fastify, NestJS, Django, Flask, FastAPI, and more.

Conventions: naming patterns (camelCase/snake_case), import style (relative/absolute/aliases), file naming, semicolons, quote style.

Tooling: package manager, test framework, linter, formatter.

Structure: source directories, test directories, CI/CD, documentation, entry points.

Why Not Just Use /init?

Claude Code's built-in /init generates a basic CLAUDE.md. RulesForge goes deeper:

| Feature | /init | RulesForge | |---------|---------|------------| | Framework detection | Basic | 15+ frameworks with version detection | | Convention analysis | No | Naming, imports, quotes, semicolons | | Cross-tool output | CLAUDE.md only | CLAUDE.md + .cursorrules + AGENTS.md + Copilot | | Framework-specific rules | Generic | React hooks, Next.js App Router, Express middleware, etc. | | Security rules | No | Stack-specific security best practices | | Quality score | No | Rate your existing rules coverage |

Options

Usage: rulesforge [path] [options]

Arguments:
  path                    Project directory to scan (default: ".")

Options:
  --format <formats>      Output formats (comma-separated: claude-md,cursorrules,agents-md,copilot)
  --dry-run               Preview generated content without writing files
  --diff                  Show what would change in existing files
  --output <dir>          Output directory (default: project root)
  --force                 Overwrite existing files without asking
  --quiet                 Minimal output
  --json                  Output scan results as JSON
  -v, --version           Show version
  -h, --help              Show help

Examples

Generate only CLAUDE.md:

npx rulesforge --format claude-md

Preview without writing:

npx rulesforge --dry-run

Scan a specific project:

npx rulesforge /path/to/project

Get scan results as JSON (for scripting):

npx rulesforge --json

Supported Frameworks

| Framework | Detection Method | Specific Rules | |-----------|-----------------|----------------| | React | package.json + JSX files | Hooks, components, keys, state | | Next.js | next.config.* | App Router, server components, metadata | | Express | package.json | Middleware, error handling, routing | | TypeScript | tsconfig.json | Strict types, interfaces, generics | | Python | .py files | Type hints, docstrings, imports | | And more... | Auto-detected | Framework-specific best practices |

How It Works

  1. Scan — Walks your project tree, reads config files, samples source code
  2. Analyze — Detects frameworks, infers conventions, maps structure
  3. Generate — Applies framework-specific rules + convention enforcement + security rules
  4. Write — Creates rules files in your project root

No AI. No API calls. No data leaves your machine. Pure static analysis.

Contributing

Found a framework we should support? Have better rules for your stack? PRs welcome!

git clone https://github.com/Wittlesus/rulesforge
cd rulesforge
npm install
npm test

License

MIT


Built by @WSDevGuy | GitHub