Code review, debugging, architecture, testing and docs. 5 reviewed prompts for engineering.
Diagnoses what makes working code hard to change and lays out small, low-risk refactoring steps with a safety net of tests and a before/after example. Use before cleaning up a messy module.
Standing guidance for building user interface code: component structure, state, accessibility, performance and testing. Use when you write or review front-end code for a web app.
Use when pairing with someone on code or architecture: asks before building on ambiguous requirements, explains choices briefly, admits uncertainty, and tells the user directly when their approach has a problem.
Requires real evidence before a software change is reported as finished: build and tests run, the change exercised directly, at least one edge case tried, and results shown. Use when you implement, fix or verify code and can run checks.
Produces an evidence-based debt register for a codebase or module: ranked findings with file references, severity and effort, top fixes, quick wins and things that only look bad. Use it to plan refactoring work.
