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

spec-init

v1.2.0

Published

Throughspec - Spec-driven. Drift-proof. Token-lean. Scaffolds a Claude Code project around a deterministic SDLC.

Readme

spec-init

Throughspec - spec-driven, drift-proof, token-lean scaffolding for Claude Code. spec-init bootstraps a project around a deterministic, spec-first SDLC: you make the decisions, Claude does the heavy lifting, and a fixed structure keeps the work from drifting.

The same CLI ships on npm (this package) and PyPI from one source-of-truth template tree, verified byte-for-byte.

Install

# one-off
npx spec-init my-project

# or globally
npm install -g spec-init
spec-init my-project

Requires Node ≥ 18.

Quickstart

# scaffold, then open in Claude Code and run /spec-requirements
npx spec-init my-project
cd my-project

Run with no arguments in a terminal for an interactive welcome (arrow-key selects for new-vs-existing, persona, and integrations). In a non-interactive shell (CI, pipes) it prints help instead, so scripts are unaffected.

spec-init <name> scaffolds the canonical Throughspec tree:

my-project/
├── CLAUDE.md
├── README.md
├── CHANGELOG.md
├── SECURITY.md
├── CONTRIBUTING.md
├── claude/
│   ├── srs.md
│   ├── plan.md
│   ├── context.md
│   ├── features.md
│   ├── design-decisions.md
│   └── learnings.md
├── design/
│   └── design.md
├── .claude/
│   ├── skills/
│   └── agents/
└── .spec-init/base/    # pristine snapshot for upgrade

Commands

| Command | Purpose | | --------------------------------------------- | ------------------------------------------------------------------- | | spec-init | With no args on a terminal, launch the interactive welcome | | spec-init init <name> | Scaffold a new project into <name>/ | | spec-init reinit [dir] | Adopt Throughspec in an existing project in place (non-destructive) | | spec-init customize --add / --remove <name> | Toggle an integration in an existing project | | spec-init customize --persona <name> | Swap the CLAUDE.md persona block | | spec-init add-skill <name> | Copy one skill from the payload catalog into .claude/skills/ | | spec-init upgrade | Three-way-merge a newer template payload into an existing project | | spec-init doctor | Verify a scaffolded project's shape |

Flags

  • --persona vibe\|student\|engineer\|team - which CLAUDE.md persona block to keep.
  • --integrations <csv> - activate integrations at scaffold time (see below).
  • --force - overwrite an existing directory (init) or replace existing spec files (reinit).
  • --dry-run - print the plan without writing files.
  • -h, --help / -v, --version.

Integrations

Opt-in, free/open-source tools layered in without touching your source. Add at scaffold time (--integrations graphify,caveman) or later (spec-init customize --add obsidian); remove with customize --remove <name>.

graphify, obsidian, caveman, agentmemory, openwiki, ponytail, opencodereview.

See the Integrations docs for what each does.

The .spec-init/base/ snapshot

init writes a pristine copy of the payload into <project>/.spec-init/base/. upgrade uses it as the common ancestor for its three-way merge against the newer shipped payload; doctor checks it exists. Don't edit files under .spec-init/ - they are the CLI's private state.

Links

  • Docs: https://throughspec.v-ai.org/docs/
  • Changelog: https://throughspec.v-ai.org/changelog/
  • Source & issues: https://github.com/VishalPatil18/throughspec

License

MIT © Vishal Patil