agentleFS
mementomori-comementomori-co/maker-mastery/.claude/skills/dfm-review/SKILL.md

dfm-review

Skill2 starsChanged 26 days agoMITView on GitHub

Use when an STL or part spec must be reviewed for FDM before slicing (orientation, plate face, overhangs, islands, bridges, material and assembly path). Runs the dfm-engineer in a fresh context and returns the review; the lead saves it beside the part.

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Every part before /qa-gate or /preprint-check, and after any geometry change from cad-engineer or organic-modeler.

    line 12

≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Overview

Input: $ARGUMENTS, an STL path, optionally mating-part paths. Output: the review in the reply (dfm-engineer has no Write tool), 50 lines or fewer.

When to use

Every part before /qa-gate or /preprint-check, and after any geometry change from cad-engineer or organic-modeler.

Steps

  1. Measure with .venv\Scripts\python.exe plus trimesh/manifold3d: bounds, watertight, volume, bodies.
  2. Overhang angle = angle between the face normal and -Z; a face is an overhang when it is below support_threshold_angle (read the value for your process profile from knowledge\02-bambu-studio\support-settings.md or with tools\resolve_profile.py). Table per candidate orientation; islands per layer; longest bridge. tools\overhang_gate.py can produce the per-z table.
  3. Material pointer to knowledge\03-materials\ (for example the HDT/Vicat table and the PLA vs PETG note). One material per part unless multi-material is the point. Assembly: interference at nominal and translation sweeps against mating parts; state the verdict. Splits only at natural part boundaries, with keyed joints.
  4. Report: orientation, plate face and finish, supports (target none) with numbers, material, assembly, checks not run.

Common rationalizations

RationalizationReality
"Another session already checked assembly."No check counts without its script and output on disk.
"Slope or angle, same thing."The convention is easy to invert; use the definition in step 2.

Red flags

  • An orientation chosen without the overhang table.
  • Writing into a folder listed in protected_roots in config\paths.yaml.

Verification

  • Numbers for overhang area, islands, bridges per orientation.
  • Assembly verdict stated with the sweep that proves it.
  • Checks not run listed.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.