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

context-bank

v0.0.3

Published

A CLI tool to standardise AI context in projects.

Readme

🏦 Context Bank

npm version license downloads

The git init for AI Context. Standardize, persist, and evolve your project's AI context with a single command. Works with Cursor, Windsurf, and GitHub Copilot.


⚡ The Problem

Every time you start a new chat with an AI Code Editor, you face the same friction:

  • Amnesia: "Wait, are we using Tailwind or CSS Modules? I forgot."
  • Token Waste: Manually pasting huge documentation files burns your quota.
  • Inconsistency: Cursor follows one rule, while Copilot suggests something else.

🚀 The Solution

Context Bank creates a standardized, self-evolving brain for your project.

It generates a structured .ai directory that acts as a Single Source of Truth (SSOT) for all your AI tools.

📦 Installation & Usage

Prerequisites

You need Node.js 18+ installed on your machine. (Most developers already have this. If not, download it here.)

Quick Start

Go to your project root (any language: Python, Go, C#, Node, etc.) and run:

npx context-bank init

That's it! 🚀

✨ Key Features

🧠 1. Self-Evolving Rules

Instead of static .txt files, Context Bank sets up a living rules.md.

  • Dynamic Learning: The AI is instructed to update its own rules when you state a preference.
  • Example: You tell the AI "I prefer arrow functions". The AI updates .ai/rules.md. Next time, it remembers.

💾 2. Smart Memory (Token Saver)

Stop feeding the AI your entire chat history. Context Bank uses "State Management":

  • active-context.md (Short-term): Tracks the current task. (e.g., "Fixing the login bug").
  • story.md (Long-term): Logs major milestones and architectural decisions.
  • The Benefit: You can start a fresh chat, point the AI to active-context.md, and resume work instantly without reading 10k tokens of history.

🔌 3. Universal Tool Support

One brain, multiple interfaces. The init command automatically configures pointers for:

| Tool | Support Type | File Created | |------|--------------|--------------| | Cursor | Native ✅ | .cursorrules | | Windsurf | Native ✅ | .windsurfrules | | GitHub Copilot | Native ✅ | .github/copilot-instructions.md | | Aider (CLI) | Native ✅ | CONVENTIONS.md | | Other CLIs | Manual 🛠️ | (See below) |

🖥️ Using with Gemini CLI, Claude Code, or ChatGPT

If your tool doesn't automatically read configuration files, just start your session with this Magic Prompt:

"I am starting a session. Please read .ai/rules.md for project standards and .ai/active-context.md for the current state. Update these files if plans change."

📂 Generated Structure

When you run the command, your project gets this power-pack:

my-project/
├── .ai/
│   ├── rules.md           # 🧠 The Master Brain (SSOT)
│   ├── active-context.md  # 📝 Current focus & next steps
│   └── story.md           # 📜 Project history & decisions
├── .cursorrules           # 🔗 Pointer for Cursor
├── .windsurfrules         # 🔗 Pointer for Windsurf
└── .github/
    └── copilot-instructions.md # 🔗 Pointer for Copilot

🤝 Contributing

Contributions are welcome! Whether it's a new template or a bug fix.

  1. Fork the repo
  2. Create your branch (git checkout -b feature/amazing-feature)
  3. Commit your changes (git commit -m 'feat: add amazing feature')
  4. Push to the branch (git push origin feature/amazing-feature)
  5. Open a Pull Request

📄 License

MIT © Kadir Esen