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 🙏

© 2025 – Pkg Stats / Ryan Hefner

rhachet-roles-ehmpathy

v1.13.3

Published

empathetic software construction roles and skills, via rhachet

Readme

rhachet-roles-ehmpathy

test publish

empathetic software construction roles and skills, via rhachet

purpose

install

npm install rhachet-roles-ehmpathy

use

readme --registry

npx rhachet readme --registry ehmpathy

produces

# 🤝 ehmpathy role registry

This registry defines the four core roles used to craft empathetic, evolvable, and maintainable software.

Each role represents a lens — a way of thinking about the system — grounded in empathy for both the **people using the product** and the **engineers maintaining the system**.

All roles maximize:

- clarity over cleverness
- maintainability over magic
- empathy over ego

---

## 🌱 Ecologist

- **scale**: domain fundamentals, real-world systems
- **focus**: what changes, what flows, what matters — ignoring software
- **maximizes**: fidelity to the real world

Used to understand the physics, incentives, and causal flows beneath the system.

---

## 🏛 Architect

- **scale**: cross-repo, organizational boundaries
- **focus**: bounded contexts, trust layers, language design
- **maximizes**: ubiqlang, evolvability, decoupling

Used to shape contracts and interfaces that survive change.

---

## 🎨 Designer

- **scale**: feature-level, user-experience layer
- **focus**: nudges, guardrails, pit-of-success defaults
- **maximizes**: usability, ergonomics, reliability

Used to sculpt workflows and interfaces that feel obvious and safe.

---

## 🔧 Mechanic

- **scale**: repo-level, implementation detail
- **focus**: maintainability, observability, readability
- **maximizes**: empathy for the 3am on-call engineer

Used to write and revise the actual logic that runs the system.

ask -r mechanic

the mechanic writes code within a repo

ask -r mechanic -s upsert

you can ask the mechanic to upsert the code in a target file or dir

  • if it exists, it'll update
  • if it doesn't, it'll create
npx rhachet ask -r mechanic -s upsert -t ./path/to/file.ts "your ask"
npx rhachet ask \
  --role mechanic \
  --skill upsert \
  --target ./path/to/file.ts \
  "your ask"

once it's self reviewed, it'll ask you for feedback

? have notes? (Use arrow keys)
❯ no notes
  yes notes

it'll loop until you tell it you have no notes