fec-backend-requirements-handoffUse when frontend work needs to communicate data, action, state, permission, validation, or business-rule needs to backend teams without dictating endpoint design, field names, database shape, or implementation details; Chinese triggers include front-end and back-end requirements handover, back-end
Install via ClawdBot CLI:
clawdbot install bovinphang/fec-backend-requirements-handoffGrade Fair — based on market validation, documentation quality, package completeness, maintenance status, and authenticity signals.
Calls external URL not in known-safe list
https://github.com/bovinphang/frontend-craftAudited Nov 17, 2026 · audit v1.0
Generated Nov 17, 2026
A frontend team needs to align with backend engineers on data, filters, and permission states for a new analytics dashboard. The skill produces a structured requirements document covering display needs, UI states, and open questions without prescribing endpoints or schemas.
Frontend developers must communicate validation rules, order states, and failure feedback for a redesigned checkout to the backend team. The handoff clarifies business rules like timezones, refunds, and retry behavior while leaving API design to backend.
A frontend team working on KYC and account onboarding needs to describe role-based visibility and lifecycle states to backend. The skill captures permission denied, expired, and conflict states plus unresolved compliance questions for joint review.
Frontend engineers specify what patient records, appointments, and status indicators must be shown, including sorting and partial data states. The requirements doc surfaces uncertainties around consent and data freshness for backend discussion.
A team migrating a legacy admin panel needs to communicate batch actions, dangerous-operation confirmations, and long task progress to backend engineers. The handoff documents actions, feedback, and idempotence needs without dictating implementation.
Teams pay subscription fees for a development collaboration platform where this skill standardizes frontend-backend requirement handoffs. Faster alignment reduces rework and shortens delivery cycles.
The skill is distributed as a licensed capability within an AI agent platform, with organizations paying for skill packages that improve engineering workflows.
Agencies offer workshops and templates around requirements handoff best practices, bundling this skill into process consulting for product teams.
💬 Integration Tip
Feed the skill real design docs, user stories, and permission roles as context so the generated handoff stays grounded in facts rather than guesses. Route uncertain business rules into the Questions for Backend section rather than letting the model invent them.
Scored Nov 17, 2026
Use when building UI with shadcn/ui components, Tailwind CSS layouts, form patterns with react-hook-form and zod, theming, dark mode, sidebar layouts, mobile navigation, or any shadcn component question.
Tailwind reference tool. Use when working with tailwind in frontend contexts.
A product creation skill based on the "Bee Website Builder" Open API. It is used to create a new product under a specified site language and product group, w...
A product update skill based on the "Bee Website Builder" Open API. It is used to update an existing product under a specified site language and supports upd...
Build WCAG 2.1 AA compliant websites with semantic HTML, proper ARIA, focus management, and screen reader support. Includes color contrast (4.5:1 text), keyboard navigation, form labels, and live regions. Use when implementing accessible interfaces, fixing screen reader issues, keyboard navigation, or troubleshooting "focus outline missing", "aria-label required", "insufficient contrast".
Use when building Vue 3 applications with Composition API, Nuxt 3, or Quasar. Invoke for Pinia, TypeScript, PWA, Capacitor mobile apps, Vite configuration.