fec-backend-requirements-handoff SKILL.md skillA
fec-backend-requirements-handoff from bovinphang/frontend-craft is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add bovinphang/frontend-craft/fec-backend-requirements-handoff@git:20260611.9d7f5e4Pins git:20260611.9d7f5e4 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- bovinphang/frontend-craft
- Path
skills/fec-backend-requirements-handoff/SKILL.md- Versions recorded
- 2
- Latest version
- git:20260611.9d7f5e4, committed Jun 11, 2026
- First version recorded
- Jun 9, 2026
- Size
- 3,450 bytes
- Repository stars
- 22
- License
- MIT
Use 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 requirements, API requirements clarification, data requirements description.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# Handover of front-end and back-end requirements ## Purpose Organize the data, actions, status, and questions required for front-end pages and interactions into discussion-ready requirements for the back-end. ## Procedure 1. Clarify the functional context - Describe what the page, process, or component is, what type of user it is intended for, and the success status of the user completing the task. - If there are existing designs, routes, user stories, or permission roles, use them as sources of truth first. 2. Describe front-end display requirements - List information to be displayed by screen or component, relationships between information, sorting/filtering/pagination requirements and visibility rules. - Use business language to describe "what needs to be displayed" and do not specify endpoints, field names, DTOs, database tables or response nested structures in advance. 3. Describe user actions and results - List the actions the user can perform, expected results, success feedback, failure feedback and whether optimistic updates are needed. …
Read the whole file at its exact version.
How to install
mdr add bovinphang/frontend-craft/fec-backend-requirements-handoff@sha256:07499feec9f0f5ebThe line at the top of this page pins the label git:20260611.9d7f5e4, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_pe7lcnpeytysddi7)
2 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 2 versions of this file, between Jun 9, 2026 and Jun 11, 2026, about one every 2 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260611.9d7f5e4 latest | 2026-06-11 | 9d7f5e4 | 3,450 B | A | view · diff |
| git:20260609.e2e224a | 2026-06-09 | e2e224a | 2,762 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (3450 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
bovinphang/frontend-craft · 22 stars · license MIT · pushed 2026-09-26 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_pe7lcnpeytysddi7 GET https://markdownregistry.com/api/v1/resolve?ref=bovinphang/frontend-craft/fec-backend-requirements-handoff GET https://markdownregistry.com/api/v1/blob/07499feec9f0f5eb38126a9cff83d041d5d52f77c967d68f316e2cf5091f59c9
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.
More from bovinphang/frontend-craft
Every file in bovinphang/frontend-craft