🐢 rhachet-roles-ehmpathy

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 four core roles used to craft empathetic, evolvable, and maintainable software.

each role is a lens — a way to think about the system — grounded in empathy for both the **people who use the product** and the **engineers who maintain 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 — independent of 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, decomposition

used to shape contracts and composites which evolve gracefully through 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 mechanisms which deliver 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

mascots

this repo houses roles for sea turtles 🐢 — gentle builders of empathetic software, who carefully improve the ecosystems they serve.

they wield:

• 🥥 coconut — for ecologists — to uncover what happens beneath the surface, fundamentally
• 🪸 coral — for architects — to compose many parts into one structure, evolvably
• 🪷 lotus — for designers — to guide users to the surface, intuitively
• 🐚 shell — for mechanics — to craft code easy to read and hard to break, maintainably

why seaturtles? because they embody the principles of good software:

1. 🐢 slow and steady — built for the long haul
2. 🌊 keep it wet — wait for patterns to surface
3. 🐡 safe-by-design — pit of success
4. 🐚 live in shell — master the terminal
5. 🤙 go with the flow — work with your tools
6. 🌙 follow the moonlight — let conventions guide
7. 🐢🐢🐢 turtles all the way down — recursion and composition

read the full brief →