4 reviewed skills.
Reviews a drafted customer reply for tone, clarity and risky promises, then returns a cleaner version. Use when a support agent pastes a draft and wants it checked before it goes to the customer.
Use when generating or reviewing interface designs, mockups or front-end code: steers away from generic template looks toward restrained color, clear type hierarchy, complete states, realistic copy and smooth, accessible motion.
Use when you have just written or changed code and before presenting it: runs a focused second pass for the mistakes generated code commonly contains, fixes what it can, and reports what was fixed and what needs the author's attention.
Standing approach for reviewing code: rank findings by impact, explain why, and suggest a fix. Use when asked to review code, a change or a pull request.
