[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M70GX250J170DSEVHZ8RSVTP":3,"skill-same:01M70GX250J170DSEVHZ8RSVTP":84},{"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":28,"publishedAt":49,"linkOnly":50,"markdownContent":51,"markdownBody":52,"frontMatter":53,"refName":54,"commitSha":55,"skillDirectory":56,"forksCount":57,"repositoryHtmlUrl":58,"repositoryHomepageUrl":59,"ownerHtmlUrl":60,"ownerBlogUrl":61,"ownerDescription":62,"updatedAt":63,"install":64,"resources":77},"01M70GX250J170DSEVHZ8RSVTP","pattern-detection",null,"Identify existing codebase patterns (naming conventions, architectural patterns, testing patterns) to maintain consistency. Use when generating code, reviewing changes, or understanding established practices. Ensures new code aligns with project conventions.","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\u002F_collections\u002Fplugins\u002Fteam\u002Fskills\u002Fcross-cutting\u002Fpattern-detection\u002FSKILL.md",[18,23],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000008","测试与质量","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44,45,46,47,48],"pattern detection","detection","pattern","naming conventions","conventions","codebase","naming","changes","with","Existing","use","consistency","patterns","project conventions","code","when","maintain","testing","project","testing patterns","2026-11-10 10:12:30",false,"---\nname: pattern-detection\ndescription: Identify existing codebase patterns (naming conventions, architectural patterns, testing patterns) to maintain consistency. Use when generating code, reviewing changes, or understanding established practices. Ensures new code aligns with project conventions.\n---\n\n# Pattern Recognition\n\n## When to Use\n\n- Before writing new code to ensure consistency with existing patterns\n- During code review to verify alignment with established conventions\n- When onboarding to understand project-specific practices\n- Before refactoring to preserve intentional design decisions\n\n## Core Methodology\n\n### Pattern Discovery Process\n\n1. **Survey representative files**: Read 3-5 files of the type you will create or modify\n2. **Identify recurring structures**: Note repeated patterns in naming, organization, imports\n3. **Verify intentionality**: Check if patterns are documented or consistently applied\n4. **Apply discovered patterns**: Use the same conventions in new code\n\n### Priority Order for Pattern Sources\n\n1. **Existing code in the same module\u002Ffeature** - Most authoritative\n2. **Project style guides or CONTRIBUTING.md** - Explicit documentation\n3. **Test files** - Often reveal expected patterns and naming\n4. **Similar files in adjacent modules** - Fallback when no direct examples exist\n\n## Naming Convention Recognition\n\n### File Naming Patterns\n\nDetect and follow the project's file naming style:\n\n| Pattern | Example | Common In |\n|---------|---------|-----------|\n| kebab-case | `user-profile.ts` | Node.js, Vue, Angular |\n| PascalCase | `UserProfile.tsx` | React components |\n| snake_case | `user_profile.py` | Python |\n| camelCase | `userProfile.js` | Legacy JS, Java |\n\n### Function\u002FMethod Naming\n\nIdentify the project's verb conventions:\n\n- **get** vs **fetch** vs **retrieve** for data access\n- **create** vs **add** vs **new** for creation\n- **update** vs **set** vs **modify** for mutations\n- **delete** vs **remove** vs **destroy** for deletion\n- **is\u002Fhas\u002Fcan\u002Fshould** prefixes for booleans\n\n### Variable Naming\n\nDetect pluralization and specificity patterns:\n\n- Singular vs plural for collections (`user` vs `users` vs `userList`)\n- Hungarian notation presence (`strName`, `iCount`)\n- Private member indicators (`_private`, `#private`, `mPrivate`)\n\n## Architectural Pattern Recognition\n\n### Layer Identification\n\nRecognize how the codebase separates concerns:\n\n```\nCOMMON LAYERING PATTERNS:\n- MVC: controllers\u002F, models\u002F, views\u002F\n- Clean Architecture: domain\u002F, application\u002F, infrastructure\u002F\n- Hexagonal: core\u002F, adapters\u002F, ports\u002F\n- Feature-based: features\u002Fauth\u002F, features\u002Fbilling\u002F\n- Type-based: components\u002F, services\u002F, utils\u002F\n```\n\n### Dependency Direction\n\nIdentify import patterns that reveal architecture:\n\n- Which modules import from which (dependency flow)\n- Shared vs feature-specific code boundaries\n- Framework code vs application code separation\n\n### State Management Patterns\n\nRecognize how state flows through the application:\n\n- Global stores (Redux, Vuex, MobX patterns)\n- React Context usage patterns\n- Service layer patterns for backend state\n- Event-driven vs request-response patterns\n\n## Testing Pattern Recognition\n\n### Test Organization\n\nIdentify how tests are structured:\n\n| Pattern | Structure | Example |\n|---------|-----------|---------|\n| Co-located | `src\u002Fuser.ts`, `src\u002Fuser.test.ts` | Common in modern JS\u002FTS |\n| Mirror tree | `src\u002Fuser.ts`, `tests\u002Fsrc\u002Fuser.test.ts` | Traditional, Java-style |\n| Feature-based | `src\u002Fuser\u002F`, `src\u002Fuser\u002F__tests__\u002F` | React, organized features |\n\n### Test Naming Conventions\n\nDetect the project's test description style:\n\n- **BDD style**: `it('should return user when found')`\n- **Descriptive**: `test('getUser returns user when id exists')`\n- **Function-focused**: `test_get_user_returns_user_when_found`\n\n### Test Structure Patterns\n\nRecognize Arrange-Act-Assert or Given-When-Then patterns:\n\n- Setup block conventions (beforeEach, fixtures, factories)\n- Assertion style (expect vs assert vs should)\n- Mock\u002Fstub patterns (jest.mock vs sinon vs manual)\n\n## Code Organization Patterns\n\n### Import Organization\n\nIdentify import ordering and grouping:\n\n```\nCOMMON IMPORT PATTERNS:\n1. External packages first, internal modules second\n2. Grouped by type (React, libraries, local)\n3. Alphabetized within groups\n4. Absolute imports vs relative imports preference\n```\n\n### Export Patterns\n\nRecognize module boundary conventions:\n\n- Default exports vs named exports preference\n- Barrel files (index.ts re-exports) presence\n- Public API definition patterns\n\n### Comment and Documentation Patterns\n\nIdentify documentation conventions:\n\n- JSDoc\u002FTSDoc presence and style\n- Inline comment frequency and style\n- README conventions per module\u002Ffeature\n\n## Best Practices\n\n- **Follow existing patterns even if imperfect** - Consistency trumps personal preference\n- **Document deviations explicitly** - When breaking patterns intentionally, explain why\n- **Pattern changes require migration** - Dont introduce new patterns without updating existing code\n- **Check tests for patterns too** - Test code often reveals expected conventions\n- **Prefer explicit over implicit** - When patterns are unclear, ask or document assumptions\n\n## Anti-Patterns to Avoid\n\n- Mixing naming conventions in the same codebase\n- Introducing new architectural patterns without team consensus\n- Assuming patterns from other projects apply here\n- Ignoring test patterns when writing implementation\n- Creating \"special\" files that dont follow established structure\n\n## References\n\n- `examples\u002Fcommon-patterns.md` - Concrete examples of pattern recognition in action\n","# Pattern Recognition\n\n## When to Use\n\n- Before writing new code to ensure consistency with existing patterns\n- During code review to verify alignment with established conventions\n- When onboarding to understand project-specific practices\n- Before refactoring to preserve intentional design decisions\n\n## Core Methodology\n\n### Pattern Discovery Process\n\n1. **Survey representative files**: Read 3-5 files of the type you will create or modify\n2. **Identify recurring structures**: Note repeated patterns in naming, organization, imports\n3. **Verify intentionality**: Check if patterns are documented or consistently applied\n4. **Apply discovered patterns**: Use the same conventions in new code\n\n### Priority Order for Pattern Sources\n\n1. **Existing code in the same module\u002Ffeature** - Most authoritative\n2. **Project style guides or CONTRIBUTING.md** - Explicit documentation\n3. **Test files** - Often reveal expected patterns and naming\n4. **Similar files in adjacent modules** - Fallback when no direct examples exist\n\n## Naming Convention Recognition\n\n### File Naming Patterns\n\nDetect and follow the project's file naming style:\n\n| Pattern | Example | Common In |\n|---------|---------|-----------|\n| kebab-case | `user-profile.ts` | Node.js, Vue, Angular |\n| PascalCase | `UserProfile.tsx` | React components |\n| snake_case | `user_profile.py` | Python |\n| camelCase | `userProfile.js` | Legacy JS, Java |\n\n### Function\u002FMethod Naming\n\nIdentify the project's verb conventions:\n\n- **get** vs **fetch** vs **retrieve** for data access\n- **create** vs **add** vs **new** for creation\n- **update** vs **set** vs **modify** for mutations\n- **delete** vs **remove** vs **destroy** for deletion\n- **is\u002Fhas\u002Fcan\u002Fshould** prefixes for booleans\n\n### Variable Naming\n\nDetect pluralization and specificity patterns:\n\n- Singular vs plural for collections (`user` vs `users` vs `userList`)\n- Hungarian notation presence (`strName`, `iCount`)\n- Private member indicators (`_private`, `#private`, `mPrivate`)\n\n## Architectural Pattern Recognition\n\n### Layer Identification\n\nRecognize how the codebase separates concerns:\n\n```\nCOMMON LAYERING PATTERNS:\n- MVC: controllers\u002F, models\u002F, views\u002F\n- Clean Architecture: domain\u002F, application\u002F, infrastructure\u002F\n- Hexagonal: core\u002F, adapters\u002F, ports\u002F\n- Feature-based: features\u002Fauth\u002F, features\u002Fbilling\u002F\n- Type-based: components\u002F, services\u002F, utils\u002F\n```\n\n### Dependency Direction\n\nIdentify import patterns that reveal architecture:\n\n- Which modules import from which (dependency flow)\n- Shared vs feature-specific code boundaries\n- Framework code vs application code separation\n\n### State Management Patterns\n\nRecognize how state flows through the application:\n\n- Global stores (Redux, Vuex, MobX patterns)\n- React Context usage patterns\n- Service layer patterns for backend state\n- Event-driven vs request-response patterns\n\n## Testing Pattern Recognition\n\n### Test Organization\n\nIdentify how tests are structured:\n\n| Pattern | Structure | Example |\n|---------|-----------|---------|\n| Co-located | `src\u002Fuser.ts`, `src\u002Fuser.test.ts` | Common in modern JS\u002FTS |\n| Mirror tree | `src\u002Fuser.ts`, `tests\u002Fsrc\u002Fuser.test.ts` | Traditional, Java-style |\n| Feature-based | `src\u002Fuser\u002F`, `src\u002Fuser\u002F__tests__\u002F` | React, organized features |\n\n### Test Naming Conventions\n\nDetect the project's test description style:\n\n- **BDD style**: `it('should return user when found')`\n- **Descriptive**: `test('getUser returns user when id exists')`\n- **Function-focused**: `test_get_user_returns_user_when_found`\n\n### Test Structure Patterns\n\nRecognize Arrange-Act-Assert or Given-When-Then patterns:\n\n- Setup block conventions (beforeEach, fixtures, factories)\n- Assertion style (expect vs assert vs should)\n- Mock\u002Fstub patterns (jest.mock vs sinon vs manual)\n\n## Code Organization Patterns\n\n### Import Organization\n\nIdentify import ordering and grouping:\n\n```\nCOMMON IMPORT PATTERNS:\n1. External packages first, internal modules second\n2. Grouped by type (React, libraries, local)\n3. Alphabetized within groups\n4. Absolute imports vs relative imports preference\n```\n\n### Export Patterns\n\nRecognize module boundary conventions:\n\n- Default exports vs named exports preference\n- Barrel files (index.ts re-exports) presence\n- Public API definition patterns\n\n### Comment and Documentation Patterns\n\nIdentify documentation conventions:\n\n- JSDoc\u002FTSDoc presence and style\n- Inline comment frequency and style\n- README conventions per module\u002Ffeature\n\n## Best Practices\n\n- **Follow existing patterns even if imperfect** - Consistency trumps personal preference\n- **Document deviations explicitly** - When breaking patterns intentionally, explain why\n- **Pattern changes require migration** - Dont introduce new patterns without updating existing code\n- **Check tests for patterns too** - Test code often reveals expected conventions\n- **Prefer explicit over implicit** - When patterns are unclear, ask or document assumptions\n\n## Anti-Patterns to Avoid\n\n- Mixing naming conventions in the same codebase\n- Introducing new architectural patterns without team consensus\n- Assuming patterns from other projects apply here\n- Ignoring test patterns when writing implementation\n- Creating \"special\" files that dont follow established structure\n\n## References\n\n- `examples\u002Fcommon-patterns.md` - Concrete examples of pattern recognition in action\n",{"name":5,"description":7},"main","7850740bd837adb32f0a109ab2af82482196c6f2","skills\u002F_collections\u002Fplugins\u002Fteam\u002Fskills\u002Fcross-cutting\u002Fpattern-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":65,"prompt":75,"zipAvailable":76},[66,69,72],{"tool":67,"command":68},"npx","npx skills add shengdabai\u002FTony-Claude-Code-Skills --skill pattern-detection",{"tool":70,"command":71},"bunx","bunx skills add shengdabai\u002FTony-Claude-Code-Skills --skill pattern-detection",{"tool":73,"command":74},"pnpm","pnpm dlx skills add shengdabai\u002FTony-Claude-Code-Skills --skill pattern-detection","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002F_collections\u002Fplugins\u002Fteam\u002Fskills\u002Fcross-cutting\u002Fpattern-detection\u002FSKILL.md",true,[78],{"path":79,"resourceType":80,"resourceTypeDesc":81,"sizeBytes":82,"sourceHtmlUrl":83},"examples\u002Fcommon-patterns.md","REFERENCE","参考文档",8354,"https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002F_collections\u002Fplugins\u002Fteam\u002Fskills\u002Fcross-cutting\u002Fpattern-detection\u002Fexamples\u002Fcommon-patterns.md",[85,94,102,110,118,126],{"skillNo":86,"name":87,"nameZh":6,"description":88,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":89,"sourceHtmlUrl":90,"categories":91,"keywords":92,"publishedAt":93},"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":95,"name":96,"nameZh":6,"description":97,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":98,"sourceHtmlUrl":99,"categories":100,"keywords":101,"publishedAt":93},"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":103,"name":104,"nameZh":6,"description":105,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":106,"sourceHtmlUrl":107,"categories":108,"keywords":109,"publishedAt":93},"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":111,"name":112,"nameZh":6,"description":113,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":114,"sourceHtmlUrl":115,"categories":116,"keywords":117,"publishedAt":93},"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":119,"name":120,"nameZh":6,"description":121,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":122,"sourceHtmlUrl":123,"categories":124,"keywords":125,"publishedAt":93},"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":127,"name":128,"nameZh":6,"description":129,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":130,"categories":131,"keywords":132,"publishedAt":93},"01M73G086AXAH9DW1H5G5N3CPB","dbs-video-extract","接收抖音、小红书、微信视频号等短视频链接或分享文案，查询作品／账号数据并提取语音文字稿，按作者和标题归档为 Markdown。用户希望完整解析短视频、取得数据或文字稿时使用；运行前检查 TikHub 与轻抖使用凭证，缺少时用新手能理解的方式引导购买和安全配置。","https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fdbs-video-extract\u002FSKILL.md",[],[]]