Where does the skill save the requirements documentation?

All documentation is automatically saved to the .claude/docs/ai/ /backend-requirements.md directory within your project.

How does this improve team collaboration?

By surfacing uncertainties and explicitly inviting pushback, it turns requirement gathering into a dialogue rather than a one-way demand, leading to better architectural decisions.

Can I use this for refactoring existing features?

Absolutely. It is an excellent tool for documenting what data is missing from current APIs or how requirements have changed for an existing component.

Why does the skill discourage specifying endpoint names?

To maintain a healthy separation of concerns. The backend team owns the implementation (endpoints, field names, types), while the frontend team owns the data requirements.

Does this skill generate backend API code?

No, this skill is designed for documentation and communication. It helps frontend developers articulate 'what' data they need so backend developers can decide 'how' to best implement it.

Frontend-to-Backend Requirements Bridge

Name: Frontend-to-Backend Requirements Bridge
Author: Microck

byMicrock

•

API開発

Documents frontend data requirements for backend developers without prescribing technical implementation details.

This skill facilitates seamless collaboration between frontend and backend teams by providing a structured framework for communicating data needs. It empowers frontend developers to describe required UI states, user actions, and data relationships while leaving technical implementation details—such as endpoint design and field naming—to the backend experts. By generating standardized documentation in a dedicated project folder, it minimizes friction and fosters a 'request, don't demand' culture in full-stack development workflows.

主な機能

01Automated generation of structured requirement markdown files

02Integrated Discussion Log for documenting backend feedback and decisions

032 GitHub stars

04Comprehensive templates for UI states (loading, empty, error)

05Built-in uncertainty tracking for unresolved business rules

06Separation of concerns between UI needs and API implementation

ユースケース

01Defining the data needs for a new UI feature before API development begins

02Clarifying complex business logic that affects data visibility and user permissions

03Facilitating handoff meetings between frontend and backend engineering teams

What are Skills?·How to Install

Install with 🐟 Skill.Fish

npx skillfish add microck/opendots-microck frontend-to-backend-requirements

For use in Claude.ai and ChatGPT

Download Skill