[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M79SC2ZWR40FF7ZHSAGH57R6":3,"skill-same:01M79SC2ZWR40FF7ZHSAGH57R6":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},"01M79SC2ZWR40FF7ZHSAGH57R6","dfam-check",null,"根据增材制造设计 (DfAM) 规则测量网格文件，并报告每个流程（FDM、SLS、SLA\u002FDLP、金属 PBF、MJF）的适印性结果。当用户询问零件是否可打印，需要对“.stl”、“.obj”、“.ply”或“.3mf”网格进行悬垂\u002F壁厚\u002F支撑分析，需要构建方向建议，或者需要在使用“$gcode”切片或使用“$cad”重新生成几何图形之前获得 DfAM 重新设计指导时使用。","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\u002Fdfam-check\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fzzz2929\u002Fskills-zh-CN\u002Fblob\u002Fmain\u002Ftext-to-cad\u002Fdfam-check\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: dfam-check\ndescription: 根据增材制造设计 (DfAM) 规则测量网格文件，并报告每个流程（FDM、SLS、SLA\u002FDLP、金属 PBF、MJF）的适印性结果。当用户询问零件是否可打印，需要对“.stl”、“.obj”、“.ply”或“.3mf”网格进行悬垂\u002F壁厚\u002F支撑分析，需要构建方向建议，或者需要在使用“$gcode”切片或使用“$cad”重新生成几何图形之前获得 DfAM 重新设计指导时使用。\n---\n# DfAM Check\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 to produce conservative, evidence-backed DfAM reports for mesh\nfiles before slicing or printing. It measures geometry facts locally and\ncompares them against per-process design limits; it never slices, uploads, or\nstarts print jobs.\n\n## Geometry Inspection\n\nUse `scripts\u002Fdfam_tool.py` in the active project Python environment for all\ngeometry facts (requires `trimesh`, `numpy`, `rtree`). The tool is fact-only:\nit reports measurements and never emits pass\u002Ffail or readiness statuses.\nComparisons and verdicts belong to this workflow. Do not estimate wall\nthickness, overhang angles, or support volume by eye or from renders when the\ntool can measure them.\n\n```bash\npython scripts\u002Fdfam_tool.py measure part.stl --angle-limit 45\npython scripts\u002Fdfam_tool.py orientations part.stl --angle-limit 45\n```\n\nSet `--angle-limit` to the target process's self-supporting angle from\n`references\u002Fprocess-limits.md` before measuring, and re-run when the target\nprocess changes: the aggregate support-area facts are binned against it.\n\nSTEP\u002FSTP input is boundary-representation CAD, not a mesh. When the `$cad`\nskill is installed, export an STL sidecar with it first, then measure the STL\nhere. Report that remediation instead of attempting raw STEP parsing.\n\n## Workflow\n\n1. Collect print intent: target process, material, layer height, and any\n   machine or material datasheet the user can provide. If the process is\n   unknown, measure once with the default 45° limit, then present findings\n   per candidate process rather than guessing a single verdict.\n2. Read `references\u002Fprocess-limits.md` and select the limit column for the\n   target process. A user-provided machine\u002Fmaterial datasheet overrides the\n   defaults; cite whichever source is used for every comparison.\n3. Run `measure` on the exact upload file. Do not inspect only a generator\n   script, source CAD model, or console summary of the file.\n4. Run `orientations` when the process requires supports and the measured\n   support area is nonzero. Report any candidate that materially reduces\n   support area, with its build-height tradeoff.\n5. Compare each measured fact to the cited limit and report findings with\n   restrained status labels:\n   - `✅ pass`: the measured fact satisfies the cited limit.\n   - `❌ fail`: a measured fact directly violates the cited limit.\n   - `❓ need more info`: missing process context, unmeasured geometry,\n     sampling too sparse to trust, or tool limitations.\n6. Order findings by severity: watertightness first (blocks slicing for\n   every process), then wall thickness, then overhangs\u002Fsupports, then\n   orientation and cost signals.\n\n## Comparison\n\nCompare only trustworthy pairs of evidence.\n\n- Cite the limit source (process-limits table row, or the user's datasheet\n  field) and the measured fact (JSON field path) for every finding.\n- Treat `p05_mm` below the wall-thickness limit as a violation even when\n  `min_mm` alone could be a sampling outlier; report both values.\n- On an assembly, `wall_thickness` reports `body_count` and a `per_body`\n  breakdown. Attribute a violation to the body it belongs to; a thin figure\n  pooled across bodies is not a finding against the part as a whole.\n- Do not apply support-angle findings to powder processes (SLS, MJF); the\n  relevant powder-process check is trapped-volume powder escape, which this\n  tool does not yet measure — report that as `❓ need more info` when\n  enclosed cavities are likely.\n- Do not silently rescale geometry. `scale.units_suspect` is measured from\n  the bounding-box diagonal: when it is `true`, the source is probably in\n  meters or inches, every down-facing face reads as resting on the plate, and\n  overhang and support figures of 0.0 mean nothing. Report a unit\u002Fscale\n  finding and ask the user to confirm units before comparing anything against\n  a material limit.\n- Support-volume ratios are coarse upper bounds; report them as cost\n  signals, not hard failures, unless the user has set an explicit budget.\n\n## Redesign Handoff\n\nFor every `❌ fail`, include a concrete, plain-language redesign instruction\nwith target numbers (for example \"thicken the wall at [12.4, 3.0, 8.1] from\n0.6 mm to ≥1.2 mm\" or \"chamfer the overhang at [23.3, 10.0, 52.0] to ≥45°\").\nWhen the `$cad` skill is installed, offer to apply the redesign instructions\nwith it and re-measure the regenerated geometry here, repeating until no\n`❌ fail` findings remain. When `$cad-viewer` is installed, hand the measured\nfile path(s) to it so the user can inspect the findings visually.\n","# DfAM Check\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 to produce conservative, evidence-backed DfAM reports for mesh\nfiles before slicing or printing. It measures geometry facts locally and\ncompares them against per-process design limits; it never slices, uploads, or\nstarts print jobs.\n\n## Geometry Inspection\n\nUse `scripts\u002Fdfam_tool.py` in the active project Python environment for all\ngeometry facts (requires `trimesh`, `numpy`, `rtree`). The tool is fact-only:\nit reports measurements and never emits pass\u002Ffail or readiness statuses.\nComparisons and verdicts belong to this workflow. Do not estimate wall\nthickness, overhang angles, or support volume by eye or from renders when the\ntool can measure them.\n\n```bash\npython scripts\u002Fdfam_tool.py measure part.stl --angle-limit 45\npython scripts\u002Fdfam_tool.py orientations part.stl --angle-limit 45\n```\n\nSet `--angle-limit` to the target process's self-supporting angle from\n`references\u002Fprocess-limits.md` before measuring, and re-run when the target\nprocess changes: the aggregate support-area facts are binned against it.\n\nSTEP\u002FSTP input is boundary-representation CAD, not a mesh. When the `$cad`\nskill is installed, export an STL sidecar with it first, then measure the STL\nhere. Report that remediation instead of attempting raw STEP parsing.\n\n## Workflow\n\n1. Collect print intent: target process, material, layer height, and any\n   machine or material datasheet the user can provide. If the process is\n   unknown, measure once with the default 45° limit, then present findings\n   per candidate process rather than guessing a single verdict.\n2. Read `references\u002Fprocess-limits.md` and select the limit column for the\n   target process. A user-provided machine\u002Fmaterial datasheet overrides the\n   defaults; cite whichever source is used for every comparison.\n3. Run `measure` on the exact upload file. Do not inspect only a generator\n   script, source CAD model, or console summary of the file.\n4. Run `orientations` when the process requires supports and the measured\n   support area is nonzero. Report any candidate that materially reduces\n   support area, with its build-height tradeoff.\n5. Compare each measured fact to the cited limit and report findings with\n   restrained status labels:\n   - `✅ pass`: the measured fact satisfies the cited limit.\n   - `❌ fail`: a measured fact directly violates the cited limit.\n   - `❓ need more info`: missing process context, unmeasured geometry,\n     sampling too sparse to trust, or tool limitations.\n6. Order findings by severity: watertightness first (blocks slicing for\n   every process), then wall thickness, then overhangs\u002Fsupports, then\n   orientation and cost signals.\n\n## Comparison\n\nCompare only trustworthy pairs of evidence.\n\n- Cite the limit source (process-limits table row, or the user's datasheet\n  field) and the measured fact (JSON field path) for every finding.\n- Treat `p05_mm` below the wall-thickness limit as a violation even when\n  `min_mm` alone could be a sampling outlier; report both values.\n- On an assembly, `wall_thickness` reports `body_count` and a `per_body`\n  breakdown. Attribute a violation to the body it belongs to; a thin figure\n  pooled across bodies is not a finding against the part as a whole.\n- Do not apply support-angle findings to powder processes (SLS, MJF); the\n  relevant powder-process check is trapped-volume powder escape, which this\n  tool does not yet measure — report that as `❓ need more info` when\n  enclosed cavities are likely.\n- Do not silently rescale geometry. `scale.units_suspect` is measured from\n  the bounding-box diagonal: when it is `true`, the source is probably in\n  meters or inches, every down-facing face reads as resting on the plate, and\n  overhang and support figures of 0.0 mean nothing. Report a unit\u002Fscale\n  finding and ask the user to confirm units before comparing anything against\n  a material limit.\n- Support-volume ratios are coarse upper bounds; report them as cost\n  signals, not hard failures, unless the user has set an explicit budget.\n\n## Redesign Handoff\n\nFor every `❌ fail`, include a concrete, plain-language redesign instruction\nwith target numbers (for example \"thicken the wall at [12.4, 3.0, 8.1] from\n0.6 mm to ≥1.2 mm\" or \"chamfer the overhang at [23.3, 10.0, 52.0] to ≥45°\").\nWhen the `$cad` skill is installed, offer to apply the redesign instructions\nwith it and re-measure the regenerated geometry here, repeating until no\n`❌ fail` findings remain. When `$cad-viewer` is installed, hand the measured\nfile path(s) to it so the user can inspect the findings visually.\n",{"name":5,"description":7},"main","9f046539cc7b77fcc2cdcc31dee08c104218a554","text-to-cad\u002Fdfam-check","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 dfam-check",{"tool":37,"command":38},"bunx","bunx skills add zzz2929\u002Fskills-zh-CN --skill dfam-check",{"tool":40,"command":41},"pnpm","pnpm dlx skills add zzz2929\u002Fskills-zh-CN --skill dfam-check","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fzzz2929\u002Fskills-zh-CN\u002Fblob\u002Fmain\u002Ftext-to-cad\u002Fdfam-check\u002FSKILL.md",true,[45,51,55,59,63],{"path":46,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":49,"sourceHtmlUrl":50},"agents\u002Fopenai.yaml","REFERENCE","参考文档",209,"https:\u002F\u002Fgithub.com\u002Fzzz2929\u002Fskills-zh-CN\u002Fblob\u002Fmain\u002Ftext-to-cad\u002Fdfam-check\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\u002Fprocess-limits.md",3089,"https:\u002F\u002Fgithub.com\u002Fzzz2929\u002Fskills-zh-CN\u002Fblob\u002Fmain\u002Ftext-to-cad\u002Fdfam-check\u002Freferences\u002Fprocess-limits.md",{"path":60,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":61,"sourceHtmlUrl":62},"requirements.txt",367,"https:\u002F\u002Fgithub.com\u002Fzzz2929\u002Fskills-zh-CN\u002Fblob\u002Fmain\u002Ftext-to-cad\u002Fdfam-check\u002Frequirements.txt",{"path":64,"resourceType":65,"resourceTypeDesc":66,"sizeBytes":67,"sourceHtmlUrl":68},"scripts\u002Fdfam_tool.py","SCRIPT","脚本",14089,"https:\u002F\u002Fgithub.com\u002Fzzz2929\u002Fskills-zh-CN\u002Fblob\u002Fmain\u002Ftext-to-cad\u002Fdfam-check\u002Fscripts\u002Fdfam_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",[],[]]