Where are the requirements documents saved?

All documentation is automatically saved to .claude/docs/ai/ /backend-requirements.md within your repository for easy version control.

Does this skill generate API code?

No, it focuses on documenting the data requirements and UI states to help backend developers design the correct implementation without prescribing the structure.

Why should I use this instead of a standard task ticket?

This skill provides a specific, structured framework for technical data needs that often get lost in high-level task descriptions, ensuring no edge cases are missed.

Can it handle complex business logic?

Yes, it includes dedicated sections for describing business rules that affect the UI, ensuring the backend supports all necessary visibility and permission logic.

Frontend-to-Backend Requirements Bridge

Name: Frontend-to-Backend Requirements Bridge
Author: alchimie-di-circe

byalchimie-di-circe

•

API 개발

Standardizes how frontend developers communicate data needs and UI requirements to backend engineers without overstepping into implementation details.

This skill facilitates seamless collaboration between frontend and backend developers by providing a structured framework for documenting data needs. Instead of dictating API endpoints or data structures, it empowers frontend developers to describe the 'what'—including UI states, business logic, and required data points—while leaving the 'how' to the backend experts. By generating standardized Markdown documentation in a dedicated directory, it ensures that requirements are clear, uncertainties are highlighted, and a discussion log is maintained to track architectural decisions and technical alignment.

주요 기능

01Automated generation of standardized backend requirements documentation

02Structured templates for UI states including loading, empty, and error scenarios

03Clear separation of concerns between UI data needs and backend implementation

041 GitHub stars

05Persistent discussion logs to record backend feedback and architectural decisions

06Uncertainty tracking to proactively invite technical pushback and clarification

사용 사례

01Drafting API requirements for a new feature before backend development begins

02Communicating complex UI state dependencies and business rules to backend engineers

03Standardizing technical handoffs within cross-functional agile teams

What are Skills?·How to Install

Install with 🐟 Skill.Fish

npx skillfish add alchimie-di-circe/extractor-desktop-app frontend-to-backend-requirements

For use in Claude.ai and ChatGPT

Download Skill

주요 기능

01Automated generation of standardized backend requirements documentation

02Structured templates for UI states including loading, empty, and error scenarios

03Clear separation of concerns between UI data needs and backend implementation

041 GitHub stars

05Persistent discussion logs to record backend feedback and architectural decisions

06Uncertainty tracking to proactively invite technical pushback and clarification

사용 사례

01Drafting API requirements for a new feature before backend development begins

02Communicating complex UI state dependencies and business rules to backend engineers

03Standardizing technical handoffs within cross-functional agile teams

What are Skills?·How to Install

Install with 🐟 Skill.Fish

npx skillfish add alchimie-di-circe/extractor-desktop-app frontend-to-backend-requirements

For use in Claude.ai and ChatGPT

Download Skill