[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6QJ51719KB7TG0VBRAS5TD0":3,"skill-same:01M6QJ51719KB7TG0VBRAS5TD0":70},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":22,"publishedAt":43,"linkOnly":44,"markdownContent":45,"markdownBody":46,"frontMatter":47,"refName":50,"commitSha":51,"skillDirectory":52,"forksCount":13,"repositoryHtmlUrl":53,"repositoryHomepageUrl":6,"ownerHtmlUrl":54,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":55,"install":56,"resources":69},"01M6QJ51719KB7TG0VBRAS5TD0","tech-stack-detection",null,"Systematically scans project config files to identify tech stack composition, version info, and engineering tooling. Should be used when the user needs to understand what technologies a project uses — onboarding, evaluating upgrade feasibility, or troubleshooting build issues. Distinguished from explore which investigates project structure and problems, this skill focuses on identifying technology stacks.","ImaginerLabs\u002Fskill-manager","ImaginerLabs","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F214277308?v=4","01M6QGGDPNF15RMMT1RCFDH9FN","01M6QGGDTH5BY64DQ123NR8M33",0,"MIT","https:\u002F\u002Fgithub.com\u002FImaginerLabs\u002Fskill-manager\u002Fblob\u002Fmain\u002Fskills\u002Fcoding\u002Ftech-stack-detection\u002FSKILL.md",[17],{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000009","前端开发","SCENARIO","使用场景",[23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42],"tech stack detection","tech","detection","stack","files","which","project","technology","structure","upgrade","info","build","project structure","version","coding","explore","Composition","issues","feasibility","config","2026-11-10 10:12:30",false,"---\nname: tech-stack-detection\ndescription: >-\n  Systematically scans project config files to identify tech stack composition, version info, and engineering tooling.\n  Should be used when the user needs to understand what technologies a project uses — onboarding, evaluating\n  upgrade feasibility, or troubleshooting build issues.\n  Distinguished from explore which investigates project structure and problems, this skill focuses on\n  identifying technology stacks.\ncategory: coding\nboundary:\n  vs_explore: \"explore investigates project structure and problems, this skill focuses on identifying technology stacks\"\n---\n\n# Frontend Project Tech Stack Detection\n\n## Core Capability\n\nGiven a project path, systematically scan config files in a predefined order, identify tech stack composition, and output a clear tech stack report.\n\n## When to Use\n\n- Onboarding to a new project, quickly understand tech choices\n- Evaluating project upgrade\u002Fmigration feasibility\n- Aligning team understanding of project tech stack\n- Understanding toolchain config before troubleshooting build\u002Fruntime issues\n\n---\n\n## File Reading Order\n\nRead files in this priority order. Skip files that don't exist.\n\n### Layer 1: Project Basics\n\n| Order | File                                                 | Extract                               |\n| ----- | ---------------------------------------------------- | ------------------------------------- |\n| 1     | `package.json`                                       | Framework, core dependencies, scripts |\n| 2     | `package-lock.json` \u002F `yarn.lock` \u002F `pnpm-lock.yaml` | Package manager type                  |\n\n### Layer 2: Build Tool Config\n\n| Order | File                                      | Extract                    |\n| ----- | ----------------------------------------- | -------------------------- |\n| 3     | `vite.config.ts` \u002F `vite.config.js`       | Vite plugins, alias, proxy |\n| 4     | `webpack.config.js` \u002F `webpack.config.ts` | Webpack loader, plugin     |\n| 5     | `next.config.js` \u002F `next.config.ts`       | Next.js SSR\u002FSSG mode       |\n| 6     | `craco.config.js` \u002F `react-scripts`       | CRA project identifier     |\n| 7     | `rollup.config.js`                        | Rollup config              |\n\n### Layer 3: Language & Type Config\n\n| Order | File                                   | Extract                                  |\n| ----- | -------------------------------------- | ---------------------------------------- |\n| 8     | `tsconfig.json` \u002F `tsconfig.base.json` | TypeScript, compile target, path aliases |\n| 9     | `babel.config.js` \u002F `.babelrc`         | Babel presets, plugins                   |\n\n### Layer 4: Code Standards Config\n\n| Order | File                                 | Extract                |\n| ----- | ------------------------------------ | ---------------------- |\n| 10    | `.eslintrc*` \u002F `eslint.config.js`    | ESLint rule set        |\n| 11    | `.prettierrc` \u002F `prettier.config.js` | Code formatting config |\n| 12    | `stylelint.config.js`                | CSS lint rules         |\n\n### Layer 5: Git & Commit Standards\n\n| Order | File                   | Extract              |\n| ----- | ---------------------- | -------------------- |\n| 13    | `.husky\u002F` directory    | Git Hooks config     |\n| 14    | `commitlint.config.js` | Commit message rules |\n\n### Layer 6: Environment & Deployment\n\n| Order | File                                | Extract                              |\n| ----- | ----------------------------------- | ------------------------------------ |\n| 15    | `.env*` files                       | Environment variables, API addresses |\n| 16    | `Dockerfile` \u002F `docker-compose.yml` | Containerized deployment             |\n| 17    | `nginx.conf`                        | Deployment server config             |\n\n---\n\n## Tech Stack Identification Rules\n\n### Framework\n\n| Key package     | Conclusion                                  |\n| --------------- | ------------------------------------------- |\n| `react`         | React project                               |\n| `vue`           | Vue project (check version for Vue2 \u002F Vue3) |\n| `next`          | Next.js (React SSR\u002FSSG)                     |\n| `nuxt`          | Nuxt.js (Vue SSR\u002FSSG)                       |\n| `@angular\u002Fcore` | Angular project                             |\n| `@tarojs\u002Ftaro`  | Taro mini-program project                   |\n| `remix`         | Remix (React full-stack)                    |\n\n### Build Tool\n\n| Key package\u002Ffile        | Conclusion               |\n| ----------------------- | ------------------------ |\n| `vite` in devDeps       | Vite                     |\n| `webpack` in devDeps    | Webpack                  |\n| `react-scripts` in deps | CRA                      |\n| `@vue\u002Fcli-service`      | Vue CLI                  |\n| `turbo`                 | Turborepo (Monorepo)     |\n| `rsbuild`               | Rspack (Rust build tool) |\n\n### State Management\n\n| Key package                  | Conclusion              |\n| ---------------------------- | ----------------------- |\n| `redux` \u002F `@reduxjs\u002Ftoolkit` | Redux                   |\n| `zustand`                    | Zustand                 |\n| `mobx`                       | MobX                    |\n| `pinia`                      | Pinia (Vue)             |\n| `jotai` \u002F `recoil`           | Atomic state management |\n\n### CSS Solution\n\n| Key package                               | Conclusion           |\n| ----------------------------------------- | -------------------- |\n| `tailwindcss`                             | Tailwind CSS         |\n| `styled-components` \u002F `@emotion\u002Freact`    | CSS-in-JS            |\n| `sass` \u002F `less`                           | Preprocessor         |\n| `@mui\u002Fmaterial` \u002F `antd` \u002F `@arco-design` | UI component library |\n\n### Testing Framework\n\n| Key package              | Conclusion             |\n| ------------------------ | ---------------------- |\n| `jest` \u002F `vitest`        | Unit testing framework |\n| `@testing-library\u002Freact` | React testing utility  |\n| `cypress` \u002F `playwright` | E2E testing framework  |\n\n---\n\n## Output Format\n\n```markdown\n## Tech Stack Detection Report: `[project name\u002Fpath]`\n\n### Overview\n\n- **Project type**: Web app \u002F Mini-program \u002F SSR app \u002F Monorepo\n- **Main framework**: [framework name] [version]\n- **Build tool**: [tool name] [version]\n- **Language**: TypeScript \u002F JavaScript\n\n### Core Tech Stack\n\n| Category          | Choice                     | Version | Notes  |\n| ----------------- | -------------------------- | ------- | ------ |\n| Framework         | React \u002F Vue \u002F ...          | x.x.x   |        |\n| Build tool        | Vite \u002F Webpack \u002F ...       | x.x.x   |        |\n| Language          | TypeScript \u002F JavaScript    | x.x     |        |\n| Package manager   | pnpm \u002F yarn \u002F npm          | x.x.x   |        |\n| State management  | Zustand \u002F Redux \u002F ...      | x.x.x   | If any |\n| CSS solution      | Tailwind \u002F CSS-in-JS \u002F ... | —       |        |\n| UI library        | Ant Design \u002F MUI \u002F ...     | x.x.x   | If any |\n| Testing framework | Jest \u002F Vitest \u002F ...        | x.x.x   | If any |\n\n### Engineering Config\n\n| Tool       | Status                            | Notes              |\n| ---------- | --------------------------------- | ------------------ |\n| ESLint     | ✅ Configured \u002F ❌ Not configured | Using xxx rule set |\n| Prettier   | ✅ Configured \u002F ❌ Not configured | —                  |\n| Husky      | ✅ Configured \u002F ❌ Not configured | —                  |\n| TypeScript | ✅ Configured \u002F ❌ Not configured | target: ESNext     |\n\n### Key Scripts\n\n| Command         | Description      |\n| --------------- | ---------------- |\n| `npm run dev`   | Start dev server |\n| `npm run build` | Production build |\n\n### Detection Basis\n\n**Read**: package.json ✅, vite.config.ts ✅, tsconfig.json ✅\n\n**Not found**: webpack.config.js ⚠️, .eslintrc ⚠️\n\n### Next Steps\n\n1. [Improvement suggestions based on detection results]\n2. [Tech stack upgrade or optimization directions]\n```\n\n---\n\n## Output Principles\n\n- **Conclusions first** — Core tech stack table before details\n- **Versions explicit** — Extract exact version numbers from package.json when possible\n- **Missing means skip** — Don't error on missing files, don't guess, just skip\n- **Actionable suggestions** — Include specific next-step recommendations\n","# Frontend Project Tech Stack Detection\n\n## Core Capability\n\nGiven a project path, systematically scan config files in a predefined order, identify tech stack composition, and output a clear tech stack report.\n\n## When to Use\n\n- Onboarding to a new project, quickly understand tech choices\n- Evaluating project upgrade\u002Fmigration feasibility\n- Aligning team understanding of project tech stack\n- Understanding toolchain config before troubleshooting build\u002Fruntime issues\n\n---\n\n## File Reading Order\n\nRead files in this priority order. Skip files that don't exist.\n\n### Layer 1: Project Basics\n\n| Order | File                                                 | Extract                               |\n| ----- | ---------------------------------------------------- | ------------------------------------- |\n| 1     | `package.json`                                       | Framework, core dependencies, scripts |\n| 2     | `package-lock.json` \u002F `yarn.lock` \u002F `pnpm-lock.yaml` | Package manager type                  |\n\n### Layer 2: Build Tool Config\n\n| Order | File                                      | Extract                    |\n| ----- | ----------------------------------------- | -------------------------- |\n| 3     | `vite.config.ts` \u002F `vite.config.js`       | Vite plugins, alias, proxy |\n| 4     | `webpack.config.js` \u002F `webpack.config.ts` | Webpack loader, plugin     |\n| 5     | `next.config.js` \u002F `next.config.ts`       | Next.js SSR\u002FSSG mode       |\n| 6     | `craco.config.js` \u002F `react-scripts`       | CRA project identifier     |\n| 7     | `rollup.config.js`                        | Rollup config              |\n\n### Layer 3: Language & Type Config\n\n| Order | File                                   | Extract                                  |\n| ----- | -------------------------------------- | ---------------------------------------- |\n| 8     | `tsconfig.json` \u002F `tsconfig.base.json` | TypeScript, compile target, path aliases |\n| 9     | `babel.config.js` \u002F `.babelrc`         | Babel presets, plugins                   |\n\n### Layer 4: Code Standards Config\n\n| Order | File                                 | Extract                |\n| ----- | ------------------------------------ | ---------------------- |\n| 10    | `.eslintrc*` \u002F `eslint.config.js`    | ESLint rule set        |\n| 11    | `.prettierrc` \u002F `prettier.config.js` | Code formatting config |\n| 12    | `stylelint.config.js`                | CSS lint rules         |\n\n### Layer 5: Git & Commit Standards\n\n| Order | File                   | Extract              |\n| ----- | ---------------------- | -------------------- |\n| 13    | `.husky\u002F` directory    | Git Hooks config     |\n| 14    | `commitlint.config.js` | Commit message rules |\n\n### Layer 6: Environment & Deployment\n\n| Order | File                                | Extract                              |\n| ----- | ----------------------------------- | ------------------------------------ |\n| 15    | `.env*` files                       | Environment variables, API addresses |\n| 16    | `Dockerfile` \u002F `docker-compose.yml` | Containerized deployment             |\n| 17    | `nginx.conf`                        | Deployment server config             |\n\n---\n\n## Tech Stack Identification Rules\n\n### Framework\n\n| Key package     | Conclusion                                  |\n| --------------- | ------------------------------------------- |\n| `react`         | React project                               |\n| `vue`           | Vue project (check version for Vue2 \u002F Vue3) |\n| `next`          | Next.js (React SSR\u002FSSG)                     |\n| `nuxt`          | Nuxt.js (Vue SSR\u002FSSG)                       |\n| `@angular\u002Fcore` | Angular project                             |\n| `@tarojs\u002Ftaro`  | Taro mini-program project                   |\n| `remix`         | Remix (React full-stack)                    |\n\n### Build Tool\n\n| Key package\u002Ffile        | Conclusion               |\n| ----------------------- | ------------------------ |\n| `vite` in devDeps       | Vite                     |\n| `webpack` in devDeps    | Webpack                  |\n| `react-scripts` in deps | CRA                      |\n| `@vue\u002Fcli-service`      | Vue CLI                  |\n| `turbo`                 | Turborepo (Monorepo)     |\n| `rsbuild`               | Rspack (Rust build tool) |\n\n### State Management\n\n| Key package                  | Conclusion              |\n| ---------------------------- | ----------------------- |\n| `redux` \u002F `@reduxjs\u002Ftoolkit` | Redux                   |\n| `zustand`                    | Zustand                 |\n| `mobx`                       | MobX                    |\n| `pinia`                      | Pinia (Vue)             |\n| `jotai` \u002F `recoil`           | Atomic state management |\n\n### CSS Solution\n\n| Key package                               | Conclusion           |\n| ----------------------------------------- | -------------------- |\n| `tailwindcss`                             | Tailwind CSS         |\n| `styled-components` \u002F `@emotion\u002Freact`    | CSS-in-JS            |\n| `sass` \u002F `less`                           | Preprocessor         |\n| `@mui\u002Fmaterial` \u002F `antd` \u002F `@arco-design` | UI component library |\n\n### Testing Framework\n\n| Key package              | Conclusion             |\n| ------------------------ | ---------------------- |\n| `jest` \u002F `vitest`        | Unit testing framework |\n| `@testing-library\u002Freact` | React testing utility  |\n| `cypress` \u002F `playwright` | E2E testing framework  |\n\n---\n\n## Output Format\n\n```markdown\n## Tech Stack Detection Report: `[project name\u002Fpath]`\n\n### Overview\n\n- **Project type**: Web app \u002F Mini-program \u002F SSR app \u002F Monorepo\n- **Main framework**: [framework name] [version]\n- **Build tool**: [tool name] [version]\n- **Language**: TypeScript \u002F JavaScript\n\n### Core Tech Stack\n\n| Category          | Choice                     | Version | Notes  |\n| ----------------- | -------------------------- | ------- | ------ |\n| Framework         | React \u002F Vue \u002F ...          | x.x.x   |        |\n| Build tool        | Vite \u002F Webpack \u002F ...       | x.x.x   |        |\n| Language          | TypeScript \u002F JavaScript    | x.x     |        |\n| Package manager   | pnpm \u002F yarn \u002F npm          | x.x.x   |        |\n| State management  | Zustand \u002F Redux \u002F ...      | x.x.x   | If any |\n| CSS solution      | Tailwind \u002F CSS-in-JS \u002F ... | —       |        |\n| UI library        | Ant Design \u002F MUI \u002F ...     | x.x.x   | If any |\n| Testing framework | Jest \u002F Vitest \u002F ...        | x.x.x   | If any |\n\n### Engineering Config\n\n| Tool       | Status                            | Notes              |\n| ---------- | --------------------------------- | ------------------ |\n| ESLint     | ✅ Configured \u002F ❌ Not configured | Using xxx rule set |\n| Prettier   | ✅ Configured \u002F ❌ Not configured | —                  |\n| Husky      | ✅ Configured \u002F ❌ Not configured | —                  |\n| TypeScript | ✅ Configured \u002F ❌ Not configured | target: ESNext     |\n\n### Key Scripts\n\n| Command         | Description      |\n| --------------- | ---------------- |\n| `npm run dev`   | Start dev server |\n| `npm run build` | Production build |\n\n### Detection Basis\n\n**Read**: package.json ✅, vite.config.ts ✅, tsconfig.json ✅\n\n**Not found**: webpack.config.js ⚠️, .eslintrc ⚠️\n\n### Next Steps\n\n1. [Improvement suggestions based on detection results]\n2. [Tech stack upgrade or optimization directions]\n```\n\n---\n\n## Output Principles\n\n- **Conclusions first** — Core tech stack table before details\n- **Versions explicit** — Extract exact version numbers from package.json when possible\n- **Missing means skip** — Don't error on missing files, don't guess, just skip\n- **Actionable suggestions** — Include specific next-step recommendations\n",{"name":5,"boundary":48,"category":37,"description":7},{"vs_explore":49},"explore investigates project structure and problems, this skill focuses on identifying technology stacks","main","b9a52d8e27455bdad953d64928696d028223ea1b","skills\u002Fcoding\u002Ftech-stack-detection","https:\u002F\u002Fgithub.com\u002FImaginerLabs\u002Fskill-manager","https:\u002F\u002Fgithub.com\u002FImaginerLabs","2026-04-18 16:27:13",{"source":8,"skillName":5,"commands":57,"prompt":67,"zipAvailable":68},[58,61,64],{"tool":59,"command":60},"npx","npx skills add ImaginerLabs\u002Fskill-manager --skill tech-stack-detection",{"tool":62,"command":63},"bunx","bunx skills add ImaginerLabs\u002Fskill-manager --skill tech-stack-detection",{"tool":65,"command":66},"pnpm","pnpm dlx skills add ImaginerLabs\u002Fskill-manager --skill tech-stack-detection","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FImaginerLabs\u002Fskill-manager\u002Fblob\u002Fmain\u002Fskills\u002Fcoding\u002Ftech-stack-detection\u002FSKILL.md",true,[],[71,104,124,152,188,213],{"skillNo":72,"name":73,"nameZh":6,"description":74,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":75,"categories":76,"keywords":85,"publishedAt":43},"01M6QJCB2SD5KHC41ZDQC0GA1T","meeting-minutes","Generate concise, actionable meeting minutes for internal meetings. Includes metadata, attendees, agenda, decisions, action items (owner + due date), and follow-up steps.","https:\u002F\u002Fgithub.com\u002FImaginerLabs\u002Fskill-manager\u002Fblob\u002Fmain\u002Fskills\u002Fwriting\u002Fmeeting-minutes\u002FSKILL.md",[77,80],{"categoryNo":78,"categoryName":79,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000023","Skill与智能体开发",{"categoryNo":81,"categoryName":82,"taxonomyType":83,"taxonomyTypeDesc":84},"01JBSEEDCAT000000000000034","行政与办公人员","PROFESSION","适用职业",[86,87,88,89,90,91,92,93,94,95,73,50,96,97,98,99,100,101,102,103],"meeting minutes","meeting","minutes","writing","github","copilot","generate","decisions","meetings","up","agenda","actionable","concise","follow-up","tree","true","action","for",{"skillNo":105,"name":106,"nameZh":6,"description":107,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":108,"categories":109,"keywords":110,"publishedAt":43},"01M6QJC71RRGTGNNFEHJG6S20G","documentation-writer","Diátaxis Documentation Expert. An expert technical writer specializing in creating high-quality software documentation, guided by the principles and structure of the Diátaxis technical documentation authoring framework.","https:\u002F\u002Fgithub.com\u002FImaginerLabs\u002Fskill-manager\u002Fblob\u002Fmain\u002Fskills\u002Fwriting\u002Fdocumentation-writer\u002FSKILL.md",[],[111,112,113,89,90,91,114,115,116,117,118,119,50,31,120,121,122,100,101,123],"documentation","documentation writer","writer","https","quality","technical","technical writer","expert","documentation expert","authoring","software","principles","high",{"skillNo":125,"name":126,"nameZh":6,"description":127,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":128,"categories":129,"keywords":137,"publishedAt":43},"01M6QJC0V3C7C4R9768J1AJYWY","doc-coauthoring","Guide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks.","https:\u002F\u002Fgithub.com\u002FImaginerLabs\u002Fskill-manager\u002Fblob\u002Fmain\u002Fskills\u002Fwriting\u002Fdoc-coauthoring\u002FSKILL.md",[130,133,134],{"categoryNo":131,"categoryName":132,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000018","写作与文案",{"categoryNo":78,"categoryName":79,"taxonomyType":20,"taxonomyTypeDesc":21},{"categoryNo":135,"categoryName":136,"taxonomyType":83,"taxonomyTypeDesc":84},"01JBSEEDCAT000000000000036","内容创作者",[138,139,89,140,141,111,142,143,144,145,146,147,50,148,149,120,150,151,100,103],"doc coauthoring","doc","workflow","official","tasks","decision","write","context","proposals","guide","refine","iteration","trigger","co",{"skillNo":153,"name":154,"nameZh":6,"description":155,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":156,"categories":157,"keywords":168,"publishedAt":43},"01M6QJBJ0YPVEWGEXZH3PJRRTT","code-review-workflow","Executes comprehensive 4-phase code review: basic review, quality check, bundle analysis, and test coverage. Should be used when the user mentions comprehensive code review, checking code quality, or reviewing staged changes with multi-phase analysis. This is the comprehensive review workflow, distinct from focused skills like frontend-code-review, staged-code-review, or code-change-test-designer.","https:\u002F\u002Fgithub.com\u002FImaginerLabs\u002Fskill-manager\u002Fblob\u002Fmain\u002Fskills\u002Ftesting\u002Fcode-review-workflow\u002FSKILL.md",[158,161,164,165],{"categoryNo":159,"categoryName":160,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000007","代码审查",{"categoryNo":162,"categoryName":163,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000008","测试与质量",{"categoryNo":78,"categoryName":79,"taxonomyType":20,"taxonomyTypeDesc":21},{"categoryNo":166,"categoryName":167,"taxonomyType":83,"taxonomyTypeDesc":84},"01JBSEEDCAT000000000000030","开发工程师",[169,170,140,171,172,173,174,175,176,177,178,179,180,181,182,183,184,185,186,187],"code review","review","code","code review workflow","testing","frontend","test","change","code quality","code-review","analysis","check","coverage","quality check","basic","multi","comprehensive code review","with","phase",{"skillNo":189,"name":190,"nameZh":6,"description":191,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":192,"categories":193,"keywords":203,"publishedAt":43},"01M6QJB7XNHV3VEEQF4W7FMWF6","code-change-test-designer","Analyzes code changes and designs comprehensive test cases. Reads diffs, summarizes capability changes, and designs test cases covering main flows and edge cases. Should be used when the user mentions test coverage, designing tests for code changes, or analyzing diff\u002Fcommit for testing purposes. Distinguished from code-review-workflow which provides comprehensive review, this skill focuses on test case design for code changes.","https:\u002F\u002Fgithub.com\u002FImaginerLabs\u002Fskill-manager\u002Fblob\u002Fmain\u002Fskills\u002Ftesting\u002Fcode-change-test-designer\u002FSKILL.md",[194,195,198,199,200],{"categoryNo":162,"categoryName":163,"taxonomyType":20,"taxonomyTypeDesc":21},{"categoryNo":196,"categoryName":197,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000015","视觉设计",{"categoryNo":78,"categoryName":79,"taxonomyType":20,"taxonomyTypeDesc":21},{"categoryNo":166,"categoryName":167,"taxonomyType":83,"taxonomyTypeDesc":84},{"categoryNo":201,"categoryName":202,"taxonomyType":83,"taxonomyTypeDesc":84},"01JBSEEDCAT000000000000032","设计师",[175,176,171,204,205,173,206,207,140,208,178,209,181,210,50,211,212,28,103,187],"designer","code change test designer","design","diffs","commit","edge","diff","tests","flows",{"skillNo":214,"name":215,"nameZh":6,"description":216,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":217,"categories":218,"keywords":220,"publishedAt":43},"01M6QJB195WD7DCJWDMKWKB29S","skill-creator","Create new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.","https:\u002F\u002Fgithub.com\u002FImaginerLabs\u002Fskill-manager\u002Fblob\u002Fmain\u002Fskills\u002Fmeta-skills\u002Fskill-creator\u002FSKILL.md",[219],{"categoryNo":78,"categoryName":79,"taxonomyType":20,"taxonomyTypeDesc":21},[221,222,223,224,141,225,226,227,228,229,179,230,231,232,50,233,234,100,103,215],"skill creator","creator","performance","run evals","variance analysis","create","run","benchmark","Meta","improve","edit","evals","optimize","existing skill"]