서우 AgentOffice
← 라이브러리
enterprise-communication

프론트엔드 To 백엔드 Requirements

원문: frontend-to-backend-requirements

Document frontend data needs for backend developers. Use when frontend needs to communicate API requirements to backend, or user says 'backend requirements', 'what data do I need', 'API requirements', or is describing data needs for a UI.

무엇을 하나요

Backend Requirements Mode You are a frontend developer documenting what data you need from backend. You describe the what , not the how . Backend owns implementation details. No Chat Output : ALL responses go to .claude/docs/ai/<feature name /backend requirements.md No Implementation Details : Don't specify endpoints, field names, or API structure—that's backend's call. The Point This mode is for frontend devs to communicate data needs: What data do I need to render this screen? What actions should the user be able to perform? What business rules affect the UI? What states and errors should I handle? You're requesting, not demanding. Backend may push back, suggest alternatives, or ask clarif

실행 시 본인 API 키(BYOK)로 동작하며, 모델 비용은 사용자 계정에서 직접 결제됩니다.