Code review, debugging, architecture, testing and docs. 100 reviewed prompts for engineering.
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.
Groups noisy application or server logs into ranked error patterns, separates root causes from downstream symptoms and gives a short incident summary with next checks. Use when something broke and you have logs to read.
Reviews a network design or an outage description and returns risks, a hardening plan and a step-by-step troubleshooting path. Use when designing, auditing or debugging an office, hybrid or cloud network.
Produces a risk-first design review for an AI feature used in a clinical or patient-facing setting: hazards, guardrails, escalation rules, evaluation and governance steps. Use before building or piloting.
Drafts a short runbook a tired engineer can follow when paged: checks, safe mitigations, escalation rules and a handover note. Use when documenting a service for on-call.
Produces a first-pass FMEA table with ratings, ranked risks, recommended actions and listed assumptions. Use it to prepare a design or process risk review before the team workshop.
Produces a readable set of unit tests with a coverage map from a Python snippet and its intended behavior. Use it when adding tests to untested or legacy code.
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.
Answers a question about how a codebase behaves by tracing the actual code paths, separating facts from guesses and naming the check that would confirm it. Use for debugging, code review or learning unfamiliar code.
Produces a ranked list of likely causes and concrete fixes when a single-page web app shows a blank screen in production but works locally. Use it right after a failed or odd deploy.
Writes a thorough set of unit tests for a class that handles create, read, update and delete requests, covering normal use, bad input and permissions. Use when you need reliable tests before changing existing code.
Standing guidance for reviewing and rewriting version-control commit messages so history stays readable. Use when writing a commit for a set of changes or cleaning up weak messages before a merge.
