From frontend-craft
Structures frontend data, action, state, permission, and validation needs into backend-ready requirements without dictating endpoints or implementation. Useful for API requirement handoffs.
How this skill is triggered — by the user, by Claude, or both
Slash command
/frontend-craft:fec-backend-requirements-handoffThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Organize the data, actions, status, and questions required for front-end pages and interactions into discussion-ready requirements for the back-end.
Organize the data, actions, status, and questions required for front-end pages and interactions into discussion-ready requirements for the back-end.
Describe front-end display requirements
Describe user actions and results
Complete status and business rules
Output discussion document
docs/backend-requirements/<feature-name>.md; if the warehouse already has a requirements document directory, the existing location will be used.Produce a back-end requirements handover description from a front-end perspective, clearly describing what data and behaviors the UI requires, which rules still need to be confirmed, and subsequent issues that need to be decided jointly by the front-end and back-end.
npx claudepluginhub bovinphang/frontend-craftImplements UI components and frontend architecture. Breaks down designs into component trees, manages state, integrates with backend APIs, ensures accessibility and responsive behavior.
Generates production-ready frontend task breakdowns from UX design handoffs, Figma links, screenshots, or PRDs. Includes component inventory and state matrices for planning frontend work.
Builds React/Next.js web frontends: components, pages, design systems, state management, typed API clients. Uses structured phases and engagement modes.