agentleFS
Sign inStart free
faiz-gearfaiz-gear/superpowers-contract-patch/skills/backend-contract-exit-gate/SKILL.md

backend-contract-exit-gate

Skill0 starsChanged 8 months agoMITView on GitHub

Use when backend API work appears complete and the agent must verify the published contract before claiming success

The file

We split this skill into the rules it gives an agent

7 rules. About 0 are common, 2 are distinctive, and 5 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 5

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use this skill when:

    line 14
  2. Very specific:

    every public endpoint has an operationId

    line 23
  3. Very specific:

    every 2xx response resolves to a concrete business DTO

    line 24
  4. Very specific:

    every response follows the standard envelope

    line 25
  5. Very specific:

    Read gates/backend-exit-gate.md and gates/contract-invariants.md.

    line 30
  6. Very specific:

    Write a gate report with pass or fail per invariant using templates/gate-report.md.

    line 32
  7. Distinctive:

    Stop the task if any blocker fails.

    line 33

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Backend Contract Exit Gate

Overview

Code is not complete until the contract is publishable. This gate blocks completion unless the backend output is recognizable, typed, and aligned with OpenAPI.

Trigger

Use this skill when:

  • an endpoint was added or changed
  • DTOs changed
  • OpenAPI output changed
  • the agent is about to claim backend API work is complete

Blocking Checks

  • every public endpoint has an operationId
  • every 2xx response resolves to a concrete business DTO
  • every response follows the standard envelope
  • generated or exported OpenAPI matches the implementation

Process

  1. Read gates/backend-exit-gate.md and gates/contract-invariants.md.
  2. Compare the implementation against the authoritative OpenAPI contract.
  3. Write a gate report with pass or fail per invariant using templates/gate-report.md.
  4. Stop the task if any blocker fails.

Output

Produce one explicit outcome:

  • PASS: backend contract is publishable
  • FAIL: do not claim completion; list the blocking invariant failures

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free