tw93-claude-health

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 doesn't make you think more clearly, ship more carefully, or understand more deeply. Waza packages these habits into skills Claude can run.

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.

Skills

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, 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 with reference docs, helper scripts, and gotchas from real failures.

Chaining Skills

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
• 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.

Extras

Statusline

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 | bash

English Coaching

Most 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.