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

@ner076/prd-toolkit

v0.1.5

Published

AI-powered PRD toolkit: guided discovery + auto-dev ready PRD generation for Claude Code and Opencode

Readme

@ner076/prd-toolkit

AI-powered PRD toolkit — guided discovery + auto-dev ready PRD generation for Claude Code and Opencode.

Turn a fuzzy product idea into a PRD that AI coding agents can implement without going off-rails.


What you get

Two skills, one install:

  • prd-discovery — guided 8-phase discovery session (Express / Guided / Deep modes) that captures features, sub-features, dependencies, data model, business rules, and granular design tokens. Outputs a structured discovery-output.md.
  • prd-generator — transforms the discovery output into a 16-section PRD with API contracts, data schemas, screen specs, state machines, test scenarios, and a full traceability matrix.

Install

One command, auto-detects your environment:

npx @ner076/prd-toolkit install

Or be explicit:

# Both targets, user-wide
npx @ner076/prd-toolkit install --target=all --scope=user

# Only Opencode, non-interactive
npx @ner076/prd-toolkit install --target=opencode -y

# Preview without writing
npx @ner076/prd-toolkit install --dryRun

Install locations

| Target | Scope | Location | |--------|-------|----------| | Claude Code | user | ~/.claude/skills/<name>/SKILL.md | | Claude Code | project | ./.claude/skills/<name>/SKILL.md | | Opencode | user | ~/.config/opencode/command/<name>.md | | Opencode | project | ./.opencode/command/<name>.md |

Default scope is project so you don't pollute global config.


Usage

In Claude Code

$ cd my-product
$ claude
> jalankan prd-discovery, gua mau bikin aplikasi X

Claude Code will auto-load the prd-discovery skill and start the guided session.

In Opencode

$ opencode
> /prd-discovery

The command runs the same discovery workflow as a subtask.

Chained workflow

1. /prd-discovery       → produces discovery-output.md
2. /prd-generator       → produces PRD-<slug>.md
3. Feed PRD to your AI coding agent for auto-implementation

Command reference

npx @ner076/prd-toolkit <command> [flags]

Commands:
  install       Install skills to target environment(s)
  uninstall     Remove installed skills (tracked via manifest)
  update        Re-install to pick up latest version
  list          Show installed skills across all targets
  doctor        Diagnose environment & install health
  help          Show help

Flags:
  --target=<t>  claude-code | opencode | all | auto (default: auto)
  --scope=<s>   user | project (default: project)
  -y, --yes     Skip confirmation prompts
  -f, --force   Overwrite existing files
  --dryRun      Preview without writing
  -v, --version Print version

Design

Why a toolkit, not just skill files?

  • One-command install works across environments
  • Format transformation — source of truth is one SKILL.md, adapters handle target-specific formatting
  • Manifest-based uninstall — clean removal without touching unrelated files
  • Environment detection — no manual "where do I put this?" hunt

Architecture

prd-toolkit/
├── bin/prd-toolkit.js        # CLI entry
├── src/
│   ├── install.js            # orchestrator
│   ├── uninstall.js
│   ├── list.js
│   ├── doctor.js
│   ├── detect.js             # env detection
│   ├── help.js
│   ├── version.js
│   └── adapters/
│       ├── claude-code.js    # copies SKILL.md verbatim
│       └── opencode.js       # transforms frontmatter for command format
└── skills/
    ├── prd-discovery/SKILL.md
    └── prd-generator/SKILL.md

Source SKILL.md files use Claude Code frontmatter (name, description). The Opencode adapter transforms this into command-style frontmatter (description, agent, subtask) while preserving the body verbatim.

Requirements

  • Node.js 18+ (uses native parseArgs)
  • At least one of: Claude Code CLI, Opencode CLI

Publishing (maintainer notes)

This package publishes to npm under @ner076. To release:

# Bump version
npm version patch|minor|major

# Push tag — CI publishes automatically
git push --follow-tags

CI runs on Node 18/20/22 across Ubuntu, macOS, and Windows. Publish requires an npm access token stored as NPM_TOKEN in GitHub Actions secrets.


License

MIT © Bagas