Labsco
Labsco/Repos/tw93/waza
REPO PACKAGE

tw93 waza

COMMUNITY
tw93 · publisher6,218 repository starsMIT · Freegithub.com/tw93/waza
8skills
7ready to use

Each skill maps to one habit and one slash command: /think produces a decision-complete plan before code is written; /ui produces UI with a committed aesthetic direction rather than generic defaults; /check reviews a diff or gates a release; /hunt finds a bug's root cause before any fix is applied; /write rewrites prose in Chinese or English and strips AI-sounding phrasing; /learn runs a six-phase research pass over a source bundle; /read fetches and summarizes a URL or PDF; and /health audits Claude Code's, Codex's, or Pi's own configuration for drift. The README lays out a suggested chain for each of four common workflows — plan a feature, ship a fix, research and write, debug and verify — but every handoff between skills is a manual step the user triggers, not an automatic pipeline.

It's for someone already running Claude Code, Codex, Cursor, or a compatible harness who wants a fixed set of habits enforced consistently rather than reinventing them per session — and, going by the README's own framing, wants exactly these eight and no more. Waza's author built it smaller on purpose, contrasting it with heavier alternatives like Superpowers, on the theory that fewer, sharper skills beat a large library.

READ THE FULL ANALYSIS

What we can't verify. The README says the project is "refined through 300+ sessions across 7 projects" and that every documented gotcha traces to a real failure; that's the author's own account of Waza's history, not something we independently checked. Two of the eight skills need a local tool already on the machine rather than installing clean — our dependency check splits the eight six ready, two local_tool — but the descriptions don't say which two, so we can't tell you without opening each skill file.

7Work with nothing else to set up.
6,218Stars on the GitHub repository, at last check.