Code review, debugging, architecture, testing and docs. 7 reviewed prompts for engineering.
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.
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.
Reviews smart contract code for security flaws, risky admin powers and wasteful gas use, with exploit scenarios, fixes and tests to add. Use it before an external audit or any deployment that holds funds.
Critiques a product requirements draft or one-pager, ranking its weakest points, listing missing evidence and suggesting the questions to answer before building. Use before committing engineering time.
Use when you are about to commit a non-trivial technical or business decision, claim something is safe or correct, or change something hard to undo. Runs a short, bounded adversarial review of the decision before it stands.
Maps how a feature or system you own could be attacked or misused and lists prioritized defenses, detection and tests. Use during design or before a security review of your own product.
Reviews an infrastructure-as-code change and its plan output for destroyed or replaced resources, leaked secrets, blast radius and version drift, then gives a validation and rollback plan. Use it before applying changes to shared environments.
