[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6AF12JZC9Y1C8M92PG3J4P9":3,"skill-same:01M6AF12JZC9Y1C8M92PG3J4P9":80},{"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":26,"publishedAt":45,"linkOnly":46,"markdownContent":47,"markdownBody":48,"frontMatter":49,"refName":50,"commitSha":51,"skillDirectory":52,"forksCount":53,"repositoryHtmlUrl":54,"repositoryHomepageUrl":55,"ownerHtmlUrl":56,"ownerBlogUrl":57,"ownerDescription":58,"updatedAt":59,"install":60,"resources":73},"01M6AF12JZC9Y1C8M92PG3J4P9","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'.","davila7\u002Fclaude-code-templates","davila7","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F6216945?v=4","01M6ADEWWFPS191NFM0Y1EX1JH","Daniel Avila","01M6ADJHGM78PHQRD3XZTFDVKK",33481,"MIT","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fenterprise-communication\u002Fbackend-to-frontend-handoff-docs\u002FSKILL.md",[18,23],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000009","前端开发","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000010","后端与接口",[27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44],"handoff","docs","frontend","backend to frontend handoff docs","backend","when","for","complete","document","api documentation","use","create handoff","user","work","api","integration","create","documentation","2026-11-10 10:12:30",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","2b749c82b5d11fac39d9a6e021ce3f5b8a541bd1","cli-tool\u002Fcomponents\u002Fskills\u002Fenterprise-communication\u002Fbackend-to-frontend-handoff-docs",3931,"https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates","https:\u002F\u002Faitmpl.com","https:\u002F\u002Fgithub.com\u002Fdavila7","https:\u002F\u002Fdanielavila.me","Building AI dev tools with LLMs","2026-11-14 06:14:46",{"source":8,"skillName":5,"commands":61,"prompt":71,"zipAvailable":72},[62,65,68],{"tool":63,"command":64},"npx","npx skills add davila7\u002Fclaude-code-templates --skill backend-to-frontend-handoff-docs",{"tool":66,"command":67},"bunx","bunx skills add davila7\u002Fclaude-code-templates --skill backend-to-frontend-handoff-docs",{"tool":69,"command":70},"pnpm","pnpm dlx skills add davila7\u002Fclaude-code-templates --skill backend-to-frontend-handoff-docs","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fenterprise-communication\u002Fbackend-to-frontend-handoff-docs\u002FSKILL.md",true,[74],{"path":75,"resourceType":76,"resourceTypeDesc":77,"sizeBytes":78,"sourceHtmlUrl":79},"README.md","REFERENCE","参考文档",8861,"https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fenterprise-communication\u002Fbackend-to-frontend-handoff-docs\u002FREADME.md",[81,108,134,165,197,221],{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":90,"publishedAt":45},"01M70NHBTQ8BV0A2SCAZXEPHCX","wealthville-pool-scoring","Score DeFi liquidity pools before providing liquidity. Returns a 0-100 pool score and an Enter\u002FHold\u002FExit\u002FReduce\u002FAvoid verdict with calibrated confidence for ~68,800 Solana pools and 575 EVM pools, plus a public miss-inclusive track record. Use when asked whether a pool is worth LPing into, which pools look best right now, or how accurate the scores have actually been.","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fweb-data\u002Fwealthville-pool-scoring\u002FSKILL.md",[87],{"categoryNo":88,"categoryName":89,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",[91,92,93,94,95,33,96,97,37,32,98,99,100,101,102,103,104,105,106,107],"scoring","pool","wealthville pool scoring","liquidity","which","exit","now","reduce","with","record","track","verdict","evm","solana","how","public","look",{"skillNo":109,"name":110,"nameZh":6,"description":111,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":112,"categories":113,"keywords":115,"publishedAt":45},"01M70MB6VR8ERJ4EM8D5KHBMEV","technical-debt-auditor","Scans a codebase and produces a quantified technical debt report with a prioritized remediation plan. Analyzes dead code, TODO\u002FFIXME\u002FHACK markers, dependency staleness, complexity hotspots, code duplication signals, test coverage gaps, unused exports, and outdated patterns. Use this skill when the user asks to audit their codebase for tech debt, wants a health check of their code quality, says things like \"where should I focus refactoring\", \"find code smells\", \"audit my codebase\", \"what technical debt do we have\", \"prioritize cleanup work\", or asks about code quality metrics. Also trigger when the user mentions \"code rot\", \"legacy cleanup\", \"refactoring priorities\", or wants to understand the overall health of a project before a major effort. Trigger even if the user doesn't say \"technical debt\" explicitly — any request to systematically assess code quality and identify improvement priorities belongs here.","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fdevelopment\u002Ftechnical-debt-auditor\u002FSKILL.md",[114],{"categoryNo":88,"categoryName":89,"taxonomyType":21,"taxonomyTypeDesc":22},[116,117,118,119,120,121,122,123,124,125,126,32,127,128,40,129,130,131,132,133],"technical debt","debt","technical","technical debt auditor","auditor","coverage","complexity","markers","project","cleanup","unused","code","todo","plan","focus","signals","audit","dependency",{"skillNo":135,"name":136,"nameZh":6,"description":137,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":138,"categories":139,"keywords":147,"publishedAt":45},"01M70KPYH9QNHCNME5GJQGE22K","readonly-sql-guard","Make an agent's database access provably read-only. Use when an agent runs caller-supplied SQL against a production\u002FERP\u002Fanalytics database (a \"query\" MCP tool, text-to-SQL, an admin console), or when reviewing DB-access code for write\u002FDDL\u002Fside-effect\u002Ftransaction-escape risks. Checks what a statement CALLS, not just its shape.","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fdatabase\u002Freadonly-sql-guard\u002FSKILL.md",[140,141,142],{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":88,"categoryName":89,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":143,"categoryName":144,"taxonomyType":145,"taxonomyTypeDesc":146},"01JBSEEDCAT000000000000033","数据分析师","PROFESSION","适用职业",[148,149,150,151,152,153,154,33,155,156,157,158,159,160,161,37,162,163,32,164],"readonly","guard","sql guard","sql","readonly sql guard","erp","effect","read-only","db","just","tool","calls","only","MCP","access","database","query",{"skillNo":166,"name":167,"nameZh":6,"description":168,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":169,"licenseFileUrl":170,"sourceHtmlUrl":171,"categories":172,"keywords":174,"publishedAt":45},"01M6AFY6F7CC2BBZP1QD6VTNVC","web-artifacts-builder","Suite of tools for creating elaborate, multi-component claude.ai HTML artifacts using modern frontend web technologies (React, Tailwind CSS, shadcn\u002Fui). Use for complex artifacts requiring state management, routing, or shadcn\u002Fui components - not for simple single-file HTML\u002FJSX artifacts.","Apache-2.0","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Futilities\u002Fweb-artifacts-builder\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Futilities\u002Fweb-artifacts-builder\u002FSKILL.md",[173],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[175,176,177,178,179,180,181,182,183,184,29,185,186,187,188,189,190,191,192,193,194,195,33,196],"artifacts builder","web","web artifacts builder","artifacts","builder","state","routing","state management","component","css","ui","Tools","file","components","shadcn","react","Tailwind","suite","jsx","html","single-file","ui components",{"skillNo":198,"name":199,"nameZh":6,"description":200,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":169,"licenseFileUrl":201,"sourceHtmlUrl":202,"categories":203,"keywords":208,"publishedAt":45},"01M6AFWF33SFV9Z3SF4PEEE4BF","webapp-testing","Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fsecurity\u002Fwebapp-testing\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fsecurity\u002Fwebapp-testing\u002FSKILL.md",[204,207],{"categoryNo":205,"categoryName":206,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000008","测试与质量",{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[209,210,211,212,213,176,214,29,185,215,216,217,218,33,219,99,220],"webapp testing","testing","webapp","browser","playwright","applications","debugging","toolkit","logs","screenshots","local","behavior",{"skillNo":222,"name":223,"nameZh":6,"description":224,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":169,"licenseFileUrl":225,"sourceHtmlUrl":226,"categories":227,"keywords":235,"publishedAt":45},"01M6AF67Q67JJJ5V51JR2P52KA","discernment-nudge","After you give a substantive answer or draft that the user may act on — advice or recommendations, drafted artifacts such as goals, plans, pitches, proposals, or emails, estimates or projections, analysis or interpretation of data, factual claims they may rely on, or a multi-step argument — invoke this skill BEFORE finalizing your reply and then, if it applies, append 2-3 short follow-up questions, each tied to something specific in what you just produced, that help the user check key facts, probe the reasoning or assumptions, and notice missing context. Do this at most once per conversation. Skip it when the user asked a trivial how-to or simple lookup, wants a purely educational explanation, asked you only to format, convert, or assemble a file from content they provided, is writing code they will run, is doing creative writing or casual chat, or already asked you to double-check, cite, or review — the skill file explains these boundaries and the exact output format.","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fproductivity\u002Fdiscernment-nudge\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fproductivity\u002Fdiscernment-nudge\u002FSKILL.md",[228,231,232],{"categoryNo":229,"categoryName":230,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000018","写作与文案",{"categoryNo":88,"categoryName":89,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":233,"categoryName":234,"taxonomyType":145,"taxonomyTypeDesc":146},"01JBSEEDCAT000000000000036","内容创作者",[236,237,238,239,240,241,242,243,178,244,187,127,245,246,247,248,249,160,250,32,251,252,253,254,255,105,256],"discernment nudge","nudge","interpretation","help","run","reasoning","data","writing","lookup","content","review","conversation","short","up","invoke","you","analysis","claims","argument","assemble","recommendations"]