agentleFS
randomonkey05randomonkey05/SolidCraft-Agent-Skills/skills/solidcraft-modeling/SKILL.md

solidcraft-modeling

Skill12 starsChanged 17 days agoApache-2.0View on GitHub

Use when building a new part, enclosure, bracket, plate, flange or any other 3D solid in SolidCraft through its MCP server (tools such as batch, execute, measure, screenshot), or when a SolidCraft session is using many tool calls or tokens.

2 other projects use a version of this, 2 of them edited.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

11 rules. About 0 are common, 5 are distinctive, and 6 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈5

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 6

    Very specific

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

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

    Run inspect_design {"measure":false,"sketches":false}, even when you think the session is empty.

    line 13
  2. Very specific:

    If the design has timeline features, ask before calling new_design or open, because both discard unsaved work.

    line 15
  3. Distinctive:

    every feature, with the world point you will use for each edge or face pick

    line 19
  4. Distinctive:

    Stages: use one batch per stage:

    line 23
  5. Distinctive:

    Risky steps: put a risky step in a batch of its own, so a failure does not roll back the work around it.

    line 28
  6. Distinctive:

    Do not split a batch just to read ids back.

    line 33
  7. Distinctive:

    All 12 edges of the cube in one call and one by one gave the identical body (R5: 61 590.76 mm3, 26 faces: 12 cylinder, 8 sphere, 6 plane.

    line 52
  8. Very specific:

    Not tested: different radii on edges of the same vertex (use separate features and measure each).

    line 54
  9. Very specific:

    Each stage: run measure {} (about 0.9 KB per body) and compare the volume, bbox and face count with your numbers.

    line 59
  10. Very specific:

    Parameter test: run set_parameter. Expect errors: [], then measure again.

    line 61
  11. Very specific:

    When the server is bridged, source defaults to the whole app window and view also turns the user's camera, so pass "source":"model" and …

    line 68

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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

SolidCraft modeling

Overview

Work the part out as numbers first. Then build it in a few large batch calls, and check each stage with measure against values you computed yourself. A clean build takes 3-4 build batches, about 10-13 calls with the checks. Command shapes, plane axes, ids, reply sizes and known traps are in reference.md next to this file, so you do not need to explore the command catalog.

Before the first call

  1. In SolidCraft's own chat or any MCP client, call skill_reference {"skill":"solidcraft-modeling"}. Elsewhere, read reference.md.
  2. Run inspect_design {"measure":false,"sketches":false}, even when you think the session is empty.
    • The SolidCraft server's instructions end with Backend: connected to the SolidCraft app when it drives the user's open app, and with Backend: headless otherwise.
    • If the design has timeline features, ask before calling new_design or open, because both discard unsaved work. You can also build into the open design.
  3. Write a plan:
    • the parameters
    • the placement: centre the part on the origin so patterns and mirrors can work from the planes
    • every feature, with the world point you will use for each edge or face pick
    • the expected volume and bounding box

Build

  • Stages: use one batch per stage:
    1. parameters, sketch, dimensions, finish and the first feature
    2. fillets and shell
    3. holes, cuts and patterns
  • Failures: a batch is all-or-nothing. On failure, read failed.index and failed.error, fix that step only, and send the batch again.
  • Risky steps: put a risky step in a batch of its own, so a failure does not roll back the work around it. This covers booleans between curved faces that touch, and anything you have not done before.
  • Reply size: in large designs, pass "verbose": false to batch and execute.
  • Sketch ids are predictable, so later steps in the same batch can use them:
    • Each sketch counts each kind from 1 (l1, c1, a1, p1).
    • Count what the earlier steps of that sketch created. For example, rectangle.center makes l1-l6 and p1-p5.
    • Do not split a batch just to read ids back.
  • Positions that must follow a parameter come from:

    • sketch dimensions to "origin" with expression values ("w/2 - wall - 6")
    • expression fields such as solid.cylinder base:["w/2-6","d/2-6","wall"]

    A plain number never follows a parameter.

  • Repeats: solid.pattern.rectangular takes expression spacing; solid.mirror takes XY/XZ/YZ, a construction plane or {origin, normal} (origin coordinates may be length expressions such as ["half", 0, 0]). A mirror or pattern feature cannot be mirrored or patterned again.
  • Edge and face picks snap to the nearest edge or face. An edge pick farther than 5% of the body's size from every edge is refused (the nearest edge is 15.000 mm away). On a large body that limit is wide (about 48 mm on a 949 mm board), so compute the exact midpoint from your geometry (the vertical corner edge of a centred box is [w/2, d/2, h/2]).
    • Picks must be plain numbers.
    • A pick is resolved once and then follows its edge when parameters change.
    • A face can be given by name instead of a point (faces:["F1:+z"], the face of sheet.convert). body_topology lists each face's name, a point that lies on it (the centroid of a face with a hole is in the hole) and, for a cylinder, {origin, axis, radius}.
  • Profiles: extrude takes every region by default, and a region inside another is a hole in it: two concentric circles give a ring. A third circle inside the ring gives a separate disc body. Pass profiles to choose regions.
  • Order: fillet the outside edges before you shell, so the shell follows the fillets. There are two exceptions:
    • An edge of the face the shell removes, such as the rim of an open box: round it after the shell, because the shell can fail on it.
    • A fillet between two curved faces, such as a sphere joined to a cylinder: the shell then fails with offset: only bodies with planes, cylinders, cones, spheres and tori. Shell first. The inside corner then stays sharp, so the wall there is thinner than thickness.

Fillets and chamfers at corners where edges meet (tested on 0.29.0)

Tests on 40 mm cubes, picks on the edge midpoints:

  • Three non-coplanar edges that meet at a vertex round with a spherical patch at the corner. One by one and all three in one solid.fillet call gave the identical body (R5: 63 376.73 mm3, 10 faces, 1 sphere).
  • All 12 edges of the cube in one call and one by one gave the identical body (R5: 61 590.76 mm3, 26 faces: 12 cylinder, 8 sphere, 6 plane; analytic value 61 592.2).
  • Radius limit on a 40 mm cube: three edges at a vertex pass with R15 (58 768.9 mm3) and R39 (34 758.5 mm3) and fail with R40 ("not supported yet: a fillet larger than the faces next to it"). All 12 edges pass with R19 (35 990.7 mm3) and fail with R20 ("the blend is larger than a corner radius") and R21 ("the blend is larger than the neighbouring faces; the largest radius that fits is 20 mm"). Half of the side is the limit when fillets of neighbouring edges meet. A failed fillet leaves the design unchanged.
  • Not tested: different radii on edges of the same vertex (use separate features and measure each).
  • Check by formula. Removal at a vertex with three edges of length L and radius r: 3(1 - pi/4) r^2 (L - r) + r^3 (1 - pi/6). Rounded cube (side a, all 12 edges): (a-2r)^3 + 6r(a-2r)^2 + 3 pi r^2 (a-2r) + 4 pi r^3 / 3. Measured against these: 0.002 % (R5, 12 edges), 0.003 % (R15, 3 edges), 0.013 % (R39, 3 edges) and 0.025 % (R19, 12 edges: 9 mm3 under the analytic value; cause not investigated).
  • Sketch chamfers on several corners: sketch.chamfer.equal_distance, sketch.chamfer.two_distance and sketch.chamfer.distance_angle take points:[corners] and are one operation. On a 60 x 40 x 10 plate they gave 23 500, 23 520 and 23 584.3 mm3, all exact. distance_angle makes the second leg d*tan(angle). The sketch dof goes up with each chamfer.

Verify

  • Each stage: run measure {} (about 0.9 KB per body) and compare the volume, bbox and face count with your numbers. A cut or hole that leaves the volume unchanged has missed, even though it reported success.
  • Timeline health: inspect_design {"measure":false,"sketches":false} shows each feature's error and warning.
  • Parameter test: run set_parameter. Expect errors: [], then measure again; the COM and bbox should move by the amounts you computed.
  • Positions: measure does not say where a feature sits.
    • On an asymmetric part, check the COM shift you computed.
    • On a symmetric part (a mirrored or patterned layout) the COM does not move, so take a top-view screenshot and compare distances in pixels against a known size.
    • body_topology is a last resort: it costs 25-45 KB and splits cylinders into half faces.
  • Final look: one screenshot {"source":"model","view":"iso","width":480,"height":320}. Use "view":"top" for features inside walls, which the iso view hides.
    • width and height apply only to model renders.
    • When the server is bridged, source defaults to the whole app window and view also turns the user's camera, so pass "source":"model" and leave out view unless the user wants the camera moved.

Finish

export {path} writes .step for CAD, .3mf/.stl for printing, or .urdf (an assembly with joints, for robot simulators). save {path} writes .solidcraft. A design saved by 0.29.0 has format solidcraft/46, which 0.28 and older cannot open (from the release video): keep the original.

Red flags

ThoughtDo instead
"Offset inward means a negative distance"On a rectangle chain sketch.offset went inward with a POSITIVE distance (0.29.0). A wrong sign gave a full block of 56 700 mm3 instead of 12 900: measure.
"List all commands first"reference.md, or list_commands {"filter":"<distinctive word>"}. The unfiltered list is over 100 KB.
"Check positions with body_topology"measure COM and bbox against your numbers.
"Inspect the sketch"sketch.solve returns dof and the profile count in under 100 bytes. Run sketch.inspect on its own, never inside a big batch.
"new_design for a clean start"When the server is bridged, ask first.
"It reported ok, so it worked"Only a measure that matches the computed values counts.

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.