Skip to content

About

codex-coding-skills

Resources

Stars

1 star

Watchers

0 watching

Forks

 
 

Latest commit

 

History

220 Commits

Folders and files

Repository files navigation

Waza

Engineering habits you already know, turned into skills Codex can run.

Stars Version License Twitter

中文说明:README_CN.md

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 Codex can run.

Skills

Each engineering habit gets a Codex skill. Use the matching skill name or ask Codex to follow the playbook for that workflow.

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, 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 Codex workspace setup Checks AGENTS.md, task docs, skills, MCP/config, and verification paths. 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.

Extras

This fork focuses on Codex skills only. Legacy vendor-specific statusline and coaching extras were intentionally removed from the installation flow.

Install

Install all skills into Codex:

export CODEX_HOME="${CODEX_HOME:-$HOME/.codex}"
mkdir -p "$CODEX_HOME/skills"
cp -R skills/* "$CODEX_HOME/skills/"

Restart Codex after copying so the new skills are discovered.

Install a single skill:

export CODEX_HOME="${CODEX_HOME:-$HOME/.codex}"
mkdir -p "$CODEX_HOME/skills"
cp -R skills/health "$CODEX_HOME/skills/"

Replace health with any skill name.

For updates, recopy the modified skill directory into "$CODEX_HOME/skills" and restart Codex.

Compatibility: This fork is maintained for Codex. think, hunt, learn, write, design, check, and the Codex-adapted health workflow are kept in sync with ~/.codex/skills.

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'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 in this fork is adapted from the six-layer framework described in this post, but rewritten for Codex workspace conventions.

Support

  • If Waza helped you, share this fork 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 🥩.

License

MIT License. Feel free to use Waza and contribute.

About

codex-coding-skills

Resources

Stars

1 star

Watchers

0 watching

Forks

Releases

Packages

Contributors

Languages