sendcutsend
Compare original and translation side by side
🇺🇸
Original
English🇨🇳
Translation
ChineseSendCutSend
SendCutSend
Use this skill to produce conservative, evidence-backed SendCutSend preflight reports for DXF and STEP/STP files.
Treat SendCutSend's ordering guide, catalog JSON, and specs JSON as evidence feeds, not stable APIs. Field names, types, and coverage may vary. Do not turn missing, unparsable, , or conflicting source data into a pass or fail. Use scripts only to fetch source files or measure specific file facts; write the final report from explicit comparisons.
N/A使用该skill为DXF和STEP/STP文件生成严谨、有依据的SendCutSend预检报告。
将SendCutSend的订购指南、目录JSON和规格JSON视为数据源,而非稳定API。字段名称、类型及覆盖范围可能有所不同。请勿将缺失、无法解析、或冲突的源数据判定为通过或不通过。仅使用脚本获取源文件或测量特定文件信息;最终报告需基于明确的对比结果撰写。
N/AGeometry Inspection
几何检测
Use the active project Python environment for local inspection scripts. If the skill is available, use it first for STEP/STP/DXF geometry inspection, measurement, and validation workflows, then add any SendCutSend-specific targeted measurements that are still missing. Use for STEP/STP inspection and for DXF inspection when geometry facts are required. Do not use raw text parsing or alternate geometry backends for geometry facts.
$cadbuild123d.import_stepbuild123d.ezdxfIf this workflow creates or updates a DXF, STEP, or STP upload candidate, hand the explicit file path to when available; checks/reuses a live viewer and returns a link. For visual feedback on CAD/DXF geometry, prefer snapshots over opening the viewer manually or using Playwright. Use still snapshots only; SendCutSend review should not generate GIFs.
$render$render$render使用当前项目的Python环境执行本地检测脚本。若 skill可用,优先使用它完成STEP/STP/DXF文件的几何检测、测量及验证流程,再补充任何仍缺失的SendCutSend专项测量内容。当需要获取几何信息时,使用检测STEP/STP文件,使用检测DXF文件。请勿使用原始文本解析或其他几何后端获取几何信息。
$cadbuild123d.import_stepbuild123d.ezdxf若该流程创建或更新了DXF、STEP或STP上传候选文件,在可用时,将明确的文件路径传递给它;会检查/复用实时查看器并返回链接。如需CAD/DXF几何结构的视觉反馈,优先使用快照,而非手动打开查看器或使用Playwright。仅使用静态快照;SendCutSend审核不应生成GIF文件。
$render$render$renderSource Refresh
源文件刷新
Before each review, download or refresh the three SendCutSend source files:
bash
python scripts/download_sources.pyThe downloader writes , , , and . The cache is fresh for 24 hours. If the user explicitly asks to skip cache, force a fresh fetch:
references/generated/sendcutsend-ordering-guide.mdreferences/generated/sendcutsend-catalog.jsonreferences/generated/sendcutsend-specs.jsonreferences/generated/sources-manifest.jsonbash
python scripts/download_sources.py --skip-cacheUse the manifest's , , , and JSON values in the source bibliography when helpful. If a source cannot be fetched and only stale files are available, report that limitation and avoid ready verdicts for dependent checks.
fetched_atcache_expires_atsha256_meta每次审核前,下载或刷新三个SendCutSend源文件:
bash
python scripts/download_sources.py下载器会生成、、和文件。缓存有效期为24小时。若用户明确要求跳过缓存,强制获取最新版本:
references/generated/sendcutsend-ordering-guide.mdreferences/generated/sendcutsend-catalog.jsonreferences/generated/sendcutsend-specs.jsonreferences/generated/sources-manifest.jsonbash
python scripts/download_sources.py --skip-cache当有帮助时,在源文献中使用清单的、、及JSON的值。若无法获取源文件且仅存在过期文件,需报告此限制,并避免对依赖该检查的内容做出就绪判定。
fetched_atcache_expires_atsha256_metaWorkflow
工作流程
- Collect order intent.
- Prefer DXF for laser sheet cutting and 2D sheet profiles.
- Prefer STEP/STP for CNC routing and 3D model upload workflows.
- Record file type, intended process, material/SKU, thickness, quantity, services, finish, and hardware.
- If order context is missing or ambiguous, inspect enough source data to present concrete options, then ask the user to confirm before writing a readiness verdict. Include candidate SKUs/materials/thicknesses/services with relevant source links; include images and
photo_urllinks from the specs JSON when available.learn_more_url
- Read , run the source downloader, then inspect the generated source files directly. Normalize source facts defensively: parse numeric strings, size strings,
references/official-sources.md, missing fields, mixed types, and absent service arrays into explicit notes.N/A - Inspect the exact upload file with when available and with targeted Python/
$cadfor any missing facts. Do not inspect only the source generator, CAD model, or generator console summary.build123d- DXF: measure units, bounds, layers, entity types, open/duplicate geometry, unsupported annotations, candidate holes/circles, linework stats, bend-line candidates, bend-to-cut distances, bend-adjacent cut geometry, local flange depths, and degenerate zero-area contours as needed for the selected service.
- STEP/STP: measure parseability, units hints, solid/surface signals, bounding box, shell/body signals, validity, sheet thickness where available, cylindrical bend-face radii where bending is in scope, and limitations as needed for the selected service.
- Keep each inspection script fact-only. It may report measurements, parse errors, and limitations, but it must not emit pass/fail/readiness statuses.
- Select source records by evidence quality.
- Use exact SKU as the only authoritative catalog/spec join.
- If only material and thickness are provided, use a selected material only when the candidate match is unique and exact enough; otherwise list candidates with links/images from the source records and ask the user to choose.
- Use the catalog JSON for orderability: stock, cutting process, available services, size limits, hardware, and finishes.
- Use the specs JSON for engineering values: tolerances, holes, bridges, bending, tapping, countersinking, hardware insertion, finishing, and material properties.
- Use the ordering guide for plain-language workflow and general file-format rules.
- 收集订单意向。
- 激光板材切割和2D板材轮廓优先使用DXF格式。
- CNC铣削和3D模型上传流程优先使用STEP/STP格式。
- 记录文件类型、预期工艺、材料/SKU、厚度、数量、服务、表面处理及硬件信息。
- 若订单上下文缺失或不明确,需检查足够的源数据以提供具体选项,然后请用户确认后再撰写就绪判定。包含候选SKU/材料/厚度/服务及相关源链接;若规格JSON中有图片和
photo_url链接,也需一并包含。learn_more_url
- 阅读,运行源文件下载器,然后直接检查生成的源文件。谨慎标准化源数据:将数字字符串、尺寸字符串、
references/official-sources.md、缺失字段、混合类型及缺失服务数组转换为明确说明。N/A - 若可用,使用它检查上传文件的具体内容;若有缺失信息,使用针对性的Python/
$cad工具补充。请勿仅检查源生成器、CAD模型或生成器控制台摘要。build123d- DXF:根据所选服务的需要,测量单位、边界、图层、实体类型、开放/重复几何结构、不支持的注释、候选孔/圆、线条统计、折弯线候选、折弯与切割距离、折弯附近的切割几何结构、局部法兰深度及退化零面积轮廓。
- STEP/STP:根据所选服务的需要,测量可解析性、单位提示、实体/曲面信号、边界框、壳/实体信号、有效性、可用的板材厚度、涉及折弯时的圆柱折弯面半径及限制条件。
- 每个检测脚本仅记录事实。可报告测量结果、解析错误及限制条件,但不得输出通过/不通过/就绪状态。
- 依据证据质量选择源记录。
- 仅使用精确SKU作为目录/规格关联的唯一权威依据。
- 若仅提供材料和厚度,仅当候选匹配唯一且足够精确时才选择该材料;否则列出候选选项及源记录中的链接/图片,并请用户选择。
- 使用目录JSON确认可订购性:库存、切割工艺、可用服务、尺寸限制、硬件及表面处理。
- 使用规格JSON获取工程参数:公差、孔、桥接、折弯、攻丝、沉孔、硬件安装、表面处理及材料属性。
- 使用订购指南获取通俗易懂的工作流程及通用文件格式规则。
Comparison
对比分析
Compare only trustworthy pairs of evidence.
- Determine whether a check applies.
- Cite the source field path or guide section.
- Cite the measured file fact.
- Compare only when both the source requirement and measured file fact are available and trustworthy.
- If a needed measurement is missing or risky, write a small targeted /
build123dinspector for that specific geometry fact.ezdxf - Treat every measured upload risk, manufacturability issue, or cited requirement violation as an error for now. Do not infer any alternate SendCutSend UI classification.
- For DXF units, inspect , header extents, measured bounds, and order context together. If
$INSUNITSis missing, unsupported, or not one of the SendCutSend guide's expected DXF unit codes ($INSUNITSinches or1mm), report a unit/scale error and recommend re-exporting or confirming units before applying size-, flange-, or material-specific comparisons. Do not silently rescale geometry or use an uncertain scale to issue material-specific pass/fail checks.4 - For 2D files with bend lines, check flange length locally along every bend line. Measure the nearest cut/free edge on both sides of each bend at each span or sample point, including notches, slots, gaps, split tabs, and cutouts that interrupt the bend span or create a local free edge. Compare the minimum local flange depth to the selected SKU's and
bending_specs.min_flange_length_before_bend. Do not apply flange-length limits to ordinary enclosed holes or interior cutouts unless a cited source gives a hole-to-bend or feature-to-bend rule for that service; report those separately with centerline-to-bend or edge-to-bend measurements as the cited rule requires. Do not treat nearby bend-adjacent cut geometry as only corner relief unless the remaining local flange still passes the flange-length minimum. If any local flange depth is below the SKU minimum, reportbending_specs.min_flange_length_after_bend. Do not rely on aggregate source-level values when exported geometry has local cutouts, interrupted bends, split bend segments, reliefs, tabs, or unsupported regions.❌ fail - Keep bend findings separate by physical cause. Do not collapse bend-adjacent geometry into a generic flange failure. Report distinct rows for minimum flange/contact length errors, bend line or die-area geometry crossings, insufficient bend contact/support from nearby free edges or cutouts, bend lines that do not span the bent region, split/common-axis bend segments, and cut geometry touching or crossing bend lines. If a SendCutSend source does not expose the exact die-area/contact threshold, cite the measured file fact as direct file inspection and mark the source-limited comparison explicitly.
- For STEP/STP bent parts, inspect bend radii when the model contains sheet-metal bend geometry or the intended service includes bending. Extract cylindrical or toroidal bend faces and their radii with /
$cad/OCP where possible, group repeated bend radii, and compare them to the selected SKU'sbuild123dorbending_specs.effective_bend_radius. If the selected material/SKU is unknown, report the measured bend-radius set and ask for material/thickness before readiness verdicts. If measured radii conflict with the selected SKU tooling radius, report a bend-radius mismatch error.bending_specs.bend_radius
Report with restrained status labels:
- : the measured file fact satisfies the cited current requirement.
✅ pass - : a measured upload risk, manufacturability issue, or direct measured violation of a cited current requirement.
❌ fail - : missing context, missing source evidence, unmeasured geometry, source conflicts, or tool limitations.
❓ need more info
仅对比可信的证据对。
- 判断检查是否适用。
- 引用源字段路径或指南章节。
- 引用测量得到的文件信息。
- 仅当源要求和测量得到的文件信息均可用且可信时才进行对比。
- 若所需测量信息缺失或存在风险,编写一个小型针对性的/
build123d检测工具获取该特定几何信息。ezdxf - 目前将所有测量到的上传风险、可制造性问题或违反引用要求的情况视为错误。请勿推断SendCutSend UI的任何替代分类。
- 对于DXF单位,需结合、页眉范围、测量边界及订单上下文进行检查。若
$INSUNITS缺失、不支持或不属于SendCutSend指南中预期的DXF单位代码($INSUNITS代表英寸或1代表毫米),需报告单位/缩放错误,并建议重新导出或确认单位后再进行尺寸、法兰或材料相关的对比。请勿静默缩放几何结构或使用不确定的缩放比例进行材料相关的通过/不通过检查。4 - 对于带有折弯线的2D文件,需沿每条折弯线检查局部法兰长度。在每个跨度或采样点测量折弯两侧最近的切割/自由边,包括中断折弯跨度或形成局部自由边的缺口、槽、间隙、拆分凸舌及切口。将最小局部法兰深度与所选SKU的和
bending_specs.min_flange_length_before_bend进行对比。除非引用的源文件针对该服务给出了孔到折弯或特征到折弯的规则,否则请勿将法兰长度限制应用于普通封闭孔或内部切口;需单独报告这些情况,并按照引用规则要求提供中心线到折弯或边缘到折弯的测量值。请勿将附近的折弯相邻切割几何结构仅视为边角释放,除非剩余的局部法兰仍满足法兰长度最小值。若任何局部法兰深度低于SKU最小值,需报告bending_specs.min_flange_length_after_bend。当导出的几何结构存在局部切口、中断折弯、拆分折弯段、释放槽、凸舌或不支持区域时,请勿依赖汇总的源级别值。❌ fail - 按物理原因单独报告折弯问题。请勿将折弯相邻几何结构合并为通用法兰故障。针对最小法兰/接触长度错误、折弯线或模区几何结构交叉、附近自由边或切口导致的折弯接触/支撑不足、未覆盖折弯区域的折弯线、拆分/共轴折弯段以及接触或交叉折弯线的切割几何结构,分别报告不同的条目。若SendCutSend源文件未明确模区/接触阈值,需将测量得到的文件信息作为直接文件检查结果引用,并明确标记该对比受限于源文件。
- 对于STEP/STP折弯零件,若模型包含钣金折弯几何结构或预期服务包含折弯,需检查折弯半径。尽可能使用/
$cad/OCP提取圆柱或环形折弯面及其半径,分组重复的折弯半径,并与所选SKU的build123d或bending_specs.effective_bend_radius进行对比。若所选材料/SKU未知,需报告测量得到的折弯半径集合,并请用户提供材料/厚度后再做出就绪判定。若测量半径与所选SKU的工装半径冲突,需报告折弯半径不匹配错误。bending_specs.bend_radius
使用严谨的状态标签报告:
- :测量得到的文件信息符合引用的当前要求。
✅ pass - :测量到的上传风险、可制造性问题或直接违反引用的当前要求的情况。
❌ fail - :上下文缺失、源证据缺失、几何结构未测量、源数据冲突或工具限制。
❓ need more info
Diagnostic Images
诊断图像
When findings would be easier to understand visually, produce a concise diagnostic diagram proactively if image-generation or image-editing capabilities are available. Use snapshots first for CAD/DXF geometry views when available; use generated or edited images for callouts, legends, and before/after explanations. Do this without waiting for the user to ask whenever there is a , a spatially ambiguous geometry issue, or a geometry edit that needs a before/after explanation. If image-generation tools are unavailable, state that limitation and describe the intended diagram in the report.
$render❌ failBefore generating an image, run a layout preflight:
- Choose the smallest set of callouts needed to explain the fix.
- Estimate whether labels will crowd the geometry, overlap each other, or run outside the canvas. If crowding is likely, flag it before generation and switch to numbered markers plus a side legend, a larger canvas, or separate detail views.
- Keep long measured values and rule text in the legend, not directly over dense geometry.
- Include the measured failing distance, the cited minimum, and the proposed movement or clearance target.
After generating an image, inspect the rendered image before delivery. If labels overlap, are clipped, are hard to read, or obscure the geometry, regenerate or revise the diagram before reporting it.
若通过视觉方式能更易理解检查结果,且具备图像生成或编辑能力,需主动生成简洁的诊断图。若可用,优先使用其快照获取CAD/DXF几何结构视图;使用生成或编辑的图像添加标注、图例及前后对比说明。只要出现、空间模糊的几何问题或需要前后对比说明的几何编辑,无需等待用户请求即可执行此操作。若无法使用图像生成工具,需说明此限制并在报告中描述预期的诊断图内容。
$render❌ fail生成图像前,需执行布局预检:
- 选择解释修复所需的最少标注数量。
- 预估标签是否会遮挡几何结构、相互重叠或超出画布范围。若可能出现拥挤,需在生成前标记此问题,并切换为编号标记加侧边图例、更大画布或单独的细节视图。
- 将较长的测量值和规则文本放在图例中,而非直接覆盖密集的几何结构。
- 包含测量到的不合格距离、引用的最小值以及建议的移动或间隙目标。
生成图像后,需在交付前检查渲染图像。若标签重叠、被裁剪、难以阅读或遮挡几何结构,需重新生成或修改诊断图后再报告。
DXF Review
DXF审核
For laser sheet cutting, start from the refreshed sources and measured DXF geometry facts.
Check for:
- single, uploadable DXF file with model geometry at 1:1 scale
- units and overall part size; treat missing, unsupported, or unexpected as a scale error until the user confirms units
$INSUNITS - closed cut profiles where the service requires closed contours
- degenerate or zero-area closed contours, two-point closed polylines, and odd-degree cut endpoints
- duplicate or overlapping cut geometry
- unsupported annotation, text, dimensions, images, construction lines, or hidden instruction layers
- layer/color/linework conventions from the ordering guide and upload workflow
- bend-line entities, bend segment lengths, split/common-axis bends, local flange depth on both sides of each bend line, nearest non-bend cut edge or cutout distances, bend-line span coverage, insufficient bend contact/support, die-area or bend-adjacent cut geometry crossings, and cut geometry touching or crossing bend lines when bending is in scope
- minimum holes, slots, web widths, interior geometry, part density, nesting, and spacing only when both source facts and measured file facts support a comparison
- secondary-service requirements for bending, tapping, countersinking, hardware, finishing, or deburring when requested
对于激光板材切割,从刷新后的源文件和测量得到的DXF几何信息开始检查。
检查内容包括:
- 单一、可上传的DXF文件,模型几何结构为1:1比例
- 单位及零件整体尺寸;若缺失、不支持或不符合预期,在用户确认单位前视为缩放错误
$INSUNITS - 服务要求闭合轮廓时的闭合切割轮廓
- 退化或零面积的闭合轮廓、两点闭合多段线及奇数度切割端点
- 重复或重叠的切割几何结构
- 不支持的注释、文本、尺寸、图像、构造线或隐藏的指令图层
- 订购指南及上传流程中的图层/颜色/线条规范
- 涉及折弯时的折弯线实体、折弯段长度、拆分/共轴折弯、每条折弯线两侧的局部法兰深度、最近的非折弯切割边或切口距离、折弯线跨度覆盖范围、折弯接触/支撑不足、模区或折弯相邻切割几何结构交叉以及接触或交叉折弯线的切割几何结构
- 仅当源数据和测量得到的文件信息均支持对比时,检查最小孔、槽、腹板宽度、内部几何结构、零件密度、排样及间距
- 若有需求,检查折弯、攻丝、沉孔、硬件、表面处理或去毛刺等二次服务要求
STEP Review
STEP审核
For CNC routing or 3D model upload, start from the refreshed sources and measured STEP geometry facts.
Check for:
- STEP/STP file readability and a solid body rather than loose curves or surfaces
- units, scale, bounding box, thickness, and feature dimensions
- sheet-metal bend radii when bending is in scope; compare measured cylindrical bend-face radii to the selected SKU's or
bending_specs.effective_bend_radiusbending_specs.bend_radius - sharp inside corners, small holes/slots, thin walls, islands, deep pockets, tool access, and tolerances only when the file inspection can measure the fact
- whether geometry represents a sheet profile better served as DXF for laser cutting
- material, thickness, finish, and secondary-service compatibility
对于CNC铣削或3D模型上传,从刷新后的源文件和测量得到的STEP几何信息开始检查。
检查内容包括:
- STEP/STP文件的可读性及实体(而非松散曲线或曲面)
- 单位、缩放比例、边界框、厚度及特征尺寸
- 涉及折弯时的钣金折弯半径;将测量得到的圆柱折弯面半径与所选SKU的或
bending_specs.effective_bend_radius进行对比bending_specs.bend_radius - 仅当文件检查可测量相关信息时,检查尖锐内角、小孔/槽、薄壁、孤岛、深槽、刀具可达性及公差
- 判断几何结构是否更适合作为DXF文件用于激光切割的板材轮廓
- 材料、厚度、表面处理及二次服务兼容性
Reporting
报告撰写
Include the file path, assumed service, material/order context, source files checked with access date, inspected geometry facts, findings ordered by practical impact, and specific next edits. In the findings table, include a column with Markdown links to the source URL plus the specific JSON field path or guide section used for that row. If a row is based only on direct file inspection and has no external rule, say ; do not leave the source blank. Do not call a file "SendCutSend ready" unless every required cited check either passes or is explicitly outside the selected service.
Rule sourceDirect file inspectionUse when a structured report would help.
references/report-template.md包含文件路径、假设的服务、材料/订单上下文、已检查的源文件及访问日期、检查的几何信息、按实际影响排序的检查结果及具体后续编辑建议。在检查结果表格中,包含“规则来源”列,使用Markdown链接指向源URL及该行所用的具体JSON字段路径或指南章节。若某一行仅基于直接文件检查且无外部规则,需标注“直接文件检查”;请勿留空。仅当所有必需的引用检查均通过或明确不属于所选服务时,才可判定文件“SendCutSend就绪”。
如需结构化报告,可使用。
references/report-template.mdReferences
参考资料
- Official source selection:
references/official-sources.md - Report shape:
references/report-template.md
- 官方源文件选择:
references/official-sources.md - 报告格式:
references/report-template.md