Waza Adds Engineering Habits to Claude Code

This is useful because it turns “be a better engineer” into executable tooling, which is far more likely to survive real workflows than a one-off prompt template.

• –The strongest idea is operational discipline: `/think`, `/check`, `/hunt`, and `/health` encode review, debugging, and setup verification into repeatable commands
• –`/design` and `/write` aim at output quality, pushing Claude away from generic UI and awkward AI prose
• –The repo goes beyond markdown by bundling helper scripts, hooks, and per-skill folders, which makes the habits harder to ignore and easier to maintain
• –It is most compelling for teams already deep in Claude Code who want shared defaults, not just individual prompt tricks
• –The downside is obvious too: these habits only help if the underlying skill content is strong and the team actually adopts the workflow