[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M79SCCF9Q09X3C5WY3MSPZP3":3,"skill-same:01M79SCCF9Q09X3C5WY3MSPZP3":69},{"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":16,"sourceHtmlUrl":17,"categories":18,"keywords":19,"publishedAt":20,"linkOnly":21,"markdownContent":22,"markdownBody":23,"frontMatter":24,"refName":25,"commitSha":26,"skillDirectory":27,"forksCount":14,"repositoryHtmlUrl":28,"repositoryHomepageUrl":6,"ownerHtmlUrl":29,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":30,"install":31,"resources":44},"01M79SCCF9Q09X3C5WY3MSPZP3","gcode",null,"通过编排真正的切片器 CLI，从 3D 网格文件生成、检查、试运行和静态验证纯 FDM“.gcode”。当 Codex 需要将“.stl”、“.obj”、未切片的“.3mf”、“.ply”、“.glb”或“.gltf”切片为打印机配置文件的 G 代码、发现本地切片器后端、检查网格是否已准备好切片或在任何特定于打印机的切换之前验证生成的 G 代码时使用。","zzz2929\u002Fskills-zh-CN","zzz2929","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F145306978?v=4","01M79S11YZNA13C4SZEN9M9QH1","zxyzzz","01M79S1204VZEHJSESQE300A6N",0,"MIT","https:\u002F\u002Fgithub.com\u002Fzzz2929\u002Fskills-zh-CN\u002Fblob\u002Fmain\u002Ftext-to-cad\u002Fgcode\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fzzz2929\u002Fskills-zh-CN\u002Fblob\u002Fmain\u002Ftext-to-cad\u002Fgcode\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: gcode\ndescription: 通过编排真正的切片器 CLI，从 3D 网格文件生成、检查、试运行和静态验证纯 FDM“.gcode”。当 Codex 需要将“.stl”、“.obj”、未切片的“.3mf”、“.ply”、“.glb”或“.gltf”切片为打印机配置文件的 G 代码、发现本地切片器后端、检查网格是否已准备好切片或在任何特定于打印机的切换之前验证生成的 G 代码时使用。\n---\n# G-code\n\nProvenance: maintained in [earthtojake\u002Ftext-to-cad](https:\u002F\u002Fgithub.com\u002Fearthtojake\u002Ftext-to-cad).\nUse the installed local skill files as the runtime source of truth; the\nrepository link is only for provenance and release review.\n\nUse this skill for plain `.gcode` generation from mesh files. It is printer-agnostic and never uploads, starts, or packages print jobs.\n\n## Workflow\n\n1. Confirm the input is a supported mesh: `.stl`, `.obj`, unsliced `.3mf`, `.ply`, `.glb`, or `.gltf`.\n2. Require an explicit printer\u002Fprofile wrapper JSON. Do not invent real-printer profiles.\n3. Discover slicer backends when the backend is unknown:\n\n```bash\npython scripts\u002Fgcode_tool.py discover\n```\n\n4. Inspect the input:\n\n```bash\npython scripts\u002Fgcode_tool.py inspect --input path\u002Fto\u002Fmodel.stl --json\n```\n\n5. Dry-run the slicer command before executing:\n\n```bash\npython scripts\u002Fgcode_tool.py slice \\\n  --input path\u002Fto\u002Fmodel.stl \\\n  --output \u002Ftmp\u002Fmodel.gcode \\\n  --profile path\u002Fto\u002Fprofile.json \\\n  --backend auto \\\n  --dry-run\n```\n\n6. Execute only after the dry-run command and profile are appropriate:\n\n```bash\npython scripts\u002Fgcode_tool.py slice \\\n  --input path\u002Fto\u002Fmodel.stl \\\n  --output \u002Ftmp\u002Fmodel.gcode \\\n  --profile path\u002Fto\u002Fprofile.json \\\n  --backend auto \\\n  --execute\n```\n\n7. Validate the generated G-code:\n\n```bash\npython scripts\u002Fgcode_tool.py validate \\\n  --gcode \u002Ftmp\u002Fmodel.gcode \\\n  --profile path\u002Fto\u002Fprofile.json \\\n  --json\n```\n\n## Profile Contract\n\nEvery slice requires a wrapper profile JSON with an absolute native slicer profile path:\n\n```json\n{\n  \"backend\": \"orcaslicer\",\n  \"native_config\": \"\u002Fabsolute\u002Fpath\u002Fto\u002Fnative-slicer-profile\",\n  \"machine\": {\n    \"name\": \"Example Printer\",\n    \"bed_size_mm\": [180, 180],\n    \"z_height_mm\": 180,\n    \"motion_bounds_mm\": {\n      \"x\": [0, 180],\n      \"y\": [0, 180],\n      \"z\": [0, 180]\n    }\n  },\n  \"filament\": {\n    \"type\": \"PLA\",\n    \"nozzle_temp_c\": 220,\n    \"bed_temp_c\": 65\n  }\n}\n```\n\nThe wrapper supplies validation bounds and backend selection. `machine.motion_bounds_mm` is optional; omit it for the default `0..bed_size` and `0..z_height` bounds, or set it from a native printer profile when start\u002Fend G-code intentionally uses safe wipe\u002Fpurge positions outside the printable area. The native slicer profile remains the source of detailed process, printer, and filament behavior.\n\nFor OrcaSlicer, use `native_settings` and `native_filaments` when the real profile is split across machine, process, and filament JSON files. Keep `native_config` as an absolute path to the primary native profile for compatibility:\n\n```json\n{\n  \"backend\": \"orcaslicer\",\n  \"native_config\": \"\u002Fabsolute\u002Fpath\u002Fto\u002Fmachine-or-process.json\",\n  \"native_settings\": [\n    \"\u002Fabsolute\u002Fpath\u002Fto\u002Fmachine.json\",\n    \"\u002Fabsolute\u002Fpath\u002Fto\u002Fprocess.json\"\n  ],\n  \"native_filaments\": [\n    \"\u002Fabsolute\u002Fpath\u002Fto\u002Ffilament.json\"\n  ],\n  \"machine\": {\n    \"name\": \"Example Printer\",\n    \"bed_size_mm\": [180, 180],\n    \"z_height_mm\": 180\n  },\n  \"filament\": {\n    \"type\": \"PLA\",\n    \"nozzle_temp_c\": 220,\n    \"bed_temp_c\": 65\n  }\n}\n```\n\n## Backends And Inputs\n\nPreferred slicer backend order is `orcaslicer`, `prusa-slicer`, then `curaengine`. Prefer installing OrcaSlicer when no preferred backend is available; on macOS use `brew install --cask orcaslicer` and then rerun `discover`. The helper checks both `PATH` and the usual `\u002FApplications\u002FOrcaSlicer.app` cask location. Bambu Studio may be reported by discovery as available but is not preferred because its CLI export path has shown macOS instability.\n\nPass `.stl`, `.obj`, and unsliced `.3mf` directly to the slicer. Convert `.ply`, `.glb`, and `.gltf` to temporary STL at execution time with optional `trimesh`; if `trimesh` is unavailable, ask the user to install it or provide `.stl`, `.obj`, or unsliced `.3mf`.\n\nReject `.step`, `.stp`, `.dxf`, `.svg`, `.urdf`, and `.sdf` in v1. `inspect` and `slice` fail with a structured `remediation` object naming the skill and command that produce a sliceable mesh; use it instead of inferring a conversion workflow:\n\n- `.step`, `.stp`: boundary-representation CAD, not a mesh. Export an STL sidecar with `$cad` (`python scripts\u002Fexport \u003Cinput> --stl \u003Coutput>.stl`, or target the generator with `python scripts\u002Fexport \u003Cmodel>.step.py --stl \u003Coutput>.stl`), then slice the exported `.stl` here.\n- `.dxf`, `.svg`: 2D drawings with no 2D-to-mesh conversion in this toolchain. Model the 3D solid in `$cad` with `gen_step()` and export an STL sidecar, then slice that. If the part is a flat cut rather than a print, use `$sendcutsend` instead of this skill.\n- `.urdf`, `.sdf`: robot descriptions that reference per-link mesh files. Slice the referenced `.stl`\u002F`.obj` meshes one at a time; regenerate stale or missing ones from the owning CAD source with `$cad` first. Use `$urdf` or `$sdf` for the robot description itself.\n\nRead `references\u002Fslicer-backends.md` when backend behavior, profile expectations, or source links matter.\n\n## Validation\n\nAlways validate generated G-code before handing it to printer-specific workflows. The validator checks for non-empty content, temperature commands, movement commands, extrusion moves, XYZ bounds, and unknown command warnings.\n\nRead `references\u002Fgcode-validation.md` when interpreting validation output or deciding whether a warning is acceptable.\n\n## Bambu Boundary\n\nThis skill generates plain `.gcode` only. It does not create Bambu `.gcode.3mf` archives and does not contact printers. For Bambu upload\u002Fstart workflows, hand off the validated plain `.gcode` to `$bambu-labs`. Let `$bambu-labs` choose the printer-specific LAN handoff, such as an A1 Mini template project or an explicitly enabled bambox project package.\n","# G-code\n\nProvenance: maintained in [earthtojake\u002Ftext-to-cad](https:\u002F\u002Fgithub.com\u002Fearthtojake\u002Ftext-to-cad).\nUse the installed local skill files as the runtime source of truth; the\nrepository link is only for provenance and release review.\n\nUse this skill for plain `.gcode` generation from mesh files. It is printer-agnostic and never uploads, starts, or packages print jobs.\n\n## Workflow\n\n1. Confirm the input is a supported mesh: `.stl`, `.obj`, unsliced `.3mf`, `.ply`, `.glb`, or `.gltf`.\n2. Require an explicit printer\u002Fprofile wrapper JSON. Do not invent real-printer profiles.\n3. Discover slicer backends when the backend is unknown:\n\n```bash\npython scripts\u002Fgcode_tool.py discover\n```\n\n4. Inspect the input:\n\n```bash\npython scripts\u002Fgcode_tool.py inspect --input path\u002Fto\u002Fmodel.stl --json\n```\n\n5. Dry-run the slicer command before executing:\n\n```bash\npython scripts\u002Fgcode_tool.py slice \\\n  --input path\u002Fto\u002Fmodel.stl \\\n  --output \u002Ftmp\u002Fmodel.gcode \\\n  --profile path\u002Fto\u002Fprofile.json \\\n  --backend auto \\\n  --dry-run\n```\n\n6. Execute only after the dry-run command and profile are appropriate:\n\n```bash\npython scripts\u002Fgcode_tool.py slice \\\n  --input path\u002Fto\u002Fmodel.stl \\\n  --output \u002Ftmp\u002Fmodel.gcode \\\n  --profile path\u002Fto\u002Fprofile.json \\\n  --backend auto \\\n  --execute\n```\n\n7. Validate the generated G-code:\n\n```bash\npython scripts\u002Fgcode_tool.py validate \\\n  --gcode \u002Ftmp\u002Fmodel.gcode \\\n  --profile path\u002Fto\u002Fprofile.json \\\n  --json\n```\n\n## Profile Contract\n\nEvery slice requires a wrapper profile JSON with an absolute native slicer profile path:\n\n```json\n{\n  \"backend\": \"orcaslicer\",\n  \"native_config\": \"\u002Fabsolute\u002Fpath\u002Fto\u002Fnative-slicer-profile\",\n  \"machine\": {\n    \"name\": \"Example Printer\",\n    \"bed_size_mm\": [180, 180],\n    \"z_height_mm\": 180,\n    \"motion_bounds_mm\": {\n      \"x\": [0, 180],\n      \"y\": [0, 180],\n      \"z\": [0, 180]\n    }\n  },\n  \"filament\": {\n    \"type\": \"PLA\",\n    \"nozzle_temp_c\": 220,\n    \"bed_temp_c\": 65\n  }\n}\n```\n\nThe wrapper supplies validation bounds and backend selection. `machine.motion_bounds_mm` is optional; omit it for the default `0..bed_size` and `0..z_height` bounds, or set it from a native printer profile when start\u002Fend G-code intentionally uses safe wipe\u002Fpurge positions outside the printable area. The native slicer profile remains the source of detailed process, printer, and filament behavior.\n\nFor OrcaSlicer, use `native_settings` and `native_filaments` when the real profile is split across machine, process, and filament JSON files. Keep `native_config` as an absolute path to the primary native profile for compatibility:\n\n```json\n{\n  \"backend\": \"orcaslicer\",\n  \"native_config\": \"\u002Fabsolute\u002Fpath\u002Fto\u002Fmachine-or-process.json\",\n  \"native_settings\": [\n    \"\u002Fabsolute\u002Fpath\u002Fto\u002Fmachine.json\",\n    \"\u002Fabsolute\u002Fpath\u002Fto\u002Fprocess.json\"\n  ],\n  \"native_filaments\": [\n    \"\u002Fabsolute\u002Fpath\u002Fto\u002Ffilament.json\"\n  ],\n  \"machine\": {\n    \"name\": \"Example Printer\",\n    \"bed_size_mm\": [180, 180],\n    \"z_height_mm\": 180\n  },\n  \"filament\": {\n    \"type\": \"PLA\",\n    \"nozzle_temp_c\": 220,\n    \"bed_temp_c\": 65\n  }\n}\n```\n\n## Backends And Inputs\n\nPreferred slicer backend order is `orcaslicer`, `prusa-slicer`, then `curaengine`. Prefer installing OrcaSlicer when no preferred backend is available; on macOS use `brew install --cask orcaslicer` and then rerun `discover`. The helper checks both `PATH` and the usual `\u002FApplications\u002FOrcaSlicer.app` cask location. Bambu Studio may be reported by discovery as available but is not preferred because its CLI export path has shown macOS instability.\n\nPass `.stl`, `.obj`, and unsliced `.3mf` directly to the slicer. Convert `.ply`, `.glb`, and `.gltf` to temporary STL at execution time with optional `trimesh`; if `trimesh` is unavailable, ask the user to install it or provide `.stl`, `.obj`, or unsliced `.3mf`.\n\nReject `.step`, `.stp`, `.dxf`, `.svg`, `.urdf`, and `.sdf` in v1. `inspect` and `slice` fail with a structured `remediation` object naming the skill and command that produce a sliceable mesh; use it instead of inferring a conversion workflow:\n\n- `.step`, `.stp`: boundary-representation CAD, not a mesh. Export an STL sidecar with `$cad` (`python scripts\u002Fexport \u003Cinput> --stl \u003Coutput>.stl`, or target the generator with `python scripts\u002Fexport \u003Cmodel>.step.py --stl \u003Coutput>.stl`), then slice the exported `.stl` here.\n- `.dxf`, `.svg`: 2D drawings with no 2D-to-mesh conversion in this toolchain. Model the 3D solid in `$cad` with `gen_step()` and export an STL sidecar, then slice that. If the part is a flat cut rather than a print, use `$sendcutsend` instead of this skill.\n- `.urdf`, `.sdf`: robot descriptions that reference per-link mesh files. Slice the referenced `.stl`\u002F`.obj` meshes one at a time; regenerate stale or missing ones from the owning CAD source with `$cad` first. Use `$urdf` or `$sdf` for the robot description itself.\n\nRead `references\u002Fslicer-backends.md` when backend behavior, profile expectations, or source links matter.\n\n## Validation\n\nAlways validate generated G-code before handing it to printer-specific workflows. The validator checks for non-empty content, temperature commands, movement commands, extrusion moves, XYZ bounds, and unknown command warnings.\n\nRead `references\u002Fgcode-validation.md` when interpreting validation output or deciding whether a warning is acceptable.\n\n## Bambu Boundary\n\nThis skill generates plain `.gcode` only. It does not create Bambu `.gcode.3mf` archives and does not contact printers. For Bambu upload\u002Fstart workflows, hand off the validated plain `.gcode` to `$bambu-labs`. Let `$bambu-labs` choose the printer-specific LAN handoff, such as an A1 Mini template project or an explicitly enabled bambox project package.\n",{"name":5,"description":7},"main","9f046539cc7b77fcc2cdcc31dee08c104218a554","text-to-cad\u002Fgcode","https:\u002F\u002Fgithub.com\u002Fzzz2929\u002Fskills-zh-CN","https:\u002F\u002Fgithub.com\u002Fzzz2929","2026-09-29 15:32:20",{"source":8,"skillName":5,"commands":32,"prompt":42,"zipAvailable":43},[33,36,39],{"tool":34,"command":35},"npx","npx skills add zzz2929\u002Fskills-zh-CN --skill gcode",{"tool":37,"command":38},"bunx","bunx skills add zzz2929\u002Fskills-zh-CN --skill gcode",{"tool":40,"command":41},"pnpm","pnpm dlx skills add zzz2929\u002Fskills-zh-CN --skill gcode","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fzzz2929\u002Fskills-zh-CN\u002Fblob\u002Fmain\u002Ftext-to-cad\u002Fgcode\u002FSKILL.md",true,[45,51,55,59,63],{"path":46,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":49,"sourceHtmlUrl":50},"agents\u002Fopenai.yaml","REFERENCE","参考文档",179,"https:\u002F\u002Fgithub.com\u002Fzzz2929\u002Fskills-zh-CN\u002Fblob\u002Fmain\u002Ftext-to-cad\u002Fgcode\u002Fagents\u002Fopenai.yaml",{"path":52,"resourceType":52,"resourceTypeDesc":53,"sizeBytes":54,"sourceHtmlUrl":16},"LICENSE","许可证",1074,{"path":56,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":57,"sourceHtmlUrl":58},"references\u002Fgcode-validation.md",2232,"https:\u002F\u002Fgithub.com\u002Fzzz2929\u002Fskills-zh-CN\u002Fblob\u002Fmain\u002Ftext-to-cad\u002Fgcode\u002Freferences\u002Fgcode-validation.md",{"path":60,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":61,"sourceHtmlUrl":62},"references\u002Fslicer-backends.md",3824,"https:\u002F\u002Fgithub.com\u002Fzzz2929\u002Fskills-zh-CN\u002Fblob\u002Fmain\u002Ftext-to-cad\u002Fgcode\u002Freferences\u002Fslicer-backends.md",{"path":64,"resourceType":65,"resourceTypeDesc":66,"sizeBytes":67,"sourceHtmlUrl":68},"scripts\u002Fgcode_tool.py","SCRIPT","脚本",29375,"https:\u002F\u002Fgithub.com\u002Fzzz2929\u002Fskills-zh-CN\u002Fblob\u002Fmain\u002Ftext-to-cad\u002Fgcode\u002Fscripts\u002Fgcode_tool.py",[70,77,84,91,98,106],{"skillNo":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":20},"01M79SG5BDV2ZDS4QA238B9ZCR","vercel-react-view-transitions","使用 React 的视图转换 API（`\u003CViewTransition>` 组件、`addTransitionType` 和 CSS 视图转换伪元素）实现流畅、原生感觉的动画的指南。每当用户想要添加页面转换、为路线更改设置动画、创建共享元素动画、为组件的进入\u002F退出设置动画、为列表重新排序设置动画、实现定向（向前\u002F向后）导航动画或在 Next.js 中集成视图转换时，请使用此技能。当用户提及视图转换、startViewTransition、ViewTransition、转换类型或询问有关在 React 中的 UI 状态之间设置动画而无需第三方动画库时也可使用。","https:\u002F\u002Fgithub.com\u002Fzzz2929\u002Fskills-zh-CN\u002Fblob\u002Fmain\u002Fvercel-labs\u002Freact-view-transitions\u002FSKILL.md",[],[],{"skillNo":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":20},"01M79SG04BFAVYZ2C3RQ7YX9C6","vercel-react-native-skills","React Native和Expo构建高性能移动应用程序的最佳实践。在构建React Native组件、优化列表性能、实现动画或使用本机模块时使用。涉及React Native、Expo、移动性能或本机平台API的任务的触发器。","https:\u002F\u002Fgithub.com\u002Fzzz2929\u002Fskills-zh-CN\u002Fblob\u002Fmain\u002Fvercel-labs\u002Freact-native-skills\u002FSKILL.md",[],[],{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":20},"01M79SFVFWYQKG0V95RXM3MEAW","vercel-react-best-practices","Vercel Engineering的React和Next.js性能优化指南。在编写、审查或重构React\u002FNext.js代码时，应使用此技能，以确保最佳性能模式。涉及React组件、Next.js页面、数据获取、捆绑优化或性能改进的任务的触发器。","https:\u002F\u002Fgithub.com\u002Fzzz2929\u002Fskills-zh-CN\u002Fblob\u002Fmain\u002Fvercel-labs\u002Freact-best-practices\u002FSKILL.md",[],[],{"skillNo":92,"name":93,"nameZh":6,"description":94,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":95,"categories":96,"keywords":97,"publishedAt":20},"01M79SFJXD83X39ZFV0SR8Z6TY","vercel-composition-patterns","可扩展的React组合模式。在重构具有布尔属性增殖的组件、构建灵活的组件库或设计可重用的API时使用。涉及复合组件、渲染道具、上下文提供者或组件架构的任务的触发器。包括React 19 API变更。","https:\u002F\u002Fgithub.com\u002Fzzz2929\u002Fskills-zh-CN\u002Fblob\u002Fmain\u002Fvercel-labs\u002Fcomposition-patterns\u002FSKILL.md",[],[],{"skillNo":99,"name":100,"nameZh":6,"description":101,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":102,"sourceHtmlUrl":103,"categories":104,"keywords":105,"publishedAt":20},"01M79SEC8F4BW45HKSK7VSYQ1Y","ui-styling","使用 shadcn\u002Fui 组件（基于 Radix UI + Tailwind 构建）、Tailwind CSS 实用优先样式和基于画布的视觉设计创建美观、可访问的用户界面。在构建用户界面、实现设计系统、创建响应式布局、添加可访问组件（对话框、下拉菜单、表单、表格）、自定义主题和颜色、实现深色模式、生成视觉设计和海报或跨应用程序建立一致的样式模式时使用。","https:\u002F\u002Fgithub.com\u002Fzzz2929\u002Fskills-zh-CN\u002Fblob\u002Fmain\u002Fui-ux-pro-max\u002Fui-styling\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fzzz2929\u002Fskills-zh-CN\u002Fblob\u002Fmain\u002Fui-ux-pro-max\u002Fui-styling\u002FSKILL.md",[],[],{"skillNo":107,"name":108,"nameZh":6,"description":109,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":110,"categories":111,"keywords":112,"publishedAt":20},"01M79SE0JWV6111HE4M0A5K6XW","design","“综合设计技能：品牌标识、设计标记、UI 样式、徽标生成（55 种样式、Gemini 或 Atlas Cloud AI）、企业形象程序（50 个可交付成果、CIP 模型）、HTML 演示文稿（Chart.js）、横幅设计（22 种样式、社交\u002F广告\u002F网页\u002F打印）、图标设计（15 种样式、SVG、Gemini 3.1 Pro）、社交照片（HTML→屏幕截图、多平台）。操作：设计徽标、创建 CIP、生成模型、构建幻灯片、设计横幅、生成图标、创建社交照片、社交媒体图像、品牌标识、设计系统：Facebook、Twitter、LinkedIn、YouTube、Instagram、Pinterest、TikTok、Threads、Google Ads。”","https:\u002F\u002Fgithub.com\u002Fzzz2929\u002Fskills-zh-CN\u002Fblob\u002Fmain\u002Fui-ux-pro-max\u002Fdesign\u002FSKILL.md",[],[]]