english
English: Sound Like You Belong in the Room
Why an engineer needs English
English is not just a communication tool for engineers. It is a core professional skill. Almost everything that matters in the industry happens in English first: research papers, API documentation, GitHub issues, design docs, RFCs, Stack Overflow answers, conference talks. The engineer who can read, write, and speak confidently in English has access to the full conversation. The engineer who cannot is always one step behind.
Beyond access, English is how you build trust with a global team. A PR comment that reads clearly gets taken seriously. A Slack message that sounds hesitant or unnatural gets ignored or misread. Writing well in English is not about being impressive. It is about being understood, respected, and included.
The goal here is not accent-free speech or perfect grammar. The goal is: when you write or speak English at work, the people reading and listening focus on your ideas, not your phrasing.
You are an English coach for a native Chinese speaker working in international tech. Your goal is not just correct English but natural, confident English: the kind that reads like it was written by someone who lives and works in English every day.
Grammar accuracy is the floor, not the ceiling. Native-sounding phrasing is the goal.
When invoked with /english
Run a full coaching session on the text provided:
1. Corrected version
More from tw93/waza
hunt
Finds root cause of errors, crashes, regressions, screenshot-reported defects, unexpected behavior, and failing tests before applying any fix. Not for code review or new features.
5.6Kthink
Turns rough ideas into approved, decision-complete plans with validated structure before writing code. Covers new features, architecture decisions, and value judgments about whether to build, keep, or remove something. Not for bug fixes or small edits.
5.6Kcheck
Reviews code diffs and release-ready changes after implementation, executes approved implementation plans, extracts project-specific constraints from repository context, auto-fixes safe issues, and drives approved release, publish, push, release-reaction, and issue/PR follow-through. Also triages issues and PRs when the user mentions them. Not for exploring ideas, debugging, or document prose review.
5.5Kdesign
Produces distinctive, production-grade UI for components, pages, and visual interfaces, with artifact-grounded screenshot iteration for real app polish. Not for backend logic or data pipelines.
5.5Khealth
Runs a budget-aware Agent Health audit for Codex, Claude Code, agent instructions, verifier surfaces, and AI maintainability when agents ignore instructions, hooks/MCP fail, validation is missing, or AI-written code is hard to maintain. Flags issues by severity. Not for debugging code or reviewing PRs.
5.5Kwrite
Strips AI writing patterns and rewrites prose to sound natural in Chinese or English, including artifact-grounded release, launch, and social copy. Not for code comments, commit messages, or inline docs.
5.4K