Overview

rulepack is a registry and CLI for AI memory files. You write your memories once, describe them in a single rulepack.json at your project root, and ship them to every agent — Claude Code, Cursor, Gemini CLI, GitHub Copilot, Cline, Windsurf, and the 20+ tools that read AGENTS.md.

Think of it as npm for AI memory. A pack bundles the Markdown files an agent reads (like AGENTS.md, CLAUDE.md, or .cursor/rules/main.mdc), is versioned with immutable semver, and installs into any project with one command.

The shape of a project

rulepack.json lives at the root of your repository, right next to package.json — the same place every other ecosystem keeps its manifest. That's deliberate: it should feel instantly familiar.

.
├── rulepack.json          # the manifest — at the root
├── package.json
├── AGENTS.md
├── CLAUDE.md
└── .cursor/
    └── rules/
        └── main.mdc

Install in seconds

npx rulepack add nextjs

That resolves the pack from the registry, verifies its SHA-256, and writes the memory files into your project — recording the result in your rulepack.json.

Public, private, or paid

A pack's visibility decides who can read its files: public (anyone), private (only your scope), or pay (the metadata and README stay public, but the files unlock with a purchase). Public and private work today; paid checkout is coming soon. See Visibility and access.

Articles

Beyond packs, rulepack hosts articles — AI operating know-how and playbooks. An article can be published free or with a paid, gated body, and can link the memory pack behind it so a reader goes from the write-up to rulepack add in one step. See Articles.

Next steps

• Quickstart — publish your first pack in five minutes.
• rulepack.json — every field in the manifest, explained.
• CLI commands — init, add, publish, login, search.
• Publishing & installing — the author → registry → consumer lifecycle.
• Articles — publish know-how, free or paid, and link it to packs.