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

product-engineer

v0.4.0

Published

Your agent ships code. product-engineer makes it ship outcomes. Four agent skills plus a zero-dependency check for the For-the-customer block in commit messages and pull requests.

Readme

一个智能体技能,让 AI 编码智能体像产品工程师一样思考,而不是像打印代码的机器。动手之前, 它先把任务改写成一句客户能看懂的结果。每个 commit 和 pull request 里,它都写一段通俗的 "For the customer" 说明。没有亲眼看到的工作,它不说"完成";有意没做的事,它点名说出来; 没有数过的数字,它一个也不写。

三十秒安装

npx skills add Bubblegunn/product-engineer

这是 skills.sh 的安装器。它会识别当前项目里的智能体,并为每一个放好 技能;--all 面向所有支持的智能体,-g 安装到用户级别而不是项目级别。

每个智能体的文件落在哪里、Claude Code 插件命令、git 钩子和 CI 步骤,都在 docs/install.md。仓库带四个技能:product-engineer(七条规则)、 customer-block(只要客户说明块)、done-means-observed(只要有据可查的"完成"报告)和 release-notes(给写发布说明、不写代码的智能体)。

之前和之后

之前:

fix(notifications): classify IsSystem events as idempotent and skip the badge increment

之后:

fix(notifications): classify IsSystem events as idempotent and skip the badge increment

For the customer:
What changed: Things the system handles on its own no longer light up the phone or the menu badge; only items that need a person do.
Why it matters: The badge count means "something needs you" again, so people stop ignoring it.
Automation effect: Automatic housekeeping events are now fully handled without anyone looking at them.

之前智能体这样汇报:

Done. All 42 tests pass.

之后:

Watched it in staging logs: 3 of 3 webhook retries logged, final failure recorded with the booking id.
Could not check: production, no deploy yet.
Not shipped:
- Dead-letter queue: three retries cover every failure in 90 days of logs.

七条规则

  1. 动手前先改写。一句话说清客户得到什么,否则只问一个问题。
  2. 每次都写给客户。改了什么,为什么重要,自动化效果只在真实时才写。
  3. 完成意味着看见。日志、数据或真实设备;否则说出没能检查的部分。
  4. 做被要求的事,说出没做的事。一份有理由的 Not shipped: 清单。
  5. 没有数过的数字不写。每个数字背后都有一条命令和一个范围。
  6. 说相关方的语言。技能自带术语与通俗说法的对照表。
  7. 用能推动指标的最小改动。每个设计之前先写一行账。

全文:skills/product-engineer/SKILL.md。模板、五个 问题、完成清单、通俗用语表和 not-shipped 格式在 references/ 下。

它不做什么

它不运行流程,也不接管工作流;它和规格、TDD、代码评审技能并行工作。它不写产品战略。 不安装钩子,它不强制任何事。

它从哪里来

这些是 Efe Genç 四年里作为一家住宿平台的创始工程师、以及一个主动式助手的唯一作者所遵循 的规则:一种向非技术读者解释每次改动的 commit 习惯,一种以亲眼看到运行为准的"完成"定义, 以及把有意没做的事写下来的习惯 (The feature I chose not to ship)。

参与

规则改动需要一组之前/之后的对照和一个评测任务;见 CONTRIBUTING.md路线图 有意保持简短。翻译和按技术栈的术语表标为 good first issue

引用

每个版本都在 Zenodo 上以 DOI 归档。

DOI

这是概念 DOI,始终解析到最新版本。要引用某个具体版本,请在该页面的侧栏中选择版本并使用那里显示的 DOI。仓库中的 CITATION.cff 带有同一标识符。

Star 数

MIT.