by tw93
🥷 Engineering habits you already know, turned into skills AI assistants like Claude Code, Codex and Cursor can run.
From $49 · 30 days · terms & refunds
⚠️ Third-Party Software Notice
This skill is third-party open-source software developed and hosted independently on GitHub. SkillsLLM lists this project for discovery and does not control or maintain the underlying repository.
Any security checks, ratings, or warnings displayed by SkillsLLM are automated and limited in scope. They do not constitute a security certification or guarantee that the software is safe, error-free, or free from malicious code, vulnerabilities, compromised dependencies, or prompt-injection risks.
Review the source code, permissions, dependencies, and configuration before installing or running any third-party skill. Use is at your own risk. To the maximum extent permitted by applicable law, SkillsLLM is not liable for losses arising from third-party software.
Automated security scan — not a certification.
# Add to your Claude Code skills
git clone https://github.com/tw93/WazaGuides for using ai agents skills like Waza.
Last scanned: 4/21/2026
{
"issues": [],
"status": "PASSED",
"scannedAt": "2026-04-21T06:03:05.858Z",
"semgrepRan": false,
"npmAuditRan": true,
"pipAuditRan": true
}See how Waza compares with popular alternatives.
Each engineering habit gets an installed skill, a folder with reference docs, helper scripts, and gotchas from real failures. 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. |
/ui |
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 against project constraints, verifies the result, and handles approved release and maintainer actions. |
/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 | Returns a concise summary, or clean Markdown for conversion, quotes, citations, saving, or further research. |
/health |
Auditing agent setup | Checks Codex, Claude Code, project instructions, verifier output, and AI maintainability with a budget-aware summary pass before deep inspection. |
Claude Code, Codex, Cursor, and other agents
npx skills add tw93/Waza -a claude-code codex cursor -g -y
One copy lands in ~/.agents/skills, the shared skills directory. Claude Code is symlinked in; Codex, Cursor, Gemini CLI, Copilot, Amp, Kimi Code CLI, and every other agent that reads that directory picks the eight skills up as /check, /think, and so on. Agents with a private skills directory take their id after -a (for example antigravity-cli or qwen-code). Update with npx skills update -g -y. You can also tell your agent to install it:
Install Waza for me by reading https://github.com/tw93/Waza/blob/main/llms.txt
Host plugin, if you prefer the host's own update command (skills are namespaced, /waza:check)
# Claude Code (update: claude plugin update waza)
/plugin marketplace add tw93/Waza
/plugin install waza@waza
# Codex (update: codex plugin marketplace upgrade waza, then codex plugin add waza@waza)
codex plugin marketplace add tw93/Waza
codex plugin add waza@waza
Claude Desktop: download waza.zip, open Customize > Skills > "+" > Create skill, and upload the ZIP. To update, click "..." on the skill card, choose Replace, and upload the latest ZIP.
Pi: pi install npm:@tw93/waza, update with pi update npm:@tw93/waza.
You decide how skills chain together. Each skill stops at the requested outcome; an explicitly authorized workflow continues without asking you to approve every transition.
Common workflows:
/think to settle the plan, implement after approval, then /check before merging/hunt to find the root cause, fix it, then /check to review the changes and, when needed, handle release, publish, push, and issue follow-through/read to fetch sources, /learn to synthesize, /write to polishThe stages a task moves through, and the rules each one holds, are in the AI coding rules.
Waza ships only generic engineering habits. /check becomes project-aware at runtime by reading the target repository's public context (READMEs, package manifests, Makefiles, CI workflows) and your task constraints, never private paths, credentials, or tokens. See skills/check/references/project-context.md for the review context template.
Curl URLs use the latest GitHub release asset. Set WAZA_REF=main before the command if you want bleeding-edge scripts.
A minimal statusline for Claude Code: context window, 5-hour quota, and 7-day quota. Color-coded by usage, no progress bars, no noise.
(
set -e
WAZA_STATUSLINE_SCRIPT="$(mktemp -t waza-statusline.XXXXXX)"
trap 'rm -f "$WAZA_STATUSLINE_SCRIPT"' EXIT
curl -fL https://github.com/tw93/Waza/releases/latest/download/setup-statusline.sh -o "$WAZA_STATUSLINE_SCRIPT"
# review it first: less "$WAZA_STATUSLINE_SCRIPT"
bash "$WAZA_STATUSLINE_SCRIPT"
)
Codex has native statusline items. Add to ~/.codex/config.toml:
[tui]
status_line = ["model-with-reasoning", "current-dir", "context-used", "five-hour-limit", "weekly-limit"]
status_line_use_colors = true
Codex shows remaining quota; the Claude Code statusline above shows used percentage (upstream does not yet expose five-hour-used / weekly-used).
Optional rules apply beyond skill invocations when installed into your agent's persistent instructions. Installing Waza skills alone does not enable them. Copy the ones you want (swap claude-code for codex or antigravity-cli on those agents):
(
set -e
WAZA_RULE_SCRIPT="$(mktemp -t waza-rule.XXXXXX)"
trap 'rm -f "$WAZA_RULE_SCRIPT"' EXIT
curl -fL https://github.com/tw93/Waza/releases/latest/download/setup-rule.sh -o "$WAZA_RULE_SCRIPT"
# review it first: less "$WAZA_RULE_SCRIPT"
# English coaching: appends a short 😇 correction when your prompt has an English mistake
bash "$WAZA_RULE_SCRIPT" english claude-code
# Anti-patterns: always-on cross-skill guardrails (read before acting, no scope creep, no unsolicited summaries)
bash "$WAZA_RULE_SCRIPT" anti-patterns claude-code
# Routing hint: tells non-Claude hosts to prefer Waza skills when a request matches their triggers
bash "$WAZA_RULE_SCRIPT" waza-routing claude-code
# Clear everyday replies: consistent terms, explicit conditions, preserved uncertainty
bash "$WAZA_RULE_SCRIPT" clarity claude-code
# Chinese writing: applies these habits to Chinese replies and prose
bash "$WAZA_RULE_SCRIPT" chinese claude-code
)
Clarity uses clear-writing principles from ASD-STE100 without imposing controlled-English grammar or changing your voice. Re-run its command to update the installed rule, then start a new session. Codex installs a marked block in ~/.codex/AGENTS.md; Claude Code and Antigravity install a rule file. For other tools, copy the rule into their persistent custom instructions.
Waza (技, わざ) is a Japanese martial arts term for technique: a move practiced until it becomes instinct. A good engineer does more than write code. They pressure-test requirements, debug to root cause, review their own diffs, and read primary sources. AI has the raw output for all of it, but without structure that output drifts into generic, imprecise work. Each Waza skill states the outcome, the red lines, and how the result gets verified, then steps back and lets the model choose the path. As models improve, that restraint pays compound interest.
Tools like Superpowers and gstack are powerful but heavy: too many skills, too much configuration. Waza stays small, eight skills for the habits that actually matter, each with one job and a clear trigger. The skills were built from real projects and refined through 300+ sessions across 7 projects, and every gotcha traces to a real failure. The /health skill grew from the six-layer Claude Code framework in this post.
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.
npx skills remove tw93/Waza -g
rm -f ~/.claude/statusline.sh
rm -f ~/.claude/rules/english.md
rm -f ~/.claude/rules/anti-patterns.md
rm -f ~
Waza is an open-source ai agents skill for AI coding assistants such as Claude Code, Codex CLI, and ChatGPT, built by tw93. 🥷 Engineering habits you already know, turned into skills AI assistants like Claude Code, Codex and Cursor can run. It has 7,608 GitHub stars.
Yes. Waza passed SkillsLLM's automated security scan — a dependency vulnerability audit plus prompt-injection heuristics — with no high-severity issues. You can read the full report in the Security Report section on this page.
Clone the repository with "git clone https://github.com/tw93/Waza" and add it to your Claude Code skills directory (see the Installation section above).
Waza is primarily written in Python. It is open-source under tw93 on GitHub, so you can review or fork the full source.
Yes. SkillsLLM lists many other AI Agents skills you can browse and compare side by side. Open the AI Agents category from the badge at the top of this page, or use the Related Skills and comparison links further down to weigh Waza against similar tools.
No comments yet. Be the first to share your thoughts!