Waza

Why

Waza (技) is a Japanese martial arts term for technique: a move practiced until it becomes instinct.

A good engineer does not just write code. They think through requirements, review their own work, debug systematically, design interfaces that feel intentional, and read primary sources. They write clearly, and learn new domains by producing output, not consuming content.

AI makes you faster. It does not make you think more clearly, ship more carefully, or understand more deeply. Waza turns each of these habits into a skill Claude can execute.

Skills

Each engineering habit gets a Claude Code skill. Type the slash command, Claude follows the playbook.

Skill	When	What it does
/think	Before building anything new	Challenges the problem, pressure-tests the design, validates architecture before any code is written.
/design	Building frontend interfaces	Produces distinctive UI with a committed aesthetic direction, not generic defaults.
/check	After a task, before merging	Reviews the diff, auto-fixes safe issues, blocks destructive commands via hooks, verifies with evidence.
/hunt	Any bug or unexpected behavior	Systematic debugging. Root cause confirmed before any fix is applied.
/write	Writing or editing prose	Rewrites prose to sound natural in Chinese and English. Strips AI writing patterns.
/learn	Diving into an unfamiliar domain	Six-phase research workflow: collect, digest, outline, fill in, refine, then self-review and publish.
/read	Any URL or PDF	Fetches content as clean Markdown via proxy cascade script. Dedicated handlers for WeChat and Feishu.
/health	Auditing Claude Code setup	Checks CLAUDE.md, rules, skills, hooks, MCP, and behavior. Flags issues by severity.

Each skill is a folder, not just a markdown file. Skills include reference docs, helper scripts, scoped hooks, and gotchas sections built from real project failures.

Extras

Statusline

A minimal Claude Code statusline that shows only what matters: context window usage, 5-hour quota, and 7-day quota, each with the time remaining until reset.

Color coding: green below 70%, yellow at 70-85%, red above 85% for context; blue, magenta, red for quota thresholds. No progress bars, no noise.

curl -sL https://raw.githubusercontent.com/tw93/Waza/main/scripts/setup-statusline.sh | bash

English Coaching

English should be every engineer's first language when working with AI. The model thinks in English, the best resources are in English, and writing clearly in English is a skill that compounds over time.

Passive grammar correction on every reply. Claude flags mistakes with the pattern name so you learn why.

😇 it is not good to be read → it's hard to read (Unnatural phrasing)

curl -sL https://raw.githubusercontent.com/tw93/Waza/main/templates/coaching-en.md >> ~/.claude/CLAUDE.md

Install

npx skills add tw93/Waza -g -y

Install a single skill:

npx skills add tw93/Waza -a claude-code -s health -y

Replace health with any skill name. Requires Node 18+ and Claude Code.

Background

Tools like Superpowers and gstack are impressive, but they are heavy. Too many skills, too much configuration, too steep a learning curve for engineers who just want to get things done.

There is a deeper issue with heavy skill collections: every rule the author writes becomes a ceiling. The model can only do what the instructions prescribe, and it cannot outgrow them. Waza takes the opposite approach. Each skill states a goal and the constraints that matter, then gets out of the way. As models improve, that restraint pays compound interest.

Waza is the opposite: eight skills that cover the habits that actuall