Package Exports

This package does not declare an exports field, so the exports above have been automatically detected and optimized by JSPM instead. If any package subpath is missing, it is recommended to post an issue to the original package (rulepack) to support the "exports" field. If that is not possible, create a JSPM override to customize the exports field for this package.

Readme

rulepack

One rulepack.json, every AI coding agent.

Manage CLAUDE.md, AGENTS.md, .cursor/rules/*.mdc, .clinerules, and .windsurfrules from a single manifest. Publish a pack once, install it into any project with one command.

npx rulepack add nextjs-strict

That single command drops the right files into your project for every AI coding agent listed in the pack's manifest.

Why

You're already using Claude Code, Cursor, Cline, Windsurf… and each one wants its own file. Hand-syncing them across projects gets old fast. rulepack treats agent rules the way npm treats libraries: published, versioned, addressable by name, reinstallable everywhere.

Install

You don't need to. Just npx rulepack .... If you do want a global binary:

npm install -g rulepack
# or: pnpm add -g rulepack

Requires Node.js >=22.0.0.

Commands

rulepack add <pack>          # install a pack into the current project
rulepack init                # generate rulepack.json interactively
rulepack publish             # publish the current pack (login required)
rulepack search <query>      # search packs on the registry
rulepack login               # authenticate via browser (or set RULEPACK_TOKEN)
rulepack logout
rulepack whoami

House packs vs community packs

Packs published under the @rulepack scope can be installed by their bare name — npx rulepack add nextjs-strict resolves to @rulepack/nextjs-strict. Community packs always use the full form: npx rulepack add @yourname/your-pack.

Authoring a pack

mkdir my-pack && cd my-pack
npx rulepack init
# ...edit CLAUDE.md / AGENTS.md / .cursor/rules/*.mdc...
npx rulepack login
npx rulepack publish

rulepack.json declares the agents your pack targets and the files that ship in the tarball. See the manifest reference for the full schema.

Configuration

The CLI reads ~/.rulepackrc (chmod 0600). Both can be overridden via environment variables:

Variable	Meaning
`RULEPACK_REGISTRY`	Registry base URL
`RULEPACK_TOKEN`	Bearer token for publish

License

Proprietary — see the project LICENSE. This CLI is free to use; redistribution and derivative works require permission.