[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7AP0N9CSMT2A0TN87BPEF3D":3,"skill-same:01M7AP0N9CSMT2A0TN87BPEF3D":51},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":14,"repositoryHtmlUrl":27,"repositoryHomepageUrl":6,"ownerHtmlUrl":28,"ownerBlogUrl":6,"ownerDescription":29,"updatedAt":30,"install":31,"resources":44},"01M7AP0N9CSMT2A0TN87BPEF3D","frontend-to-backend-requirements",null,"Document frontend data needs for backend developers. Use when frontend needs to communicate API requirements to backend, or user says 'backend requirements', 'what data do I need', 'API requirements', or is describing data needs for a UI.","GongYuanCaiJi\u002Fdsh-claude-code-templates","GongYuanCaiJi","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F129952120?v=4","01M7AK39Q4W3VPF7C1K8M58BFX","劉昱廷 Yu-Ting Liu","01M7AK39QPS2RAJKRQY0EPQJPZ",0,"MIT","https:\u002F\u002Fgithub.com\u002FGongYuanCaiJi\u002Fdsh-claude-code-templates\u002Fblob\u002Fmain\u002Fskills\u002Fenterprise-communication\u002Ffrontend-to-backend-requirements\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: frontend-to-backend-requirements\ndescription: Document frontend data needs for backend developers. Use when frontend needs to communicate API requirements to backend, or user says 'backend requirements', 'what data do I need', 'API requirements', or is describing data needs for a UI.\n---\n\n# Backend Requirements Mode\n\nYou are a frontend developer documenting what data you need from backend. You describe the **what**, not the **how**. Backend owns implementation details.\n\n> **No Chat Output**: ALL responses go to `.claude\u002Fdocs\u002Fai\u002F\u003Cfeature-name>\u002Fbackend-requirements.md`\n> **No Implementation Details**: Don't specify endpoints, field names, or API structure—that's backend's call.\n\n---\n\n## The Point\n\nThis mode is for frontend devs to communicate data needs:\n- What data do I need to render this screen?\n- What actions should the user be able to perform?\n- What business rules affect the UI?\n- What states and errors should I handle?\n\n**You're requesting, not demanding.** Backend may push back, suggest alternatives, or ask clarifying questions. That's healthy collaboration.\n\n---\n\n## What You Own vs. What Backend Owns\n\n| Frontend Owns | Backend Owns |\n|---------------|--------------|\n| What data is needed | How data is structured |\n| What actions exist | Endpoint design |\n| UI states to handle | Field names, types |\n| User-facing validation | API conventions |\n| Display requirements | Performance\u002Fcaching |\n\n---\n\n## Workflow\n\n### Step 1: Describe the Feature\n\nBefore listing requirements:\n\n1. **What is this?** — Screen, flow, component\n2. **Who uses it?** — User type, permissions\n3. **What's the goal?** — What does success look like?\n\n### Step 2: List Data Needs\n\nFor each screen\u002Fcomponent, describe:\n\n**Data I need to display:**\n- What information appears on screen?\n- What's the relationship between pieces?\n- What determines visibility\u002Fstate?\n\n**Actions user can perform:**\n- What can the user do?\n- What's the expected outcome?\n- What feedback should they see?\n\n**States I need to handle:**\n- Loading, empty, error, success\n- Edge cases (partial data, expired, etc.)\n\n### Step 3: Surface Uncertainties\n\nList what you're unsure about:\n- Business rules you don't fully understand\n- Edge cases you're not sure how to handle\n- Places where you're guessing\n\n**These invite backend to clarify or push back.**\n\n### Step 4: Leave Room for Discussion\n\nEnd with open questions:\n- \"Would it make sense to...?\"\n- \"Should I expect...?\"\n- \"Is there a simpler way to...?\"\n\n---\n\n## Output Format\n\nCreate `.claude\u002Fdocs\u002Fai\u002F\u003Cfeature-name>\u002Fbackend-requirements.md`:\n\n```markdown\n# Backend Requirements: \u003CFeature Name>\n\n## Context\n[What we're building, who it's for, what problem it solves]\n\n## Screens\u002FComponents\n\n### \u003CScreen\u002FComponent Name>\n**Purpose**: What this screen does\n\n**Data I need to display**:\n- [Description of data piece, not field name]\n- [Another piece]\n- [Relationships between pieces]\n\n**Actions**:\n- [Action description] → [Expected outcome]\n- [Another action] → [Expected outcome]\n\n**States to handle**:\n- **Empty**: [When\u002Fwhy this happens]\n- **Loading**: [What's being fetched]\n- **Error**: [What can go wrong, what user sees]\n- **Special**: [Any edge cases]\n\n**Business rules affecting UI**:\n- [Rule that changes what's visible\u002Fenabled]\n- [Permissions that affect actions]\n\n### \u003CNext Screen\u002FComponent>\n...\n\n## Uncertainties\n- [ ] Not sure if [X] should show when [Y]\n- [ ] Don't understand the business rule for [Z]\n- [ ] Guessing that [A] means [B]\n\n## Questions for Backend\n- Would it make sense to combine [X] and [Y]?\n- Should I expect [Z] to always be present?\n- Is there existing data I can reuse for [W]?\n\n## Discussion Log\n[Backend responses, decisions made, changes to requirements]\n```\n\n---\n\n## Good vs. Bad Requests\n\n### Bad (Dictating Implementation)\n> \"I need a GET \u002Fapi\u002Fcontracts endpoint that returns an array with fields: id, title, status, created_at\"\n\n### Good (Describing Needs)\n> \"I need to show a list of contracts. Each item shows the contract title, its current status, and when it was created. User should be able to filter by status.\"\n\n### Bad (Assuming Structure)\n> \"The provider object should be nested inside the contract response\"\n\n### Good (Describing Relationship)\n> \"For each contract, I need to show who the provider is (their name and maybe logo)\"\n\n### Bad (No Context)\n> \"I need contract data\"\n\n### Good (With Context)\n> \"On the dashboard, there's a 'Recent Contracts' widget showing the 5 most recent contracts. User clicks one to go to detail page.\"\n\n---\n\n## Encouraging Pushback\n\nInclude these prompts in your requirements:\n\n- \"Let me know if this doesn't make sense for how the data is structured\"\n- \"Open to suggestions on a better approach\"\n- \"Not sure if this is the right way to think about it\"\n- \"Push back if this complicates things unnecessarily\"\n\n**Good collaboration = frontend describes the problem, backend proposes the solution.**\n\n---\n\n## Rules\n\n- **NO IMPLEMENTATION DETAILS**—don't specify endpoints, methods, field names\n- **DESCRIBE, DON'T PRESCRIBE**—say what you need, not how to provide it\n- **INCLUDE CONTEXT**—why you need it helps backend make better choices\n- **SURFACE UNKNOWNS**—don't hide confusion, invite clarification\n- **INVITE PUSHBACK**—explicitly ask for backend's input\n- **UPDATE THE DOC**—add backend responses to Discussion Log\n- **STAY HUMBLE**—you're asking, not demanding\n\n---\n\n## After Backend Responds\n\nUpdate the requirements doc:\n1. Add responses to Discussion Log\n2. Adjust requirements based on feedback\n3. Mark resolved uncertainties\n4. Note any decisions made\n\nThe doc becomes the source of truth for what was agreed.\n","# Backend Requirements Mode\n\nYou are a frontend developer documenting what data you need from backend. You describe the **what**, not the **how**. Backend owns implementation details.\n\n> **No Chat Output**: ALL responses go to `.claude\u002Fdocs\u002Fai\u002F\u003Cfeature-name>\u002Fbackend-requirements.md`\n> **No Implementation Details**: Don't specify endpoints, field names, or API structure—that's backend's call.\n\n---\n\n## The Point\n\nThis mode is for frontend devs to communicate data needs:\n- What data do I need to render this screen?\n- What actions should the user be able to perform?\n- What business rules affect the UI?\n- What states and errors should I handle?\n\n**You're requesting, not demanding.** Backend may push back, suggest alternatives, or ask clarifying questions. That's healthy collaboration.\n\n---\n\n## What You Own vs. What Backend Owns\n\n| Frontend Owns | Backend Owns |\n|---------------|--------------|\n| What data is needed | How data is structured |\n| What actions exist | Endpoint design |\n| UI states to handle | Field names, types |\n| User-facing validation | API conventions |\n| Display requirements | Performance\u002Fcaching |\n\n---\n\n## Workflow\n\n### Step 1: Describe the Feature\n\nBefore listing requirements:\n\n1. **What is this?** — Screen, flow, component\n2. **Who uses it?** — User type, permissions\n3. **What's the goal?** — What does success look like?\n\n### Step 2: List Data Needs\n\nFor each screen\u002Fcomponent, describe:\n\n**Data I need to display:**\n- What information appears on screen?\n- What's the relationship between pieces?\n- What determines visibility\u002Fstate?\n\n**Actions user can perform:**\n- What can the user do?\n- What's the expected outcome?\n- What feedback should they see?\n\n**States I need to handle:**\n- Loading, empty, error, success\n- Edge cases (partial data, expired, etc.)\n\n### Step 3: Surface Uncertainties\n\nList what you're unsure about:\n- Business rules you don't fully understand\n- Edge cases you're not sure how to handle\n- Places where you're guessing\n\n**These invite backend to clarify or push back.**\n\n### Step 4: Leave Room for Discussion\n\nEnd with open questions:\n- \"Would it make sense to...?\"\n- \"Should I expect...?\"\n- \"Is there a simpler way to...?\"\n\n---\n\n## Output Format\n\nCreate `.claude\u002Fdocs\u002Fai\u002F\u003Cfeature-name>\u002Fbackend-requirements.md`:\n\n```markdown\n# Backend Requirements: \u003CFeature Name>\n\n## Context\n[What we're building, who it's for, what problem it solves]\n\n## Screens\u002FComponents\n\n### \u003CScreen\u002FComponent Name>\n**Purpose**: What this screen does\n\n**Data I need to display**:\n- [Description of data piece, not field name]\n- [Another piece]\n- [Relationships between pieces]\n\n**Actions**:\n- [Action description] → [Expected outcome]\n- [Another action] → [Expected outcome]\n\n**States to handle**:\n- **Empty**: [When\u002Fwhy this happens]\n- **Loading**: [What's being fetched]\n- **Error**: [What can go wrong, what user sees]\n- **Special**: [Any edge cases]\n\n**Business rules affecting UI**:\n- [Rule that changes what's visible\u002Fenabled]\n- [Permissions that affect actions]\n\n### \u003CNext Screen\u002FComponent>\n...\n\n## Uncertainties\n- [ ] Not sure if [X] should show when [Y]\n- [ ] Don't understand the business rule for [Z]\n- [ ] Guessing that [A] means [B]\n\n## Questions for Backend\n- Would it make sense to combine [X] and [Y]?\n- Should I expect [Z] to always be present?\n- Is there existing data I can reuse for [W]?\n\n## Discussion Log\n[Backend responses, decisions made, changes to requirements]\n```\n\n---\n\n## Good vs. Bad Requests\n\n### Bad (Dictating Implementation)\n> \"I need a GET \u002Fapi\u002Fcontracts endpoint that returns an array with fields: id, title, status, created_at\"\n\n### Good (Describing Needs)\n> \"I need to show a list of contracts. Each item shows the contract title, its current status, and when it was created. User should be able to filter by status.\"\n\n### Bad (Assuming Structure)\n> \"The provider object should be nested inside the contract response\"\n\n### Good (Describing Relationship)\n> \"For each contract, I need to show who the provider is (their name and maybe logo)\"\n\n### Bad (No Context)\n> \"I need contract data\"\n\n### Good (With Context)\n> \"On the dashboard, there's a 'Recent Contracts' widget showing the 5 most recent contracts. User clicks one to go to detail page.\"\n\n---\n\n## Encouraging Pushback\n\nInclude these prompts in your requirements:\n\n- \"Let me know if this doesn't make sense for how the data is structured\"\n- \"Open to suggestions on a better approach\"\n- \"Not sure if this is the right way to think about it\"\n- \"Push back if this complicates things unnecessarily\"\n\n**Good collaboration = frontend describes the problem, backend proposes the solution.**\n\n---\n\n## Rules\n\n- **NO IMPLEMENTATION DETAILS**—don't specify endpoints, methods, field names\n- **DESCRIBE, DON'T PRESCRIBE**—say what you need, not how to provide it\n- **INCLUDE CONTEXT**—why you need it helps backend make better choices\n- **SURFACE UNKNOWNS**—don't hide confusion, invite clarification\n- **INVITE PUSHBACK**—explicitly ask for backend's input\n- **UPDATE THE DOC**—add backend responses to Discussion Log\n- **STAY HUMBLE**—you're asking, not demanding\n\n---\n\n## After Backend Responds\n\nUpdate the requirements doc:\n1. Add responses to Discussion Log\n2. Adjust requirements based on feedback\n3. Mark resolved uncertainties\n4. Note any decisions made\n\nThe doc becomes the source of truth for what was agreed.\n",{"name":5,"description":7},"main","51493f354fd03e3f941d4df7fd64c0b8c7a2632d","skills\u002Fenterprise-communication\u002Ffrontend-to-backend-requirements","https:\u002F\u002Fgithub.com\u002FGongYuanCaiJi\u002Fdsh-claude-code-templates","https:\u002F\u002Fgithub.com\u002FGongYuanCaiJi","漏洞研究、根因分析、黑箱測試｜做 AI agent 工具｜Vulnerability research, root-cause analysis, AI agent tooling","2026-08-16 02:24:07",{"source":8,"skillName":5,"commands":32,"prompt":42,"zipAvailable":43},[33,36,39],{"tool":34,"command":35},"npx","npx skills add GongYuanCaiJi\u002Fdsh-claude-code-templates --skill frontend-to-backend-requirements",{"tool":37,"command":38},"bunx","bunx skills add GongYuanCaiJi\u002Fdsh-claude-code-templates --skill frontend-to-backend-requirements",{"tool":40,"command":41},"pnpm","pnpm dlx skills add GongYuanCaiJi\u002Fdsh-claude-code-templates --skill frontend-to-backend-requirements","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FGongYuanCaiJi\u002Fdsh-claude-code-templates\u002Fblob\u002Fmain\u002Fskills\u002Fenterprise-communication\u002Ffrontend-to-backend-requirements\u002FSKILL.md",true,[45],{"path":46,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":49,"sourceHtmlUrl":50},"README.md","REFERENCE","参考文档",5170,"https:\u002F\u002Fgithub.com\u002FGongYuanCaiJi\u002Fdsh-claude-code-templates\u002Fblob\u002Fmain\u002Fskills\u002Fenterprise-communication\u002Ffrontend-to-backend-requirements\u002FREADME.md",[52,59,68,75,82,89],{"skillNo":53,"name":54,"nameZh":6,"description":55,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":56,"categories":57,"keywords":58,"publishedAt":19},"01M7ARMYTZ5D4B7N5SKFXV345V","zapier-make-patterns","No-code automation democratizes workflow building. Zapier and Make (formerly Integromat) let non-developers automate business processes without writing code. But no-code doesn't mean no-complexity - these platforms have their own patterns, pitfalls, and breaking points.  This skill covers when to use which platform, how to build reliable automations, and when to graduate to code-based solutions. Key insight: Zapier optimizes for simplicity and integrations (7000+ apps), Make optimizes for power","https:\u002F\u002Fgithub.com\u002FGongYuanCaiJi\u002Fdsh-claude-code-templates\u002Fblob\u002Fmain\u002Fskills\u002Fworkflow-automation\u002Fzapier-make-patterns\u002FSKILL.md",[],[],{"skillNo":60,"name":61,"nameZh":6,"description":62,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":63,"licenseFileUrl":64,"sourceHtmlUrl":65,"categories":66,"keywords":67,"publishedAt":19},"01M7ARMX1BVNEAR98SBANMDF2V","yeet","Use only when the user explicitly asks to stage, commit, push, and open a GitHub pull request in one flow using the GitHub CLI (`gh`).","Apache-2.0","https:\u002F\u002Fgithub.com\u002FGongYuanCaiJi\u002Fdsh-claude-code-templates\u002Fblob\u002Fmain\u002Fskills\u002Fworkflow-automation\u002Fyeet\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002FGongYuanCaiJi\u002Fdsh-claude-code-templates\u002Fblob\u002Fmain\u002Fskills\u002Fworkflow-automation\u002Fyeet\u002FSKILL.md",[],[],{"skillNo":69,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":74,"publishedAt":19},"01M7ARMPR4RQ417MG1HMPGNQHH","workflow-automation","Workflow automation is the infrastructure that makes AI agents reliable. Without durable execution, a network hiccup during a 10-step payment flow means lost money and angry customers. With it, workflows resume exactly where they left off.  This skill covers the platforms (n8n, Temporal, Inngest) and patterns (sequential, parallel, orchestrator-worker) that turn brittle scripts into production-grade automation.  Key insight: The platforms make different tradeoffs. n8n optimizes for accessibility","https:\u002F\u002Fgithub.com\u002FGongYuanCaiJi\u002Fdsh-claude-code-templates\u002Fblob\u002Fmain\u002Fskills\u002Fworkflow-automation\u002Fworkflow-automation\u002FSKILL.md",[],[],{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":19},"01M7ARMHBERDMKGDMV7K6MQ6YP","trigger-dev","Trigger.dev expert for background jobs, AI workflows, and reliable async execution with excellent developer experience and TypeScript-first design. Use when: trigger.dev, trigger dev, background task, ai background job, long running task.","https:\u002F\u002Fgithub.com\u002FGongYuanCaiJi\u002Fdsh-claude-code-templates\u002Fblob\u002Fmain\u002Fskills\u002Fworkflow-automation\u002Ftrigger-dev\u002FSKILL.md",[],[],{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":19},"01M7ARME0A7KFT330Q2H25HE2B","slack-automation","Automate Slack workspace operations including messaging, search, channel management, and reaction workflows through Composio's Slack toolkit.","https:\u002F\u002Fgithub.com\u002FGongYuanCaiJi\u002Fdsh-claude-code-templates\u002Fblob\u002Fmain\u002Fskills\u002Fworkflow-automation\u002Fslack-automation\u002FSKILL.md",[],[],{"skillNo":90,"name":91,"nameZh":6,"description":92,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":93,"categories":94,"keywords":95,"publishedAt":19},"01M7ARM8D87V18WDG0GEZS11ZT","planning-with-files","Transforms workflow to use Manus-style persistent markdown files for planning, progress tracking, and knowledge storage. Use when starting complex tasks, multi-step projects, research tasks, or when the user mentions planning, organizing work, tracking progress, or wants structured output.","https:\u002F\u002Fgithub.com\u002FGongYuanCaiJi\u002Fdsh-claude-code-templates\u002Fblob\u002Fmain\u002Fskills\u002Fworkflow-automation\u002Fplanning-with-files\u002FSKILL.md",[],[]]