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

pozzolanic

v0.1.0

Published

An antifragile operating system for Claude Code

Readme

Pozzolanic

An antifragile operating system for Claude Code.

Named for pozzolanic concrete — the Roman volcanic ash formula that gets stronger when exposed to seawater. Where normal concrete degrades, pozzolanic concrete heals its own cracks.

Pozzolanic follows the same principle: every session that finds a gap heals it. New knowledge gets committed to memory. Missing context gets added to slash commands. The system gets stronger with use.

How It Works

Pozzolanic organizes Claude Code around three layers:

  1. Global config (~/.claude/CLAUDE.md) — Operating principles and workstream routing. Loads every session.
  2. Slash commands (~/.claude/commands/*.md) — Deep context for specific workstreams. Load on demand.
  3. Memory (~/.claude/projects/*/memory/) — Accumulated knowledge. Auto-loaded (MEMORY.md) or agent-read (reference files).
Session starts → CLAUDE.md loads (principles + routing)
                → MEMORY.md loads (critical rules + index)
User types /bq  → commands/bq.md loads (BigQuery context)
Agent needs ref → reads memory/revenue-data-sources.md
Agent learns    → updates memory → next session starts smarter

Principles

  1. System > Feature > Fix — Fix the system once, not symptoms repeatedly.
  2. Repeatable before Smart — Manual → Scripted → Automated → Intelligent. Never skip steps.
  3. Observability first — A slow system you can see beats a fast system you can't explain.
  4. Preserve invariants — Adding a fix must not break existing behavior.
  5. Fewer concepts — New abstractions are a cost, not a win.
  6. One source of truth — Each concept has exactly one authoritative source.
  7. Reversible decisions — Early decisions should be easy to undo.
  8. Stop when unclear — Don't guess. Ask.
  9. Done = boring and stable — If it feels clever, it's not done.
  10. Bias toward action — Do the work, don't describe the work.

The Antifragile Loop

Use the system → Find a gap → Fill it → System gets stronger
  • Agent missing context? → Update the slash command or memory file.
  • New workstream? → Create a new command .md.
  • Learned something the hard way? → Add it to memory.
  • New repo? → Create a repo-level CLAUDE.md.

License

MIT