agentleFS
hushh-labshushh-labs/hushh-research/.agents/skills/backend-api-contracts/SKILL.md

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.

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
  1. Very specific:

    Avoid overlap with backend-runtime-governance and frontend-architecture.

    line 12
  2. Very specific:

    Treat the backend route and the Next.js proxy as one contract surface.

    line 51
  3. Distinctive:

    Keep docs and tests aligned with any wire-shape or endpoint change.

    line 52
  4. Very specific:

    If the request is still broad or ambiguous, route it back to backend.

    line 57
  5. Very specific:

    If the task becomes route/service ownership instead of API contract work, use backend-runtime-governance.

    line 58
  6. Very specific:

    If the task becomes frontend route architecture rather than proxy contract alignment, use frontend.

    line 59

≈ “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.

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

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-governance and frontend-architecture.

Coverage and Ownership

  • Role: spoke
  • Owner family: backend

Owned repo surfaces:

  1. consent-protocol/api/routes
  2. hushh-webapp/app/api
  3. docs/development/contracts/api-contracts.md

Non-owned surfaces:

  1. backend
  2. frontend
  3. security-audit

Do Use

  1. Backend route contract changes.
  2. Next.js proxy-to-backend request and response alignment.
  3. API-doc and proxy-contract updates tied to runtime behavior.

Do Not Use

  1. Broad backend intake where the correct spoke is still unclear.
  2. Service-layer placement or runtime ownership work without a contract change.
  3. Native plugin contract work.

Read First

  1. docs/development/contracts/api-contracts.md
  2. docs/development/guides/new-feature.md
  3. consent-protocol/api/routes

Workflow

  1. Treat the backend route and the Next.js proxy as one contract surface.
  2. Keep docs and tests aligned with any wire-shape or endpoint change.
  3. Route trust/IAM-specific authorization policy questions into security-audit.

Handoff Rules

  1. If the request is still broad or ambiguous, route it back to backend.
  2. If the task becomes route/service ownership instead of API contract work, use backend-runtime-governance.
  3. 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 -q

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.