frontend-contract-entry-gate
Skill0 starsChanged 8 months agoMITView on GitHub
Use when frontend work will consume an API and the agent must confirm the latest OpenAPI contract before implementation starts
In this repository19 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- backend-contract-exit-gateSkill
- brainstormingSkill
- compound-knowledge-summarySkill
- dispatching-parallel-agentsSkill
- executing-plansSkill
- finishing-a-development-branchSkill
- recall-contract-contextSkill
- receiving-code-reviewSkill
- requesting-code-reviewSkill
- subagent-driven-developmentSkill
- systematic-debuggingSkill
- test-driven-developmentSkill
- using-git-worktreesSkill
- using-superpowersSkill
- verification-before-completionSkill
- writing-plansSkill
- writing-skillsSkill
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 2 are distinctive, and 1 is 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.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 14
Use this skill when:
- Distinctive: line 25
stop if generation fails or the contract is stale
- Very specific: line 29
Read gates/frontend-entry-gate.md and contracts/source-of-truth.md.
≈ “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.
Files
Frontend Contract Entry Gate
Overview
Frontend API work starts from the latest contract, not from stale memory. This gate makes OpenAPI freshness and client generation mandatory before consumption work begins.
Trigger
Use this skill when:
- a frontend task depends on API changes
- TanStack Query or other client methods need regeneration
- a team is preparing for frontend and backend integration
Blocking Checks
- compare the current local contract with the latest authoritative
OpenAPI - confirm the frontend is using the fresh contract revision
- generate or refresh client methods from that contract
- stop if generation fails or the contract is stale
Process
- Read
gates/frontend-entry-gate.mdandcontracts/source-of-truth.md. - Verify contract freshness.
- Regenerate client artifacts.
- Record the outcome in a gate report.
Output
Produce one explicit outcome:
READY: the frontend may consume the APIBLOCKED: fix freshness or generation issues first
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
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.