Code review, debugging, architecture, testing and docs. 88 reviewed prompts for engineering.
Reviews a schematic and PCB layout for electrical errors, power and signal integrity, thermal and EMC risks, manufacturability and parts sourcing, ending with a fabrication readiness verdict. Use it before sending a board to fab.
Writes a robust script that automates a repetitive file, data or web task, with error handling, a dry-run mode and a plain-language explanation. Use when you want a script you can trust and run yourself.
Ports code from one language to another using the target language's own idioms, and lists behavior differences to test. Use it when migrating or learning a new language.
Turns a list of software dependencies and their licenses into a ranked list of licensing risks and fixes, based on how you ship. Use it before a release, customer questionnaire or due diligence review.
Turns a feature idea into a testable specification: requirements with MUST/SHOULD/MAY, Given/When/Then scenarios, explicit out-of-scope items, small delivery phases and a validation checklist. Use it before handing work to developers.
Defines user-focused reliability indicators, realistic targets, error budgets, burn-rate alerts and dashboards for a service. Use it when setting up on-call or when alerts are too noisy to trust.
Builds a regular expression for a text pattern, explains it piece by piece and proves it with matching and non-matching examples. Use when you need a pattern for a specific tool or language.
Reviews a code change against its requirements and lists concrete defects by severity, each with a trigger scenario, fix and test. Use before merging or releasing.
Designs a practical testing strategy for an application: risk map, test layers with targets, dependency handling, the first ten tests to write, CI gates and a four-week rollout. Use it when a suite is missing, slow or untrusted.
Walks the path a new developer takes from finding your product to a first working result, finds the friction at each step, and prioritizes fixes to the product and the docs. Use before a launch or when developer sign-ups are not turning into usage.
Builds a practical test plan for an AI assistant or automated workflow: realistic test cases, pass/fail rules, metrics and review triggers. Use before rolling a workflow out to a team.
Turns commit messages or change lists into user-facing release notes, a short engineering note, and a rollout and risk summary. Use when preparing a release announcement.
