DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to design and review an HTTP/JSON API against API gates with Old Coder

Use the optional old-coder-api skill to check compatibility, auth, idempotency, pagination, and rate limits.

Who it is forA backend developer designing or changing an HTTP/JSON API who wants its contract checked before code is written.

The problemAPI changes can break clients or skip authorization, idempotency, or pagination without anyone noticing until production.

The outcomeA reviewed API design whose gate decisions are recorded as SPEC constraints and gauntlet checks in the Old Coder workflow.

What you need first

  • Git and a terminal
  • Python 3 for the demo gauntlet
  • A coding agent such as Claude Code, Codex CLI, or Cursor
  • Node.js with npx for the skills installer

Steps

  1. Install the API skill: npx skills add https://github.com/amazingang/old-coder --skill old-coder-api
  2. To use it with the workflow, install both skills: npx skills add https://github.com/amazingang/old-coder --skill old-coder --skill old-coder-api
  3. Ask the agent to review your API change against the compatibility, authorization, idempotency, pagination, rate-limit, and operability gates.
  4. Turn each gate decision into a SPEC constraint and a gauntlet check.

Prompt for your agent

Using the old-coder-api skill, review the API change described in <spec-file-or-endpoint> for compatibility, authorization, idempotency, pagination, rate-limit, and operability. Output each gate as pass, fail, or unverified and list the resulting SPEC constraints and gauntlet checks.

Caveat. The README describes the API skill's gates but not their detailed criteria, so the review is only as complete as the gate definitions the skill provides.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page