Unit tests for a Python function or module
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.
Code review, debugging, architecture, testing and docs. 88 reviewed prompts for engineering.
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.
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.
Reviews how an organization stores and shares sensitive data and proposes a prioritized protection plan covering access, encryption, sharing rules and monitoring. Use when tightening data handling in a small team.
Designs a tested, low-noise detection rule for a suspicious behavior in your own logs, with false-positive tuning, evasion considerations, a safe test plan and analyst triage steps. Use it for defensive security monitoring.
Guides a bug fix that starts with a failing test, then the smallest fix, then proof nothing else broke. Use it when you or an assistant must fix a defect without causing regressions.
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.
Designs a firmware module for a resource-limited microcontroller: stated hardware assumptions, task and interrupt layout, memory and timing rules, a C code skeleton, and a verification and rollout plan. Use when starting a driver or feature on embedded hardware.
Produces a cloud architecture proposal for a workload with components, trade-offs, cost drivers, security and reliability notes, and a migration path. Use it when designing a new system or reviewing an existing setup.
Designs a reliable connection between two systems: data flow, pattern choice, authentication, retries, duplicate protection, monitoring and a build plan. Use when planning a new integration or fixing a fragile one.
Reviews an AI agent or automation design for human control, handling of unclear instructions, prompt-injection defenses, transparency and data exposure, and names concrete fixes. Use it before giving an agent real tools or data.