Files
makeCAD/skills
momysnow 60b9e9d188 Edit Joint: show the two sides and pick them again (#9686) (#9692)
* claim: #9686

Co-Authored-By: Claude <noreply@anthropic.com>

* Edit Joint: joint.edit takes the two sides

joint.edit accepts a and b in the form joint.create takes them (read by the same origin_param), so a joint can move its attachment without being deleted. A side left out keeps its place. The two sides must stay on different occurrences, checked as joint.create does. Limits, values, expressions and the name are kept; a relation's values start again where its parts are.

joint.edit gets an input contract and reply type (schema/joints.rs), and leaves schema/unconverted.txt.

Co-Authored-By: Claude <noreply@anthropic.com>

* Edit Joint shows both sides and picks them again

The Edit Joint dialog now shows the two sides in the same selection inputs as Joint, each pre-filled with the face or edge of its own component under the origin. OK sends joint.edit a or b only for a side picked again, so an untouched side keeps its origin exactly.

Co-Authored-By: Claude <noreply@anthropic.com>

* Edit Joint: a moved side turns the part as joint.create would

joint.edit kept the joint's old angle when a side changed, so the part could turn by a half turn about its axis when the new origin's x lay the other way. When a side moves and no angle is given, the angle is worked out again as joint.create does (the least turn from where the part is now); a relation's angle is its tilt and stays.

The mechanisms reference says joint.edit takes a and b.

Co-Authored-By: Claude <noreply@anthropic.com>

* Edit Joint: pre-fill sides by name, send the angle only when changed

A side shows the face or edge its snap names, the piece nearest its stored pick when the name has several, else the one nearest that pick; it no longer searches outward from the frame origin, which could show the plate beside a hole for the hole's wall. A point or frame side shows nothing. OK sends the angle only when the user changed it, so a side moved without it turns the part as joint.create would.

Co-Authored-By: Claude <noreply@anthropic.com>

* Edit Joint: a moved side leaves an angle expression alone (#9686)

Co-Authored-By: Claude <noreply@anthropic.com>

---------

Co-authored-by: Claude <noreply@anthropic.com>
2026-10-31 02:27:54 +00:00
..

Agent skills

Skills for contributing to SolidCraft and modelling through its MCP server. Each folder is one skill in the Agent Skills format: a SKILL.md with a name and a description that tell the agent when to load it, and an optional supporting reference file.

The modelling documents are built into SolidCraft: its MCP server's skill_reference tool returns them, so an agent without file access (such as the one in SolidCraft's own chat) can still read a skill's reference. The contributor skills (everything except modeling, editing, checking and mechanisms) are for repository work and are not embedded in that tool. AGENTS.md routes to them; cargo xtask skills fails when its table and this folder disagree or a file, cargo xtask command or skill they name is gone.

Skill Loads when the agent
solidcraft-contributing helps someone set up a fork, choose and claim an issue, and submit a contribution for review; the rules every PR follows
solidcraft-ground-rules adds a dependency, asset or wording: independence, licences, attribution, the product name
solidcraft-crash-safety writes non-test Rust, handles hostile input or investigates a crash report
solidcraft-commands adds a command or decides which crate code belongs in
solidcraft-ui adds a dialog, panel, camera input, icon or colour
solidcraft-ui-text adds a label, message or translation
solidcraft-file-formats changes what a design saves, or touches import and export
solidcraft-preferences adds a setting or changes a default
solidcraft-tests places or runs tests
solidcraft-performance works on slow code, the window thread or the wasm build
solidcraft-packaging prepares a release or changes packages
solidcraft-agent-tools runs the app, drives the control channel or changes MCP tools
solidcraft-modeling builds a new part (enclosure, bracket, plate, flange, …)
solidcraft-editing changes, fixes or extends an existing design
solidcraft-checking builds, changes or ports a design, next to the two above: parameter ranges, every allowed value, exact STEP comparison, regression tests, designs kept in git
solidcraft-mechanisms builds, drives or animates an assembly: components, joints, motion links, closed loops such as actuators, contact sets, motion studies
solidcraft-reporting hears that something went wrong (a crash, a failed command, a wrong shape or number, a hang): reproduces it in a fresh design, shrinks it to a minimal script and writes the bug report

The modelling skills teach the agent to:

  • plan the part as numbers
  • build it in a few batch calls with parametric positions
  • verify every stage with measure against values it computed itself
  • skip the large replies it doesn't need, such as the unfiltered command catalog and full topology dumps

They also list the traps that otherwise cost failed calls. Examples are the sketch axes of the XZ plane, edge picks that snap to the nearest edge, and cuts that miss but still report success.

The modelling skills are written for SolidCraft 0.8 and later; solidcraft-mechanisms for main after 0.11.1 (the next release), which counts the degrees of freedom of closed loops; solidcraft-reporting for 0.18 and later.

Install

The modelling skills, for Claude Code in all projects:

git clone --depth 1 https://github.com/tangency-labs/solidcraft
cp -r solidcraft/skills/solidcraft-{modeling,editing,checking,mechanisms} ~/.claude/skills/

Windows (PowerShell):

git clone --depth 1 https://github.com/tangency-labs/solidcraft
foreach ($s in 'modeling','editing','checking','mechanisms') { Copy-Item -Recurse solidcraft\skills\solidcraft-$s $HOME\.claude\skills\ }
  • One project only: copy the folders into that project's .claude/skills/ instead.
  • Other agents: for agents that read the Agent Skills format, copy the folders into the skills directory their documentation names.
  • Updating: copy the folders again after you update SolidCraft.
  • Contributing: the contributor skills need no install. Tell your assistant: "I want to contribute to SolidCraft. Read https://github.com/tangency-labs/solidcraft/blob/main/skills/solidcraft-contributing/SKILL.md and help me get started."

Maintaining

  • The worked example in solidcraft-modeling/reference.md runs in CI. skill_reference_example_builds_as_documented in crates/mcp/src/tests.rs builds it, checks the documented volume, changes a parameter and checks it again.
  • The sketch-plane table is covered by sketch_plane_axes_match_the_skill_reference in the same file.
  • The worked example in solidcraft-mechanisms/reference.md runs in CI too: mechanisms_skill_example_moves_as_documented builds it, drives the hinge and checks the actuator stroke, the linked panel and the stop against their analytic values.
  • skills_name_only_real_tools_and_commands checks that every tool and command the skills call exists.
  • solidcraft-checking/scripts/tests checks that skill's helpers, its traps and conventions, and the facts behind the corrections in solidcraft-modeling: PYTHONDONTWRITEBYTECODE=1 uv run --no-project --with pytest --with build123d pytest -p no:cacheprovider skills/solidcraft-checking/scripts/tests. The tests run the solidcraft-cli on PATH, not the workspace build, and CI does not run them.
  • When a command, a parameter name or a behaviour that these files describe changes, update them in the same PR.
  • Facts that describe current limitations, such as edge picks without a distance limit, should go once the limitation is fixed.