Code review, debugging, architecture, testing and docs. 88 reviewed prompts for engineering.
Engineering prompts and skills help with the written side of building software: reviewing a change, narrowing down a bug, weighing an architecture choice, planning tests and documenting what you built. Paste in the actual code, error or constraints, and ask for reasoning you can verify. Run and test anything it suggests before it goes near production, and leave secrets and customer data out of what you share.
Works through a software bug methodically: restates expected vs. actual behavior, ranks testable hypotheses, names the cheapest check for each, and proposes a root-cause fix with a regression test. Use when something is broken and the cause is unclear.
Turns incident notes, chat logs and timestamps into a blameless postmortem with timeline, impact, contributing factors and owned follow-up actions. Use within a few days of any production incident.
Compares an old and new API specification and writes a front-end focused change summary with breaking changes, new fields and migration steps. Use when a backend team ships a new spec version.
Turns rough testing notes into clear, reproducible bug reports with steps, expected and actual results, severity and suggested checks. Use it after a test session so developers can act without follow-up.
Plans the smallest throwaway prototype, logic or visual, that settles one open design question, with cases to try and how to judge the result. Use before committing to a design.
Reviews a schema migration for production risks such as long locks, data loss and breaking running code, and proposes a safer rollout. Use before shipping any change to a live database.
Reviews code or a system design you own for security weaknesses, including web, API and AI-feature risks, with severity, impact, fixes and how to verify each fix. Use it before a release or a design sign-off.
Translates the values in a key-value localization file while leaving keys, placeholders and formatting intact, and flags strings needing context. Use when localizing an app's strings file.
Compares an existing project document with the current state of the code or a change summary and returns a precise list of edits plus an updated version. Use it when docs have drifted from reality.
Reviews an algorithm you describe or paste, finds weak points and bottlenecks, and proposes ranked improvements with trade-offs. Use it when something works but is slow, inaccurate or will not scale.
Reviews the structure of a web API project and lists strengths, weaknesses and ranked improvements for a large user base. Use before scaling a service or planning a refactor.
Rewrites a vague coding request into a complete brief with a clear goal, relevant context, constraints and a verifiable done condition, ready to hand to any AI coding assistant or developer. Use before delegating a coding task.
