Use when Codex on Windows needs to connect to a locally reachable MySQL or PostgreSQL database. Apply for client detection, PATH repair, connectivity validation, read-only SQL execution, and socket 10106 troubleshooting that may require bypassing the shell network stack with Node REPL MCP.
Use when working in Windows terminals where `rg` may resolve to an inaccessible bundled binary. Apply whenever searching files or text with ripgrep (`rg`, `rg --files`, `rg -n`) to force resolution of the machine-local rg.exe path and execute ripgrep by absolute path.
Use when writing, refactoring, reviewing, or documenting code where comments should be improved. Prefer structured, intent-focused comments with Chinese business-context style when appropriate, including section headers for major phases, professional tags for risks/performance/business constraints, Javadoc for public methods in Controller/Service/ServiceImpl classes, and concise call-site notes before important private helper method calls inside long public methods. Avoid noisy comments that only repeat syntax.
Use when writing, refactoring, reviewing, or modernizing Java code that should target Java 8 style. Prefer safe IntelliJ IDEA inspection suggestions and Java 8 idioms such as Map.computeIfAbsent, getOrDefault, removeIf, streams for clear transformations, method references, Optional where it improves null-handling, and String.trim().isEmpty() over length checks. Avoid overusing Optional, streams, or clever one-liners when plain code is clearer.