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

project-memory-cli

v0.1.1

Published

Plain-markdown project-memory layer for your repo. npm i -g project-memory-cli; CLI: project-memory.

Readme

project-memory

CLI: project-memory · npm: https://www.npmjs.com/package/project-memory-cli

The file system is the system. Structure defines execution. Agents are interchangeable executors.

project-memory is a filesystem convention plus a CLI that scaffolds a plain-markdown “project memory layer” inside your repo — so AI coding tools can read real project context instead of reconstructing it from scratch.

Spec: v1.0.0 — SPEC.md


Why this exists

AI tools are powerful, but they:

  • lose context between tasks
  • guess architecture from code
  • duplicate work or break things

project-memory solves this by making context explicit and persistent.

  • Predictable layout — One folder (project-memory/), no hidden state
  • Tool-agnostic — Works with Cursor, Claude, Codex, or anything that reads a repo
  • Git-native — Everything is plain Markdown, diffable, and reviewable

It is not:

  • an agent framework
  • a runtime
  • a plugin system

Install

npm install -g project-memory-cli

Then run:

project-memory init

Package name: project-memory-cli CLI command: project-memory


Quickstart

mkdir my-project
cd my-project

project-memory init
project-memory tree
project-memory validate

project-memory new task "Build login page"

Commands

project-memory init

Detects your repo, shows a scaffold plan, then writes the structure under project-memory/.

project-memory init
project-memory init --yes
project-memory init --new
project-memory init --existing

project-memory new task "<title>"

Creates a new task folder and updates the active task list.

project-memory new task "Build login page"

Creates:

project-memory/tasks/TASK-NNN/

project-memory new workflow "<title>"

Creates a workflow folder for multi-step work.

project-memory new workflow "User onboarding"

project-memory tree

Prints a clean ASCII view of your project-memory structure.

project-memory tree

project-memory validate

Validates the base structure against the spec.

project-memory validate

Example structure

After running init:

project-memory/
├── README.md
├── project/
│   ├── overview.md
│   └── architecture.md
├── context/
│   └── decisions.md
├── tasks/
│   └── active.md
├── tools/
│   └── global-tools.md
├── data/
└── workflows/

Optional at repo root:

AI.md

This file points AI tools to the correct entrypoints.


Using with AI tools

The workflow is simple and consistent:

  1. Open the repo
  2. Have the AI read the project-memory layer
  3. Execute tasks using structured context

Recommended read order

Cold start:

  • project-memory/project/overview.md
  • project-memory/context/current-state.md
  • project-memory/tasks/active.md

Assigned task:

  • project-memory/tasks/TASK-XXX/instructions.md
  • project-memory/tasks/TASK-XXX/context.md
  • project-memory/tasks/TASK-XXX/tools.md

Works with:

  • Cursor
  • Claude Code / Cowork
  • Codex
  • Any repo-aware AI

Philosophy

  • The file system is the system
  • Structure > prompts
  • Context is stored, not inferred
  • Everything is visible and editable

Contributing

See CONTRIBUTING.md


License

MIT — see LICENSE.md