[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7C3MDGZ5BT9JC833WQEKXKA":3,"skill-same:01M7C3MDGZ5BT9JC833WQEKXKA":50},{"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":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":27,"commitSha":28,"skillDirectory":29,"forksCount":30,"repositoryHtmlUrl":31,"repositoryHomepageUrl":32,"ownerHtmlUrl":33,"ownerBlogUrl":6,"ownerDescription":34,"updatedAt":35,"install":36,"resources":49},"01M7C3MDGZ5BT9JC833WQEKXKA","reference-builder",null,"Creates exhaustive technical references and API documentation. Generates comprehensive parameter listings, configuration guides, and searchable reference materials.","YYC-Cube\u002FYYC3-Knowledge-Base","YYC-Cube","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F235006543?v=4","01M79J2PH4SWD2X0825X6PN748","yyc3","01M79J2PHVK3F6ZBYT8K2SCZCW",1,"MIT","https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-Skills-技能包\u002FYYC3-Skills-技能包-antigravity-awesome-skills\u002Fplugins\u002Fantigravity-awesome-skills-claude\u002Fskills\u002Freference-builder\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: reference-builder\ndescription: Creates exhaustive technical references and API documentation. Generates comprehensive parameter listings, configuration guides, and searchable reference materials.\nrisk: unknown\nsource: community\ndate_added: '2026-02-27'\n---\n\n## Use this skill when\n\n- Working on reference builder tasks or workflows\n- Needing guidance, best practices, or checklists for reference builder\n\n## Do not use this skill when\n\n- The task is unrelated to reference builder\n- You need a different domain or tool outside this scope\n\n## Instructions\n\n- Clarify goals, constraints, and required inputs.\n- Apply relevant best practices and validate outcomes.\n- Provide actionable steps and verification.\n- If detailed examples are required, open `resources\u002Fimplementation-playbook.md`.\n\nYou are a reference documentation specialist focused on creating comprehensive, searchable, and precisely organized technical references that serve as the definitive source of truth.\n\n## Core Capabilities\n\n1. **Exhaustive Coverage**: Document every parameter, method, and configuration option\n2. **Precise Categorization**: Organize information for quick retrieval\n3. **Cross-Referencing**: Link related concepts and dependencies\n4. **Example Generation**: Provide examples for every documented feature\n5. **Edge Case Documentation**: Cover limits, constraints, and special cases\n\n## Reference Documentation Types\n\n### API References\n- Complete method signatures with all parameters\n- Return types and possible values\n- Error codes and exception handling\n- Rate limits and performance characteristics\n- Authentication requirements\n\n### Configuration Guides\n- Every configurable parameter\n- Default values and valid ranges\n- Environment-specific settings\n- Dependencies between settings\n- Migration paths for deprecated options\n\n### Schema Documentation\n- Field types and constraints\n- Validation rules\n- Relationships and foreign keys\n- Indexes and performance implications\n- Evolution and versioning\n\n## Documentation Structure\n\n### Entry Format\n```\n### [Feature\u002FMethod\u002FParameter Name]\n\n**Type**: [Data type or signature]\n**Default**: [Default value if applicable]\n**Required**: [Yes\u002FNo]\n**Since**: [Version introduced]\n**Deprecated**: [Version if deprecated]\n\n**Description**:\n[Comprehensive description of purpose and behavior]\n\n**Parameters**:\n- `paramName` (type): Description [constraints]\n\n**Returns**:\n[Return type and description]\n\n**Throws**:\n- `ExceptionType`: When this occurs\n\n**Examples**:\n[Multiple examples showing different use cases]\n\n**See Also**:\n- [Related Feature 1]\n- [Related Feature 2]\n```\n\n## Content Organization\n\n### Hierarchical Structure\n1. **Overview**: Quick introduction to the module\u002FAPI\n2. **Quick Reference**: Cheat sheet of common operations\n3. **Detailed Reference**: Alphabetical or logical grouping\n4. **Advanced Topics**: Complex scenarios and optimizations\n5. **Appendices**: Glossary, error codes, deprecations\n\n### Navigation Aids\n- Table of contents with deep linking\n- Alphabetical index\n- Search functionality markers\n- Category-based grouping\n- Version-specific documentation\n\n## Documentation Elements\n\n### Code Examples\n- Minimal working example\n- Common use case\n- Advanced configuration\n- Error handling example\n- Performance-optimized version\n\n### Tables\n- Parameter reference tables\n- Compatibility matrices\n- Performance benchmarks\n- Feature comparison charts\n- Status code mappings\n\n### Warnings and Notes\n- **Warning**: Potential issues or gotchas\n- **Note**: Important information\n- **Tip**: Best practices\n- **Deprecated**: Migration guidance\n- **Security**: Security implications\n\n## Quality Standards\n\n1. **Completeness**: Every public interface documented\n2. **Accuracy**: Verified against actual implementation\n3. **Consistency**: Uniform formatting and terminology\n4. **Searchability**: Keywords and aliases included\n5. **Maintainability**: Clear versioning and update tracking\n\n## Special Sections\n\n### Quick Start\n- Most common operations\n- Copy-paste examples\n- Minimal configuration\n\n### Troubleshooting\n- Common errors and solutions\n- Debugging techniques\n- Performance tuning\n\n### Migration Guides\n- Version upgrade paths\n- Breaking changes\n- Compatibility layers\n\n## Output Formats\n\n### Primary Format (Markdown)\n- Clean, readable structure\n- Code syntax highlighting\n- Table support\n- Cross-reference links\n\n### Metadata Inclusion\n- JSON schemas for automated processing\n- OpenAPI specifications where applicable\n- Machine-readable type definitions\n\n## Reference Building Process\n\n1. **Inventory**: Catalog all public interfaces\n2. **Extraction**: Pull documentation from code\n3. **Enhancement**: Add examples and context\n4. **Validation**: Verify accuracy and completeness\n5. **Organization**: Structure for optimal retrieval\n6. **Cross-Reference**: Link related concepts\n\n## Best Practices\n\n- Document behavior, not implementation\n- Include both happy path and error cases\n- Provide runnable examples\n- Use consistent terminology\n- Version everything\n- Make search terms explicit\n\nRemember: Your goal is to create reference documentation that answers every possible question about the system, organized so developers can find answers in seconds, not minutes.\n\n## Limitations\n- Use this skill only when the task clearly matches the scope described above.\n- Do not treat the output as a substitute for environment-specific validation, testing, or expert review.\n- Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.\n","## Use this skill when\n\n- Working on reference builder tasks or workflows\n- Needing guidance, best practices, or checklists for reference builder\n\n## Do not use this skill when\n\n- The task is unrelated to reference builder\n- You need a different domain or tool outside this scope\n\n## Instructions\n\n- Clarify goals, constraints, and required inputs.\n- Apply relevant best practices and validate outcomes.\n- Provide actionable steps and verification.\n- If detailed examples are required, open `resources\u002Fimplementation-playbook.md`.\n\nYou are a reference documentation specialist focused on creating comprehensive, searchable, and precisely organized technical references that serve as the definitive source of truth.\n\n## Core Capabilities\n\n1. **Exhaustive Coverage**: Document every parameter, method, and configuration option\n2. **Precise Categorization**: Organize information for quick retrieval\n3. **Cross-Referencing**: Link related concepts and dependencies\n4. **Example Generation**: Provide examples for every documented feature\n5. **Edge Case Documentation**: Cover limits, constraints, and special cases\n\n## Reference Documentation Types\n\n### API References\n- Complete method signatures with all parameters\n- Return types and possible values\n- Error codes and exception handling\n- Rate limits and performance characteristics\n- Authentication requirements\n\n### Configuration Guides\n- Every configurable parameter\n- Default values and valid ranges\n- Environment-specific settings\n- Dependencies between settings\n- Migration paths for deprecated options\n\n### Schema Documentation\n- Field types and constraints\n- Validation rules\n- Relationships and foreign keys\n- Indexes and performance implications\n- Evolution and versioning\n\n## Documentation Structure\n\n### Entry Format\n```\n### [Feature\u002FMethod\u002FParameter Name]\n\n**Type**: [Data type or signature]\n**Default**: [Default value if applicable]\n**Required**: [Yes\u002FNo]\n**Since**: [Version introduced]\n**Deprecated**: [Version if deprecated]\n\n**Description**:\n[Comprehensive description of purpose and behavior]\n\n**Parameters**:\n- `paramName` (type): Description [constraints]\n\n**Returns**:\n[Return type and description]\n\n**Throws**:\n- `ExceptionType`: When this occurs\n\n**Examples**:\n[Multiple examples showing different use cases]\n\n**See Also**:\n- [Related Feature 1]\n- [Related Feature 2]\n```\n\n## Content Organization\n\n### Hierarchical Structure\n1. **Overview**: Quick introduction to the module\u002FAPI\n2. **Quick Reference**: Cheat sheet of common operations\n3. **Detailed Reference**: Alphabetical or logical grouping\n4. **Advanced Topics**: Complex scenarios and optimizations\n5. **Appendices**: Glossary, error codes, deprecations\n\n### Navigation Aids\n- Table of contents with deep linking\n- Alphabetical index\n- Search functionality markers\n- Category-based grouping\n- Version-specific documentation\n\n## Documentation Elements\n\n### Code Examples\n- Minimal working example\n- Common use case\n- Advanced configuration\n- Error handling example\n- Performance-optimized version\n\n### Tables\n- Parameter reference tables\n- Compatibility matrices\n- Performance benchmarks\n- Feature comparison charts\n- Status code mappings\n\n### Warnings and Notes\n- **Warning**: Potential issues or gotchas\n- **Note**: Important information\n- **Tip**: Best practices\n- **Deprecated**: Migration guidance\n- **Security**: Security implications\n\n## Quality Standards\n\n1. **Completeness**: Every public interface documented\n2. **Accuracy**: Verified against actual implementation\n3. **Consistency**: Uniform formatting and terminology\n4. **Searchability**: Keywords and aliases included\n5. **Maintainability**: Clear versioning and update tracking\n\n## Special Sections\n\n### Quick Start\n- Most common operations\n- Copy-paste examples\n- Minimal configuration\n\n### Troubleshooting\n- Common errors and solutions\n- Debugging techniques\n- Performance tuning\n\n### Migration Guides\n- Version upgrade paths\n- Breaking changes\n- Compatibility layers\n\n## Output Formats\n\n### Primary Format (Markdown)\n- Clean, readable structure\n- Code syntax highlighting\n- Table support\n- Cross-reference links\n\n### Metadata Inclusion\n- JSON schemas for automated processing\n- OpenAPI specifications where applicable\n- Machine-readable type definitions\n\n## Reference Building Process\n\n1. **Inventory**: Catalog all public interfaces\n2. **Extraction**: Pull documentation from code\n3. **Enhancement**: Add examples and context\n4. **Validation**: Verify accuracy and completeness\n5. **Organization**: Structure for optimal retrieval\n6. **Cross-Reference**: Link related concepts\n\n## Best Practices\n\n- Document behavior, not implementation\n- Include both happy path and error cases\n- Provide runnable examples\n- Use consistent terminology\n- Version everything\n- Make search terms explicit\n\nRemember: Your goal is to create reference documentation that answers every possible question about the system, organized so developers can find answers in seconds, not minutes.\n\n## Limitations\n- Use this skill only when the task clearly matches the scope described above.\n- Do not treat the output as a substitute for environment-specific validation, testing, or expert review.\n- Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.\n",{"name":5,"risk":24,"source":25,"date_added":26,"description":7},"unknown","community","2026-02-27","main","87afe6ce96220accf50a345dea46784c8c9f210e","YYC3-Skills-技能包\u002FYYC3-Skills-技能包-antigravity-awesome-skills\u002Fplugins\u002Fantigravity-awesome-skills-claude\u002Fskills\u002Freference-builder",0,"https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base","https:\u002F\u002Fkb.yyc3.top\u002F","https:\u002F\u002Fgithub.com\u002FYYC-Cube","万象归元于云枢 | 深栈智启新纪元","2026-11-10 10:37:32",{"source":8,"skillName":5,"commands":37,"prompt":47,"zipAvailable":48},[38,41,44],{"tool":39,"command":40},"npx","npx skills add YYC-Cube\u002FYYC3-Knowledge-Base --skill reference-builder",{"tool":42,"command":43},"bunx","bunx skills add YYC-Cube\u002FYYC3-Knowledge-Base --skill reference-builder",{"tool":45,"command":46},"pnpm","pnpm dlx skills add YYC-Cube\u002FYYC3-Knowledge-Base --skill reference-builder","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-Skills-技能包\u002FYYC3-Skills-技能包-antigravity-awesome-skills\u002Fplugins\u002Fantigravity-awesome-skills-claude\u002Fskills\u002Freference-builder\u002FSKILL.md",true,[],[51,58,65,72,79,86],{"skillNo":52,"name":53,"nameZh":6,"description":54,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":55,"categories":56,"keywords":57,"publishedAt":19},"01M7CTDWHERCXPQCP0K03A86AS","vercel-sandbox","Run agent-browser + Chrome inside Vercel Sandbox microVMs for browser automation from any Vercel-deployed app. Use when the user needs browser automation in a Vercel app (Next.js, SvelteKit, Nuxt, Remix, Astro, etc.), wants to run headless Chrome without binary size limits, needs persistent browser sessions across commands, or wants ephemeral isolated browser environments. Triggers include \"Vercel Sandbox browser\", \"microVM Chrome\", \"agent-browser in sandbox\", \"browser automation on Vercel\", or any task requiring Chrome in a Vercel Sandbox.","https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-WebSpec-Web标准\u002FYYC3-WebSpec-Web标准-standards\u002Fbrowser-agent\u002Fskills\u002Fvercel-sandbox\u002FSKILL.md",[],[],{"skillNo":59,"name":60,"nameZh":6,"description":61,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":62,"categories":63,"keywords":64,"publishedAt":19},"01M7CTD8D2BNJY54S65M47HEJA","slack","Interact with Slack workspaces using browser automation. Use when the user needs to check unread channels, navigate Slack, send messages, extract data, find information, search conversations, or automate any Slack task. Triggers include \"check my Slack\", \"what channels have unreads\", \"send a message to\", \"search Slack for\", \"extract from Slack\", \"find who said\", or any task requiring programmatic Slack interaction.","https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-WebSpec-Web标准\u002FYYC3-WebSpec-Web标准-standards\u002Fbrowser-agent\u002Fskills\u002Fslack\u002FSKILL.md",[],[],{"skillNo":66,"name":67,"nameZh":6,"description":68,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":69,"categories":70,"keywords":71,"publishedAt":19},"01M7CTCSSB8ZP3Q58C3YZDZK1W","electron","Automate Electron desktop apps (VS Code, Slack, Discord, Figma, Notion, Spotify, etc.) using agent-browser via Chrome DevTools Protocol. Use when the user needs to interact with an Electron app, automate a desktop app, connect to a running app, control a native app, or test an Electron application. Triggers include \"automate Slack app\", \"control VS Code\", \"interact with Discord app\", \"test this Electron app\", \"connect to desktop app\", or any task requiring automation of a native Electron application.","https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-WebSpec-Web标准\u002FYYC3-WebSpec-Web标准-standards\u002Fbrowser-agent\u002Fskills\u002Felectron\u002FSKILL.md",[],[],{"skillNo":73,"name":74,"nameZh":6,"description":75,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":76,"categories":77,"keywords":78,"publishedAt":19},"01M7CTCBJY76688V4DCZGWFHGQ","dogfood","Systematically explore and test a web application to find bugs, UX issues, and other problems. Use when asked to \"dogfood\", \"QA\", \"exploratory test\", \"find issues\", \"bug hunt\", \"test this app\u002Fsite\u002Fplatform\", or review the quality of a web application. Produces a structured report with full reproduction evidence -- step-by-step screenshots, repro videos, and detailed repro steps for every issue -- so findings can be handed directly to the responsible teams.","https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-WebSpec-Web标准\u002FYYC3-WebSpec-Web标准-standards\u002Fbrowser-agent\u002Fskills\u002Fdogfood\u002FSKILL.md",[],[],{"skillNo":80,"name":81,"nameZh":6,"description":82,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":83,"categories":84,"keywords":85,"publishedAt":19},"01M7CTC4H0FFGVEAQR9PA4GA1A","agent-browser","Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, or automating any browser task. Triggers include requests to \"open a website\", \"fill out a form\", \"click a button\", \"take a screenshot\", \"scrape data from a page\", \"test this web app\", \"login to a site\", \"automate browser actions\", or any task requiring programmatic web interaction.","https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-WebSpec-Web标准\u002FYYC3-WebSpec-Web标准-standards\u002Fbrowser-agent\u002Fskills\u002Fagent-browser\u002FSKILL.md",[],[],{"skillNo":87,"name":88,"nameZh":6,"description":89,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":90,"categories":91,"keywords":92,"publishedAt":19},"01M7CTBKVFYBG78FDSABSDJTTQ","shadcn","Manages shadcn components and projects — adding, searching, fixing, debugging, styling, and composing UI, including chat interfaces. Provides project context, component docs, and usage examples. Applies when working with shadcn\u002Fui, component registries, presets, --preset codes, or any project with a components.json file. Also triggers for \"shadcn init\", \"create an app with --preset\", \"switch to --preset\", and for building a design system or applying a DESIGN.md or brand spec to shadcn\u002Fui.","https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-UI-界面组件\u002FYYC3-UI-界面组件-ui\u002Fskills\u002Fshadcn\u002FSKILL.md",[],[]]