[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M78FQ6DHVBHE4B4JHTR1TCKA":3,"skill-same:01M78FQ6DHVBHE4B4JHTR1TCKA":46},{"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":25,"commitSha":26,"skillDirectory":27,"forksCount":14,"repositoryHtmlUrl":28,"repositoryHomepageUrl":29,"ownerHtmlUrl":30,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":31,"install":32,"resources":45},"01M78FQ6DHVBHE4B4JHTR1TCKA","ui-to-vue",null,"Use when the user has UI screenshots or design exports that need batch conversion into Vue 3 components, especially with Vant, Element Plus, or Ant Design Vue.","princepatel04477-web\u002Ftrivoxa-group","princepatel04477-web","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F227740714?v=4","01M788ZAJ2KECD5KXVP55PZXKS","Prince Patel","01M788ZAJTCN8YSD737MRSKC5Q",0,"MIT","https:\u002F\u002Fgithub.com\u002Fprincepatel04477-web\u002Ftrivoxa-group\u002Fblob\u002Fmaster\u002F.github\u002Fskills\u002Fui-to-vue\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: ui-to-vue\ndescription: Use when the user has UI screenshots or design exports that need batch conversion into Vue 3 components, especially with Vant, Element Plus, or Ant Design Vue.\norigin: community\n---\n\n# UI To Vue\n\nBatch-convert UI design screenshots into Vue 3 Composition API component code.\n\n## When to Use\n\n- The user provides a directory of design screenshots or design-export images.\n- The target application is Vue 3.\n- The user wants a first pass of page components, shared components, and router wiring.\n- The user specifies Vant, Element Plus, or Ant Design Vue as the component library.\n\n## When Not to Use\n\n- The user has only one screenshot and wants a bespoke component.\n- The target project is not Vue.\n- The design requires detailed interaction logic, data flow, or accessibility review.\n- The screenshots contain private customer data that cannot be sent to an external model API.\n\n## Inputs\n\nUse an input directory that groups screenshots by module and page state:\n\n```text\nscreenshots\u002F\n|-- HomePage\u002F\n|   |-- List\u002F\n|   |   |-- HomePage-List-Default@3x.png\n|   |   `-- cut-images\u002F\n|   |-- cut-images\u002F\n|   `-- HomePage-Default@3x.png\n`-- cut-images\u002F\n```\n\nSupported cut-image directory names include `assets`, `icons`, `sprites`, `cut`, `images`, and `cut-images`.\n\n## Conversion Model\n\n- Page grouping: combine related screenshots into one page component when they represent list, detail, form, loading, or empty states.\n- UI library mapping: map native visual elements to Vant, Element Plus, or Ant Design Vue components where practical.\n- Cut-image priority: prefer page-level assets, then module-level assets, then global shared assets.\n- Component extraction: extract repeated UI regions into shared components when they appear more than once.\n\n## CLI Usage\n\nRun the converter with `npx` so the documented command works without relying on a global binary:\n\n```bash\nexport DASHSCOPE_API_KEY=your_key\nnpx ui-to-vue-converter@1.0.2 --input .\u002Fscreenshots --ui vant --output .\u002Fsrc\n```\n\nFor desktop UI libraries:\n\n```bash\nnpx ui-to-vue-converter@1.0.2 --input .\u002Fdesigns --ui element-plus --output .\u002Fsrc\nnpx ui-to-vue-converter@1.0.2 --input .\u002Fdesigns --ui antd-vue --output .\u002Fsrc\n```\n\nIf the package is installed globally, the `ui-to-vue` binary can be used directly:\n\n```bash\nnpm install -g ui-to-vue-converter@1.0.2\nui-to-vue --input .\u002Fscreenshots --ui vant --output .\u002Fsrc\n```\n\n## Options\n\n| Option | Description | Default |\n| --- | --- | --- |\n| `--input` | Design image directory | `.\u002Fscreenshots` |\n| `--ui` | UI library: `vant`, `element-plus`, or `antd-vue` | `vant` |\n| `--output` | Output directory | `.\u002Fsrc` |\n| `--config` | Config file path | `.\u002F.ui-to-vue.config.json` |\n\n## API Key Handling\n\nThe converter can read DashScope credentials from a config file or from the environment. Prefer an environment variable in repositories:\n\n```bash\nexport DASHSCOPE_API_KEY=your_key\n```\n\nIf a local config file is required, keep it out of version control:\n\n```json\n{\n  \"apiKey\": \"your_dashscope_key\",\n  \"input\": \".\u002Fdesigns\",\n  \"ui\": \"vant\",\n  \"output\": \".\u002Fsrc\"\n}\n```\n\n```gitignore\n.ui-to-vue.config.json\n```\n\n## Security and Privacy\n\n- Treat design screenshots as source material that may be sent to an external model API.\n- Do not run this flow on private customer designs without permission.\n- Pin the converter version in repeatable workflows instead of using `@latest`.\n- Review generated Vue code before committing it.\n- Do not commit `.ui-to-vue.config.json`, API keys, generated secrets, or customer screenshots.\n\n## Output Review Checklist\n\n- [ ] Page components were generated under `views\u002F` or the chosen output directory.\n- [ ] Repeated UI regions were extracted into `components\u002F` only when reuse is clear.\n- [ ] Router output is compatible with the target project's router style.\n- [ ] Generated components use the requested UI library consistently.\n- [ ] Generated CSS units match the design baseline.\n- [ ] The code passes the project's formatter, linter, type checker, and build.\n- [ ] Placeholder copy, mock data, and generated assets were reviewed before commit.\n\n## Troubleshooting\n\n| Issue | Check |\n| --- | --- |\n| `401` or authentication error | Confirm `DASHSCOPE_API_KEY` is set in the shell running the command. |\n| `command not found: ui-to-vue` | Use the `npx ui-to-vue-converter@1.0.2` form or install the package globally. |\n| Cut images are ignored | Confirm the asset directory name is supported and nested under the matching page or module. |\n| Components ignore the requested UI library | Re-run with an explicit `--ui` value and inspect the generated imports. |\n| Generated layout dimensions look wrong | Confirm the screenshot export width matches the target library baseline. |\n\n## References\n\n- npm package: `ui-to-vue-converter`\n","# UI To Vue\n\nBatch-convert UI design screenshots into Vue 3 Composition API component code.\n\n## When to Use\n\n- The user provides a directory of design screenshots or design-export images.\n- The target application is Vue 3.\n- The user wants a first pass of page components, shared components, and router wiring.\n- The user specifies Vant, Element Plus, or Ant Design Vue as the component library.\n\n## When Not to Use\n\n- The user has only one screenshot and wants a bespoke component.\n- The target project is not Vue.\n- The design requires detailed interaction logic, data flow, or accessibility review.\n- The screenshots contain private customer data that cannot be sent to an external model API.\n\n## Inputs\n\nUse an input directory that groups screenshots by module and page state:\n\n```text\nscreenshots\u002F\n|-- HomePage\u002F\n|   |-- List\u002F\n|   |   |-- HomePage-List-Default@3x.png\n|   |   `-- cut-images\u002F\n|   |-- cut-images\u002F\n|   `-- HomePage-Default@3x.png\n`-- cut-images\u002F\n```\n\nSupported cut-image directory names include `assets`, `icons`, `sprites`, `cut`, `images`, and `cut-images`.\n\n## Conversion Model\n\n- Page grouping: combine related screenshots into one page component when they represent list, detail, form, loading, or empty states.\n- UI library mapping: map native visual elements to Vant, Element Plus, or Ant Design Vue components where practical.\n- Cut-image priority: prefer page-level assets, then module-level assets, then global shared assets.\n- Component extraction: extract repeated UI regions into shared components when they appear more than once.\n\n## CLI Usage\n\nRun the converter with `npx` so the documented command works without relying on a global binary:\n\n```bash\nexport DASHSCOPE_API_KEY=your_key\nnpx ui-to-vue-converter@1.0.2 --input .\u002Fscreenshots --ui vant --output .\u002Fsrc\n```\n\nFor desktop UI libraries:\n\n```bash\nnpx ui-to-vue-converter@1.0.2 --input .\u002Fdesigns --ui element-plus --output .\u002Fsrc\nnpx ui-to-vue-converter@1.0.2 --input .\u002Fdesigns --ui antd-vue --output .\u002Fsrc\n```\n\nIf the package is installed globally, the `ui-to-vue` binary can be used directly:\n\n```bash\nnpm install -g ui-to-vue-converter@1.0.2\nui-to-vue --input .\u002Fscreenshots --ui vant --output .\u002Fsrc\n```\n\n## Options\n\n| Option | Description | Default |\n| --- | --- | --- |\n| `--input` | Design image directory | `.\u002Fscreenshots` |\n| `--ui` | UI library: `vant`, `element-plus`, or `antd-vue` | `vant` |\n| `--output` | Output directory | `.\u002Fsrc` |\n| `--config` | Config file path | `.\u002F.ui-to-vue.config.json` |\n\n## API Key Handling\n\nThe converter can read DashScope credentials from a config file or from the environment. Prefer an environment variable in repositories:\n\n```bash\nexport DASHSCOPE_API_KEY=your_key\n```\n\nIf a local config file is required, keep it out of version control:\n\n```json\n{\n  \"apiKey\": \"your_dashscope_key\",\n  \"input\": \".\u002Fdesigns\",\n  \"ui\": \"vant\",\n  \"output\": \".\u002Fsrc\"\n}\n```\n\n```gitignore\n.ui-to-vue.config.json\n```\n\n## Security and Privacy\n\n- Treat design screenshots as source material that may be sent to an external model API.\n- Do not run this flow on private customer designs without permission.\n- Pin the converter version in repeatable workflows instead of using `@latest`.\n- Review generated Vue code before committing it.\n- Do not commit `.ui-to-vue.config.json`, API keys, generated secrets, or customer screenshots.\n\n## Output Review Checklist\n\n- [ ] Page components were generated under `views\u002F` or the chosen output directory.\n- [ ] Repeated UI regions were extracted into `components\u002F` only when reuse is clear.\n- [ ] Router output is compatible with the target project's router style.\n- [ ] Generated components use the requested UI library consistently.\n- [ ] Generated CSS units match the design baseline.\n- [ ] The code passes the project's formatter, linter, type checker, and build.\n- [ ] Placeholder copy, mock data, and generated assets were reviewed before commit.\n\n## Troubleshooting\n\n| Issue | Check |\n| --- | --- |\n| `401` or authentication error | Confirm `DASHSCOPE_API_KEY` is set in the shell running the command. |\n| `command not found: ui-to-vue` | Use the `npx ui-to-vue-converter@1.0.2` form or install the package globally. |\n| Cut images are ignored | Confirm the asset directory name is supported and nested under the matching page or module. |\n| Components ignore the requested UI library | Re-run with an explicit `--ui` value and inspect the generated imports. |\n| Generated layout dimensions look wrong | Confirm the screenshot export width matches the target library baseline. |\n\n## References\n\n- npm package: `ui-to-vue-converter`\n",{"name":5,"origin":24,"description":7},"community","master","877653a671c51fae6476bd9f0d34ee6c408d68b9",".github\u002Fskills\u002Fui-to-vue","https:\u002F\u002Fgithub.com\u002Fprincepatel04477-web\u002Ftrivoxa-group","https:\u002F\u002Ftrivoxa-group.vercel.app","https:\u002F\u002Fgithub.com\u002Fprincepatel04477-web","2026-08-01 17:29:31",{"source":8,"skillName":5,"commands":33,"prompt":43,"zipAvailable":44},[34,37,40],{"tool":35,"command":36},"npx","npx skills add princepatel04477-web\u002Ftrivoxa-group --skill ui-to-vue",{"tool":38,"command":39},"bunx","bunx skills add princepatel04477-web\u002Ftrivoxa-group --skill ui-to-vue",{"tool":41,"command":42},"pnpm","pnpm dlx skills add princepatel04477-web\u002Ftrivoxa-group --skill ui-to-vue","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fprincepatel04477-web\u002Ftrivoxa-group\u002Fblob\u002Fmaster\u002F.github\u002Fskills\u002Fui-to-vue\u002FSKILL.md",true,[],[47,54,61,68,75,82],{"skillNo":48,"name":49,"nameZh":6,"description":50,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":51,"categories":52,"keywords":53,"publishedAt":19},"01M78G4Z5RFJ72G536XYPC77PG","zustand-store-ts","Create Zustand stores following established patterns with proper TypeScript types and middleware.","https:\u002F\u002Fgithub.com\u002Fprincepatel04477-web\u002Ftrivoxa-group\u002Fblob\u002Fmaster\u002F.github\u002Fskills\u002Fzustand-store-ts\u002FSKILL.md",[],[],{"skillNo":55,"name":56,"nameZh":6,"description":57,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":58,"categories":59,"keywords":60,"publishedAt":19},"01M78G4WQMHRST36KDP7AV3NR3","zoom-automation","Automate Zoom meeting creation, management, recordings, webinars, and participant tracking via Rube MCP (Composio). Always search tools first for current schemas.","https:\u002F\u002Fgithub.com\u002Fprincepatel04477-web\u002Ftrivoxa-group\u002Fblob\u002Fmaster\u002F.github\u002Fskills\u002Fzoom-automation\u002FSKILL.md",[],[],{"skillNo":62,"name":63,"nameZh":6,"description":64,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":65,"categories":66,"keywords":67,"publishedAt":19},"01M78G4T37F4SPS7M4KT0A8JJB","zoho-crm-automation","Automate Zoho CRM tasks via Rube MCP (Composio): create\u002Fupdate records, search contacts, manage leads, and convert leads. Always search tools first for current schemas.","https:\u002F\u002Fgithub.com\u002Fprincepatel04477-web\u002Ftrivoxa-group\u002Fblob\u002Fmaster\u002F.github\u002Fskills\u002Fzoho-crm-automation\u002FSKILL.md",[],[],{"skillNo":69,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":74,"publishedAt":19},"01M78G4QAJMF71KD1G38MNDQYK","zod-validation-expert","Expert in Zod — TypeScript-first schema validation. Covers parsing, custom errors, refinements, type inference, and integration with React Hook Form, Next.js, and tRPC.","https:\u002F\u002Fgithub.com\u002Fprincepatel04477-web\u002Ftrivoxa-group\u002Fblob\u002Fmaster\u002F.github\u002Fskills\u002Fzod-validation-expert\u002FSKILL.md",[],[],{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":19},"01M78G4MS3WE96MH5P561KFY95","zipai-optimizer","Adaptive token optimizer: intelligent filtering, surgical output, ambiguity-first, context-window-aware, VCS-aware, MCP-aware.","https:\u002F\u002Fgithub.com\u002Fprincepatel04477-web\u002Ftrivoxa-group\u002Fblob\u002Fmaster\u002F.github\u002Fskills\u002Fzipai-optimizer\u002FSKILL.md",[],[],{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":19},"01M78G4GZ0T47C6929V9CVH1AK","zeroize-audit","Detects missing zeroization of sensitive data in source code and identifies zeroization removed by compiler optimizations, with assembly-level analysis, and control-flow verification. Use for auditing C\u002FC++\u002FRust code handling secrets, keys, passwords, or other sensitive data.","https:\u002F\u002Fgithub.com\u002Fprincepatel04477-web\u002Ftrivoxa-group\u002Fblob\u002Fmaster\u002F.github\u002Fskills\u002Fzeroize-audit\u002FSKILL.md",[],[]]