plumpslabs/matcha

🍵 Deliberate engineering guidelines & deterministic lifecycle safety hooks to enforce planning, prevent bloat, and block

Stars 1 Language JavaScript Last updated 2026-08-07 Source on GitHub @plumpslabs

Actual rules from this repo

Path in source repo: .cursor/rules/matcha.mdc · format: mdc

---
description: matcha engineering convention — read AGENTS.md at project root
globs: **/*
alwaysApply: true
---

# 🍵 matcha — Engineering Convention

This project uses the **matcha** engineering convention. Read the `AGENTS.md` file at the project root and follow its philosophy:

> Simple. Efficient. Deliberate. Never twice.

Key principles (see AGENTS.md for the full ruleset):
- **⚖️ Proportionality (effort ↔ risk)** — match ceremony to task size. Trivial (≤5 LOC, 1 file, no logic): minimal plan, fast pass. Small (1-3 files): short plan + light review. Large (cross-cutting/prod risk): full gate. Planning > implementation = over-planning. Exit conditions beat STOP — proceed on a recorded assumption rather than blocking on trivia.
- **Purpose (Intent Discovery)** — know *why* before *how*. Can't explain why/how? Stop and rethink — unless the task is trivial, then proceed on a recorded assumption.
- **Reuse** — search the codebase before writing new code. Never write what exists.
- **Implementation** — one function, one job. Explicit errors. No hardcoded values. Validate inputs at boundaries. Never log secrets/PII.
- **Cleanup** — done means working *and* clean. No debug leftovers, no dead code.
- **Verify** — run tests, typecheck, and lint before declaring done.

Respect the `// matcha:` decision markers when you find them in code — they are intentional, logged shortcuts.

View raw on GitHub

Why this is listed

This repository appears on Cursor Rules Live because it matches the tracker's GitHub Search criteria (cursor-rules) and was active in the recent indexing window. The tracker refreshes every 15 minutes, so the metadata above reflects the state at the most recent index pass. If the data here looks stale, the source repository may have been archived or moved out of the tracked topic; the next cron tick will reconcile.

Similar in this tracker

Explore by category