[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M70NFCZ449HRVKVCX5NTN5C7":3,"skill-same:01M70NFCZ449HRVKVCX5NTN5C7":79},{"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":44,"linkOnly":45,"markdownContent":46,"markdownBody":47,"frontMatter":48,"refName":49,"commitSha":50,"skillDirectory":51,"forksCount":52,"repositoryHtmlUrl":53,"repositoryHomepageUrl":54,"ownerHtmlUrl":55,"ownerBlogUrl":56,"ownerDescription":57,"updatedAt":58,"install":59,"resources":72},"01M70NFCZ449HRVKVCX5NTN5C7","tech-stack-detection",null,"Auto-detect project tech stacks (React, Vue, Express, Django, etc.). Recognize package managers and configuration patterns. Use when starting work on any project, analyzing dependencies, or providing framework-specific guidance.","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\u002Frsmdt-the-startup\u002Fplugins\u002Fteam\u002Fskills\u002Fcross-cutting\u002Ftech-stack-detection\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000009","前端开发","SCENARIO","使用场景",[24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43],"stack","tech","detection","tech stack detection","django","framework","vue","patterns","analyzing","work","react","Analyzing Dependencies","express","managers","framework-specific","when","auto","auto-detect","work on","project","2026-11-10 10:12:30",false,"---\nname: tech-stack-detection\ndescription: Auto-detect project tech stacks (React, Vue, Express, Django, etc.). Recognize package managers and configuration patterns. Use when starting work on any project, analyzing dependencies, or providing framework-specific guidance.\n---\n\n# Framework Detection\n\n## When to Use\n\n- Starting work on an unfamiliar project\n- Determining appropriate tooling and patterns for recommendations\n- Providing framework-specific guidance and best practices\n- Identifying package manager for dependency operations\n- Understanding project architecture before making changes\n\n## Detection Methodology\n\n### Step 1: Package Manager Detection\n\nCheck for package manager indicators in the project root:\n\n| File | Package Manager | Ecosystem |\n|------|-----------------|-----------|\n| `package-lock.json` | npm | Node.js |\n| `yarn.lock` | Yarn | Node.js |\n| `pnpm-lock.yaml` | pnpm | Node.js |\n| `bun.lockb` | Bun | Node.js |\n| `requirements.txt` | pip | Python |\n| `Pipfile.lock` | pipenv | Python |\n| `poetry.lock` | Poetry | Python |\n| `uv.lock` | uv | Python |\n| `Cargo.lock` | Cargo | Rust |\n| `go.sum` | Go Modules | Go |\n| `Gemfile.lock` | Bundler | Ruby |\n| `composer.lock` | Composer | PHP |\n\n### Step 2: Configuration File Analysis\n\nExamine root-level configuration files for framework indicators:\n\n1. **Read `package.json`** - Check `dependencies` and `devDependencies` for framework packages\n2. **Read `pyproject.toml`** - Check `[project.dependencies]` or `[tool.poetry.dependencies]`\n3. **Read framework-specific configs** - `next.config.js`, `vite.config.ts`, `angular.json`, etc.\n\n### Step 3: Directory Structure Patterns\n\nIdentify framework conventions:\n\n- `app\u002F` or `src\u002Fapp\u002F` - Next.js App Router, Angular\n- `pages\u002F` - Next.js Pages Router, Nuxt.js\n- `components\u002F` - React\u002FVue component-based architecture\n- `routes\u002F` - Remix, SvelteKit\n- `views\u002F` - Django, Rails, Laravel\n- `controllers\u002F` - MVC frameworks (Rails, Laravel, NestJS)\n\n### Step 4: Framework-Specific Patterns\n\nApply detection patterns from the framework signatures reference.\n\n## Detection Workflow\n\n```\nSTART\n  |\n  v\n[Check lock files] --> Identify package manager\n  |\n  v\n[Read manifest] --> package.json \u002F pyproject.toml \u002F Cargo.toml\n  |\n  v\n[Check dependencies] --> Match against known frameworks\n  |\n  v\n[Check config files] --> Framework-specific configuration\n  |\n  v\n[Verify directory structure] --> Confirm framework conventions\n  |\n  v\n[Output] --> Framework, version, package manager, key patterns\n```\n\n## Output Format\n\nWhen reporting detected framework, include:\n\n1. **Framework name and version** (if determinable)\n2. **Package manager** (with command examples)\n3. **Key configuration files** to be aware of\n4. **Directory conventions** the framework expects\n5. **Common commands** for development workflow\n\n## Best Practices\n\n- Always verify detection by checking multiple indicators (config + dependencies + structure)\n- Report confidence level when patterns are ambiguous\n- Note when multiple frameworks are present (e.g., Next.js + Tailwind + Prisma)\n- Check for meta-frameworks built on top of base frameworks\n- Consider monorepo patterns where different packages may use different frameworks\n\n## References\n\nSee `references\u002Fframework-signatures.md` for comprehensive detection patterns for all major frameworks.\n","# Framework Detection\n\n## When to Use\n\n- Starting work on an unfamiliar project\n- Determining appropriate tooling and patterns for recommendations\n- Providing framework-specific guidance and best practices\n- Identifying package manager for dependency operations\n- Understanding project architecture before making changes\n\n## Detection Methodology\n\n### Step 1: Package Manager Detection\n\nCheck for package manager indicators in the project root:\n\n| File | Package Manager | Ecosystem |\n|------|-----------------|-----------|\n| `package-lock.json` | npm | Node.js |\n| `yarn.lock` | Yarn | Node.js |\n| `pnpm-lock.yaml` | pnpm | Node.js |\n| `bun.lockb` | Bun | Node.js |\n| `requirements.txt` | pip | Python |\n| `Pipfile.lock` | pipenv | Python |\n| `poetry.lock` | Poetry | Python |\n| `uv.lock` | uv | Python |\n| `Cargo.lock` | Cargo | Rust |\n| `go.sum` | Go Modules | Go |\n| `Gemfile.lock` | Bundler | Ruby |\n| `composer.lock` | Composer | PHP |\n\n### Step 2: Configuration File Analysis\n\nExamine root-level configuration files for framework indicators:\n\n1. **Read `package.json`** - Check `dependencies` and `devDependencies` for framework packages\n2. **Read `pyproject.toml`** - Check `[project.dependencies]` or `[tool.poetry.dependencies]`\n3. **Read framework-specific configs** - `next.config.js`, `vite.config.ts`, `angular.json`, etc.\n\n### Step 3: Directory Structure Patterns\n\nIdentify framework conventions:\n\n- `app\u002F` or `src\u002Fapp\u002F` - Next.js App Router, Angular\n- `pages\u002F` - Next.js Pages Router, Nuxt.js\n- `components\u002F` - React\u002FVue component-based architecture\n- `routes\u002F` - Remix, SvelteKit\n- `views\u002F` - Django, Rails, Laravel\n- `controllers\u002F` - MVC frameworks (Rails, Laravel, NestJS)\n\n### Step 4: Framework-Specific Patterns\n\nApply detection patterns from the framework signatures reference.\n\n## Detection Workflow\n\n```\nSTART\n  |\n  v\n[Check lock files] --> Identify package manager\n  |\n  v\n[Read manifest] --> package.json \u002F pyproject.toml \u002F Cargo.toml\n  |\n  v\n[Check dependencies] --> Match against known frameworks\n  |\n  v\n[Check config files] --> Framework-specific configuration\n  |\n  v\n[Verify directory structure] --> Confirm framework conventions\n  |\n  v\n[Output] --> Framework, version, package manager, key patterns\n```\n\n## Output Format\n\nWhen reporting detected framework, include:\n\n1. **Framework name and version** (if determinable)\n2. **Package manager** (with command examples)\n3. **Key configuration files** to be aware of\n4. **Directory conventions** the framework expects\n5. **Common commands** for development workflow\n\n## Best Practices\n\n- Always verify detection by checking multiple indicators (config + dependencies + structure)\n- Report confidence level when patterns are ambiguous\n- Note when multiple frameworks are present (e.g., Next.js + Tailwind + Prisma)\n- Check for meta-frameworks built on top of base frameworks\n- Consider monorepo patterns where different packages may use different frameworks\n\n## References\n\nSee `references\u002Fframework-signatures.md` for comprehensive detection patterns for all major frameworks.\n",{"name":5,"description":7},"main","7850740bd837adb32f0a109ab2af82482196c6f2","skills\u002Frsmdt-the-startup\u002Fplugins\u002Fteam\u002Fskills\u002Fcross-cutting\u002Ftech-stack-detection",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":60,"prompt":70,"zipAvailable":71},[61,64,67],{"tool":62,"command":63},"npx","npx skills add shengdabai\u002FTony-Claude-Code-Skills --skill tech-stack-detection",{"tool":65,"command":66},"bunx","bunx skills add shengdabai\u002FTony-Claude-Code-Skills --skill tech-stack-detection",{"tool":68,"command":69},"pnpm","pnpm dlx skills add shengdabai\u002FTony-Claude-Code-Skills --skill tech-stack-detection","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Frsmdt-the-startup\u002Fplugins\u002Fteam\u002Fskills\u002Fcross-cutting\u002Ftech-stack-detection\u002FSKILL.md",true,[73],{"path":74,"resourceType":75,"resourceTypeDesc":76,"sizeBytes":77,"sourceHtmlUrl":78},"references\u002Fframework-signatures.md","REFERENCE","参考文档",17471,"https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Frsmdt-the-startup\u002Fplugins\u002Fteam\u002Fskills\u002Fcross-cutting\u002Ftech-stack-detection\u002Freferences\u002Fframework-signatures.md",[80,89,97,105,113,121],{"skillNo":81,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":84,"sourceHtmlUrl":85,"categories":86,"keywords":87,"publishedAt":88},"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":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":93,"sourceHtmlUrl":94,"categories":95,"keywords":96,"publishedAt":88},"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":98,"name":99,"nameZh":6,"description":100,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":101,"sourceHtmlUrl":102,"categories":103,"keywords":104,"publishedAt":88},"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":106,"name":107,"nameZh":6,"description":108,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":109,"sourceHtmlUrl":110,"categories":111,"keywords":112,"publishedAt":88},"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":114,"name":115,"nameZh":6,"description":116,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":117,"sourceHtmlUrl":118,"categories":119,"keywords":120,"publishedAt":88},"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":122,"name":123,"nameZh":6,"description":124,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":125,"categories":126,"keywords":127,"publishedAt":88},"01M73G086AXAH9DW1H5G5N3CPB","dbs-video-extract","接收抖音、小红书、微信视频号等短视频链接或分享文案，查询作品／账号数据并提取语音文字稿，按作者和标题归档为 Markdown。用户希望完整解析短视频、取得数据或文字稿时使用；运行前检查 TikHub 与轻抖使用凭证，缺少时用新手能理解的方式引导购买和安全配置。","https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fdbs-video-extract\u002FSKILL.md",[],[]]