Code review, debugging, architecture, testing and docs. 100 reviewed prompts for engineering.
Assesses reported vulnerabilities in your software dependencies, explains the real risk and gives an ordered upgrade plan with checks. Use when a scan lists CVEs and you need to decide what to fix first.
Converts a snippet from another language into clear, idiomatic Python with comments and a list of behavior differences. Use it when porting a small script or learning Python from code you already know.
Drafts a data platform architecture for batch and real-time analytics, machine learning, and governance, with options, trade-offs, cost drivers, and a phased plan. Use when designing or modernising a company's data stack.
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.
A way of working for any code change: plan first, read before editing, change only what is needed, test, check security basics and summarise. Use when writing, fixing or refactoring code.
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.
