Find why your productivity system keeps failing, then apply the smallest fix — capacity math, bottleneck routing, durable local notes.
Design & media
Backend Requirements Handoff
Try itUse 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
What it does
1. 明确功能上下文 - 说明页面、流程或组件是什么,面向哪类用户,以及用户完成任务的成功状态。 - 如果已有设计稿、路由、用户故事或权限角色,先把它们作为事实来源。
The skill document
前后端需求交接
Purpose
把前端页面和交互所需的数据、动作、状态和疑问整理成后端可讨论的需求说明。
Procedure
-
明确功能上下文
- 说明页面、流程或组件是什么,面向哪类用户,以及用户完成任务的成功状态。
- 如果已有设计稿、路由、用户故事或权限角色,先把它们作为事实来源。
-
描述前端展示需求
- 按屏幕或组件列出需要展示的信息、信息之间的关系、排序/过滤/分页需求和可见性规则。
- 使用业务语言描述“需要展示什么”,不要提前规定 endpoint、字段名、DTO、数据库表或响应嵌套结构。
-
描述用户动作和结果
- 列出用户能执行的动作、期望结果、成功反馈、失败反馈和是否需要乐观更新。
- 标出幂等性、撤销、确认、危险操作、批量操作或长任务进度等对 UI 有影响的行为。
-
补齐状态和业务规则
- 覆盖 loading、empty、error、partial、permission denied、expired、conflict、offline 和 retrying 等状态。
- 记录影响 UI 的权限、生命周期、金额/时区/枚举、校验、可编辑条件和边界规则。
-
输出讨论文档
- 默认写到
docs/backend-requirements/.md;若仓库已有需求文档目录,沿用现有位置。 - 文档包含 Context、Screens/Components、Data Needs、User Actions、UI States、Business Rules、Uncertainties、Questions for Backend 和 Decision Log。
- 若用户只需要聊天回复,可以直接输出同样结构的 Markdown,不创建文件。
- 默认写到
Constraints
- 不替后端规定 URL、HTTP 方法、字段名、数据库 schema、缓存实现或服务拆分。
- 不把前端猜测写成事实;不确定的业务规则必须进入 Uncertainties 或 Questions。
- 不忽略错误、空态、权限和部分数据;这些状态决定接口协作质量。
- 不把内部错误栈、数据库字段或敏感实现细节要求暴露给 UI。
- 不与 API 集成流程重复:本 skill 描述需求,客户端边界、类型来源和错误映射实现应在后续实现阶段处理。
Expected Output
产出一份前端视角的后端需求交接说明,清楚描述 UI 需要什么数据和行为、哪些规则仍需确认,以及后续前后端需要共同决定的问题。
Related skills
Generate and edit Draw.io, Mermaid, and Excalidraw diagrams from natural language using a structured JSON spec.
Write, debug, and tune Playwright specs with locator strategy, trace diagnosis, and CI-aware timeouts.
Fetch raw ad creative, app, ranking, and revenue data from AdMapix as structured JSON.
Stores durable facts in a categorized, plain-markdown vault on disk, alongside your agent's built-in memory.
Join a video meeting as an AI bot with voice, avatar, and screenshare across four operating modes.
More from bovinphang
Browse all skillsGenerate or edit diagrams, visual assets, and image workflows with reviewable PNG self-checks and bounded self-repair.
Use when creating editable technical diagrams with draw.io / diagrams.net sources, including architecture diagrams, ERD, UML, sequence diagrams, flowcharts, ML model diagrams, official shape lookup, brand symbols, Graphviz auto-layout, codebase structure maps, .drawio validation, or draw.io CLI expo
Use when building, reviewing, or improving frontend UI that needs product-specific design direction, design-system generation, Master/Page overrides, distinctive visual identity, anti-generic interface choices, first-screen hierarchy, UI polish, chart UX, interaction states, responsive behavior, or
Use when creating or reviewing Next.js 14+ App Router projects, file routes, layouts, server/client component boundaries, SSR/SSG/ISR, streaming, metadata, middleware, server actions, or Next-specific data fetching. For generic client React component architecture, apply the project's React conventio
Use when creating, reviewing, or restructuring frontend monorepos with pnpm workspace, Turborepo, Nx, multi-package dependency boundaries, task orchestration, package naming, or package publishing; Chinese triggers include monorepo, workspace, multi-package.
Use when creating or reviewing Nuxt 3 projects, file routes, pages, layouts, SSR/SSG/SPA behavior, Nuxt data fetching, route middleware, plugins, modules, server routes, or Nuxt-specific Vue 3 conventions. For generic Vue component architecture, apply the project's Vue conventions separately; Chines