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

xwang-mattpocock

v0.1.2

Published

Claude Code skills for rigorous design review and product documentation. Includes grill-with-docs and to-prd.

Readme

xwang-mattpocock

A collection of Claude Code skills for rigorous design review and product documentation.

Skills

This package ships two skills for use with Claude Code:

  • grill-with-docs — interview you relentlessly about a plan until you reach shared understanding, while keeping CONTEXT.md and ADRs in sync.
  • to-prd — turn the current conversation context into a PRD and publish it to your issue tracker.

Install

Install the package as a dev dependency:

npm install --save-dev xwang-mattpocock

Then copy the skills you want into your project's Claude Code skills directory:

# grill-with-docs
cp -r node_modules/xwang-mattpocock/skills/grill-with-docs .claude/skills/

# to-prd
cp -r node_modules/xwang-mattpocock/skills/to-prd .claude/skills/

Note: node_modules/.claude/skills/ is also supported if your project stores skills inside the dependency tree.


grill-with-docs

A grilling session that challenges your plan against the existing domain model, sharpens terminology, and updates documentation (CONTEXT.md, ADRs) inline as decisions crystallise.

When to use

Use when you want to stress-test a plan against your project's language and documented decisions.

How to invoke

In Claude Code, say something like:

"grill me on this plan" "grill this design with docs"

What it does

  • Asks one focused question at a time, waiting for your answer before continuing.
  • Explores the codebase (and existing docs) instead of asking when the answer is already there.
  • Calls out terms that conflict with your CONTEXT.md glossary.
  • Proposes precise canonical terms for vague or overloaded language.
  • Stress-tests domain relationships with concrete edge-case scenarios.
  • Cross-references your claims against the code and surfaces contradictions.
  • Updates CONTEXT.md lazily as terms are resolved.
  • Offers to create ADRs only for decisions that are hard to reverse, surprising without context, and the result of a real trade-off.

Documentation it maintains

  • CONTEXT.md — the project's domain glossary. Created lazily at the repo root (or inside a bounded context for multi-context repos). See skills/grill-with-docs/CONTEXT-FORMAT.md.
  • docs/adr/000N-slug.md — architecture decision records. Created lazily with sequential numbering. See skills/grill-with-docs/ADR-FORMAT.md.

to-prd

Takes the current conversation context and codebase understanding and produces a Product Requirements Document, then publishes it to the project issue tracker.

When to use

Use when you want to turn an explored problem and agreed solution into a published PRD.

How to invoke

In Claude Code, say something like:

"turn this into a PRD" "to PRD"

What it does

  1. Explores the repo to understand the current state, using the project's domain glossary and respecting relevant ADRs.
  2. Identifies the highest-level test seams for the feature, preferring existing seams over new ones.
  3. Writes a PRD from the conversation context using the following sections:
    • Problem Statement
    • Solution
    • User Stories
    • Implementation Decisions
    • Testing Decisions
    • Out of Scope
    • Further Notes
  4. Publishes the PRD to the issue tracker and applies the ready-for-agent triage label.

The issue tracker and triage label vocabulary should have been provided beforehand — run /setup-matt-pocock-skills if not.


Package contents

xwang-mattpocock/
├── skills/
│   ├── grill-with-docs/
│   │   ├── SKILL.md
│   │   ├── CONTEXT-FORMAT.md
│   │   └── ADR-FORMAT.md
│   └── to-prd/
│       └── SKILL.md
├── README.md
└── LICENSE

License

MIT