Code review, debugging, architecture, testing and docs. 6 reviewed prompts for engineering.
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.
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.
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.
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.
Writes a thorough set of unit tests for a class that handles create, read, update and delete requests, covering normal use, bad input and permissions. Use when you need reliable tests before changing existing code.
Designs a reliable connection between two systems: data flow, pattern choice, authentication, retries, duplicate protection, monitoring and a build plan. Use when planning a new integration or fixing a fragile one.
