SnipTray logo
Coding

Review this API surface

How it reads at the call site, and what it lets you do wrong.

  • api design
  • review
  • ergonomics

The prompt

Review the interface below. Callers: {{callers}}

Judge it by the call site, not the implementation: write out what using it looks
like for the two most common cases. Then name every way a caller could hold it
wrong — a bad order of operations, a state that compiles but makes no sense, an
optional that is never actually optional.

Suggest the smallest change that removes the worst of those. Say if it is already
fine.

{{api}}

What to fill in

{{api}}
The interface — e.g. Paste the signatures or protocol
{{callers}}
Who calls it — e.g. two app targets, plus tests

117 prompts, in the app you already paste from

The whole library, searchable, with your own prompts alongside it. Free to browse here; Pro to keep them a keystroke away on every device.