Engineering habits you already know, turned into skills your agent can run.
Stars Version License TwitterWaza (技, わざ) 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 is more capable than most engineers at raw output. But without structure, that capability drifts into generic, imprecise work. Waza channels it into precision: eight skills that set clear goals and constraints, then let the model do what it does best.
Part of a trilogy: Kaku (書く) writes code, Waza (技) drills habits, Kami (紙) ships documents. Think of them as a family: Kaku is the dad, Waza the big sister, Kami the little sister.
Each engineering habit gets an installed skill. In Claude Code, type the slash command. In Codex, invoke the installed skill by name and follow the same playbook.
| Skill | When | What it does |
|---|---|---|
/think |
Before building anything new | Challenges the problem, pressure-tests the design, and produces a decision-complete plan another agent can implement. |
/design |
Building frontend interfaces | Produces distinctive UI, including screenshot-driven aesthetic iteration, with a committed direction rather than generic defaults. |
/check |
After a task, before merging or release | Reviews the diff, extracts project-specific constraints, handles approved release/publish/push/reaction follow-through, and verifies with evidence. |
/hunt |
Any bug, regression, or unexpected behavior | Systematic debugging. Root cause confirmed before any fix is applied, especially when something used to work. |
/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 agent setup | Checks Claude Code or Codex instructions, skills, plugins/tools, MCP, permissions, and verifiers with a budget-aware summary pass before deep inspection. |
Each skill is a folder with reference docs, helper scripts, and gotchas from real failures.
Most users should install Waza globally, so the same skills are available in every project.
Claude Code direct slash commands
npx skills add tw93/Waza -a claude-code -g -y
This installs the individual /think, /design, /check, /hunt, /write, /learn, /read, and /health skills. Install just one with --skill:
npx skills add tw93/Waza --skill think -a claude-code -g -y
Claude Code plugin marketplace
Install all skills via the waza bundle, or just one via a waza-<skill> entry:
/plugin marketplace add tw93/Waza /plugin install waza@waza /plugin install waza-think@waza
Codex
npx skills add tw93/Waza -a codex -g -y
Install just one with --skill:
npx skills add tw93/Waza --skill think -a codex -g -y
In Codex, press $ and select the installed skill, or name it directly in your prompt:
$think 判断这个方案要不要做
$hunt 排查这个测试失败
$check review 当前 diff
$health 检查我的 Codex 配置是不是太重
Claude Desktop
Download waza.zip, open Customize > Skills > "+" > Create skill, and upload the ZIP.
Update
npx skills update -g -y
Marketplace installs use claude plugin update <skill>. Claude Desktop users can replace the old skill with the latest waza.zip.
Compatibility
/health supports Claude Code and Codex. It defaults to a summary audit to avoid burning quota on first run; ask for a deep or full health audit when you want full conversation extracts and inspector subagents. The other skills are written to use the host environment's native question, search, fetch, and agent mechanisms. /check runs parallel specialist reviewers when the host supports them; otherwise it performs the same passes inline.
Waza keeps the generic programmer habits inside the public skill. /check becomes project-aware by reading the target repository's public context and the user's task constraints.
- Project commands come from README files, package manifests, Makefiles, CI workflows, and explicit user instructions.
- Project hard stops include generated artifacts, protected files, version synchronization, release assets, and domain-specific safety risks.
- Public docs and examples must not include credentials, certificate paths, private key filenames, tokens, or personal machine details.
See skills/check/references/project-context.md for the review context template.
Skills are designed to be chained together, but transitions are manual. Each skill stops after completing its task and waits for you to decide the next step.
Common workflows:
- Design a feature:
/think→ approve → say "implement X" →/check→ merge - Ship a fix:
/hunt→ fix →/check→ release/publish/push/issue follow-through - Research and write:
/read(fetch sources) →/learn(synthesize) →/write(polish) - Debug and verify:
/hunt(find root cause) → fix →/check(review changes)
Each arrow represents a manual user action. Skills don't automatically trigger each other.
A minimal statusline for Claude Code: context window, 5-hour quota, and 7-day quota.
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 | bashOptional rule for English practice. When your prompt contains an English mistake, the agent appends a short 😇 correction; Chinese-only prompts stay untouched.
# Claude Code curl -sL https://raw.githubusercontent.com/tw93/Waza/main/scripts/setup-english-coaching.sh | bash -s -- claude-code # Codex curl -sL https://raw.githubusercontent.com/tw93/Waza/main/scripts/setup-english-coaching.sh | bash -s -- codex
# Remove all skills npx skills remove tw93/Waza -g # Remove Claude Desktop skill # Open Customize > Skills, find Waza, click "..." > Delete # Remove statusline rm -f ~/.claude/statusline.sh # Then remove the statusLine key from ~/.claude/settings.json # Remove English Coaching (Claude Code) rm -f ~/.claude/rules/english.md # Remove English Coaching (Codex): remove the Waza English Coaching marked block from ~/.codex/AGENTS.md
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.