[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7AKXP4SE1HXTDFMP0JSPZM5":3,"skill-same:01M7AKXP4SE1HXTDFMP0JSPZM5":48},{"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":24,"commitSha":25,"skillDirectory":26,"forksCount":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":29,"ownerHtmlUrl":30,"ownerBlogUrl":31,"ownerDescription":32,"updatedAt":33,"install":34,"resources":47},"01M7AKXP4SE1HXTDFMP0JSPZM5","cad-reference",null,"Use when checking a CAD or printing anti-pattern, looking up a tolerance, temperature or dimensional value, asking what actually moved (OpenSCAD's Manifold backend, the slicer landscape, code-CAD and the LLM angle, verified August 2026), finding the books and tools, or needing a picker and a pre-print checklist. Companion to the other cad-3d-printing skills.","the-vibey-project\u002Fvibey","the-vibey-project","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F329298758?v=4","01M7AJHGZ9722CTJ4JNQZVRH0Q","the vibey project","01M7AJHGZVMG2K7TGXQ6XFHVG3",5,"MIT","https:\u002F\u002Fgithub.com\u002Fthe-vibey-project\u002Fvibey\u002Fblob\u002Fdevelop\u002Fsrc\u002Fvibey_tools\u002Fskills\u002Fplugins\u002Fcad-3d-printing\u002Fskills\u002Fcad-reference\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: cad-reference\ndescription: \"Use when checking a CAD or printing anti-pattern, looking up a tolerance, temperature or dimensional value, asking what actually moved (OpenSCAD's Manifold backend, the slicer landscape, code-CAD and the LLM angle, verified August 2026), finding the books and tools, or needing a picker and a pre-print checklist. Companion to the other cad-3d-printing skills.\"\n---\n\n# CAD and 3D Printing: Anti-Patterns, Numbers, What Moved, and Tools\n\n> **Part 5 of 5** of the *CAD and 3D Printing* reference (plugin `cad-3d-printing`), covering §13–§18. Sibling skills: `cad-geometry-kernels-formats-and-code-cad` (§0–§4), `cad-slicing-pipeline-and-processes` (§5–§6), `cad-design-tolerances-and-materials` (§7–§9), `cad-generative-automation-and-scanning` (§10–§12). Section numbers are shared across the set; a reference written as §N → `skill` points into that sibling skill.\n>\n> **Currency:** The geometry mathematics and process physics are stable; the code-CAD tooling and slicer landscape moved. See §16 below for both, dated.\n\n> **Scope.** Written for people who write code. **§2–§4 → `cad-geometry-kernels-formats-and-code-cad` are the software engineering\n> (kernels, scripting, formats); §6–§9 → `cad-slicing-pipeline-and-processes`, `cad-design-tolerances-and-materials` are the manufacturing physics you need for the\n> software to produce parts that work.**\n>\n> **⚠️ GOTCHA** boxes mark what silently produces a bad model or an unprintable part.\n>\n> **The three ideas that organize everything:**\n> 1. **⚠️ Choose your representation before your tool.** B-rep, mesh, and implicit fields\n>    are not interchangeable — each makes some operations trivial and others impossible,\n>    and **most CAD frustration is a representation mismatch** (§1 → `cad-geometry-kernels-formats-and-code-cad`).\n> 2. **⚠️ Every export loses something.** STL loses units, topology, colour, and all\n>    parametric intent. STEP keeps the solid but not the feature tree. **Know what falls\n>    off at each hop** (§3 → `cad-geometry-kernels-formats-and-code-cad`).\n> 3. **⚠️ The printer does not build your model, it builds your G-code.** Slicing is a\n>    lossy, opinionated transformation, and the part's real properties — strength,\n>    accuracy, surface — are determined there and by the process physics, not by the\n>    CAD (§5 → `cad-slicing-pipeline-and-processes`, §6 → `cad-slicing-pipeline-and-processes`).\n\n---\n\n## §13. Anti-Patterns\n\n| Anti-pattern | Why |\n|---|---|\n| Choosing the tool before the representation | ⚠️ **Most CAD frustration is a representation mismatch** (§1 → `cad-geometry-kernels-formats-and-code-cad`) |\n| Expecting arbitrary-edge fillets in OpenSCAD | ⚠️ **CSG has no edges to select** (§4.2 → `cad-geometry-kernels-formats-and-code-cad`) |\n| Coplanar faces in a boolean | ⚠️ **Numerically ambiguous. Overlap by an epsilon** (§2 → `cad-geometry-kernels-formats-and-code-cad`) |\n| STL as an interchange format between CAD tools | ⚠️ **Lossy and unit-less. Use STEP** (§3 → `cad-geometry-kernels-formats-and-code-cad`) |\n| STL to the printer when 3MF is available | 3MF carries units, colour, settings (§3 → `cad-geometry-kernels-formats-and-code-cad`) |\n| Assuming an STL's units | ⚠️ **There are none. 25.4× errors are real** (§3 → `cad-geometry-kernels-formats-and-code-cad`) |\n| Round-tripping CAD → STL → CAD | You get an uneditable mesh back (§3 → `cad-geometry-kernels-formats-and-code-cad`) |\n| High `$fn` \u002F fine tessellation while iterating | ⚠️ **2 seconds becomes 2 minutes** (§4.3 → `cad-geometry-kernels-formats-and-code-cad`) |\n| Magic numbers instead of named parameters | Defeats the point of code-CAD (§4.3 → `cad-geometry-kernels-formats-and-code-cad`) |\n| Version-controlling the STL instead of the source | ⚠️ **Same** (§4.3 → `cad-geometry-kernels-formats-and-code-cad`) |\n| Trusting automatic mesh repair blindly | ⚠️ **Heuristic; silently changes geometry** (§4.5 → `cad-geometry-kernels-formats-and-code-cad`) |\n| Laplacian smoothing on a dimensioned part | ⚠️ **It shrinks the model** (§4.5 → `cad-geometry-kernels-formats-and-code-cad`) |\n| Ignoring print orientation for structural parts | ⚠️ **Z is 20–50% weaker. Orientation is a design decision** (§6.1 → `cad-slicing-pipeline-and-processes`) |\n| Horizontal circular holes on FDM | ⚠️ **Sagging top. Use a teardrop** (§7 → `cad-design-tolerances-and-materials`) |\n| Wall thickness not a multiple of extrusion width | Gaps or over-extrusion (§7 → `cad-design-tolerances-and-materials`) |\n| Fully enclosed voids in SLS or SLA | ⚠️ **Trapped powder \u002F resin, permanently** (§6.2 → `cad-slicing-pipeline-and-processes`, §7 → `cad-design-tolerances-and-materials`) |\n| Modelling holes at nominal size for FDM | ⚠️ **They print undersize** (§8 → `cad-design-tolerances-and-materials`) |\n| Trusting a clearance table over a test print | Calibrate your machine and material (§8 → `cad-design-tolerances-and-materials`) |\n| Printed threads for load-bearing joints | ⚠️ **Use heat-set inserts** (§8 → `cad-design-tolerances-and-materials`) |\n| Printing hygroscopic filament without drying | ⚠️ **The most common invisible cause of bad prints** (§9 → `cad-design-tolerances-and-materials`) |\n| Infill density as the strength lever | ⚠️ **Perimeters do more above ~40%** (§5.3 → `cad-slicing-pipeline-and-processes`) |\n| Topology optimization on one load case | Fragile in every other direction (§10 → `cad-generative-automation-and-scanning`) |\n| Manual slicing in a repeatable workflow | ⚠️ **Every slicer has a CLI** (§11 → `cad-generative-automation-and-scanning`) |\n| Treating a scan as a model | ⚠️ **A mesh is not CAD** (§12 → `cad-generative-automation-and-scanning`) |\n\n---\n\n## §14. Numbers\n\n```\nFDM\nNozzle 0.4 mm typical (0.2–0.8) · Layer 0.1–0.3 mm (⚠️ ~25–75% of nozzle Ø)\nExtrusion width ≈ nozzle Ø to 1.2× · Filament 1.75 mm (or 2.85)\n⚠️ Overhang limit ~45–55° · Bridging to ~50 mm with good cooling\n⚠️ Z-strength 50–80% of XY · Accuracy ±0.1–0.5 mm\nFirst layer squish, elephant's foot compensation ~0.1–0.5 mm\n\nCLEARANCES (FDM, per side)\nPress fit 0 to −0.1 · Tight sliding 0.15–0.2 · Free 0.3–0.4 · Print-in-place 0.3–0.5\n⚠️ Holes print undersize: oversize by 0.1–0.4 mm\n\nRESOLUTION BY PROCESS\nMaterial jetting 16 µm · SLA\u002FMSLA 25–100 µm · SLM 20–50 µm\nMJF ~80 µm · SLS ~100 µm · FDM 100–300 µm\n\nTEMPERATURES (nozzle \u002F bed)\nPLA 200\u002F60 · PETG 240\u002F80 · ABS 250\u002F100 · Nylon 260\u002F90 · PC 280\u002F110 · TPU 225\u002F50\n⚠️ PLA softens ~60 °C — glass transition, not melting\n\nEXTRUSION MATH\nE = (layer_h × width × dist) \u002F (π (filament_d\u002F2)²)\n⚠️ 1.75 mm nominal at 1.70 mm actual = ~6% under-extrusion\n\nMESH\n⚠️ Euler: V − E + F = 2 − 2g  for a closed surface of genus g\nManifold: every edge in exactly 2 faces\n```\n\n---\n\n## §15. Books and Tools\n\n| Source | Why |\n|---|---|\n| **Piegl & Tiller, *The NURBS Book*** | ⚠️ **The reference for §1 → `cad-geometry-kernels-formats-and-code-cad`'s surface math** |\n| **Farin, *Curves and Surfaces for CAGD*** | The readable companion |\n| **Botsch et al., *Polygon Mesh Processing*** | ⚠️ **§4.5 → `cad-geometry-kernels-formats-and-code-cad`, definitively** |\n| **de Berg et al., *Computational Geometry*** | Algorithms and the robustness problem |\n| **Shirley, *Ray Tracing in One Weekend*** | ⚠️ **The best free introduction to thinking in 3D geometry code** |\n| **Gibson, Rosen & Stucker, *Additive Manufacturing Technologies*** | ⚠️ **The academic AM reference** |\n| **Redwood et al., *The 3D Printing Handbook*** | ⚠️ **The practical DfAM book — get this one first** |\n| **Bendsøe & Sigmund, *Topology Optimization*** | §10 → `cad-generative-automation-and-scanning` |\n| **ASME Y14.5 (GD&T)** | Tolerancing formally (§8 → `cad-design-tolerances-and-materials`) |\n\n**Tools**: **OpenSCAD**, **CadQuery**, **build123d**, **FreeCAD**, **SolveSpace**\n(⚠️ **an underrated constraint-based parametric modeller**), **Blender**, **Rhino +\nGrasshopper**, **nTop** (implicits), **Onshape** (⚠️ **best commercial API**),\n**Fusion 360**. **Mesh**: trimesh, pymeshlab, MeshLab, Open3D, libigl, Manifold, OpenVDB.\n**Slicers**: §16.2. **Print management**: OctoPrint, Klipper\u002FMoonraker, Mainsail, Fluidd.\n**Communities**: Printables, Thingiverse, MakerWorld, ⚠️ **and the slicer projects'\nGitHub issues, which are the best documentation of real failure modes.**\n\n---\n\n## §16. What Actually Moved — verified August 2026\n\n### 16.1 ⚠️ OpenSCAD's Manifold backend\n**The most significant change to open code-CAD in years, and one worth getting right\nbecause outdated descriptions are everywhere.**\n\n- **OpenSCAD historically used CGAL**, which is exact and ⚠️ **notoriously slow.**\n- **Manifold** replaced it as an alternative backend. **Reported speedups:\n  5–30× over CGAL's fast-csg**, which was itself **30–150× over baseline CGAL Nef\n  routines** — ⚠️ **with a 1,000× improvement reported on at least one model.**\n- **⚠️ Since 2024-09-28 the Manifold backend is no longer experimental** — selectable in\n  Preferences → Advanced → 3D Rendering → Backend, or `openscad --backend=manifold` on the\n  command line. ⚠️ **The old feature-flag method was removed, which broke some\n  command-line scripts.**\n- **⚠️ At that announcement, CGAL was still the default backend**, with Manifold opt-in.\n- **⚠️ That changed on 2025-08-17**, when OpenSCAD maintainer Marius Kintel announced on the\n  project mailing list that **Manifold is now the default backend in development\n  snapshots**, calling it \"battle tested\"; CGAL remains selectable via preferences or\n  `--backend=cgal`. ⚠️ **The most recent tagged \"stable\" release is still 2021.01, which\n  predates Manifold support entirely** — anyone using Manifold at all is already on a\n  development snapshot, where the default has now flipped.\n\n> **⚠️ GOTCHA — two things to be careful about here.**\n> **First, many current sources — including reference documentation and comparison\n> articles — still describe OpenSCAD's kernel as simply \"CGAL.\"** That was accurate and\n> is now at best incomplete. ⚠️ **Check which backend you're actually running before\n> attributing behaviour to a kernel.**\n> **Second, the backends are not equivalent in output.** A February 2026 bug report shows\n> **a model where Manifold produced STL with open edges that PrusaSlicer auto-repaired,\n> while CGAL made most of the model vanish entirely** — and ⚠️ **the reporter's fix was\n> adding a small overlap, i.e. the §2 → `cad-geometry-kernels-formats-and-code-cad` epsilon problem.** **If a model behaves oddly, try\n> the other backend as a diagnostic.**\n\n### 16.2 The slicer landscape\n**⚠️ Almost everything descends from Slic3r.** **OrcaSlicer** is a fork of **Bambu\nStudio**, which forked **PrusaSlicer**, which began as **Slic3r PE**. **Cura** is the\nseparate lineage.\n\n**As of 2026**: **OrcaSlicer** is widely described as the strongest for advanced FDM\ntuning — ⚠️ **best-in-class calibration workflows (temperature, flow, pressure advance,\nretraction, max volumetric speed), the broadest third-party printer support, native\npresets for Klipper input-shaping and pressure-advance, no cloud requirement, and leading\ntree\u002Forganic support generation.** **Bambu Studio** is strongest on Bambu hardware,\n**PrusaSlicer** on Prusa hardware and mature multi-material with a 1–3 month-slower\nrelease cadence, and **Cura** remains the broad beginner-friendly standby with the plugin\necosystem.\n\n**⚠️ Read that as ecosystem fit, not a ranking**: the honest summary from the comparisons\nis that **the right slicer depends almost entirely on what you're printing on**, and\n**Klipper users in particular have a clear answer.**\n\n### 16.3 Code-CAD and the LLM angle\n**CadQuery and build123d** wrap **OCCT**, giving exact B-rep, true fillets and chamfers,\nand **STEP import\u002Fexport that OpenSCAD cannot do.** **build123d** replaces CadQuery's\nfluent method-chaining with **context managers, so ordinary Python loops, references and\nfiltering work naturally.**\n\n⚠️ **One genuinely interesting current finding, reported by more than one party building\nLLM-to-CAD tooling**: **language models write OpenSCAD substantially more reliably than\nCadQuery or build123d** — one benchmark reports **3–4× fewer code errors** — attributed to\ntraining-data volume and to OCCT's complexity leaking through the Python wrapper.\n> **⚠️ GOTCHA — take that with real caution.** ⚠️ **Both sources reporting it are\n> companies whose product is built on OpenSCAD**, so they are not disinterested. **The\n> underlying reasoning is plausible** (OpenSCAD's language is small and its corpus is\n> large), **but this is a vendor-adjacent benchmark, not an independent one.** ⚠️ **And it\n> says nothing about which kernel is better for a human** — the same sources concede that\n> OCCT is the more capable kernel.\n\n---\n\n## §17. Quick Reference\n\n### 17.1 Picker\n| Need | Use |\n|---|---|\n| Parametric part, simple geometry, scriptable | **OpenSCAD** (§4.1 → `cad-geometry-kernels-formats-and-code-cad`) |\n| Same, but needs fillets\u002Fchamfers and STEP | ⚠️ **CadQuery or build123d** (§4.2 → `cad-geometry-kernels-formats-and-code-cad`) |\n| Full CAD app automation | **FreeCAD Python**, or **Onshape REST** (§4.4 → `cad-geometry-kernels-formats-and-code-cad`) |\n| Constraint-based parametric, lightweight GUI | **SolveSpace** (§15) |\n| Organic\u002Fartistic modelling | Blender (⚠️ not engineering CAD) (§4.1 → `cad-geometry-kernels-formats-and-code-cad`) |\n| Lattices, implicit geometry, millions of features | ⚠️ **Implicit\u002FSDF representation** (§1 → `cad-geometry-kernels-formats-and-code-cad`, §10 → `cad-generative-automation-and-scanning`) |\n| Reliable booleans on messy meshes | **Manifold** (§2 → `cad-geometry-kernels-formats-and-code-cad`) |\n| Repair a broken mesh | trimesh \u002F pymeshlab \u002F Netfabb; ⚠️ **voxel remesh as last resort** (§4.5 → `cad-geometry-kernels-formats-and-code-cad`) |\n| CAD → CAD interchange | ⚠️ **STEP** (§3 → `cad-geometry-kernels-formats-and-code-cad`) |\n| CAD → printer | ⚠️ **3MF** (§3 → `cad-geometry-kernels-formats-and-code-cad`) |\n| Batch\u002FCI generation | ⚠️ **Headless CLI — all of them have one** (§11 → `cad-generative-automation-and-scanning`) |\n| Klipper printer | **OrcaSlicer** (§16.2) |\n| Strong part, FDM | ⚠️ **Orient for load along layers; add perimeters, not infill** (§5.3 → `cad-slicing-pipeline-and-processes`, §6.1 → `cad-slicing-pipeline-and-processes`) |\n| Load-bearing threaded joint, FDM | **Heat-set insert** (§8 → `cad-design-tolerances-and-materials`) |\n| Complex geometry, no supports | ⚠️ **SLS\u002FMJF — the powder bed supports it** (§6 → `cad-slicing-pipeline-and-processes`) |\n| Fine detail | SLA\u002FMSLA (§6 → `cad-slicing-pipeline-and-processes`) |\n\n### 17.2 Pre-print checklist\n- [ ] Mesh manifold, watertight, correct normals? (§4.5 → `cad-geometry-kernels-formats-and-code-cad`)\n- [ ] Units correct — and is it 3MF rather than STL? (§3 → `cad-geometry-kernels-formats-and-code-cad`)\n- [ ] Oriented for the load path, not just for print time? (§6.1 → `cad-slicing-pipeline-and-processes`)\n- [ ] Overhangs under ~45°, or supported, or redesigned as chamfers? (§7 → `cad-design-tolerances-and-materials`)\n- [ ] Horizontal holes teardropped? (§7 → `cad-design-tolerances-and-materials`)\n- [ ] Walls a whole multiple of extrusion width? (§7 → `cad-design-tolerances-and-materials`)\n- [ ] Clearances calibrated for *this* machine and material? (§8 → `cad-design-tolerances-and-materials`)\n- [ ] Escape holes for powder\u002Fresin if applicable? (§6.2 → `cad-slicing-pipeline-and-processes`)\n- [ ] Filament dried if hygroscopic? (§9 → `cad-design-tolerances-and-materials`)\n- [ ] Perimeters increased before infill for strength? (§5.3 → `cad-slicing-pipeline-and-processes`)\n\n---\n\n## §18. Method\n\n**§1–§12 → `cad-geometry-kernels-formats-and-code-cad`, `cad-slicing-pipeline-and-processes`, `cad-design-tolerances-and-materials`, `cad-generative-automation-and-scanning` rest on stable material** — NURBS and B-rep mathematics, computational geometry,\nmesh processing, and additive manufacturing process physics — sourced from the references\nin §15, chiefly **Piegl & Tiller**, **Botsch et al.**, and **Gibson, Rosen & Stucker**,\nplus the file-format specifications. ⚠️ **None of that needed web verification; the\ngeometry math is decades old and the process physics is thermodynamics.**\n\n**Two searches were run in August 2026**, confined to the tooling: **the code-CAD\necosystem** and **the OpenSCAD kernel and slicer landscape.**\n\n**⚠️ The second search materially corrected the first.** Several sources returned by the\ncode-CAD search — **including CadQuery's own documentation and multiple 2026\ncomparison articles** — describe OpenSCAD's kernel as CGAL and contrast it unfavourably\nwith OCCT on that basis. **That framing predates the Manifold work.** I followed up\nspecifically and found the **OpenSCAD mailing list announcement (2024-09-28) that Manifold\nis no longer experimental**, a **later mailing list post (2025-08-17) from the same\nmaintainer confirming Manifold became the default backend in development snapshots**, plus\n**the Manifold project's own performance discussion** for the speedup figures. ⚠️ **§16.1\nreflects that; the widely-repeated \"OpenSCAD uses CGAL\" line is now incomplete.**\n\n**Confidence.** **High** in §1–§12 → `cad-geometry-kernels-formats-and-code-cad`, `cad-slicing-pipeline-and-processes`, `cad-design-tolerances-and-materials`, `cad-generative-automation-and-scanning` — established mathematics and process physics, with\nnumbers stated as representative ranges that vary by machine and material. **High** in\n§16.1's Manifold facts, which come from the project and the OpenSCAD maintainers directly,\nincluding that **CGAL remained the default backend at the time of the 2024-09-28\nannouncement, and that Manifold became the default in development snapshots as of\n2025-08-17** — ⚠️ **verify which snapshot and backend you are actually running rather than\nassuming, since the tagged \"stable\" release (2021.01) predates either backend option.**\n\n⚠️ **Two explicit hedges.** **§16.2's slicer assessment is drawn from comparison articles,\nwhich are opinion-shaped and frequently affiliate-monetized**; I have framed it as\necosystem fit rather than a ranking, and the technical lineage (Slic3r → PrusaSlicer →\nBambu Studio → OrcaSlicer) is the part that is unambiguous. And ⚠️ **§16.3's LLM benchmark\nis flagged in place as vendor-adjacent** — **both parties reporting it build products on\nOpenSCAD.** The mechanism they propose is plausible and the finding may well be right, but\n**it is not an independent evaluation and I have not treated it as one.**\n\n**§14's tolerance and clearance figures are starting points, not specifications** —\n⚠️ **the §8 → `cad-design-tolerances-and-materials` advice to run a calibration print is the actual recommendation, and it\nsupersedes any table including mine.**\n","# CAD and 3D Printing: Anti-Patterns, Numbers, What Moved, and Tools\n\n> **Part 5 of 5** of the *CAD and 3D Printing* reference (plugin `cad-3d-printing`), covering §13–§18. Sibling skills: `cad-geometry-kernels-formats-and-code-cad` (§0–§4), `cad-slicing-pipeline-and-processes` (§5–§6), `cad-design-tolerances-and-materials` (§7–§9), `cad-generative-automation-and-scanning` (§10–§12). Section numbers are shared across the set; a reference written as §N → `skill` points into that sibling skill.\n>\n> **Currency:** The geometry mathematics and process physics are stable; the code-CAD tooling and slicer landscape moved. See §16 below for both, dated.\n\n> **Scope.** Written for people who write code. **§2–§4 → `cad-geometry-kernels-formats-and-code-cad` are the software engineering\n> (kernels, scripting, formats); §6–§9 → `cad-slicing-pipeline-and-processes`, `cad-design-tolerances-and-materials` are the manufacturing physics you need for the\n> software to produce parts that work.**\n>\n> **⚠️ GOTCHA** boxes mark what silently produces a bad model or an unprintable part.\n>\n> **The three ideas that organize everything:**\n> 1. **⚠️ Choose your representation before your tool.** B-rep, mesh, and implicit fields\n>    are not interchangeable — each makes some operations trivial and others impossible,\n>    and **most CAD frustration is a representation mismatch** (§1 → `cad-geometry-kernels-formats-and-code-cad`).\n> 2. **⚠️ Every export loses something.** STL loses units, topology, colour, and all\n>    parametric intent. STEP keeps the solid but not the feature tree. **Know what falls\n>    off at each hop** (§3 → `cad-geometry-kernels-formats-and-code-cad`).\n> 3. **⚠️ The printer does not build your model, it builds your G-code.** Slicing is a\n>    lossy, opinionated transformation, and the part's real properties — strength,\n>    accuracy, surface — are determined there and by the process physics, not by the\n>    CAD (§5 → `cad-slicing-pipeline-and-processes`, §6 → `cad-slicing-pipeline-and-processes`).\n\n---\n\n## §13. Anti-Patterns\n\n| Anti-pattern | Why |\n|---|---|\n| Choosing the tool before the representation | ⚠️ **Most CAD frustration is a representation mismatch** (§1 → `cad-geometry-kernels-formats-and-code-cad`) |\n| Expecting arbitrary-edge fillets in OpenSCAD | ⚠️ **CSG has no edges to select** (§4.2 → `cad-geometry-kernels-formats-and-code-cad`) |\n| Coplanar faces in a boolean | ⚠️ **Numerically ambiguous. Overlap by an epsilon** (§2 → `cad-geometry-kernels-formats-and-code-cad`) |\n| STL as an interchange format between CAD tools | ⚠️ **Lossy and unit-less. Use STEP** (§3 → `cad-geometry-kernels-formats-and-code-cad`) |\n| STL to the printer when 3MF is available | 3MF carries units, colour, settings (§3 → `cad-geometry-kernels-formats-and-code-cad`) |\n| Assuming an STL's units | ⚠️ **There are none. 25.4× errors are real** (§3 → `cad-geometry-kernels-formats-and-code-cad`) |\n| Round-tripping CAD → STL → CAD | You get an uneditable mesh back (§3 → `cad-geometry-kernels-formats-and-code-cad`) |\n| High `$fn` \u002F fine tessellation while iterating | ⚠️ **2 seconds becomes 2 minutes** (§4.3 → `cad-geometry-kernels-formats-and-code-cad`) |\n| Magic numbers instead of named parameters | Defeats the point of code-CAD (§4.3 → `cad-geometry-kernels-formats-and-code-cad`) |\n| Version-controlling the STL instead of the source | ⚠️ **Same** (§4.3 → `cad-geometry-kernels-formats-and-code-cad`) |\n| Trusting automatic mesh repair blindly | ⚠️ **Heuristic; silently changes geometry** (§4.5 → `cad-geometry-kernels-formats-and-code-cad`) |\n| Laplacian smoothing on a dimensioned part | ⚠️ **It shrinks the model** (§4.5 → `cad-geometry-kernels-formats-and-code-cad`) |\n| Ignoring print orientation for structural parts | ⚠️ **Z is 20–50% weaker. Orientation is a design decision** (§6.1 → `cad-slicing-pipeline-and-processes`) |\n| Horizontal circular holes on FDM | ⚠️ **Sagging top. Use a teardrop** (§7 → `cad-design-tolerances-and-materials`) |\n| Wall thickness not a multiple of extrusion width | Gaps or over-extrusion (§7 → `cad-design-tolerances-and-materials`) |\n| Fully enclosed voids in SLS or SLA | ⚠️ **Trapped powder \u002F resin, permanently** (§6.2 → `cad-slicing-pipeline-and-processes`, §7 → `cad-design-tolerances-and-materials`) |\n| Modelling holes at nominal size for FDM | ⚠️ **They print undersize** (§8 → `cad-design-tolerances-and-materials`) |\n| Trusting a clearance table over a test print | Calibrate your machine and material (§8 → `cad-design-tolerances-and-materials`) |\n| Printed threads for load-bearing joints | ⚠️ **Use heat-set inserts** (§8 → `cad-design-tolerances-and-materials`) |\n| Printing hygroscopic filament without drying | ⚠️ **The most common invisible cause of bad prints** (§9 → `cad-design-tolerances-and-materials`) |\n| Infill density as the strength lever | ⚠️ **Perimeters do more above ~40%** (§5.3 → `cad-slicing-pipeline-and-processes`) |\n| Topology optimization on one load case | Fragile in every other direction (§10 → `cad-generative-automation-and-scanning`) |\n| Manual slicing in a repeatable workflow | ⚠️ **Every slicer has a CLI** (§11 → `cad-generative-automation-and-scanning`) |\n| Treating a scan as a model | ⚠️ **A mesh is not CAD** (§12 → `cad-generative-automation-and-scanning`) |\n\n---\n\n## §14. Numbers\n\n```\nFDM\nNozzle 0.4 mm typical (0.2–0.8) · Layer 0.1–0.3 mm (⚠️ ~25–75% of nozzle Ø)\nExtrusion width ≈ nozzle Ø to 1.2× · Filament 1.75 mm (or 2.85)\n⚠️ Overhang limit ~45–55° · Bridging to ~50 mm with good cooling\n⚠️ Z-strength 50–80% of XY · Accuracy ±0.1–0.5 mm\nFirst layer squish, elephant's foot compensation ~0.1–0.5 mm\n\nCLEARANCES (FDM, per side)\nPress fit 0 to −0.1 · Tight sliding 0.15–0.2 · Free 0.3–0.4 · Print-in-place 0.3–0.5\n⚠️ Holes print undersize: oversize by 0.1–0.4 mm\n\nRESOLUTION BY PROCESS\nMaterial jetting 16 µm · SLA\u002FMSLA 25–100 µm · SLM 20–50 µm\nMJF ~80 µm · SLS ~100 µm · FDM 100–300 µm\n\nTEMPERATURES (nozzle \u002F bed)\nPLA 200\u002F60 · PETG 240\u002F80 · ABS 250\u002F100 · Nylon 260\u002F90 · PC 280\u002F110 · TPU 225\u002F50\n⚠️ PLA softens ~60 °C — glass transition, not melting\n\nEXTRUSION MATH\nE = (layer_h × width × dist) \u002F (π (filament_d\u002F2)²)\n⚠️ 1.75 mm nominal at 1.70 mm actual = ~6% under-extrusion\n\nMESH\n⚠️ Euler: V − E + F = 2 − 2g  for a closed surface of genus g\nManifold: every edge in exactly 2 faces\n```\n\n---\n\n## §15. Books and Tools\n\n| Source | Why |\n|---|---|\n| **Piegl & Tiller, *The NURBS Book*** | ⚠️ **The reference for §1 → `cad-geometry-kernels-formats-and-code-cad`'s surface math** |\n| **Farin, *Curves and Surfaces for CAGD*** | The readable companion |\n| **Botsch et al., *Polygon Mesh Processing*** | ⚠️ **§4.5 → `cad-geometry-kernels-formats-and-code-cad`, definitively** |\n| **de Berg et al., *Computational Geometry*** | Algorithms and the robustness problem |\n| **Shirley, *Ray Tracing in One Weekend*** | ⚠️ **The best free introduction to thinking in 3D geometry code** |\n| **Gibson, Rosen & Stucker, *Additive Manufacturing Technologies*** | ⚠️ **The academic AM reference** |\n| **Redwood et al., *The 3D Printing Handbook*** | ⚠️ **The practical DfAM book — get this one first** |\n| **Bendsøe & Sigmund, *Topology Optimization*** | §10 → `cad-generative-automation-and-scanning` |\n| **ASME Y14.5 (GD&T)** | Tolerancing formally (§8 → `cad-design-tolerances-and-materials`) |\n\n**Tools**: **OpenSCAD**, **CadQuery**, **build123d**, **FreeCAD**, **SolveSpace**\n(⚠️ **an underrated constraint-based parametric modeller**), **Blender**, **Rhino +\nGrasshopper**, **nTop** (implicits), **Onshape** (⚠️ **best commercial API**),\n**Fusion 360**. **Mesh**: trimesh, pymeshlab, MeshLab, Open3D, libigl, Manifold, OpenVDB.\n**Slicers**: §16.2. **Print management**: OctoPrint, Klipper\u002FMoonraker, Mainsail, Fluidd.\n**Communities**: Printables, Thingiverse, MakerWorld, ⚠️ **and the slicer projects'\nGitHub issues, which are the best documentation of real failure modes.**\n\n---\n\n## §16. What Actually Moved — verified August 2026\n\n### 16.1 ⚠️ OpenSCAD's Manifold backend\n**The most significant change to open code-CAD in years, and one worth getting right\nbecause outdated descriptions are everywhere.**\n\n- **OpenSCAD historically used CGAL**, which is exact and ⚠️ **notoriously slow.**\n- **Manifold** replaced it as an alternative backend. **Reported speedups:\n  5–30× over CGAL's fast-csg**, which was itself **30–150× over baseline CGAL Nef\n  routines** — ⚠️ **with a 1,000× improvement reported on at least one model.**\n- **⚠️ Since 2024-09-28 the Manifold backend is no longer experimental** — selectable in\n  Preferences → Advanced → 3D Rendering → Backend, or `openscad --backend=manifold` on the\n  command line. ⚠️ **The old feature-flag method was removed, which broke some\n  command-line scripts.**\n- **⚠️ At that announcement, CGAL was still the default backend**, with Manifold opt-in.\n- **⚠️ That changed on 2025-08-17**, when OpenSCAD maintainer Marius Kintel announced on the\n  project mailing list that **Manifold is now the default backend in development\n  snapshots**, calling it \"battle tested\"; CGAL remains selectable via preferences or\n  `--backend=cgal`. ⚠️ **The most recent tagged \"stable\" release is still 2021.01, which\n  predates Manifold support entirely** — anyone using Manifold at all is already on a\n  development snapshot, where the default has now flipped.\n\n> **⚠️ GOTCHA — two things to be careful about here.**\n> **First, many current sources — including reference documentation and comparison\n> articles — still describe OpenSCAD's kernel as simply \"CGAL.\"** That was accurate and\n> is now at best incomplete. ⚠️ **Check which backend you're actually running before\n> attributing behaviour to a kernel.**\n> **Second, the backends are not equivalent in output.** A February 2026 bug report shows\n> **a model where Manifold produced STL with open edges that PrusaSlicer auto-repaired,\n> while CGAL made most of the model vanish entirely** — and ⚠️ **the reporter's fix was\n> adding a small overlap, i.e. the §2 → `cad-geometry-kernels-formats-and-code-cad` epsilon problem.** **If a model behaves oddly, try\n> the other backend as a diagnostic.**\n\n### 16.2 The slicer landscape\n**⚠️ Almost everything descends from Slic3r.** **OrcaSlicer** is a fork of **Bambu\nStudio**, which forked **PrusaSlicer**, which began as **Slic3r PE**. **Cura** is the\nseparate lineage.\n\n**As of 2026**: **OrcaSlicer** is widely described as the strongest for advanced FDM\ntuning — ⚠️ **best-in-class calibration workflows (temperature, flow, pressure advance,\nretraction, max volumetric speed), the broadest third-party printer support, native\npresets for Klipper input-shaping and pressure-advance, no cloud requirement, and leading\ntree\u002Forganic support generation.** **Bambu Studio** is strongest on Bambu hardware,\n**PrusaSlicer** on Prusa hardware and mature multi-material with a 1–3 month-slower\nrelease cadence, and **Cura** remains the broad beginner-friendly standby with the plugin\necosystem.\n\n**⚠️ Read that as ecosystem fit, not a ranking**: the honest summary from the comparisons\nis that **the right slicer depends almost entirely on what you're printing on**, and\n**Klipper users in particular have a clear answer.**\n\n### 16.3 Code-CAD and the LLM angle\n**CadQuery and build123d** wrap **OCCT**, giving exact B-rep, true fillets and chamfers,\nand **STEP import\u002Fexport that OpenSCAD cannot do.** **build123d** replaces CadQuery's\nfluent method-chaining with **context managers, so ordinary Python loops, references and\nfiltering work naturally.**\n\n⚠️ **One genuinely interesting current finding, reported by more than one party building\nLLM-to-CAD tooling**: **language models write OpenSCAD substantially more reliably than\nCadQuery or build123d** — one benchmark reports **3–4× fewer code errors** — attributed to\ntraining-data volume and to OCCT's complexity leaking through the Python wrapper.\n> **⚠️ GOTCHA — take that with real caution.** ⚠️ **Both sources reporting it are\n> companies whose product is built on OpenSCAD**, so they are not disinterested. **The\n> underlying reasoning is plausible** (OpenSCAD's language is small and its corpus is\n> large), **but this is a vendor-adjacent benchmark, not an independent one.** ⚠️ **And it\n> says nothing about which kernel is better for a human** — the same sources concede that\n> OCCT is the more capable kernel.\n\n---\n\n## §17. Quick Reference\n\n### 17.1 Picker\n| Need | Use |\n|---|---|\n| Parametric part, simple geometry, scriptable | **OpenSCAD** (§4.1 → `cad-geometry-kernels-formats-and-code-cad`) |\n| Same, but needs fillets\u002Fchamfers and STEP | ⚠️ **CadQuery or build123d** (§4.2 → `cad-geometry-kernels-formats-and-code-cad`) |\n| Full CAD app automation | **FreeCAD Python**, or **Onshape REST** (§4.4 → `cad-geometry-kernels-formats-and-code-cad`) |\n| Constraint-based parametric, lightweight GUI | **SolveSpace** (§15) |\n| Organic\u002Fartistic modelling | Blender (⚠️ not engineering CAD) (§4.1 → `cad-geometry-kernels-formats-and-code-cad`) |\n| Lattices, implicit geometry, millions of features | ⚠️ **Implicit\u002FSDF representation** (§1 → `cad-geometry-kernels-formats-and-code-cad`, §10 → `cad-generative-automation-and-scanning`) |\n| Reliable booleans on messy meshes | **Manifold** (§2 → `cad-geometry-kernels-formats-and-code-cad`) |\n| Repair a broken mesh | trimesh \u002F pymeshlab \u002F Netfabb; ⚠️ **voxel remesh as last resort** (§4.5 → `cad-geometry-kernels-formats-and-code-cad`) |\n| CAD → CAD interchange | ⚠️ **STEP** (§3 → `cad-geometry-kernels-formats-and-code-cad`) |\n| CAD → printer | ⚠️ **3MF** (§3 → `cad-geometry-kernels-formats-and-code-cad`) |\n| Batch\u002FCI generation | ⚠️ **Headless CLI — all of them have one** (§11 → `cad-generative-automation-and-scanning`) |\n| Klipper printer | **OrcaSlicer** (§16.2) |\n| Strong part, FDM | ⚠️ **Orient for load along layers; add perimeters, not infill** (§5.3 → `cad-slicing-pipeline-and-processes`, §6.1 → `cad-slicing-pipeline-and-processes`) |\n| Load-bearing threaded joint, FDM | **Heat-set insert** (§8 → `cad-design-tolerances-and-materials`) |\n| Complex geometry, no supports | ⚠️ **SLS\u002FMJF — the powder bed supports it** (§6 → `cad-slicing-pipeline-and-processes`) |\n| Fine detail | SLA\u002FMSLA (§6 → `cad-slicing-pipeline-and-processes`) |\n\n### 17.2 Pre-print checklist\n- [ ] Mesh manifold, watertight, correct normals? (§4.5 → `cad-geometry-kernels-formats-and-code-cad`)\n- [ ] Units correct — and is it 3MF rather than STL? (§3 → `cad-geometry-kernels-formats-and-code-cad`)\n- [ ] Oriented for the load path, not just for print time? (§6.1 → `cad-slicing-pipeline-and-processes`)\n- [ ] Overhangs under ~45°, or supported, or redesigned as chamfers? (§7 → `cad-design-tolerances-and-materials`)\n- [ ] Horizontal holes teardropped? (§7 → `cad-design-tolerances-and-materials`)\n- [ ] Walls a whole multiple of extrusion width? (§7 → `cad-design-tolerances-and-materials`)\n- [ ] Clearances calibrated for *this* machine and material? (§8 → `cad-design-tolerances-and-materials`)\n- [ ] Escape holes for powder\u002Fresin if applicable? (§6.2 → `cad-slicing-pipeline-and-processes`)\n- [ ] Filament dried if hygroscopic? (§9 → `cad-design-tolerances-and-materials`)\n- [ ] Perimeters increased before infill for strength? (§5.3 → `cad-slicing-pipeline-and-processes`)\n\n---\n\n## §18. Method\n\n**§1–§12 → `cad-geometry-kernels-formats-and-code-cad`, `cad-slicing-pipeline-and-processes`, `cad-design-tolerances-and-materials`, `cad-generative-automation-and-scanning` rest on stable material** — NURBS and B-rep mathematics, computational geometry,\nmesh processing, and additive manufacturing process physics — sourced from the references\nin §15, chiefly **Piegl & Tiller**, **Botsch et al.**, and **Gibson, Rosen & Stucker**,\nplus the file-format specifications. ⚠️ **None of that needed web verification; the\ngeometry math is decades old and the process physics is thermodynamics.**\n\n**Two searches were run in August 2026**, confined to the tooling: **the code-CAD\necosystem** and **the OpenSCAD kernel and slicer landscape.**\n\n**⚠️ The second search materially corrected the first.** Several sources returned by the\ncode-CAD search — **including CadQuery's own documentation and multiple 2026\ncomparison articles** — describe OpenSCAD's kernel as CGAL and contrast it unfavourably\nwith OCCT on that basis. **That framing predates the Manifold work.** I followed up\nspecifically and found the **OpenSCAD mailing list announcement (2024-09-28) that Manifold\nis no longer experimental**, a **later mailing list post (2025-08-17) from the same\nmaintainer confirming Manifold became the default backend in development snapshots**, plus\n**the Manifold project's own performance discussion** for the speedup figures. ⚠️ **§16.1\nreflects that; the widely-repeated \"OpenSCAD uses CGAL\" line is now incomplete.**\n\n**Confidence.** **High** in §1–§12 → `cad-geometry-kernels-formats-and-code-cad`, `cad-slicing-pipeline-and-processes`, `cad-design-tolerances-and-materials`, `cad-generative-automation-and-scanning` — established mathematics and process physics, with\nnumbers stated as representative ranges that vary by machine and material. **High** in\n§16.1's Manifold facts, which come from the project and the OpenSCAD maintainers directly,\nincluding that **CGAL remained the default backend at the time of the 2024-09-28\nannouncement, and that Manifold became the default in development snapshots as of\n2025-08-17** — ⚠️ **verify which snapshot and backend you are actually running rather than\nassuming, since the tagged \"stable\" release (2021.01) predates either backend option.**\n\n⚠️ **Two explicit hedges.** **§16.2's slicer assessment is drawn from comparison articles,\nwhich are opinion-shaped and frequently affiliate-monetized**; I have framed it as\necosystem fit rather than a ranking, and the technical lineage (Slic3r → PrusaSlicer →\nBambu Studio → OrcaSlicer) is the part that is unambiguous. And ⚠️ **§16.3's LLM benchmark\nis flagged in place as vendor-adjacent** — **both parties reporting it build products on\nOpenSCAD.** The mechanism they propose is plausible and the finding may well be right, but\n**it is not an independent evaluation and I have not treated it as one.**\n\n**§14's tolerance and clearance figures are starting points, not specifications** —\n⚠️ **the §8 → `cad-design-tolerances-and-materials` advice to run a calibration print is the actual recommendation, and it\nsupersedes any table including mine.**\n",{"name":5,"description":7},"develop","ae32736a1aabddabca5d2c96d665aa0ebc7d8700","src\u002Fvibey_tools\u002Fskills\u002Fplugins\u002Fcad-3d-printing\u002Fskills\u002Fcad-reference",3,"https:\u002F\u002Fgithub.com\u002Fthe-vibey-project\u002Fvibey","https:\u002F\u002Fthe-vibey-project.github.io\u002Fvibey\u002F","https:\u002F\u002Fgithub.com\u002Fthe-vibey-project","https:\u002F\u002Fvibewithadam.matthewsteinberger.com","freedom for software engineers","2026-11-15 05:47:42",{"source":8,"skillName":5,"commands":35,"prompt":45,"zipAvailable":46},[36,39,42],{"tool":37,"command":38},"npx","npx skills add the-vibey-project\u002Fvibey --skill cad-reference",{"tool":40,"command":41},"bunx","bunx skills add the-vibey-project\u002Fvibey --skill cad-reference",{"tool":43,"command":44},"pnpm","pnpm dlx skills add the-vibey-project\u002Fvibey --skill cad-reference","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fthe-vibey-project\u002Fvibey\u002Fblob\u002Fdevelop\u002Fsrc\u002Fvibey_tools\u002Fskills\u002Fplugins\u002Fcad-3d-printing\u002Fskills\u002Fcad-reference\u002FSKILL.md",true,[],[49,56,63,70,77,84],{"skillNo":50,"name":51,"nameZh":6,"description":52,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":53,"categories":54,"keywords":55,"publishedAt":19},"01M7AT1FQJAE1FQYAMDTF490Y4","white-paper-writing","Use when writing white papers, technical reports, policy documents, thought leadership pieces, or any long-form authoritative document. Triggers on requests to write, structure, outline, or review white papers, technical reports, position papers, policy briefs, or evidence-driven arguments. Also use for B2B content marketing strategy, technical documentation requiring authority, academic-style reports, or any document that must educate while persuading. Use when someone asks \"how should I structure this\" for a long-form document.","https:\u002F\u002Fgithub.com\u002Fthe-vibey-project\u002Fvibey\u002Fblob\u002Fdevelop\u002Fsrc\u002Fvibey_tools\u002Fskills\u002Fplugins\u002Fwriting-craft\u002Fskills\u002Fwhite-paper-writing\u002FSKILL.md",[],[],{"skillNo":57,"name":58,"nameZh":6,"description":59,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":60,"categories":61,"keywords":62,"publishedAt":19},"01M7AT16BJRJJKK2MASXRZS76G","prose-technical-mechanics","Use when editing or writing prose at a technical\u002Fmechanical level: choosing between Anglo-Saxon and Latinate diction, placing information in topic vs stress positions, writing periodic vs cumulative sentences, handling sentence rhythm, punctuation as logic, transitions, paragraph structure, or phonesthetics. Use when someone wants to understand WHY prose works or doesn't, not just surface-level style advice. Triggers on word choice, sentence structure, emphasis, rhythm, diction, or any deep writing mechanics question.","https:\u002F\u002Fgithub.com\u002Fthe-vibey-project\u002Fvibey\u002Fblob\u002Fdevelop\u002Fsrc\u002Fvibey_tools\u002Fskills\u002Fplugins\u002Fwriting-craft\u002Fskills\u002Fprose-technical-mechanics\u002FSKILL.md",[],[],{"skillNo":64,"name":65,"nameZh":6,"description":66,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":67,"categories":68,"keywords":69,"publishedAt":19},"01M7AT0W9HT0ZZ9Y287NW99MR3","prose-mechanics","Use when writing, editing, or analyzing prose style; when trying to avoid generic AI-sounding writing; when applying specific prose styles such as journalistic, academic, narrative, KJV biblical, Hemingway plain, Latinate\u002FJamesian, Orwellian, Augustan, Victorian, Early Modern (Bacon, Browne, Milton), or free indirect discourse; or when coaching someone on writing voice and mechanics. Triggers on any request to improve, analyze, or write in a specific prose style, to fix \"AI-sounding\" writing, to make prose more vivid or concrete, to vary sentence rhythm, or to understand how a particular writer achieves their effects.","https:\u002F\u002Fgithub.com\u002Fthe-vibey-project\u002Fvibey\u002Fblob\u002Fdevelop\u002Fsrc\u002Fvibey_tools\u002Fskills\u002Fplugins\u002Fwriting-craft\u002Fskills\u002Fprose-mechanics\u002FSKILL.md",[],[],{"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":19},"01M7AT0KR635JX66X2X6F3E2CP","narrative-structure","Use when structuring stories, pitches, presentations, white papers, or any persuasive narrative; analyzing the hero's journey in fiction or non-fiction; applying StoryBrand for business communication; designing narrative arcs for thought leadership; or understanding Vogler, Snyder, Propp, or Campbell frameworks. Triggers on any narrative structure, storytelling, pitch structure, StoryBrand, hero's journey, three-act structure, Freytag, Save the Cat, narrative arc, or \"how should I structure this story\u002Fpitch\u002Fpresentation\" request.","https:\u002F\u002Fgithub.com\u002Fthe-vibey-project\u002Fvibey\u002Fblob\u002Fdevelop\u002Fsrc\u002Fvibey_tools\u002Fskills\u002Fplugins\u002Fwriting-craft\u002Fskills\u002Fnarrative-structure\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":19},"01M7AT0AKGW09NKKZDYBT8VRDE","legal-brief-writing","Use when writing legal briefs, motions, or any court filing; when analyzing judicial cognition and persuasion; when applying elite brief-writing techniques from Roberts, Clement, Kagan, Garner; or when structuring legal arguments for maximum persuasion. Also use for autistic\u002Fneurodivergent advocates who need to understand how their natural communication style maps to elite legal advocacy. Triggers on any legal writing, brief drafting, motion preparation, or legal argument structuring request.","https:\u002F\u002Fgithub.com\u002Fthe-vibey-project\u002Fvibey\u002Fblob\u002Fdevelop\u002Fsrc\u002Fvibey_tools\u002Fskills\u002Fplugins\u002Fwriting-craft\u002Fskills\u002Flegal-brief-writing\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":19},"01M7AT00VWPS4Q8B5VEMXX9NQT","journal-publishability-criteria","Use whenever a research paper, article or preprint is being written, revised, reviewed or published, and specifically before every publication of docs\u002Fpaper.md. Covers what legitimate journals actually gate on, in order of gating — the editor's desk screen (scope, novelty, package problems), what reviewers judge (methodological soundness, claims the evidence can carry, statistical and qualitative reporting), EQUATOR reporting guidelines, the ICMJE authorship criteria, COPE's view of text recycling, the near-universal generative-AI policy (no AI author, disclosure, author responsibility), TOP 2025 transparency standards, how to verify a journal is legitimate, submitting without an institution, and a pre-submission checklist. Triggers on requests to evaluate, review, prepare or submit a paper, to judge publishability, to write a declarations or data-availability section, to disclose AI use, or to check a journal.","https:\u002F\u002Fgithub.com\u002Fthe-vibey-project\u002Fvibey\u002Fblob\u002Fdevelop\u002Fsrc\u002Fvibey_tools\u002Fskills\u002Fplugins\u002Fwriting-craft\u002Fskills\u002Fjournal-publishability-criteria\u002FSKILL.md",[],[]]