[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M70M3T17RWDXBS1EQHV2Z481":3,"skill-same:01M70M3T17RWDXBS1EQHV2Z481":65},{"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":23,"publishedAt":36,"linkOnly":37,"markdownContent":38,"markdownBody":39,"frontMatter":40,"refName":41,"commitSha":42,"skillDirectory":43,"forksCount":44,"repositoryHtmlUrl":45,"repositoryHomepageUrl":46,"ownerHtmlUrl":47,"ownerBlogUrl":48,"ownerDescription":49,"updatedAt":50,"install":51,"resources":64},"01M70M3T17RWDXBS1EQHV2Z481","deprecation-and-migration",null,"Manages deprecation and migration. Use when removing old systems, APIs, or features. Use when migrating users from one implementation to another. Use when deciding whether to maintain or sunset existing code.","shengdabai\u002FTony-Claude-Code-Skills","shengdabai","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F116417419?v=4","01M70F6D2WY5PQV5A92BKYJQEW","Tony Sheng","01M70F6D3GAAAYZ5H4CC1G8VXM",3,"MIT","https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fdeprecation-and-migration\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[24,25,26,27,28,29,30,31,32,33,34,35],"deprecation","migration","deprecation and migration","maintain","use","Existing","when","code","users","features","systems","implementation","2026-11-10 10:12:30",false,"---\nname: deprecation-and-migration\ndescription: Manages deprecation and migration. Use when removing old systems, APIs, or features. Use when migrating users from one implementation to another. Use when deciding whether to maintain or sunset existing code.\n---\n\n# Deprecation and Migration\n\n## Overview\n\nCode is a liability, not an asset. Every line of code has ongoing maintenance cost — bugs to fix, dependencies to update, security patches to apply, and new engineers to onboard. Deprecation is the discipline of removing code that no longer earns its keep, and migration is the process of moving users safely from the old to the new.\n\nMost engineering organizations are good at building things. Few are good at removing them. This skill addresses that gap.\n\n## When to Use\n\n- Replacing an old system, API, or library with a new one\n- Sunsetting a feature that's no longer needed\n- Consolidating duplicate implementations\n- Removing dead code that nobody owns but everybody depends on\n- Planning the lifecycle of a new system (deprecation planning starts at design time)\n- Deciding whether to maintain a legacy system or invest in migration\n\n## Core Principles\n\n### Code Is a Liability\n\nEvery line of code has ongoing cost: it needs tests, documentation, security patches, dependency updates, and mental overhead for anyone working nearby. The value of code is the functionality it provides, not the code itself. When the same functionality can be provided with less code, less complexity, or better abstractions — the old code should go.\n\n### Hyrum's Law Makes Removal Hard\n\nWith enough users, every observable behavior becomes depended on — including bugs, timing quirks, and undocumented side effects. This is why deprecation requires active migration, not just announcement. Users can't \"just switch\" when they depend on behaviors the replacement doesn't replicate.\n\n### Deprecation Planning Starts at Design Time\n\nWhen building something new, ask: \"How would we remove this in 3 years?\" Systems designed with clean interfaces, feature flags, and minimal surface area are easier to deprecate than systems that leak implementation details everywhere.\n\n## The Deprecation Decision\n\nBefore deprecating anything, answer these questions:\n\n```\n1. Does this system still provide unique value?\n   → If yes, maintain it. If no, proceed.\n\n2. How many users\u002Fconsumers depend on it?\n   → Quantify the migration scope.\n\n3. Does a replacement exist?\n   → If no, build the replacement first. Don't deprecate without an alternative.\n\n4. What's the migration cost for each consumer?\n   → If trivially automated, do it. If manual and high-effort, weigh against maintenance cost.\n\n5. What's the ongoing maintenance cost of NOT deprecating?\n   → Security risk, engineer time, opportunity cost of complexity.\n```\n\n## Compulsory vs Advisory Deprecation\n\n| Type | When to Use | Mechanism |\n|------|-------------|-----------|\n| **Advisory** | Migration is optional, old system is stable | Warnings, documentation, nudges. Users migrate on their own timeline. |\n| **Compulsory** | Old system has security issues, blocks progress, or maintenance cost is unsustainable | Hard deadline. Old system will be removed by date X. Provide migration tooling. |\n\n**Default to advisory.** Use compulsory only when the maintenance cost or risk justifies forcing migration. Compulsory deprecation requires providing migration tooling, documentation, and support — you can't just announce a deadline.\n\n## The Migration Process\n\n### Step 1: Build the Replacement\n\nDon't deprecate without a working alternative. The replacement must:\n\n- Cover all critical use cases of the old system\n- Have documentation and migration guides\n- Be proven in production (not just \"theoretically better\")\n\n### Step 2: Announce and Document\n\n```markdown\n## Deprecation Notice: OldService\n\n**Status:** Deprecated as of 2025-03-01\n**Replacement:** NewService (see migration guide below)\n**Removal date:** Advisory — no hard deadline yet\n**Reason:** OldService requires manual scaling and lacks observability.\n            NewService handles both automatically.\n\n### Migration Guide\n1. Replace `import { client } from 'old-service'` with `import { client } from 'new-service'`\n2. Update configuration (see examples below)\n3. Run the migration verification script: `npx migrate-check`\n```\n\n### Step 3: Migrate Incrementally\n\nMigrate consumers one at a time, not all at once. For each consumer:\n\n```\n1. Identify all touchpoints with the deprecated system\n2. Update to use the replacement\n3. Verify behavior matches (tests, integration checks)\n4. Remove references to the old system\n5. Confirm no regressions\n```\n\n**The Churn Rule:** If you own the infrastructure being deprecated, you are responsible for migrating your users — or providing backward-compatible updates that require no migration. Don't announce deprecation and leave users to figure it out.\n\n### Step 4: Remove the Old System\n\nOnly after all consumers have migrated:\n\n```\n1. Verify zero active usage (metrics, logs, dependency analysis)\n2. Remove the code\n3. Remove associated tests, documentation, and configuration\n4. Remove the deprecation notices\n5. Celebrate — removing code is an achievement\n```\n\n## Migration Patterns\n\n### Strangler Pattern\n\nRun old and new systems in parallel. Route traffic incrementally from old to new. When the old system handles 0% of traffic, remove it.\n\n```\nPhase 1: New system handles 0%, old handles 100%\nPhase 2: New system handles 10% (canary)\nPhase 3: New system handles 50%\nPhase 4: New system handles 100%, old system idle\nPhase 5: Remove old system\n```\n\n### Adapter Pattern\n\nCreate an adapter that translates calls from the old interface to the new implementation. Consumers keep using the old interface while you migrate the backend.\n\n```typescript\n\u002F\u002F Adapter: old interface, new implementation\nclass LegacyTaskService implements OldTaskAPI {\n  constructor(private newService: NewTaskService) {}\n\n  \u002F\u002F Old method signature, delegates to new implementation\n  getTask(id: number): OldTask {\n    const task = this.newService.findById(String(id));\n    return this.toOldFormat(task);\n  }\n}\n```\n\n### Feature Flag Migration\n\nUse feature flags to switch consumers from old to new system one at a time:\n\n```typescript\nfunction getTaskService(userId: string): TaskService {\n  if (featureFlags.isEnabled('new-task-service', { userId })) {\n    return new NewTaskService();\n  }\n  return new LegacyTaskService();\n}\n```\n\n## Zombie Code\n\nZombie code is code that nobody owns but everybody depends on. It's not actively maintained, has no clear owner, and accumulates security vulnerabilities and compatibility issues. Signs:\n\n- No commits in 6+ months but active consumers exist\n- No assigned maintainer or team\n- Failing tests that nobody fixes\n- Dependencies with known vulnerabilities that nobody updates\n- Documentation that references systems that no longer exist\n\n**Response:** Either assign an owner and maintain it properly, or deprecate it with a concrete migration plan. Zombie code cannot stay in limbo — it either gets investment or removal.\n\n## Common Rationalizations\n\n| Rationalization | Reality |\n|---|---|\n| \"It still works, why remove it?\" | Working code that nobody maintains accumulates security debt and complexity. Maintenance cost grows silently. |\n| \"Someone might need it later\" | If it's needed later, it can be rebuilt. Keeping unused code \"just in case\" costs more than rebuilding. |\n| \"The migration is too expensive\" | Compare migration cost to ongoing maintenance cost over 2-3 years. Migration is usually cheaper long-term. |\n| \"We'll deprecate it after we finish the new system\" | Deprecation planning starts at design time. By the time the new system is done, you'll have new priorities. Plan now. |\n| \"Users will migrate on their own\" | They won't. Provide tooling, documentation, and incentives — or do the migration yourself (the Churn Rule). |\n| \"We can maintain both systems indefinitely\" | Two systems doing the same thing is double the maintenance, testing, documentation, and onboarding cost. |\n\n## Red Flags\n\n- Deprecated systems with no replacement available\n- Deprecation announcements with no migration tooling or documentation\n- \"Soft\" deprecation that's been advisory for years with no progress\n- Zombie code with no owner and active consumers\n- New features added to a deprecated system (invest in the replacement instead)\n- Deprecation without measuring current usage\n- Removing code without verifying zero active consumers\n\n## Verification\n\nAfter completing a deprecation:\n\n- [ ] Replacement is production-proven and covers all critical use cases\n- [ ] Migration guide exists with concrete steps and examples\n- [ ] All active consumers have been migrated (verified by metrics\u002Flogs)\n- [ ] Old code, tests, documentation, and configuration are fully removed\n- [ ] No references to the deprecated system remain in the codebase\n- [ ] Deprecation notices are removed (they served their purpose)\n","# Deprecation and Migration\n\n## Overview\n\nCode is a liability, not an asset. Every line of code has ongoing maintenance cost — bugs to fix, dependencies to update, security patches to apply, and new engineers to onboard. Deprecation is the discipline of removing code that no longer earns its keep, and migration is the process of moving users safely from the old to the new.\n\nMost engineering organizations are good at building things. Few are good at removing them. This skill addresses that gap.\n\n## When to Use\n\n- Replacing an old system, API, or library with a new one\n- Sunsetting a feature that's no longer needed\n- Consolidating duplicate implementations\n- Removing dead code that nobody owns but everybody depends on\n- Planning the lifecycle of a new system (deprecation planning starts at design time)\n- Deciding whether to maintain a legacy system or invest in migration\n\n## Core Principles\n\n### Code Is a Liability\n\nEvery line of code has ongoing cost: it needs tests, documentation, security patches, dependency updates, and mental overhead for anyone working nearby. The value of code is the functionality it provides, not the code itself. When the same functionality can be provided with less code, less complexity, or better abstractions — the old code should go.\n\n### Hyrum's Law Makes Removal Hard\n\nWith enough users, every observable behavior becomes depended on — including bugs, timing quirks, and undocumented side effects. This is why deprecation requires active migration, not just announcement. Users can't \"just switch\" when they depend on behaviors the replacement doesn't replicate.\n\n### Deprecation Planning Starts at Design Time\n\nWhen building something new, ask: \"How would we remove this in 3 years?\" Systems designed with clean interfaces, feature flags, and minimal surface area are easier to deprecate than systems that leak implementation details everywhere.\n\n## The Deprecation Decision\n\nBefore deprecating anything, answer these questions:\n\n```\n1. Does this system still provide unique value?\n   → If yes, maintain it. If no, proceed.\n\n2. How many users\u002Fconsumers depend on it?\n   → Quantify the migration scope.\n\n3. Does a replacement exist?\n   → If no, build the replacement first. Don't deprecate without an alternative.\n\n4. What's the migration cost for each consumer?\n   → If trivially automated, do it. If manual and high-effort, weigh against maintenance cost.\n\n5. What's the ongoing maintenance cost of NOT deprecating?\n   → Security risk, engineer time, opportunity cost of complexity.\n```\n\n## Compulsory vs Advisory Deprecation\n\n| Type | When to Use | Mechanism |\n|------|-------------|-----------|\n| **Advisory** | Migration is optional, old system is stable | Warnings, documentation, nudges. Users migrate on their own timeline. |\n| **Compulsory** | Old system has security issues, blocks progress, or maintenance cost is unsustainable | Hard deadline. Old system will be removed by date X. Provide migration tooling. |\n\n**Default to advisory.** Use compulsory only when the maintenance cost or risk justifies forcing migration. Compulsory deprecation requires providing migration tooling, documentation, and support — you can't just announce a deadline.\n\n## The Migration Process\n\n### Step 1: Build the Replacement\n\nDon't deprecate without a working alternative. The replacement must:\n\n- Cover all critical use cases of the old system\n- Have documentation and migration guides\n- Be proven in production (not just \"theoretically better\")\n\n### Step 2: Announce and Document\n\n```markdown\n## Deprecation Notice: OldService\n\n**Status:** Deprecated as of 2025-03-01\n**Replacement:** NewService (see migration guide below)\n**Removal date:** Advisory — no hard deadline yet\n**Reason:** OldService requires manual scaling and lacks observability.\n            NewService handles both automatically.\n\n### Migration Guide\n1. Replace `import { client } from 'old-service'` with `import { client } from 'new-service'`\n2. Update configuration (see examples below)\n3. Run the migration verification script: `npx migrate-check`\n```\n\n### Step 3: Migrate Incrementally\n\nMigrate consumers one at a time, not all at once. For each consumer:\n\n```\n1. Identify all touchpoints with the deprecated system\n2. Update to use the replacement\n3. Verify behavior matches (tests, integration checks)\n4. Remove references to the old system\n5. Confirm no regressions\n```\n\n**The Churn Rule:** If you own the infrastructure being deprecated, you are responsible for migrating your users — or providing backward-compatible updates that require no migration. Don't announce deprecation and leave users to figure it out.\n\n### Step 4: Remove the Old System\n\nOnly after all consumers have migrated:\n\n```\n1. Verify zero active usage (metrics, logs, dependency analysis)\n2. Remove the code\n3. Remove associated tests, documentation, and configuration\n4. Remove the deprecation notices\n5. Celebrate — removing code is an achievement\n```\n\n## Migration Patterns\n\n### Strangler Pattern\n\nRun old and new systems in parallel. Route traffic incrementally from old to new. When the old system handles 0% of traffic, remove it.\n\n```\nPhase 1: New system handles 0%, old handles 100%\nPhase 2: New system handles 10% (canary)\nPhase 3: New system handles 50%\nPhase 4: New system handles 100%, old system idle\nPhase 5: Remove old system\n```\n\n### Adapter Pattern\n\nCreate an adapter that translates calls from the old interface to the new implementation. Consumers keep using the old interface while you migrate the backend.\n\n```typescript\n\u002F\u002F Adapter: old interface, new implementation\nclass LegacyTaskService implements OldTaskAPI {\n  constructor(private newService: NewTaskService) {}\n\n  \u002F\u002F Old method signature, delegates to new implementation\n  getTask(id: number): OldTask {\n    const task = this.newService.findById(String(id));\n    return this.toOldFormat(task);\n  }\n}\n```\n\n### Feature Flag Migration\n\nUse feature flags to switch consumers from old to new system one at a time:\n\n```typescript\nfunction getTaskService(userId: string): TaskService {\n  if (featureFlags.isEnabled('new-task-service', { userId })) {\n    return new NewTaskService();\n  }\n  return new LegacyTaskService();\n}\n```\n\n## Zombie Code\n\nZombie code is code that nobody owns but everybody depends on. It's not actively maintained, has no clear owner, and accumulates security vulnerabilities and compatibility issues. Signs:\n\n- No commits in 6+ months but active consumers exist\n- No assigned maintainer or team\n- Failing tests that nobody fixes\n- Dependencies with known vulnerabilities that nobody updates\n- Documentation that references systems that no longer exist\n\n**Response:** Either assign an owner and maintain it properly, or deprecate it with a concrete migration plan. Zombie code cannot stay in limbo — it either gets investment or removal.\n\n## Common Rationalizations\n\n| Rationalization | Reality |\n|---|---|\n| \"It still works, why remove it?\" | Working code that nobody maintains accumulates security debt and complexity. Maintenance cost grows silently. |\n| \"Someone might need it later\" | If it's needed later, it can be rebuilt. Keeping unused code \"just in case\" costs more than rebuilding. |\n| \"The migration is too expensive\" | Compare migration cost to ongoing maintenance cost over 2-3 years. Migration is usually cheaper long-term. |\n| \"We'll deprecate it after we finish the new system\" | Deprecation planning starts at design time. By the time the new system is done, you'll have new priorities. Plan now. |\n| \"Users will migrate on their own\" | They won't. Provide tooling, documentation, and incentives — or do the migration yourself (the Churn Rule). |\n| \"We can maintain both systems indefinitely\" | Two systems doing the same thing is double the maintenance, testing, documentation, and onboarding cost. |\n\n## Red Flags\n\n- Deprecated systems with no replacement available\n- Deprecation announcements with no migration tooling or documentation\n- \"Soft\" deprecation that's been advisory for years with no progress\n- Zombie code with no owner and active consumers\n- New features added to a deprecated system (invest in the replacement instead)\n- Deprecation without measuring current usage\n- Removing code without verifying zero active consumers\n\n## Verification\n\nAfter completing a deprecation:\n\n- [ ] Replacement is production-proven and covers all critical use cases\n- [ ] Migration guide exists with concrete steps and examples\n- [ ] All active consumers have been migrated (verified by metrics\u002Flogs)\n- [ ] Old code, tests, documentation, and configuration are fully removed\n- [ ] No references to the deprecated system remain in the codebase\n- [ ] Deprecation notices are removed (they served their purpose)\n",{"name":5,"description":7},"main","7850740bd837adb32f0a109ab2af82482196c6f2","skills\u002Fdeprecation-and-migration",1,"https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills","https:\u002F\u002Fzturnsgo.com","https:\u002F\u002Fgithub.com\u002Fshengdabai","https:\u002F\u002Fzturnsgo.com\u002F","AI × education creator — producer, not consumer. Taught 6,000+ learners; shipping learning tools & daily essays with Claude Code, practicing @xiaolai's way 🥋","2026-11-01 21:28:23",{"source":8,"skillName":5,"commands":52,"prompt":62,"zipAvailable":63},[53,56,59],{"tool":54,"command":55},"npx","npx skills add shengdabai\u002FTony-Claude-Code-Skills --skill deprecation-and-migration",{"tool":57,"command":58},"bunx","bunx skills add shengdabai\u002FTony-Claude-Code-Skills --skill deprecation-and-migration",{"tool":60,"command":61},"pnpm","pnpm dlx skills add shengdabai\u002FTony-Claude-Code-Skills --skill deprecation-and-migration","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fdeprecation-and-migration\u002FSKILL.md",true,[],[66,75,83,91,99,107],{"skillNo":67,"name":68,"nameZh":6,"description":69,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":70,"sourceHtmlUrl":71,"categories":72,"keywords":73,"publishedAt":74},"01M73H7XKBHE1ETQDZT94MF9HH","seedance-prompt-en","Write effective prompts for Jimeng Seedance 2.0 multimodal AI video generation. Use when users want to create video prompts using text, images, videos, and audio inputs with the @ reference system. Covers camera movements, effects replication, video extension, editing, music beat-matching, e-commerce ads, short dramas, and educational content.","https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fseedance-prompt-en\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fseedance-prompt-en\u002FSKILL.md",[],[],"2026-11-11 15:11:14",{"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":79,"sourceHtmlUrl":80,"categories":81,"keywords":82,"publishedAt":74},"01M73GRE9998Q1DZWC71N41JWG","onepage-pdf","Convert an HTML page into a single continuous-page PDF (one tall page, no pagination breaks), preserving desktop layout, backgrounds and selectable text. Use when the user asks to turn an HTML file\u002Freport\u002Fproposal into a \"single-page PDF\", \"long PDF\", \"不分页 PDF\", \"单页 PDF\", \"长图式 PDF\", or complains that an HTML-to-PDF export breaks into pages or cuts content. Supports optional string redaction with leak verification.","https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fonepage-pdf\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fonepage-pdf\u002FSKILL.md",[],[],{"skillNo":84,"name":85,"nameZh":6,"description":86,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":87,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":74},"01M73GQG1KZDADVPV3MHAT1J5A","native-feel-cross-platform-desktop","Use when the user is designing, prototyping, or rewriting a desktop app that must run on multiple OSes (macOS + Windows, optionally Linux) AND feel indistinguishable from a native app to its users — fast launch, native windowing, native input handling, native materials. Trigger words include \"cross-platform desktop\", \"Electron alternative\", \"Tauri vs native\", \"WebView wrapper\", \"near-native performance\", \"Raycast architecture\", \"WebKit\u002FWebView2 quirks\", \"WKWebView\", \"system tray app\", \"global hotkey app\", \"launcher app\". Do NOT trigger this skill for pure web apps, pure mobile apps, or for greenfield projects that have no native-feel requirement.","https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fnative-feel-cross-platform-desktop\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fnative-feel-cross-platform-desktop\u002FSKILL.md",[],[],{"skillNo":92,"name":93,"nameZh":6,"description":94,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":95,"sourceHtmlUrl":96,"categories":97,"keywords":98,"publishedAt":74},"01M73G87PDNSMKG2FHWCYER6N8","gstack","Router for the gstack skill suite. (gstack)","https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fgstack\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fgstack\u002FSKILL.md",[],[],{"skillNo":100,"name":101,"nameZh":6,"description":102,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":103,"sourceHtmlUrl":104,"categories":105,"keywords":106,"publishedAt":74},"01M73G3EAQWKCM8DB8D0N0QSVG","fireworks-tech-graph","Use when the user wants to create any technical diagram - architecture, data flow, flowchart, sequence, agent\u002Fmemory, or concept map - and export as SVG+PNG. Trigger on: \"画图\" \"帮我画\" \"生成图\" \"做个图\" \"架构图\" \"流程图\" \"可视化一下\" \"出图\" \"generate diagram\" \"draw diagram\" \"visualize\" or any system\u002Fflow description the user wants illustrated.","https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Ffireworks-tech-graph\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Ffireworks-tech-graph\u002FSKILL.md",[],[],{"skillNo":108,"name":109,"nameZh":6,"description":110,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":111,"categories":112,"keywords":113,"publishedAt":74},"01M73G086AXAH9DW1H5G5N3CPB","dbs-video-extract","接收抖音、小红书、微信视频号等短视频链接或分享文案，查询作品／账号数据并提取语音文字稿，按作者和标题归档为 Markdown。用户希望完整解析短视频、取得数据或文字稿时使用；运行前检查 TikHub 与轻抖使用凭证，缺少时用新手能理解的方式引导购买和安全配置。","https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fdbs-video-extract\u002FSKILL.md",[],[]]