skills.rest
binary16labs
binary16labsCOMMUNITY
Explore all skills by this author →
GitHub

Backend Reference

Document backend contracts for routing, API families, and auth boundaries.

5|Updated May 6, 2026
Search Tags:#api integration#frontend debugging#file operations#module resolution#backend contracts#auth boundaries
One-click install
npx skills add https://github.com/binary16labs/prime-silo --skill backend-reference-binary16labs
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: Backend Reference
Source: https://github.com/binary16labs/prime-silo/tree/main/app/L0/_all/mod/_core/skillset/ext/skills/development/backend-reference
Command: npx skills add https://github.com/binary16labs/prime-silo --skill backend-reference-binary16labs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It prevents frontend teams from guessing how backend APIs behave, reducing integration bugs and security mistakes when building or troubleshooting the UI.

Core Features & Use Cases

  • Read-only contract guidance: Clarifies request order, endpoint families, auth expectations, and storage conventions without authorizing backend edits.
  • Deterministic request/response flow mapping: Explains the page-shell and routing boundaries, including where authentication applies.
  • Concrete API behavior details: Documents how file operations, module/extension resolution, and user crypto/session endpoints work so frontend calls are structured correctly.

Quick Start

Use the Backend Reference skill to validate how your frontend should call a specific endpoint family (for example, file_list vs file_paths vs file_read) and what constraints and parameters it supports before you implement the UI.

Frequently Asked Questions about Backend Reference

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I understand backend contracts before building UI to prevent integration bugs?▼

Understanding backend contracts before building UI requires read-only documentation of request order, endpoint families, and auth boundaries. This approach clarifies deterministic backend semantics for files and modules, reducing integration bugs and security mistakes.

What is the correct request flow ordering for frontend API integration?▼

The correct request flow ordering for frontend API integration maps page-shell and routing boundaries explicitly. You must follow deterministic request-flow ordering to ensure endpoint calls respect authentication expectations and backend constraints.

How do I validate endpoint capabilities like file_list vs file_paths before implementing UI?▼

Validating endpoint capabilities like file_list vs file_paths before implementing UI requires checking concrete API behavior details. This documents parameters, constraints, and storage conventions so frontend calls are structured correctly without guessing.

When do I need to request backend changes instead of adjusting frontend API calls?▼

You need to request backend changes instead of adjusting frontend API calls when endpoint capabilities or auth boundaries cannot support the required UI behavior. Explicit guardrails define exactly when backend modifications must be requested.

Related Skills

Explore More Software Engineering Skills→
saranskumarsaranskumar

api-contract-designer

Define API contracts specifying endpoints, payloads, error handling, and pagination.

Community
Advanced
Razaib-khanRazaib-khan

frontend-backend-alignment

Align frontend requests with backend API contracts to fix integration failures.

Community
Advanced
wade56754wade56754

ai-ad-code-assembler

Assemble adapted backend and frontend code into multi-file modules with dependency resolution.

Community
Advanced
agent0aiagent0ai
1.4k

Backend Reference

Document backend request flow, API families, and auth semantics for frontend developers.

Official
Intermediate