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
- bherbruck/solidcraftedited, first seen Nov 8, 2026
- tangency-labs/solidcraftedited, first seen Nov 8, 2026
Other versions2 projects use a version of this.
Word for word · 0
None found.
Edited · 2
- bherbruck/solidcraft★ 15k92% same
- tangency-labs/solidcraft★ 15k92% same
Wrote their own version · 0
None found.
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository19 other files it gives its agents.
- solidcraft-3d-print-dfmSkill
- solidcraft-assembliesSkill
- solidcraft-checkingSkill
- solidcraft-delivery-gateSkill
- solidcraft-dfm-reviewSkill
- solidcraft-drawing-and-tutorial-readingSkill
- solidcraft-editingSkill
- solidcraft-engineering-drawingSkill
- solidcraft-hole-fastener-rulesSkill
- solidcraft-mechanismsSkill
- solidcraft-requirements-and-sanitySkill
- solidcraft-robust-build-orderSkill
- solidcraft-sheet-metal-flatpackSkill
- solidcraft-sheet-metalSkill
- solidcraft-shell-and-tangent-arcsSkill
- solidcraft-speed-modeling-lessonsSkill
- solidcraft-step-partsSkill
- solidcraft-sweep-and-boolean-hangsSkill
- solidcraft-tutorial-recipesSkill
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
- Very specific: line 13
Run inspect_design {"measure":false,"sketches":false}, even when you think the session is empty.
- Very specific: line 15
If the design has timeline features, ask before calling new_design or open, because both discard unsaved work.
- Distinctive: line 19
every feature, with the world point you will use for each edge or face pick
- Distinctive: line 23
Stages: use one batch per stage:
- Distinctive: line 28
Risky steps: put a risky step in a batch of its own, so a failure does not roll back the work around it.
- Distinctive: line 33
Do not split a batch just to read ids back.
- Distinctive: line 52
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.
- Very specific: line 54
Not tested: different radii on edges of the same vertex (use separate features and measure each).
- Very specific: line 59
Each stage: run measure {} (about 0.9 KB per body) and compare the volume, bbox and face count with your numbers.
- Very specific: line 61
Parameter test: run set_parameter. Expect errors: [], then measure again.
- Very specific: line 68
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 …
≈ “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.
Files
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
- In SolidCraft's own chat or any MCP client, call
skill_reference {"skill":"solidcraft-modeling"}. Elsewhere, readreference.md. - 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 appwhen it drives the user's open app, and withBackend: headlessotherwise. - If the design has timeline features, ask before calling
new_designoropen, because both discard unsaved work. You can also build into the open design.
- The SolidCraft server's instructions end with
- 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:
- parameters, sketch, dimensions, finish and the first feature
- fillets and shell
- holes, cuts and patterns
- Failures: a batch is all-or-nothing. On failure, read
failed.indexandfailed.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": falsetobatchandexecute. - 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.centermakesl1-l6andp1-p5. - Do not split a batch just to read ids back.
- Each sketch counts each kind from 1 (
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.
- sketch dimensions to
- Repeats:
solid.pattern.rectangulartakes expression spacing;solid.mirrortakesXY/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"], thefaceofsheet.convert).body_topologylists each face'sname, apointthat 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
profilesto 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 thanthickness.
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.filletcall 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
measureeach). - 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_distanceandsketch.chamfer.distance_angletakepoints:[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_anglemakes 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'serrorandwarning. - Parameter test: run
set_parameter. Expecterrors: [], thenmeasureagain; the COM and bbox should move by the amounts you computed. - Positions:
measuredoes 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_topologyis 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.widthandheightapply only to model renders.- When the server is bridged,
sourcedefaults to the whole app window andviewalso turns the user's camera, so pass"source":"model"and leave outviewunless 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
| Thought | Do 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. |
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
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.

