Backend Reference

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

1.4k|316|Updated Mar 27, 2026
One-click install
npx skills add https://github.com/agent0ai/space-agent --skill backend-reference-agent0ai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Backend Reference
Source: https://github.com/agent0ai/space-agent/tree/main/app/L0/_all/mod/_core/skillset/ext/skills/development/backend-reference
Command: npx skills add https://github.com/agent0ai/space-agent --skill backend-reference-agent0ai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It reduces frontend guesswork by documenting the backend request flow, API families, auth model, and module/extension resolution behavior that the UI relies on, so you can implement frontend changes without breaking runtime assumptions.

Core Features & Use Cases

  • Request and endpoint flow clarity: Explains how requests are ordered and routed through proxy, API endpoints, layered module resolution, and page shells.
  • API contract guidance for key frontend endpoints: Summarizes important endpoint families (file operations, module operations, runtime/identity, local history, and session-related calls) including parameter behavior and security boundaries.
  • Module/extension resolution model: Covers layer constraints (e.g., maxLayer), admin clamping behavior, and how HTML/JS extensions resolve across layers and patterns.
  • Auth and user storage model: Provides a readable map of cookies, user.yaml locations, password verifier handling, and the session-derived wrapping key approach for userCrypto.

Quick Start

Ask the assistant for the exact frontend endpoint contract and expected parameters for the task you are implementing, including any relevant layer or authentication constraints.

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 API contracts for frontend integration without modifying server code?

Backend API contracts provide read-only guidance for frontend integration, documenting request flow ordering, endpoint families, and parameter semantics so you can implement UI changes safely without modifying backend code.

Why does my frontend file operation request fail during API routing?

Frontend file operation requests fail during API routing when parameter semantics violate security boundaries or request flow ordering rules defined by backend contracts for proxy, endpoint, and layered module resolution.

How does module resolution work across layers with admin clamping and maxLayer constraints?

Module resolution across layers enforces maxLayer constraints and admin clamping behavior, controlling how HTML and JS extensions resolve through layered patterns while maintaining strict layer-based permission boundaries.

What is the session-derived wrapping key approach for userCrypto authentication?

The session-derived wrapping key approach for userCrypto authentication uses password verifier handling and user.yaml locations alongside cookies to establish secure session-based identity and runtime authorization.

Can I use backend contract guidance to diagnose request failures in frontend implementations?

Yes, backend contract guidance diagnoses request failures by mapping expected endpoint parameters, auth model boundaries, and module resolution semantics, enabling frontend developers to identify mismatches without backend code access.

What are the limitations of read-only backend contract documentation for frontend development?

Read-only backend contract documentation limits frontend developers to diagnosing and understanding API behavior, explicitly preventing any assumption of permission to modify backend code, routing logic, or server-side authentication mechanisms.