[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6RCEC92GFK4FV1QN37AV9VR":3,"skill-same:01M6RCEC92GFK4FV1QN37AV9VR":103},{"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":63,"commitSha":64,"skillDirectory":65,"forksCount":66,"repositoryHtmlUrl":67,"repositoryHomepageUrl":6,"ownerHtmlUrl":68,"ownerBlogUrl":69,"ownerDescription":6,"updatedAt":70,"install":71,"resources":84},"01M6RCEC92GFK4FV1QN37AV9VR","spec-miner",null,"Reverse-engineering specialist that extracts specifications from existing codebases. Use when working with legacy or undocumented systems, inherited projects, or old codebases with no documentation. Invoke to map code dependencies, generate API documentation from source, identify undocumented business logic, figure out what code does, or create architecture documentation from implementation. Trigger phrases: reverse engineer, old codebase, no docs, no documentation, figure out how this works, inherited project, legacy analysis, code archaeology, undocumented features.","PIXARTSeu\u002FSynapse","PIXARTSeu","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F274446381?v=4","01M6RB4XPN9YBZCRY4FVN9PJCT","Pixarts ","01M6RB4XTF8G9KHQEMC21FGDKD",12,"MIT","https:\u002F\u002Fgithub.com\u002FPIXARTSeu\u002FSynapse\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fspec-miner\u002FSKILL.md",[18,23],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发","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],"spec miner","spec","read","invoke","understand codebase","Existing","fullstack","project","document","engineer","use","system","projects","how","forge","reverse-engineering","generate","create","architecture","github","2026-11-10 10:12:30",false,"---\nname: spec-miner\ndescription: \"Reverse-engineering specialist that extracts specifications from existing codebases. Use when working with legacy or undocumented systems, inherited projects, or old codebases with no documentation. Invoke to map code dependencies, generate API documentation from source, identify undocumented business logic, figure out what code does, or create architecture documentation from implementation. Trigger phrases: reverse engineer, old codebase, no docs, no documentation, figure out how this works, inherited project, legacy analysis, code archaeology, undocumented features.\"\nlicense: MIT\nallowed-tools: Read, Grep, Glob, Bash\nmetadata:\n  author: https:\u002F\u002Fgithub.com\u002FJeffallan\n  version: \"1.1.0\"\n  domain: workflow\n  triggers: reverse engineer, legacy code, code analysis, undocumented, understand codebase, existing system\n  role: specialist\n  scope: review\n  output-format: document\n  related-skills: feature-forge, fullstack-guardian, architecture-designer\n---\n\n# Spec Miner\n\nReverse-engineering specialist who extracts specifications from existing codebases.\n\n## Role Definition\n\nYou operate with two perspectives: **Arch Hat** for system architecture and data flows, and **QA Hat** for observable behaviors and edge cases.\n\n## When to Use This Skill\n\n- Understanding legacy or undocumented systems\n- Creating documentation for existing code\n- Onboarding to a new codebase\n- Planning enhancements to existing features\n- Extracting requirements from implementation\n\n## Core Workflow\n\n1. **Scope** - Identify analysis boundaries (full system or specific feature)\n2. **Explore** - Map structure using Glob, Grep, Read tools\n   - _Validation checkpoint:_ Confirm sufficient file coverage before proceeding. If key entry points, configuration files, or core modules remain unread, continue exploration before writing documentation.\n3. **Trace** - Follow data flows and request paths\n4. **Document** - Write observed requirements in EARS format\n5. **Flag** - Mark areas needing clarification\n\n### Example Exploration Patterns\n\n```\n# Find entry points and public interfaces\nGlob('**\u002F*.py', exclude=['**\u002Ftest*', '**\u002F__pycache__\u002F**'])\n\n# Locate technical debt markers\nGrep('TODO|FIXME|HACK|XXX', include='*.py')\n\n# Discover configuration and environment usage\nGrep('os\\.environ|config\\[|settings\\.', include='*.py')\n\n# Map API route definitions (Flask\u002FDjango\u002FExpress examples)\nGrep('@app\\.route|@router\\.|router\\.get|router\\.post', include='*.py')\n```\n\n### EARS Format Quick Reference\n\nEARS (Easy Approach to Requirements Syntax) structures observed behavior as:\n\n| Type | Pattern | Example |\n|------|---------|---------|\n| Ubiquitous | The `\u003Csystem>` shall `\u003Caction>`. | The API shall return JSON responses. |\n| Event-driven | When `\u003Ctrigger>`, the `\u003Csystem>` shall `\u003Caction>`. | When a request lacks an auth token, the system shall return HTTP 401. |\n| State-driven | While `\u003Cstate>`, the `\u003Csystem>` shall `\u003Caction>`. | While in maintenance mode, the system shall reject all write operations. |\n| Optional | Where `\u003Cfeature>` is supported, the `\u003Csystem>` shall `\u003Caction>`. | Where caching is enabled, the system shall store responses for 60 seconds. |\n\n> See `references\u002Fears-format.md` for the complete EARS reference.\n\n## Reference Guide\n\nLoad detailed guidance based on context:\n\n| Topic | Reference | Load When |\n|-------|-----------|-----------|\n| Analysis Process | `references\u002Fanalysis-process.md` | Starting exploration, Glob\u002FGrep patterns |\n| EARS Format | `references\u002Fears-format.md` | Writing observed requirements |\n| Specification Template | `references\u002Fspecification-template.md` | Creating final specification document |\n| Analysis Checklist | `references\u002Fanalysis-checklist.md` | Ensuring thorough analysis |\n\n## Constraints\n\n### MUST DO\n- Ground all observations in actual code evidence\n- Use Read, Grep, Glob extensively to explore\n- Distinguish between observed facts and inferences\n- Document uncertainties in dedicated section\n- Include code locations for each observation\n\n### MUST NOT DO\n- Make assumptions without code evidence\n- Skip security pattern analysis\n- Ignore error handling patterns\n- Generate spec without thorough exploration\n\n## Output Templates\n\nSave specification as: `specs\u002F{project_name}_reverse_spec.md`\n\nInclude:\n1. Technology stack and architecture\n2. Module\u002Fdirectory structure\n3. Observed requirements (EARS format)\n4. Non-functional observations\n5. Inferred acceptance criteria\n6. Uncertainties and questions\n7. Recommendations\n","# Spec Miner\n\nReverse-engineering specialist who extracts specifications from existing codebases.\n\n## Role Definition\n\nYou operate with two perspectives: **Arch Hat** for system architecture and data flows, and **QA Hat** for observable behaviors and edge cases.\n\n## When to Use This Skill\n\n- Understanding legacy or undocumented systems\n- Creating documentation for existing code\n- Onboarding to a new codebase\n- Planning enhancements to existing features\n- Extracting requirements from implementation\n\n## Core Workflow\n\n1. **Scope** - Identify analysis boundaries (full system or specific feature)\n2. **Explore** - Map structure using Glob, Grep, Read tools\n   - _Validation checkpoint:_ Confirm sufficient file coverage before proceeding. If key entry points, configuration files, or core modules remain unread, continue exploration before writing documentation.\n3. **Trace** - Follow data flows and request paths\n4. **Document** - Write observed requirements in EARS format\n5. **Flag** - Mark areas needing clarification\n\n### Example Exploration Patterns\n\n```\n# Find entry points and public interfaces\nGlob('**\u002F*.py', exclude=['**\u002Ftest*', '**\u002F__pycache__\u002F**'])\n\n# Locate technical debt markers\nGrep('TODO|FIXME|HACK|XXX', include='*.py')\n\n# Discover configuration and environment usage\nGrep('os\\.environ|config\\[|settings\\.', include='*.py')\n\n# Map API route definitions (Flask\u002FDjango\u002FExpress examples)\nGrep('@app\\.route|@router\\.|router\\.get|router\\.post', include='*.py')\n```\n\n### EARS Format Quick Reference\n\nEARS (Easy Approach to Requirements Syntax) structures observed behavior as:\n\n| Type | Pattern | Example |\n|------|---------|---------|\n| Ubiquitous | The `\u003Csystem>` shall `\u003Caction>`. | The API shall return JSON responses. |\n| Event-driven | When `\u003Ctrigger>`, the `\u003Csystem>` shall `\u003Caction>`. | When a request lacks an auth token, the system shall return HTTP 401. |\n| State-driven | While `\u003Cstate>`, the `\u003Csystem>` shall `\u003Caction>`. | While in maintenance mode, the system shall reject all write operations. |\n| Optional | Where `\u003Cfeature>` is supported, the `\u003Csystem>` shall `\u003Caction>`. | Where caching is enabled, the system shall store responses for 60 seconds. |\n\n> See `references\u002Fears-format.md` for the complete EARS reference.\n\n## Reference Guide\n\nLoad detailed guidance based on context:\n\n| Topic | Reference | Load When |\n|-------|-----------|-----------|\n| Analysis Process | `references\u002Fanalysis-process.md` | Starting exploration, Glob\u002FGrep patterns |\n| EARS Format | `references\u002Fears-format.md` | Writing observed requirements |\n| Specification Template | `references\u002Fspecification-template.md` | Creating final specification document |\n| Analysis Checklist | `references\u002Fanalysis-checklist.md` | Ensuring thorough analysis |\n\n## Constraints\n\n### MUST DO\n- Ground all observations in actual code evidence\n- Use Read, Grep, Glob extensively to explore\n- Distinguish between observed facts and inferences\n- Document uncertainties in dedicated section\n- Include code locations for each observation\n\n### MUST NOT DO\n- Make assumptions without code evidence\n- Skip security pattern analysis\n- Ignore error handling patterns\n- Generate spec without thorough exploration\n\n## Output Templates\n\nSave specification as: `specs\u002F{project_name}_reverse_spec.md`\n\nInclude:\n1. Technology stack and architecture\n2. Module\u002Fdirectory structure\n3. Observed requirements (EARS format)\n4. Non-functional observations\n5. Inferred acceptance criteria\n6. Uncertainties and questions\n7. Recommendations\n",{"name":5,"license":15,"metadata":54,"description":7,"allowed-tools":62},{"role":55,"scope":56,"author":57,"domain":58,"version":59,"triggers":60,"output-format":37,"related-skills":61},"specialist","review","https:\u002F\u002Fgithub.com\u002FJeffallan","workflow","1.1.0","reverse engineer, legacy code, code analysis, undocumented, understand codebase, existing system","feature-forge, fullstack-guardian, architecture-designer","Read, Grep, Glob, Bash","main","c19c0bc0a04d25a849ce749fe88250e688f06437",".agents\u002Fskills\u002Fspec-miner",1,"https:\u002F\u002Fgithub.com\u002FPIXARTSeu\u002FSynapse","https:\u002F\u002Fgithub.com\u002FPIXARTSeu","https:\u002F\u002Fpixarts.eu\u002F","2026-09-24 06:30:45",{"source":8,"skillName":5,"commands":72,"prompt":82,"zipAvailable":83},[73,76,79],{"tool":74,"command":75},"npx","npx skills add PIXARTSeu\u002FSynapse --skill spec-miner",{"tool":77,"command":78},"bunx","bunx skills add PIXARTSeu\u002FSynapse --skill spec-miner",{"tool":80,"command":81},"pnpm","pnpm dlx skills add PIXARTSeu\u002FSynapse --skill spec-miner","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FPIXARTSeu\u002FSynapse\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fspec-miner\u002FSKILL.md",true,[85,91,95,99],{"path":86,"resourceType":87,"resourceTypeDesc":88,"sizeBytes":89,"sourceHtmlUrl":90},"references\u002Fanalysis-checklist.md","REFERENCE","参考文档",2040,"https:\u002F\u002Fgithub.com\u002FPIXARTSeu\u002FSynapse\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fspec-miner\u002Freferences\u002Fanalysis-checklist.md",{"path":92,"resourceType":87,"resourceTypeDesc":88,"sizeBytes":93,"sourceHtmlUrl":94},"references\u002Fanalysis-process.md",1280,"https:\u002F\u002Fgithub.com\u002FPIXARTSeu\u002FSynapse\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fspec-miner\u002Freferences\u002Fanalysis-process.md",{"path":96,"resourceType":87,"resourceTypeDesc":88,"sizeBytes":97,"sourceHtmlUrl":98},"references\u002Fears-format.md",1835,"https:\u002F\u002Fgithub.com\u002FPIXARTSeu\u002FSynapse\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fspec-miner\u002Freferences\u002Fears-format.md",{"path":100,"resourceType":87,"resourceTypeDesc":88,"sizeBytes":101,"sourceHtmlUrl":102},"references\u002Fspecification-template.md",2475,"https:\u002F\u002Fgithub.com\u002FPIXARTSeu\u002FSynapse\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fspec-miner\u002Freferences\u002Fspecification-template.md",[104,135,142,169,190,215],{"skillNo":105,"name":106,"nameZh":6,"description":107,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":108,"categories":109,"keywords":114,"publishedAt":49},"01M6X0ECZKGP44NP2JW588B9RG","vercel-react-best-practices","React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React\u002FNext.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.","https:\u002F\u002Fgithub.com\u002FPIXARTSeu\u002FSynapse\u002Fblob\u002Fmain\u002Fskills\u002Fvercel-react-best-practices\u002FSKILL.md",[110,113],{"categoryNo":111,"categoryName":112,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000009","前端开发",{"categoryNo":24,"categoryName":25,"taxonomyType":26,"taxonomyTypeDesc":27},[115,116,117,118,119,120,121,122,123,124,125,126,127,128,129,130,131,132,133,134],"react","vercel react best practices","best practices","react best practices","vercel","writing","performance","components","react components","guidelines","tasks","code","Optimization","data","refactoring","patterns","next","triggers","data fetching","when",{"skillNo":136,"name":106,"nameZh":6,"description":107,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":137,"categories":138,"keywords":141,"publishedAt":49},"01M6X05WCVH879XKZEAQ15PHQX","https:\u002F\u002Fgithub.com\u002FPIXARTSeu\u002FSynapse\u002Fblob\u002Fmain\u002Fpackages\u002Fcodegraph\u002Fdata\u002Fskill\u002Fvercel-react-best-practices\u002FSKILL.md",[139,140],{"categoryNo":111,"categoryName":112,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":24,"categoryName":25,"taxonomyType":26,"taxonomyTypeDesc":27},[115,116,117,118,119,120,121,122,123,124,125,126,127,128,129,130,131,132,133,134],{"skillNo":143,"name":144,"nameZh":6,"description":145,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":146,"categories":147,"keywords":152,"publishedAt":49},"01M6WZ286AR2SYE9GZYVW0CNYG","wordpress-pro","Develops custom WordPress themes and plugins, creates and registers Gutenberg blocks and block patterns, configures WooCommerce stores, implements WordPress REST API endpoints, applies security hardening (nonces, sanitization, escaping, capability checks), and optimizes performance through caching and query tuning. Use when building WordPress themes, writing plugins, customizing Gutenberg blocks, extending WooCommerce, working with ACF, using the WordPress REST API, applying hooks and filters, or improving WordPress performance and security.","https:\u002F\u002Fgithub.com\u002FPIXARTSeu\u002FSynapse\u002Fblob\u002Fmain\u002Fpackages\u002Fcodegraph\u002Fdata\u002Flifecycle-skills\u002Fwordpress-pro\u002FSKILL.md",[148,151],{"categoryNo":149,"categoryName":150,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000010","后端与接口",{"categoryNo":24,"categoryName":25,"taxonomyType":26,"taxonomyTypeDesc":27},[153,154,155,120,156,121,126,157,158,159,160,161,162,163,164,165,166,167,168,134],"wordpress","wordpress pro","pro","security","tuning","api","laravel","reviewer","hooks","filters","expert","query","woocommerce","caching","themes","sanitization",{"skillNo":170,"name":171,"nameZh":6,"description":172,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":173,"categories":174,"keywords":177,"publishedAt":49},"01M6WZ1ZVG6PJ4PVN9RTK0BX7Z","websocket-engineer","Use when building real-time communication systems with WebSockets or Socket.IO. Invoke for bidirectional messaging, horizontal scaling with Redis, presence tracking, room management.","https:\u002F\u002Fgithub.com\u002FPIXARTSeu\u002FSynapse\u002Fblob\u002Fmain\u002Fpackages\u002Fcodegraph\u002Fdata\u002Flifecycle-skills\u002Fwebsocket-engineer\u002FSKILL.md",[175,176],{"categoryNo":149,"categoryName":150,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":24,"categoryName":25,"taxonomyType":26,"taxonomyTypeDesc":27},[178,38,179,47,126,180,181,158,160,182,163,183,184,185,186,187,188,189,32,134],"websocket","websocket engineer","messaging","monitoring","fastapi","time","scaling","io","communication systems","presence","updates","socket",{"skillNo":191,"name":192,"nameZh":6,"description":193,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":194,"categories":195,"keywords":199,"publishedAt":49},"01M6WZ1G86ZR73H0WNM6CGNRGF","vue-expert","Builds Vue 3 components with Composition API patterns, configures Nuxt 3 SSR\u002FSSG projects, sets up Pinia stores, scaffolds Quasar\u002FCapacitor mobile apps, implements PWA features, and optimises Vite builds. Use when creating Vue 3 applications with Composition API, writing reusable composables, managing state with Pinia, building hybrid mobile apps with Quasar or Capacitor, configuring service workers, or tuning Vite configuration and TypeScript integration.","https:\u002F\u002Fgithub.com\u002FPIXARTSeu\u002FSynapse\u002Fblob\u002Fmain\u002Fpackages\u002Fcodegraph\u002Fdata\u002Flifecycle-skills\u002Fvue-expert\u002FSKILL.md",[196,197,198],{"categoryNo":111,"categoryName":112,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":149,"categoryName":150,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":24,"categoryName":25,"taxonomyType":26,"taxonomyTypeDesc":27},[200,163,201,202,120,203,122,204,205,206,41,207,39,208,209,210,211,212,213,214],"vue","vue expert","frontend","typescript","config","applications","Composition","pinia","router","workers","mobile","reusable","worker","apps","hybrid",{"skillNo":216,"name":217,"nameZh":6,"description":218,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":219,"categories":220,"keywords":223,"publishedAt":49},"01M6WZ1AP3GFCBAMD712X8KRP7","vue-expert-js","Creates Vue 3 components, builds vanilla JS composables, configures Vite projects, and sets up routing and state management using JavaScript only — no TypeScript. Generates JSDoc-typed code with @typedef, @param, and @returns annotations for full type coverage without a TS compiler. Use when building Vue 3 applications with JavaScript only (no TypeScript), when projects require JSDoc-based type hints, when migrating from Vue 2 Options API to Composition API in JS, or when teams prefer vanilla JavaScript, .mjs modules, or need quick prototypes without TypeScript setup.","https:\u002F\u002Fgithub.com\u002FPIXARTSeu\u002FSynapse\u002Fblob\u002Fmain\u002Fpackages\u002Fcodegraph\u002Fdata\u002Flifecycle-skills\u002Fvue-expert-js\u002FSKILL.md",[221,222],{"categoryNo":111,"categoryName":112,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":24,"categoryName":25,"taxonomyType":26,"taxonomyTypeDesc":27},[200,224,163,225,201,202,203,122,126,158,206,41,226,227,228,229,230,231,232,134],"js","vue expert js","coverage","only","up","modules","options","jsdoc","quick"]