JSPM

  • ESM via JSPM
  • ES Module Entrypoint
  • Export Map
  • Keywords
  • License
  • Repository URL
  • TypeScript Types
  • README
  • Created
  • Published
  • Downloads 66
  • Score
    100M100P100Q63826F
  • License SEE LICENSE IN LICENSE

Pack the AI memory — one rulepack.json publishes versioned, installable memory (rules, context, plans) across every agent: Claude Code, Cursor, Cline, Windsurf, AGENTS.md, Gemini, Copilot.

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

    Pack the AI memory.

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

    npx rulepack add nextjs

    That single command drops the right memory files into your project for every agent the pack declares — AGENTS.md, CLAUDE.md, .cursor/rules/*.mdc, .clinerules, .windsurfrules, GEMINI.md, .github/copilot-instructions.md, plus any custom project memories.

    Why

    AI coding agents can read your project, but their working context doesn't survive across sessions, machines, or teammates — and each agent wants its own file. rulepack treats that memory the way npm treats libraries: published, versioned, addressable by name, reinstallable everywhere. Read someone's workflow, then pull it into your repo.

    Install

    You don't need to — just npx rulepack .... For 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's memory files into the project
    rulepack update [pack]       # update installed packs to newer versions
    rulepack init                # generate rulepack.json interactively
    rulepack link                # link existing Markdown files into memories
    rulepack memory add          # add one standard or custom memory
    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 under the @rulepack scope install by bare name — npx rulepack add nextjs resolves to @rulepack/nextjs. Community packs use the full form: npx rulepack add @yourname/your-pack.

    Authoring a pack

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

    rulepack init does not require login — keep rulepack.json in a repo like package.json as a local manifest for AI memory, and sign in only when you publish. The manifest's memories map declares which files the pack ships (standard agent keys plus a free-form custom map), visibility sets the access policy (public / private / pay), and license is required. See the manifest reference for the full schema.

    Configuration

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

    Variable Meaning
    RULEPACK_REGISTRY Registry base URL
    RULEPACK_TOKEN Bearer token for publish (CI)
    RULEPACK_LANG CLI language (en / ja)

    License

    Proprietary — see the LICENSE file included in the npm package. This CLI is free to use; redistribution and derivative works require permission.