agentleFS
tangency-labstangency-labs/solidcraft/skills/solidcraft-sheetmetal/SKILL.md

solidcraft-sheetmetal

Skill17k starsChanged 20 days agoApache-2.0View on GitHub

Use when building or changing a sheet metal part in SolidCraft through its MCP server (flange, segments, hem, fold, unfold, flat pattern, DXF, bend table), or when a request describes bends in words.

Trending

More talk lately.about the whole repository

Dec 2025: 0 mentionsJan 2026: 0 mentionsFeb 2026: 0 mentionsMar 2026: 0 mentionsApr 2026: 0 mentionsMay 2026: 0 mentionsJun 2026: 0 mentionsJul 2026: 0 mentionsAug 2026: 0 mentionsSep 2026: 0 mentionsOct 2026: 61 mentionsNov 2026: 31 mentions
Dec 2025Jun 2026Nov 2026
Mentions a month of the tangency-labs/solidcraft repository that our weekly crawl found. There is no adoption data for this file yet.

Who's talking about tangency-labs/solidcraft

The biggest 5 of 92 mentions linking to the repository that our crawl found. Each line is their own headline.

See all 92

Talked about on GitHub, YouTube, Bluesky and the web (92 times).

On GitHub · 50

45 more on GitHub

On YouTube · 25

20 more on YouTube

On Bluesky · 9

4 more on Bluesky

On the web · 8

3 more on the web

The file

Files
SKILL.md

SolidCraft sheet metal

Overview

A sheet metal part is a flat sheet plus bends: base first, then flanges. Work the numbers first (rule, flat size, stock, angles, heights, segment boundaries), build in batch calls, then check with measure, sheet.flat_pattern and sheet.export_bend_table. Contract, bend arithmetic, recipes: reference.md.

segments needs feat/sheet-flange-segments; unfold_method needs #9911.

Before the first call

  1. skill_reference {"skill":"solidcraft-sheetmetal"}; elsewhere read reference.md.
  2. inspect_design {"measure":false,"sketches":false}; with timeline features, ask before new_design or open.
  3. sheet.rules gives thickness, K-factor, radius, reliefs, gap. A flange takes none of them; sheet.manage_rules first when no rule fits.
  4. Plan the flat size, bend fractions, flat area times thickness (the volume you check) and the stock.

Build

  • Rule: sheet.manage_rules {"name":"AL2","thickness":"2 mm","k_factor":0.5,"bend_radius":"1 mm","active":true}. Ask the shop for the K-factor; never invent it.
  • Base: a closed sketch profile, then sheet.flange {"sketch":"Base"}.
  • Edge: sheet.flange {"type":"edge","edges":[...],"height":...,"angle":...}; {point, angle, height, segments} gives one edge its own values.
  • Segments: stretches {from, to} tiling the stretch the sheet still has, each a bend with its own angle, height and side; opposite sides are cut in the flat.
  • Chains: then bends the far edge again; refused with segments, naming the edge.
  • Other: sheet.path_flange, sheet.hem, sheet.fold, sheet.convert.
  • Parameters, not numbers; edge picks are plain numbers.

Verify

  • sheet.flat_pattern and sheet.export_bend_table {"format":"json"} give the flat size, outline, each bend's centre line, length and allowance: check where a segment landed.
  • measure must match the flat area times thickness; a bend that leaves the volume unchanged has not built, unless it turns the other way.
  • inspect.interference/inspect.clearance against mating bodies; screenshot {"source":"model","view":"iso"}.

The AI workflow (FR-17 to FR-20)

  1. Segments: derive count and boundaries from the intent (stiffeners, clearances, mating faces), state the assumption and confidence, offer an alternative, compute the fractions.
  2. Angles: one angle labelled high (geometry), medium (shop standard) or low (inferred), plus an alternative; refuse when the geometry contradicts the words.
  3. Words to parameters: map the phrase, read the numbers back when ambiguous. "90 degree flange 20 mm high on the long edge" is sheet.flange {"type":"edge","edges":[[100,0,2]],"angle":"90 deg","height":"20 mm"}.
  4. Optimisation: at most 8 candidates over fractions, angles, heights and sides, scored by inspect.interference volume 0, inspect.clearance at least the gap, flat within stock, radii at or above the rule's. Stop at the objective; report the winner, its margin and each iteration.

Red flags

ThoughtDo instead
"Assume the fraction direction"Check the bend table, or keep the partition symmetric.
"Leave a gap between segments"Segments tile the edge; a set-back is a different feature.
"It reported ok"measure against flat area times thickness and the bend table.

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.