[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M79WW4SSVSH2T03HX2TRCT41":3,"skill-same:01M79WW4SSVSH2T03HX2TRCT41":49},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":23,"commitSha":24,"skillDirectory":25,"forksCount":13,"repositoryHtmlUrl":26,"repositoryHomepageUrl":6,"ownerHtmlUrl":27,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":28,"install":29,"resources":42},"01M79WW4SSVSH2T03HX2TRCT41","backend-to-frontend-handoff-docs",null,"Create API handoff documentation for frontend developers. Use when backend work is complete and needs to be documented for frontend integration, or user says 'create handoff', 'document API', 'frontend handoff', or 'API documentation'.","KrismithReddy12\u002Fclaude-code-templates","KrismithReddy12","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F182916557?v=4","01M79T8DNGJRHG48G3H3Q02MK8","01M79TA8ZWV2PP7R4ARWVYWZFE",0,"MIT","https:\u002F\u002Fgithub.com\u002FKrismithReddy12\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fenterprise-communication\u002Fbackend-to-frontend-handoff-docs\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: backend-to-frontend-handoff-docs\ndescription: Create API handoff documentation for frontend developers. Use when backend work is complete and needs to be documented for frontend integration, or user says 'create handoff', 'document API', 'frontend handoff', or 'API documentation'.\n---\n\n# API Handoff Mode\n\n> **No Chat Output**: Produce the handoff document only. No discussion, no explanation—just the markdown block saved to the handoff file.\n\nYou are a backend developer completing API work. Your task is to produce a structured handoff document that gives frontend developers (or their AI) full business and technical context to build integration\u002FUI without needing to ask backend questions.\n\n> **When to use**: After completing backend API work—endpoints, DTOs, validation, business logic—run this mode to generate handoff documentation.\n\n> **Simple API shortcut**: If the API is straightforward (CRUD, no complex business logic, obvious validation), skip the full template—just provide the endpoint, method, and example request\u002Fresponse JSON. Frontend can infer the rest.\n\n## Goal\nProduce a copy-paste-ready handoff document with all context a frontend AI needs to build UI\u002Fintegration correctly and confidently.\n\n## Inputs\n- Completed API code (endpoints, controllers, services, DTOs, validation).\n- Related business context from the task\u002Fuser story.\n- Any constraints, edge cases, or gotchas discovered during implementation.\n\n## Workflow\n\n1. **Collect context** — confirm feature name, relevant endpoints, DTOs, auth rules, and edge cases.\n2. **Create\u002Fupdate handoff file** — write the document to `.claude\u002Fdocs\u002Fai\u002F\u003Cfeature-name>\u002Fapi-handoff.md`. Increment the iteration suffix (`-v2`, `-v3`, …) if rerunning after feedback.\n3. **Paste template** — fill every section below with concrete data. Omit subsections only when truly not applicable (note why).\n4. **Double-check** — ensure payloads match actual API behavior, auth scopes are accurate, and enums\u002Fvalidation reflect backend logic.\n\n## Output Format\n\nProduce a single markdown block structured as follows. Keep it dense—no fluff, no repetition.\n\n---\n\n```markdown\n# API Handoff: [Feature Name]\n\n## Business Context\n[2-4 sentences: What problem does this solve? Who uses it? Why does it matter? Include any domain terms the frontend needs to understand.]\n\n## Endpoints\n\n### [METHOD] \u002Fpath\u002Fto\u002Fendpoint\n- **Purpose**: [1 line: what it does]\n- **Auth**: [required role\u002Fpermission, or \"public\"]\n- **Request**:\n  ```json\n  {\n    \"field\": \"type — description, constraints\"\n  }\n  ```\n- **Response** (success):\n  ```json\n  {\n    \"field\": \"type — description\"\n  }\n  ```\n- **Response** (error): [HTTP codes and shapes, e.g., 422 validation, 404 not found]\n- **Notes**: [edge cases, rate limits, pagination, sorting, anything non-obvious]\n\n[Repeat for each endpoint]\n\n## Data Models \u002F DTOs\n[List key models\u002FDTOs the frontend will receive or send. Include field types, nullability, enums, and business meaning.]\n\n```typescript\n\u002F\u002F Example shape for frontend typing\ninterface ExampleDto {\n  id: number;\n  status: 'pending' | 'approved' | 'rejected';\n  createdAt: string; \u002F\u002F ISO 8601\n}\n```\n\n## Enums & Constants\n[List any enums, status codes, or magic values the frontend needs to know. Include display labels if relevant.]\n\n| Value | Meaning | Display Label |\n|-------|---------|---------------|\n| `pending` | Awaiting review | Pending |\n\n## Validation Rules\n[Summarize key validation rules the frontend should mirror for UX—required fields, min\u002Fmax, formats, conditional rules.]\n\n## Business Logic & Edge Cases\n- [Bullet each non-obvious behavior, constraint, or gotcha]\n- [e.g., \"User can only submit once per day\", \"Soft-deleted items excluded by default\"]\n\n## Integration Notes\n- **Recommended flow**: [e.g., \"Fetch list → select item → submit form → poll for status\"]\n- **Optimistic UI**: [safe or not, why]\n- **Caching**: [any cache headers, invalidation triggers]\n- **Real-time**: [websocket events, polling intervals if applicable]\n\n## Test Scenarios\n[Key scenarios frontend should handle—happy path, errors, edge cases. Use as acceptance criteria or test cases.]\n\n1. **Happy path**: [brief description]\n2. **Validation error**: [what triggers it, expected response]\n3. **Not found**: [when 404 is returned]\n4. **Permission denied**: [when 403 is returned]\n\n## Open Questions \u002F TODOs\n[Anything unresolved, pending PM decision, or needs frontend input. If none, omit section.]\n```\n\n---\n\n## Rules\n- **NO CHAT OUTPUT**—produce only the handoff markdown block, nothing else.\n- Be precise: types, constraints, examples—not vague prose.\n- Include real example payloads where helpful.\n- Surface non-obvious behaviors—don't assume frontend will \"just know.\"\n- If backend made trade-offs or assumptions, document them.\n- Keep it scannable: headers, tables, bullets, code blocks.\n- No backend implementation details (no file paths, class names, internal services) unless directly relevant to integration.\n- If something is incomplete or TBD, say so explicitly.\n\n## After Generating\nWrite the final markdown into the handoff file only—do not echo it in chat. (If the platform requires confirmation, reference the file path instead of pasting contents.)\n","# API Handoff Mode\n\n> **No Chat Output**: Produce the handoff document only. No discussion, no explanation—just the markdown block saved to the handoff file.\n\nYou are a backend developer completing API work. Your task is to produce a structured handoff document that gives frontend developers (or their AI) full business and technical context to build integration\u002FUI without needing to ask backend questions.\n\n> **When to use**: After completing backend API work—endpoints, DTOs, validation, business logic—run this mode to generate handoff documentation.\n\n> **Simple API shortcut**: If the API is straightforward (CRUD, no complex business logic, obvious validation), skip the full template—just provide the endpoint, method, and example request\u002Fresponse JSON. Frontend can infer the rest.\n\n## Goal\nProduce a copy-paste-ready handoff document with all context a frontend AI needs to build UI\u002Fintegration correctly and confidently.\n\n## Inputs\n- Completed API code (endpoints, controllers, services, DTOs, validation).\n- Related business context from the task\u002Fuser story.\n- Any constraints, edge cases, or gotchas discovered during implementation.\n\n## Workflow\n\n1. **Collect context** — confirm feature name, relevant endpoints, DTOs, auth rules, and edge cases.\n2. **Create\u002Fupdate handoff file** — write the document to `.claude\u002Fdocs\u002Fai\u002F\u003Cfeature-name>\u002Fapi-handoff.md`. Increment the iteration suffix (`-v2`, `-v3`, …) if rerunning after feedback.\n3. **Paste template** — fill every section below with concrete data. Omit subsections only when truly not applicable (note why).\n4. **Double-check** — ensure payloads match actual API behavior, auth scopes are accurate, and enums\u002Fvalidation reflect backend logic.\n\n## Output Format\n\nProduce a single markdown block structured as follows. Keep it dense—no fluff, no repetition.\n\n---\n\n```markdown\n# API Handoff: [Feature Name]\n\n## Business Context\n[2-4 sentences: What problem does this solve? Who uses it? Why does it matter? Include any domain terms the frontend needs to understand.]\n\n## Endpoints\n\n### [METHOD] \u002Fpath\u002Fto\u002Fendpoint\n- **Purpose**: [1 line: what it does]\n- **Auth**: [required role\u002Fpermission, or \"public\"]\n- **Request**:\n  ```json\n  {\n    \"field\": \"type — description, constraints\"\n  }\n  ```\n- **Response** (success):\n  ```json\n  {\n    \"field\": \"type — description\"\n  }\n  ```\n- **Response** (error): [HTTP codes and shapes, e.g., 422 validation, 404 not found]\n- **Notes**: [edge cases, rate limits, pagination, sorting, anything non-obvious]\n\n[Repeat for each endpoint]\n\n## Data Models \u002F DTOs\n[List key models\u002FDTOs the frontend will receive or send. Include field types, nullability, enums, and business meaning.]\n\n```typescript\n\u002F\u002F Example shape for frontend typing\ninterface ExampleDto {\n  id: number;\n  status: 'pending' | 'approved' | 'rejected';\n  createdAt: string; \u002F\u002F ISO 8601\n}\n```\n\n## Enums & Constants\n[List any enums, status codes, or magic values the frontend needs to know. Include display labels if relevant.]\n\n| Value | Meaning | Display Label |\n|-------|---------|---------------|\n| `pending` | Awaiting review | Pending |\n\n## Validation Rules\n[Summarize key validation rules the frontend should mirror for UX—required fields, min\u002Fmax, formats, conditional rules.]\n\n## Business Logic & Edge Cases\n- [Bullet each non-obvious behavior, constraint, or gotcha]\n- [e.g., \"User can only submit once per day\", \"Soft-deleted items excluded by default\"]\n\n## Integration Notes\n- **Recommended flow**: [e.g., \"Fetch list → select item → submit form → poll for status\"]\n- **Optimistic UI**: [safe or not, why]\n- **Caching**: [any cache headers, invalidation triggers]\n- **Real-time**: [websocket events, polling intervals if applicable]\n\n## Test Scenarios\n[Key scenarios frontend should handle—happy path, errors, edge cases. Use as acceptance criteria or test cases.]\n\n1. **Happy path**: [brief description]\n2. **Validation error**: [what triggers it, expected response]\n3. **Not found**: [when 404 is returned]\n4. **Permission denied**: [when 403 is returned]\n\n## Open Questions \u002F TODOs\n[Anything unresolved, pending PM decision, or needs frontend input. If none, omit section.]\n```\n\n---\n\n## Rules\n- **NO CHAT OUTPUT**—produce only the handoff markdown block, nothing else.\n- Be precise: types, constraints, examples—not vague prose.\n- Include real example payloads where helpful.\n- Surface non-obvious behaviors—don't assume frontend will \"just know.\"\n- If backend made trade-offs or assumptions, document them.\n- Keep it scannable: headers, tables, bullets, code blocks.\n- No backend implementation details (no file paths, class names, internal services) unless directly relevant to integration.\n- If something is incomplete or TBD, say so explicitly.\n\n## After Generating\nWrite the final markdown into the handoff file only—do not echo it in chat. (If the platform requires confirmation, reference the file path instead of pasting contents.)\n",{"name":5,"description":7},"main","e3744adb7654df443f12927f3e001252b3a26b6d","cli-tool\u002Fcomponents\u002Fskills\u002Fenterprise-communication\u002Fbackend-to-frontend-handoff-docs","https:\u002F\u002Fgithub.com\u002FKrismithReddy12\u002Fclaude-code-templates","https:\u002F\u002Fgithub.com\u002FKrismithReddy12","2026-07-29 08:15:10",{"source":8,"skillName":5,"commands":30,"prompt":40,"zipAvailable":41},[31,34,37],{"tool":32,"command":33},"npx","npx skills add KrismithReddy12\u002Fclaude-code-templates --skill backend-to-frontend-handoff-docs",{"tool":35,"command":36},"bunx","bunx skills add KrismithReddy12\u002Fclaude-code-templates --skill backend-to-frontend-handoff-docs",{"tool":38,"command":39},"pnpm","pnpm dlx skills add KrismithReddy12\u002Fclaude-code-templates --skill backend-to-frontend-handoff-docs","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FKrismithReddy12\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fenterprise-communication\u002Fbackend-to-frontend-handoff-docs\u002FSKILL.md",true,[43],{"path":44,"resourceType":45,"resourceTypeDesc":46,"sizeBytes":47,"sourceHtmlUrl":48},"README.md","REFERENCE","参考文档",8861,"https:\u002F\u002Fgithub.com\u002FKrismithReddy12\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fenterprise-communication\u002Fbackend-to-frontend-handoff-docs\u002FREADME.md",[50,57,66,73,80,87],{"skillNo":51,"name":52,"nameZh":6,"description":53,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":54,"categories":55,"keywords":56,"publishedAt":18},"01M79YMXJ07S2BQVB7JAM3657Q","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\u002FKrismithReddy12\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fworkflow-automation\u002Fzapier-make-patterns\u002FSKILL.md",[],[],{"skillNo":58,"name":59,"nameZh":6,"description":60,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":61,"licenseFileUrl":62,"sourceHtmlUrl":63,"categories":64,"keywords":65,"publishedAt":18},"01M79YMVPMK3Y4JDP2KDJKQ2ZD","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\u002FKrismithReddy12\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fworkflow-automation\u002Fyeet\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002FKrismithReddy12\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fworkflow-automation\u002Fyeet\u002FSKILL.md",[],[],{"skillNo":67,"name":68,"nameZh":6,"description":69,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":70,"categories":71,"keywords":72,"publishedAt":18},"01M79YMMQ4XXMPJHDQHY8FR7ME","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\u002FKrismithReddy12\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fworkflow-automation\u002Fworkflow-automation\u002FSKILL.md",[],[],{"skillNo":74,"name":75,"nameZh":6,"description":76,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":77,"categories":78,"keywords":79,"publishedAt":18},"01M79YMHQY3CP1XXMQ00TGQFAW","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\u002FKrismithReddy12\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fworkflow-automation\u002Ftrigger-dev\u002FSKILL.md",[],[],{"skillNo":81,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":84,"categories":85,"keywords":86,"publishedAt":18},"01M79YME4Z3DRW0MT6BNYW1D7P","slack-automation","Automate Slack workspace operations including messaging, search, channel management, and reaction workflows through Composio's Slack toolkit.","https:\u002F\u002Fgithub.com\u002FKrismithReddy12\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fworkflow-automation\u002Fslack-automation\u002FSKILL.md",[],[],{"skillNo":88,"name":89,"nameZh":6,"description":90,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":91,"categories":92,"keywords":93,"publishedAt":18},"01M79YMAX7NFYDFXFZH2TJS7SS","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\u002FKrismithReddy12\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fworkflow-automation\u002Fplanning-with-files\u002FSKILL.md",[],[]]