frontend-to-backend-requirements

The frontend-to-backend-requirements skill acts as a structured bridge between frontend implementation and backend API design. It is designed for frontend developers who need to communicate data needs, UI states, and business logic without overstepping into backend architectural decisions or implementation specifics. By following a guided workflow, users can articulate what data is necessary for specific screens, what user actions are enabled, and what edge cases must be handled, allowing backend developers to own the 'how' while frontend owns the 'what'. This skill helps prevent ambiguity, reduces back-and-forth friction, and creates a living document of requirements that backend teams can use to propose robust, efficient solutions.

• Automatically generates a standardized markdown document located at .claude/docs/ai/<feature-name>/backend-requirements.md.

• Encourages the separation of concerns by separating UI state, user actions, and data needs from API endpoint design or field-level structures.

• Includes a dedicated Discussion Log section to track backend feedback, negotiations, and subsequent decisions.

• Forces context-first documentation by requiring descriptions of screen goals, user types, and intended workflows before requesting data pieces.

• Provides a template for surfacing uncertainties and edge cases to invite backend pushback and collaborative problem-solving.

• Use this skill whenever you need to clarify API requirements, request new data for a UI component, or describe business rules that affect data fetching.

• Always remain in 'requesting' mode rather than 'demanding' mode; be open to backend suggestions regarding data structure, performance, or caching strategies.

• The output is strictly formatted for documentation purposes—no conversational output is provided, ensuring a clean, technical artifact for the project repository.

• Ideal for agile teams needing to reduce overhead in technical design discussions while maintaining a clear source of truth for frontend-backend integration needs.

• Works seamlessly by analyzing the current feature context to ensure requirements are specific, actionable, and free from premature implementation assumptions.