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

@commerce-atoms/agents

v0.3.7

Published

Universal AI manifest, rules, skills, prompts, slash commands, and personas for the commerce-atoms ecosystem.

Downloads

1,367

Readme

@commerce-atoms/agents

Universal AI manifest, rules, skills, prompts, slash commands, and personas for the commerce-atoms ecosystem.

License: MIT

This is the npm package that distributes the AI kit consumed by every storefront forked from hydrogen-storefront-starter. The shipped product (manifests, rules, primitives, ADRs) lives under kit/ and is read by Cursor, GitHub Copilot, Claude Code, and Codex via the universal kit/AGENTS.md manifest.


How consumers use it

npm i -D @commerce-atoms/agents
npx commerce-atoms-agents sync

The CLI copies the manifest + per-tool overlays + Cursor rules into the consumer's repo, rewrites repo-relative links to absolute GitHub URLs, and pins the kit version in agents.config.json.

For a guided walkthrough from install to first deploy, see kit/QUICKSTART.md.

CLI commands

commerce-atoms-agents init <name>      # clone the starter, brand, pin, first commit
commerce-atoms-agents sync             # copy canonical content into cwd; pin version
commerce-atoms-agents sync --dry-run   # preview without writing
commerce-atoms-agents sync --force     # overwrite consumer divergence
commerce-atoms-agents sync --out <dir> # alternate output directory
commerce-atoms-agents validate-architecture    # run the boundary validators
commerce-atoms-agents version
commerce-atoms-agents help

agents.config.json

Generated on first sync; updated each run with the pinned version.

{
  "agentsVersion": "0.2.0",
  "audience": "store-fork",
  "tools": {"cursor": true, "copilot": true, "claude": true},
  "out": {
    "agentsMd": "AGENTS.md",
    "claudeMd": "CLAUDE.md",
    "copilotInstructions": ".github/copilot-instructions.md",
    "cursorRulesDir": ".cursor/rules"
  }
}

Disable a tool by setting tools.<name> to false. Customise an output path by editing out.<key>. Codex is not a flag. It auto-reads the always-synced AGENTS.md.

Conflict handling

If a consumer mutates a synced file, the next sync writes the new canonical content to a <file>.kit-incoming.<ext> sidecar next to the consumer's edit and reports the file as divergent. The consumer's edit is left untouched and all unrelated files still sync. The sidecar is auto-removed once the consumer file converges with canonical (or is deleted).

Default exit code is 0 so unrelated updates aren't blocked by one local edit. CI gates that want to fail on divergence should pass --strict. To overwrite the consumer's edit instead of producing a sidecar, pass --force.


Repo layout

The repo separates the npm package from the shipped product:

agents/
├── package.json, tsconfig.*, LICENSE, CHANGELOG.md, README.md  ← npm package metadata
├── bin/, src/                                                   ← package source (TypeScript)
├── .github/workflows/                                           ← publish.yml + verify.yml
├── CONTRIBUTING.md                                              ← kit-authoring rules
├── AGENTS.md, CLAUDE.md, .github/copilot-instructions.md,
│   .cursor/rules/                                               ← root overlays for kit authors
└── kit/                                                         ← what ships to consumers
    ├── AGENTS.md, CLAUDE.md, copilot-instructions.md            ← per-tool overlays for storefronts
    ├── .cursor/rules/                                           ← Cursor overlays for storefronts
    ├── rules/                                                   ← canonical storefront rules
    ├── skills/, commands/, prompts/, personas/                  ← the five primitives
    ├── reference/                                               ← philosophy + conventions
    ├── docs/decisions/                                          ← ADRs
    ├── INDEX.json + INDEX.schema.json                           ← registry of shipped artefacts
    ├── RUN_PROTOCOL.md, QUICKSTART.md

The split is doctrine. Root files govern the package; kit/ files ship to consumers and govern Hydrogen storefronts. See CONTRIBUTING.md for the rationale.

Where to look

| Question | Answer lives in | |---|---| | Storefront architecture rules and primitives | kit/AGENTS.md, kit/rules/core/ | | The five primitives (rule / persona / skill / command / prompt) | kit/reference/philosophy.md | | Frontmatter and naming conventions | kit/reference/conventions.md | | Why a decision was made | kit/docs/decisions/ | | How to author or extend the kit | CONTRIBUTING.md | | CLI source | src/sync.ts, src/init.ts, src/validate.ts, bin/sync.ts |


Doctrine

commerce-atoms is the adapter layer between Shopify upstream (runtime + cookbooks) and a modular, AI-consistent storefront architecture. The kit ports Shopify cookbook recipes; it does not write competing implementations.

Full statement in kit/AGENTS.md §0.


Status

  • 0.1.x. Sync CLI, init CLI, validate-architecture skill + slash command, five personas, three prompt templates, manifest + per-tool overlays. Released via Trusted Publishing (OIDC).
  • Per-tool overlays are currently hand-maintained mirrors of the canonical sources in kit/rules/core/. Deterministic generation from canonical sources is on the roadmap.

Contributing

See CONTRIBUTING.md for local setup, kit-authoring conventions, and the release workflow.

License

MIT