Code review, debugging, architecture, testing and docs. 100 reviewed prompts for engineering.
Groups security scanner alerts and dependency warnings, finds shared root causes, and ranks fixes by severity and exposure. Use it when a long alert list needs a clear remediation order.
Compares virtualization platform options against your workloads, team skills and budget, and ends with a recommendation and a pilot plan. Use it before renewing or replacing a virtualization stack.
A checklist-driven way to review code changes for security flaws and report them with severity and concrete fixes. Use when reviewing a pull request, a code snippet, or new code that handles input, data or access.
Turns a piece of code into a list of test cases plus runnable test code, with explanations a junior developer can learn from. Use it when you add or change a function and want solid coverage.
Designs a system from requirements to failure modes: clarifying questions, capacity estimates, components, data model and explicit trade-offs. Use it for real architecture decisions or to practise design interviews.
Checks a release against a readiness list, names the biggest risks, and plans staged rollout with stop thresholds and ordered rollback steps. Use before a production launch.
Turns a research paper's core method into a minimal, commented implementation, with every detail traced to the paper and every gap flagged as an assumption. Use it when reproducing or prototyping a published technique.
Compares an API before and after, classifies each change as breaking, safe or unclear, and drafts a consumer migration checklist and changelog note. Use it before releasing an API update.
Steers coding work toward the smallest correct change: reuse what exists, avoid new dependencies and speculative abstractions, never cut safety. Use when writing, reviewing or refactoring code where over-building is a risk.
Designs a clear, validated tool (function) definition that AI assistants can call reliably: naming, parameters, field order, output and error shapes, safety rules and example calls. Use it when connecting an assistant to your own APIs.
A way of working for any change that touches user-facing text. Use when adding or editing strings, translations, dates, numbers or plurals in a product.
Rewrites a rough coding request into a structured brief with goal, context, constraints, out-of-scope items and a testable done condition, ready to hand to an AI coding assistant or a developer.
