backend-api-contracts
Skill40 starsChanged 3 days agoApache-2.0View on GitHub
Use when changing backend API contracts, Next.js proxy-to-backend contracts, or route-level request/response boundaries.
In this repository69 other files it gives its agents.
- AGENTS.mdAGENTS.md
- hushh-webapp/AGENTS.mdAGENTS.md
- impeccableSkill
- agent-orchestration-governanceSkill
- analytics-observability-governanceSkill
- animateSkill
- animation-vocabularySkill
- apple-designSkill
- autonomous-rca-governanceSkill
- backend-agents-operonsSkill
- backend-runtime-governanceSkill
- backendSkill
- brandkitSkill
- client-env-paritySkill
- codex-skill-authoringSkill
- comms-communitySkill
- context-refreshSkill
- contributor-onboardingSkill
- docs-governanceSkill
- emil-design-engSkill
- find-animation-opportunitiesSkill
- founder-brief-curationSkill
- frontend-architectureSkill
- frontend-cache-coherenceSkill
- frontend-design-systemSkill
- frontend-native-surface-mapperSkill
- frontendSkill
- frontend-surface-placementSkill
- future-plannerSkill
- github-contribution-governanceSkill
- hushh-consent-mcpSkill
- hushh-icon-themeSkill
- iam-consent-governanceSkill
- imagegen-frontend-mobileSkill
- imagegen-frontend-webSkill
- improve-animationsSkill
- industrial-brutalist-uiSkill
- kai-test-account-resetSkill
- less-text-karma-jiSkill
- mcp-developer-surfaceSkill
- mobile-nativeSkill
- mobile-parity-auditSkill
- mobile-plugin-contractsSkill
- morphy-axSkill
- one-voice-governanceSkill
- oss-license-governanceSkill
- pdf-artifact-generationSkill
- pick-ui-librarySkill
- pkm-upgrade-rehearsalSkill
- planning-boardSkill
- pr-governance-reviewSkill
- profile-uiSkill
- prototypeSkill
- puppy-one-harnessSkill
- quality-contractsSkill
- release-ios-appstoreSkill
- repo-contextSkill
- repo-operationsSkill
- review-animationsSkill
- reviewer-app-testingSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
6 rules. About 0 are common, 1 is distinctive, and 5 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
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
- Very specific: line 12
Avoid overlap with backend-runtime-governance and frontend-architecture.
- Very specific: line 51
Treat the backend route and the Next.js proxy as one contract surface.
- Distinctive: line 52
Keep docs and tests aligned with any wire-shape or endpoint change.
- Very specific: line 57
If the request is still broad or ambiguous, route it back to backend.
- Very specific: line 58
If the task becomes route/service ownership instead of API contract work, use backend-runtime-governance.
- Very specific: line 59
If the task becomes frontend route architecture rather than proxy contract alignment, use frontend.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 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
Hussh Backend API Contracts Skill
Purpose and Trigger
- Primary scope:
backend-api-contracts - Trigger on backend API contract changes, Next.js proxy alignment, and route-level request/response boundary work.
- Avoid overlap with
backend-runtime-governanceandfrontend-architecture.
Coverage and Ownership
- Role:
spoke - Owner family:
backend
Owned repo surfaces:
consent-protocol/api/routeshushh-webapp/app/apidocs/development/contracts/api-contracts.md
Non-owned surfaces:
backendfrontendsecurity-audit
Do Use
- Backend route contract changes.
- Next.js proxy-to-backend request and response alignment.
- API-doc and proxy-contract updates tied to runtime behavior.
Do Not Use
- Broad backend intake where the correct spoke is still unclear.
- Service-layer placement or runtime ownership work without a contract change.
- Native plugin contract work.
Read First
docs/development/contracts/api-contracts.mddocs/development/guides/new-feature.mdconsent-protocol/api/routes
Workflow
- Treat the backend route and the Next.js proxy as one contract surface.
- Keep docs and tests aligned with any wire-shape or endpoint change.
- Route trust/IAM-specific authorization policy questions into
security-audit.
Handoff Rules
- If the request is still broad or ambiguous, route it back to
backend. - If the task becomes route/service ownership instead of API contract work, use
backend-runtime-governance. - If the task becomes frontend route architecture rather than proxy contract alignment, use
frontend.
Required Checks
cd hushh-webapp && npm run typecheck
cd consent-protocol && python3 -m pytest tests/test_developer_api_routes.py -qDoes 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.

