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

@sublang/spex

v0.2.3

Published

The essential spec layer AI agents need to build software reliably

Readme

spex

npm version Node.js CI

The essential spec layer AI agents need to build software reliably.

Scaffolds a specs/ directory so AI coding agents can read and follow your project's requirements and design.

Install

npm install -g @sublang/spex

Or run once without installing:

npx @sublang/spex scaffold

Usage

spex scaffold

This creates:

  • specs/ — directories and starter templates for writing behavioral specs, decision records, and iteration plans
  • CLAUDE.md / AGENTS.md — instructions that tell AI agents (Claude, Codex, etc.) to read and follow the specs before writing code

See specs/decisions/000-spec-structure-format.md for the spec format and naming conventions.

Idempotency: Rerunning is safe — existing files and directories are skipped.

Try it: review the sample iteration specs/iterations/000-spdx-headers.md, update the copyright text, then prompt your AI coding agent:

Complete Iteration #0

Updating templates

When a new release ships updated templates, refresh them with:

spex scaffold --update
  • Spex-authoritative files (specs/meta.md and the spec-format decision record) are refreshed unconditionally, including when they are absent.
  • Starter files (map.md, the sample iteration, boilerplate items) are refreshed when you have not customized them, and written from the bundled template when they are absent. Customized starter files are kept as-is. Remove a starter file after --update if you do not want it.
  • Anything you authored outside the bundled framework and starter files is left alone.

Review the changes with git diff -- specs. Update any citations that reference renamed sections or renumbered IDs — the command prints clear next steps and a copy-paste-ready prompt you can hand to your AI agent for that review.

Workflow

Spex does not enforce a heavyweight workflow. We believe spec-driven development is a flexible combination of a few primitives.

  1. Make Decisions — Discuss requirements, architecture, and design with AI agents. Let AI generate and review decision records in specs/decisions/.
  2. Plan Iterations — Break down work into tasks with AI agents. Let AI generate and review iteration records in specs/iterations/.
  3. Agents Execute — Let AI agents complete the tasks autonomously. They generate code and update specs/user/, specs/dev/, and specs/test/.

Then loop back to the next decision or iteration.

Requirements

  • Node.js >= 20
  • Git (optional, used for repo root detection)

Contributing

We welcome contributions of all kinds. If you'd like to help:

  • 🌟 Star our repo if you find spex useful.
  • Open an issue for bugs or feature requests.
  • Open a PR for fixes or improvements.
  • Discuss on Discord for support or new ideas.

License

Apache-2.0