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 doesn't make you think more clearly, ship more carefully, or understand more deeply. Waza packages these habits into skills Claude can run.
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, flags destructive commands, 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. Cuts stiff, formulaic phrasing. |
/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 with platform-specific routing. Special handling for GitHub, PDFs, 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, and gotchas sections built from real project failures.
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 | bashMost AI models were trained on far more English than any other language, so every prompt in your native tongue goes through an invisible translation layer. Switch to English and the reasoning sharpens, answers get more precise, and every session doubles as language practice.
Claude corrects your mistakes in place, tagging each one with its pattern name so you learn the rule, not just the fix.
curl -fsSL https://raw.githubusercontent.com/tw93/Waza/main/rules/english.md -o ~/.claude/rules/english.mdClaude Code
npx skills add tw93/Waza -a claude-code -g -yOther agents
Pick your agent interactively.
npx skills add tw93/WazaSingle skill
npx skills add tw93/Waza -a claude-code -s health -yReplace health with any skill name.
Safety
To protect against destructive git commands (git push -f, git checkout ., git clean -f), add them to the deny list in your ~/.claude/settings.json.
Compatibility
Core instruction skills /think, /hunt, /learn, /write, /design run on any agent. Claude Code-specific features are skipped on other platforms: /check loses sub-agent reviewers; /health and /read lose their shell scripts for URL fetching and config auditing.
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's also a subtler problem. Every rule the author writes becomes a ceiling. The model can only do what the instructions say and can't go further. Waza goes the other direction. Each skill sets a clear goal and the constraints that matter, then steps back. As models improve, that restraint pays compound interest.
Eight skills for the habits that actually matter. Each does one thing, has a clear trigger, and stays out of the way. Not complete by design, just the right amount done well.
Built from patterns across real projects, refined through actual use. Every gotcha traces to a real failure: a wrong code path that took four rounds to find, a release posted before artifacts were uploaded, a server restarted eight times without reading the error. 30 days, 300+ sessions, 7 projects, 500 hours.
The /health skill is based on the six-layer framework described in this post.
- If Waza helped you, share it with friends or give it a star.
- Got ideas or bugs? Open an issue or PR, feel free to contribute your best AI model.
- I have two cats, TangYuan and Coke. If you think Waza delights your life, you can feed them canned food 🥩.
MIT License. Feel free to use Waza and contribute.