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

openspec-kit

v0.2.0

Published

Project-scoped helpers for OpenSpec context templates

Readme

OpenSpec-Kit

Project-scoped helpers for OpenSpec context templates. This package provides a lightweight CLI that scaffolds template files and injects them into openspec/config.yaml so AI assistants have consistent project context.

Prerequisite: Install OpenSpec first: https://github.com/Fission-AI/OpenSpec

Install

pnpm add -D openspec-kit

Usage

# Scaffold templates into openspec/ (copies from the package templates/ directory)
pnpm exec opsx-kit init

# Inject template content into openspec/config.yaml
pnpm exec opsx-kit update

# Scaffold an enhanced workflow schema (fork spec-driven + exploration)
pnpm exec opsx-kit enhanced init <my-workflow>

Commands

opsx-kit init

Scaffold blank template files for editing.

Options:

  • --dir <target>: Target directory for scaffolded files (default: <project>/openspec)
  • --project <dir>: Project root used to locate openspec/ (default: current working directory)
  • --files <list>: Comma-separated list of files to initialize (default: all)

Example:

pnpm exec opsx-kit init --dir ./docs
pnpm exec opsx-kit init --files tech-stack,conventions

opsx-kit update

Inject template content into openspec/config.yaml.

Options:

  • --files <list>: Comma-separated list of files to inject (valid: tech-stack, conventions, architecture)
  • --source <dir>: Source directory containing filled-in templates
  • --project <dir>: Project root used to locate openspec/ (default: current working directory)

Example:

pnpm exec opsx-kit update --files tech-stack,conventions

opsx-kit enhanced init

Scaffold an enhanced workflow schema by forking spec-driven, copying the exploration template, and patching schema.yaml so exploration happens before proposal.

Options:

  • [schema]: Optional schema name (defaults to exploration-first)
  • --schema <name>: Schema name (overrides positional argument)
  • --project <dir>: Project root used to locate openspec/ (default: current working directory)

Example:

pnpm exec opsx-kit enhanced init exploration-first

Workflow

pnpm exec opsx-kit init
# Edit openspec/tech-stack.md, openspec/conventions.md, openspec/architecture.md
pnpm exec opsx-kit update

Environment Variables

  • OPENSPEC_TEMPLATE_DIR: Default source directory for update when --source is not provided.

Notes

  • update preserves the existing schema: value and any rules: section in openspec/config.yaml.
  • Templates are shipped inside the package under templates/.

Testing

See docs/testing.md for the test workflow.