Token导航 LogoToken导航

Agent Skill · 前端设计

openscad-collision-detection(openscad 碰撞检测)

openscad-collision-detection 用于处理 GitHub 仓库、Issue、Pull Request 和代码协作信息,适合在 Codex、Claude、Cursor、Gemini CLI 中需要围绕仓库状态、代码变更或协作事项进行整理时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

openscad-collision-detection 是前端设计类 Agent Skill,可用宿主为 Codex、Claude、Cursor、Gemini CLI,通过GitHub 仓库获取,权限为只读;许可证信息还不明确,第三方扫描已通过,按安装量在前端设计类的 10,216 个 Skill 里排第 6,812。

总安装 451周安装 19GitHub Stars 1下载 158核验 2026-05-01

安装说明

本站只整理中文说明,不托管安装包,也不代用户安装。
GitHub
许可证
unknown

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:openscad-collision-detection(openscad 碰撞检测)
来源仓库:https://github.com/dawiddutoit/custom-claude
仓库路径:skills/openscad-collision-detection
安装命令:
npx skills add https://github.com/dawiddutoit/custom-claude --skill openscad-collision-detection
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 npx skills 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

skills.shnpx skills
npx skills add https://github.com/dawiddutoit/custom-claude --skill openscad-collision-detection

这个 Skill 是做什么的

前端设计类 Skill 关注页面结构、视觉规范和组件写法,输出通常是可运行的界面代码。

openscad-collision-detection 用于处理 GitHub 仓库、Issue、Pull Request 和代码协作信息。适用于 Codex、Claude、Cursor、Gemini CLI 中需要围绕仓库状态、代码变更或协作事项进行整理的场景。

通过 npx skills add 命令从指定 GitHub 仓库安装,需结合原始 README 核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写操作。该技能归类为前端设计,适合 OpenSCAD 碰撞检测相关的协作支持。

来源仓库内路径:skills/openscad-collision-detection

上手步骤

4 步
  1. 1

    确认自己的宿主工具

    公开资料标注支持 Codex、Claude、Cursor、Gemini CLI;先确认自己用的是其中之一,再按对应工具的 Skills 目录放置。

  2. 2

    拿到安装命令

    可以直接复制的命令是 npx skills add https://github.com/dawiddutoit/custom-claude --skill openscad-col…;命令里的占位符换成自己的路径或密钥再执行。

  3. 3

    安装后重启宿主

    命令执行完要完全退出宿主工具再打开,让新装的 Skill 被重新扫描到,否则列表里可能看不到。

  4. 4

    按最小权限试用

    它标注为只读,先用只读任务试一次,确认行为符合预期再扩大使用范围。

常见问题

6 条

openscad-collision-detection 怎么安装?

在终端执行 npx skills add https://github.com/dawiddutoit/custom-claude --skill openscad-collision-det…。装完完全退出宿主工具再打开,让它重新扫描本地 Skill。

openscad-collision-detection 支持哪些 AI 工具?

公开资料标注支持 Codex、Claude、Cursor、Gemini CLI。其他工具只要能读取本地 Skill 目录,一般也能手动放进去,但要自己确认触发方式是否一致。

openscad-collision-detection 需要什么权限?

权限级别是只读。该 Skill 主要提供规则、说明或参考内容,本身偏只读;真正读写文件、联网或执行命令仍取决于宿主 Agent 的任务。

openscad-collision-detection 是免费的吗?

公开资料没有标注明确许可证,收费和商用限制都无法确认。正式使用前请到来源仓库核对授权说明。

openscad-collision-detection 用的人多吗?

公开数据是累计安装 451 次,近一周安装 19 次,下载 158 次,GitHub 1 星。这些数字来自第三方目录统计,只能当作热度参考,不代表质量或安全性。

openscad-collision-detection 安全吗?

第三方扫描结果为通过,但这只覆盖已知的静态检查项,不能替代自己读一遍源码和安装命令。

值得选的地方和要先想清楚的地方

值得选的地方

  • 同时适配 4 种工具,换客户端不用重新找替代品。
  • 第三方扫描已通过,常见的高风险行为没有命中。
  • 标注为只读权限,试用阶段不容易误改本地文件。

先想清楚的地方

  • 许可证没有明确标注,能不能商用、能不能再分发都不确定。
  • 第三方目录整理,版本更新和行为细节以来源仓库为准。

适不适合你

更适合

  • 已经在用 Codex,想直接扩展它能力的人。
  • 需要处理前端设计类任务、又不想每次都手写提示词的人。
  • 只想先试试效果、不希望它改动本地文件的人。

不太适合

  • 需要明确授权才能用到公司项目里的场景。
  • 需要厂商级技术支持和 SLA 的生产系统。

前端设计类 Skill 对比

6 个同类
Skill总安装GitHub 星权限许可证扫描
frontend-design

前端设计 · Codex、Claude

8,823,360126,072只读MIT通过
vercel-composition-patterns

Vercel 组合模式 · Codex、Claude

3,858,81625,893需要联网MIT通过
vercel-react-native-skills

Vercel React native skills 前端 · Codex、Claude

2,468,66425,878只读MIT通过
adapt

adapt 搜索 · Codex、Claude

2,027,04023,125操作浏览器未明确通过
bolder

bolder 分析 · Codex、Claude

2,004,28823,130只读未明确通过
openscad-collision-detection

openscad 碰撞检测 · 本页

4511只读未明确通过

按安装量取同分类前几名;数字来自第三方目录统计,只作热度参考,不代表质量结论。

SKILL.md 原文

OpenSCAD Collision Detection

Detect and visualize geometric intersections in OpenSCAD models for woodworking and assembly validation.

Quick Start

Add collision checking to any OpenSCAD model in 3 steps:

// 1. Create reusable checker module
module check_collision(show_overlap=true) {
    if (show_overlap) {
        color("red", 0.8) intersection() {
            children(0);
            children(1);
        }
    }
    %children(0);  // Ghost first object
    children(1);   // Solid second object
}

// 2. Apply to your objects
check_collision() {
    drawer();              // Moving part
    cabinet_interior();    // Fixed structure
}

// 3. Preview (F5) - red regions show collisions

Result: Transparent reference geometry + solid moving part + red overlap visualization.

Table of Contents

  1. When to Use This Skill
  2. What This Skill Does
  3. Core Techniques
  4. Reusable Patterns
  5. Woodworking Scenarios
  6. Debugging Workflow
  7. Supporting Files
  8. Expected Outcomes
  9. Integration Points
  10. Requirements
  11. Red Flags to Avoid

When to Use This Skill

Explicit Triggers

  • "Check collision between drawer and cabinet"
  • "Detect interference in door swing"
  • "Verify clearance for shelf spacing"
  • "Show overlaps in assembly"
  • "Check if drawer fits in cabinet"
  • "Door hinge collision check"
  • "Workbench against wall clearance"

Implicit Triggers

  • Designing cabinets with drawers
  • Creating furniture assemblies
  • Planning room layouts with furniture placement
  • Validating mechanical clearances
  • Debugging "won't fit" issues
  • Testing parametric designs with varying dimensions

Debugging Scenarios

  • Drawer won't close (hits back panel)
  • Door hits adjacent object when opening
  • Shelf spacing too tight for items
  • Hinge cup interferes with door panel
  • Workbench depth exceeds available space
  • Parametric model generates invalid dimensions

What This Skill Does

Provides systematic approach to collision detection:

  1. Visualize intersections using intersection() to reveal overlap volumes
  2. Ghost reference geometry using % modifier for transparent context
  3. Highlight collisions with color coding (red = problem, yellow = clearance)
  4. Measure clearances with echo statements and visual indicators
  5. Create reusable patterns for common woodworking scenarios
  6. Integrate with project libraries (woodworkers-lib, BOSL2, labels.scad)
  7. Validate assemblies before fabrication or room layout

Core Techniques

intersection() - Reveal Overlaps

Returns geometry only where objects overlap:

// Show collision volume
color("red") intersection() {
    drawer();
    cabinet_interior();
}
// If result has volume → collision exists

Debug Modifiers

ModifierEffectUse Case
%Transparent (ghost)Show reference geometry
#Highlight (red)Emphasize specific object
!Show onlyIsolate object for testing
*DisableTemporarily hide geometry
%cabinet_interior();  // Ghost
#drawer();           // Highlight

BOSL2 Utilities

include <BOSL2/std.scad>

debug_this() drawer();  // Shows bounding box + transparent object
ghost() cabinet();      // Semantic equivalent to %

Reusable Patterns

Pattern 1: Basic Collision Checker

module check_collision(show_overlap=true, overlap_color="red") {
    if (show_overlap) {
        color(overlap_color, 0.8) intersection() {
            children(0);
            children(1);
        }
    }
    %children(0);  // Ghost first object
    children(1);   // Solid second object
}

Usage:

check_collision() {
    drawer_extended();
    cabinet_side_panel();
}

Pattern 2: Clearance Visualization

module show_clearance(clearance=2, zones=true) {
    // Original objects
    %children(0);
    children(1);

    // Clearance zones
    if (zones) {
        color("yellow", 0.2)
            offset(r=clearance)
            projection(cut=false)
            children(0);
    }

    // Collision check
    color("red") intersection() {
        children(0);
        children(1);
    }
}

Pattern 3: Conditional Debug Mode

DEBUG_COLLISION = true;  // Toggle at file top

module conditional_check() {
    if (DEBUG_COLLISION) {
        color("red") intersection() {
            children(0);
            children(1);
        }
        %children(0);
        children(1);
    } else {
        children(0);
        children(1);
    }
}

Pattern 4: Assembly Interference Check

module assembly_check(explode=false) {
    spacing = explode ? 50 : 0;

    // Check overlaps when assembled (explode=false)
    if (!explode) {
        color("red", 0.8) intersection() {
            children(0);
            children(1);
        }
    }

    children(0);
    translate([spacing, 0, 0]) children(1);
}

// Usage
assembly_check(explode=$preview) {
    cabinet_shell();
    drawer_assembly();
}

Woodworking Scenarios

Drawer Clearance Check

include <woodworkers-lib/std.scad>

module drawer_clearance_check(cabinet_dim, drawer_dim, panel=18) {
    interior_w = cabinet_dim[0] - 2 * panel;
    interior_d = cabinet_dim[1] - panel;
    interior_h = cabinet_dim[2] - 2 * panel;

    // Ghost cabinet interior
    %color("blue", 0.2)
        translate([panel, 0, panel])
        cube([interior_w, interior_d, interior_h]);

    // Show drawer
    color("green", 0.5) cube(drawer_dim);

    // Highlight collision
    color("red") intersection() {
        translate([panel, 0, panel]) cube([interior_w, interior_d, interior_h]);
        cube(drawer_dim);
    }

    // Echo clearances
    side_clearance = (interior_w - drawer_dim[0]) / 2;
    echo(str("Side clearance: ", side_clearance, "mm per side"));
}

Door Swing Interference

module door_swing_check(door_width, swing_angle=90, adjacent_pos=500) {
    // Door sweep volume
    color("yellow", 0.3)
        rotate([0, 0, swing_angle])
        cube([door_width, 5, 720]);

    // Adjacent object
    translate([adjacent_pos, 0, 0])
        color("green", 0.5)
        cube([200, 400, 720]);

    // Check interference
    color("red") intersection() {
        rotate([0, 0, swing_angle]) cube([door_width, 5, 720]);
        translate([adjacent_pos, 0, 0]) cube([200, 400, 720]);
    }
}

Shelf Spacing Validation

module shelf_spacing_check(cabinet_dim, shelf_positions, item_height, panel=18) {
    // Draw shelves
    for (z = shelf_positions) {
        translate([0, 0, z])
            %planeBottom([cabinet_dim[0], cabinet_dim[1], panel]);
    }

    // Check spacing
    for (i = [0:len(shelf_positions)-2]) {
        spacing = shelf_positions[i+1] - shelf_positions[i] - panel;
        if (spacing < item_height) {
            echo(str("WARNING: Shelf ", i, " spacing (", spacing,
                     "mm) < item height (", item_height, "mm)"));

            // Highlight insufficient spacing
            translate([0, 0, shelf_positions[i] + panel])
                color("red", 0.5)
                cube([cabinet_dim[0], cabinet_dim[1], spacing]);
        }
    }
}

Debugging Workflow

Follow this systematic 5-step process:

Step 1: Isolate Components

!drawer();  // Show only drawer (use ! modifier)

Step 2: Ghost Reference Geometry

%cabinet_interior();
drawer();

Step 3: Check Intersection

color("red") intersection() {
    cabinet_interior();
    drawer();
}
// No volume = no collision

Step 4: Measure Clearance

drawer_width = 764;
interior_width = 782;
clearance = interior_width - drawer_width;
echo(str("Total clearance: ", clearance, "mm (", clearance/2, "mm per side)"));

if (clearance < 4) {
    echo("ERROR: Insufficient clearance!");
}

Step 5: Iterate with Parameters

DRAWER_CLEARANCE = 2;  // mm per side

module drawer_with_clearance(interior_width) {
    width = interior_width - 2*DRAWER_CLEARANCE;
    cube([width, 400, 100]);
}

Supporting Files

examples/examples.md

Comprehensive collision detection examples:

  • Drawer clearance checks (side, top, depth)
  • Door swing interference (hinges, adjacent objects)
  • Shelf spacing validation (item heights, bin clearance)
  • Hinge collision detection (cup-to-door, door-to-frame)
  • Room layout validation (workbench against wall)
  • Assembly interference (multi-part checking)

references/reference.md

Technical reference:

  • OpenSCAD boolean operations (intersection, difference, union)
  • Manifold vs CGAL engine comparison
  • Performance optimization techniques
  • Color coding standards for collision detection
  • Mathematical clearance calculations
  • Integration with BOSL2 and woodworkers-lib

Expected Outcomes

Successful Collision Detection

No collision:

ECHO: "Side clearance: 2.0mm per side"
ECHO: "Top clearance: 5.0mm"
ECHO: "Depth clearance: 10.0mm"

Preview shows no red regions.

Collision detected:

ECHO: "WARNING: Drawer collision detected!"
ECHO: "Overlap volume: 15mm × 18mm × 100mm"
ECHO: "Reduce drawer width by 15mm"

Preview shows red overlap region.

Visual Feedback

ColorMeaning
RedCollision/interference
YellowClearance zone
GreenMoving parts
BlueFixed structure
TransparentReference geometry

Integration Points

With woodworkers-lib

include <woodworkers-lib/std.scad>

module ww_collision_check(outer_dim, inner_dim) {
    // Outer box (cabinet)
    %color("blue", 0.2) {
        planeBottom(outer_dim);
        planeTop(outer_dim);
        planeLeft(outer_dim, t=-1, b=-1);
        planeRight(outer_dim, t=-1, b=-1);
    }

    // Inner box (drawer)
    color("green", 0.5) {
        planeBottom(inner_dim);
        // ... other planes
    }
}

With labels.scad

include <lib/labels.scad>

module labeled_collision_check() {
    labeled_cuboid([800, 400, 100],
        name="DRAWER",
        box_color="green"
    );

    translate([0, 0, 100])
    labeled_cuboid([800, 400, 18],
        name="SHELF",
        box_color="brown"
    );

    // Collision check
    color("red") intersection() {
        cube([800, 400, 100]);
        translate([0, 0, 100]) cube([800, 400, 18]);
    }
}

With BOSL2 Attachments

include <BOSL2/std.scad>

diff()
cuboid([100, 100, 50])
    attach(TOP) tag("remove")
        cyl(d=20, h=30);  // Check if penetrates too deep

Requirements

Tools

  • OpenSCAD 2025.x (Manifold engine for fast intersections)
  • BOSL2 library (optional, for debug_this/ghost utilities)
  • woodworkers-lib (optional, for cabinet/furniture patterns)

Knowledge

  • Basic OpenSCAD syntax (modules, translate, cube)
  • CSG operations (union, difference, intersection)
  • Debug modifiers (%, #,!, *)
  • Color syntax with alpha channel

Environment

  • Preview mode (F5) for fast iteration
  • Console output visible for echo statements

Red Flags to Avoid

  • Not checking clearances before fabrication - Always validate fits
  • Ignoring echo warnings - Console output reveals dimension problems
  • Using render (F6) for collision checks - Preview (F5) is 10-100x faster
  • Forgetting alpha channel in colors - color("red", 0.5) not color("red")
  • Testing only best-case scenarios - Check extreme parameter values
  • Nesting intersection() unnecessarily - Slows down renders significantly
  • Not parameterizing clearances - Hardcoded values make iteration difficult
  • Skipping validation in parametric designs - Add assert() statements
  • Assuming preview accuracy - Render (F6) for final validation if critical
  • Not documenting clearance requirements - Add comments explaining minimums

Notes

Manifold Engine: OpenSCAD 2025+ uses Manifold by default for 10-100x faster boolean operations. If intersection results look wrong, try --backend CGAL as fallback.

Preview vs Render: Collision detection is usually sufficient in preview mode (F5). Only use render (F6) for final validation of critical clearances.

Color Consistency: Use red for collisions, yellow for clearances, green for moving parts, blue for fixed structure throughout all models.

Documentation: Add echo statements for all clearance calculations. Future you will thank present you.

Parametric Validation: Use assert() to enforce clearance minimums:

assert(clearance >= 4, "Drawer clearance must be >= 4mm");

平台分布

Codex

35.97%
按下载量换算57

Claude

29.45%
按下载量换算47

Cursor

19.4%
按下载量换算31

Gemini CLI

9.55%
按下载量换算15

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

只读

该 Skill 主要提供规则、说明或参考内容,本身偏只读;真正读写文件、联网或执行命令仍取决于宿主 Agent 的任务。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。目前只有一个公开来源,建议同时核对源仓库。

继续浏览同类 Skills