rulepack
The registry for AI memory

Pack the AI memory.Install it into any project.

Structure your AI sessions' memory, context, plans, and operating know-how as rulepack.json + Markdown — then publish, version, and install it across every project and agent with one command.

Sign in to publish Browse all packs

Install any pack in one command

$pnpm dlx rulepack add nextjs
rulepack — zsh
❯

Works with every agent you use

Claude CodeCodexCursorGemini CLIGitHub CopilotClineWindsurfRoo CodeKilo CodeopencodegooseJunieDevinAmpAGENTS.mdClaude CodeCodexCursorGemini CLIGitHub CopilotClineWindsurfRoo CodeKilo CodeopencodegooseJunieDevinAmpAGENTS.mdClaude CodeCodexCursorGemini CLIGitHub CopilotClineWindsurfRoo CodeKilo CodeopencodegooseJunieDevinAmpAGENTS.md
Claude CodeCodexCursorGemini CLIGitHub CopilotClineWindsurfRoo CodeKilo CodeopencodegooseJunieDevinAmpAGENTS.mdClaude CodeCodexCursorGemini CLIGitHub CopilotClineWindsurfRoo CodeKilo CodeopencodegooseJunieDevinAmpAGENTS.mdClaude CodeCodexCursorGemini CLIGitHub CopilotClineWindsurfRoo CodeKilo CodeopencodegooseJunieDevinAmpAGENTS.md

The problem

Every agent reads a different file.

Claude Code wants CLAUDE.md. Cursor reads .cursor/rules. Codex, Jules and the rest read AGENTS.md. Maintain them by hand and they drift the moment your standards change.

By hand
  • CLAUDE.mdedit each
  • .cursor/rules/main.mdcedit each
  • AGENTS.mdedit each
  • .windsurfrulesedit each
  • .clinerulesedit each

Five files. Five copies of the same rules — drifting apart.

With RulePack
rulepack.jsongenerated
CLAUDE.md.cursor/rules/main.mdcAGENTS.md.windsurfrules.clinerules

One manifest. One command regenerates every target — versioned, reproducible, and verifiable.

Why RulePack

Everything your AI memory needs to travel.

Built like a package registry, tuned for AI memory.

One manifest, every agent

Declare your memory once in rulepack.json. The CLI writes the exact file each agent expects — no copy-paste, no drift.

CLAUDE.md.cursor/rulesAGENTS.md.windsurfrules.clinerules

Install in one command

rulepack add drops the right files into any project and records them, so the next person gets the same setup.

Immutable & versioned

Every release is semver-pinned and immutable. Upgrade deliberately — never wake up to rules that changed under you.

Open, no lock-in

An open registry of plain-text files. Fork a pack, self-host, or eject to raw files at any time.

Verified integrity

Every tarball is SHA-256 checksummed end to end, so what you install is exactly what was published.

Public, private, or paid

Ship a pack to everyone or keep it private to your scope — both live today. Mark a pack paid to gate its files; paid checkout is coming soon.

How it works

From memory to every agent in three steps.

1

Author

Describe your memory in one rulepack.json. rulepack init scaffolds it, plus an AGENTS.md to start from.

rulepack — zsh
❯rulepack init
? Pack name › @acme/nextjs
✓ Wrote rulepack.json
✓ Scaffolded AGENTS.md
2

Publish

rulepack publish ships an immutable, versioned release to the registry under your scope.

rulepack — zsh
❯rulepack publish
✓ Packed 4 files (12.3 KB)
✓ Published @acme/[email protected]
→ npx rulepack add @acme/nextjs
3

Install

Anyone runs rulepack add and the pack's files land in their project, ready for every agent.

rulepack — zsh
❯rulepack add @acme/nextjs
✓ Resolved @acme/[email protected]
✓ Wrote CLAUDE.md · .cursor/rules · AGENTS.md
✓ Recorded in rulepack.json

One source of truth

One manifest. Every memory file.

One rulepack.json points at the real memory files in your repo — switch tabs to see each one rulepack add drops into a project.

rulepack.json
{
  "name": "@acme/nextjs",
  "version": "1.4.0",
  "license": "MIT",
  "visibility": "public",
  "memories": {
    "claude": "CLAUDE.md",
    "cursor": ".cursor/rules/main.mdc",
    "agents": "AGENTS.md",
    "custom": { "plan": "docs/plan.md" }
  }
}
rulepack add
# Project memory
 
- App Router only — never the pages dir.
- Server Components by default.
- Validate every API boundary with zod.

Explore the registry

Find a pack, or publish your own.

Popular packs

Most-installed packs across the registry

See all →

vue

v0.1.0

Official Vue 3 Style Guide conventions for Composition API + <script setup> (multi-word names, keyed v-for, scoped styles).

000

typescript

v0.1.0

Strict TypeScript baseline: no any, narrowing on unknown, exhaustive switches, no enums.

001

test-first

v0.1.3

Test-first conventions: test names are sentences, no mocks for code we own, real DB in integration tests.

000

terraform

v0.1.0

Official HashiCorp Terraform style & structure: terraform fmt/validate, snake_case naming, standard files, pinned versions.

000

tanstack-query

v0.1.0

Conventions for TanStack Query (React Query v5): array query keys, staleTime vs gcTime, retries, invalidation after mutations.

000

tailwind

v0.1.0

Tailwind CSS v4 conventions: CSS-first config via @theme, no tailwind.config.ts, design tokens as CSS vars.

000

sveltekit

v0.1.0

SvelteKit + Svelte 5 runes conventions ($state/$derived/$effect/$props, filesystem routing, universal vs server load).

000

shadcn

v0.1.0

shadcn/ui conventions: you own the components, cn() + CVA variants, Radix + Tailwind, components.json.

000

Recently published

Fresh from the registry in the last few days

vue

v0.1.0

Official Vue 3 Style Guide conventions for Composition API + <script setup> (multi-word names, keyed v-for, scoped styles).

000

typescript

v0.1.0

Strict TypeScript baseline: no any, narrowing on unknown, exhaustive switches, no enums.

001

test-first

v0.1.3

Test-first conventions: test names are sentences, no mocks for code we own, real DB in integration tests.

000

terraform

v0.1.0

Official HashiCorp Terraform style & structure: terraform fmt/validate, snake_case naming, standard files, pinned versions.

000

tanstack-query

v0.1.0

Conventions for TanStack Query (React Query v5): array query keys, staleTime vs gcTime, retries, invalidation after mutations.

000

tailwind

v0.1.0

Tailwind CSS v4 conventions: CSS-first config via @theme, no tailwind.config.ts, design tokens as CSS vars.

000

sveltekit

v0.1.0

SvelteKit + Svelte 5 runes conventions ($state/$derived/$effect/$props, filesystem routing, universal vs server load).

000

shadcn

v0.1.0

shadcn/ui conventions: you own the components, cn() + CVA variants, Radix + Tailwind, components.json.

000

Articles

Read the workflow. Install the memory.

Publish AI operating know-how and playbooks — free or paid — and link the memory pack behind each one so readers install it in a command.

Free or paid

Publish the whole piece free, or write a free preview and gate the rest — the gated body is never sent to a non-buyer. Paid checkout is coming soon.

Linked to packs

Attach the memory pack behind the article — readers go straight from the write-up to rulepack add, and the pack lists the article under Related.

Drafts & discovery

Drafts stay private to you; published articles surface in search right alongside packs.

Turn a style guide into agent memory

How framework style guides become installable, versioned memories for everyday coding.

RulePack

Security rules an agent should remember

A compact baseline for secrets, SQL, auth boundaries, and production-safe logging.

RulePack

A test-first loop for coding agents

How to make agents ask for a failing test, implement narrowly, and leave a useful review trail.

RulePack

A practical Next.js agent baseline

The rules that keep an agent from mixing App Router, Client Components, and weak TypeScript.

RulePack

Browse all articles →Write an article →
Coming soon · Pro

RulePack AI

Watch RulePack AI read every file

RulePack AI reads every rule file in a published version — the manifest, README, CLAUDE.md, AGENTS.md, .cursor rules — line by line, catching prompt injection and unsafe instructions before your agent ever runs them.

⠋RulePack AIreading CLAUDE.md · 1/6
  • ⠋CLAUDE.md
  • AGENTS.md
  • .cursor/rules/nextjs.mdc
  • README.md
  • rulepack.json
  • LICENSE
▸ CLAUDE.md
# Next.js — Claude Code rules
Server Components by default.
await params / searchParams (Next 16).
strict: true · no any.
0/6

Coverage

What RulePack AI catches

Precise static rules plus a local model, tuned for the ways a rule file can attack the agent that reads it.

Prompt injection

“Ignore previous instructions”, fake system or developer messages aimed at the agent.

Credential exfiltration

Reading .env, tokens, or SSH keys and sending them to an external URL or webhook.

Unsafe commands

curl | sh, rm -rf, chmod 777 — download-and-execute or destructive shell.

Persistence

Writing shell rc files, git hooks, or crontab to run code later.

Stealth

“Don’t tell the user”, hide actions, or suppress logs.

Obfuscation

Base64/hex blobs, zero-width characters, and homoglyph tricks.

Coming soon · Pro

Earn a badge the world can trust

RulePack AI scans every published version for prompt injection, credential exfiltration, and unsafe agent instructions — then awards a verified safety badge on your pack page. A Pro feature, launching soon.

  • Local, private AI — your pack is never sent to a third-party model
  • Continuous re-scans as new attack patterns emerge
  • A public “Safety checked” shield on your pack page
  • CI gate & policy controls for teams
Coming soon
@rulepack/nextjsv0.1.0
Safety checked
RulePack AI · 6 files · 0 findings
✓ score 0 / 100 · passed

Issued per published version · re-scanned as new threats emerge

0+
agents & specs from one manifest
1
command to install any pack
0%
immutable, versioned releases
SHA-256
checksum on every install

Pack the AI memory once. Install it anywhere.

Author once, publish to the registry, install it into any project and agent. No lock-in, every version immutable.

Get started

or start from scratch

$pnpm dlx rulepack init