DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to run a JSON script to export a bracket as STEP with Solidcraft

Use the headless CLI to run a script and write a STEP file without opening the app.

Who it is forAn engineer or pipeline owner who needs the same part regenerated on demand whenever a spec changes.

The problemRebuilding a part by hand each time a value changes wastes time and invites mistakes.

The outcomeA bracket.step file produced from a versioned JSON script that can be rerun.

What you need first

  • Windows, macOS or Linux desktop, or a web browser for the browser app
  • Rust toolchain and the repo cloned from github.com/tangency-labs/solidcraft for the cargo commands
  • Claude Code installed for the MCP registration step

Steps

  1. Clone the repo from github.com/tangency-labs/solidcraft and install Rust.
  2. Check the available commands with cargo run --release -p solidcraft-cli -- commands.
  3. Run the example script with cargo run --release -p solidcraft-cli -- run examples/bracket.json --out bracket.step.
  4. Open bracket.step in any tool that reads STEP files to confirm the geometry.
  5. Copy examples/bracket.json, change a value in the copy, and rerun the command with a new output name.

Prompt for your agent

In the tangency-labs/solidcraft repo, run examples/bracket.json with solidcraft-cli and write <output-file>.step. Expected output: a STEP file at that path. Verify the file exists, is not empty, and that the command exits without errors.

Caveat. The README describes the script format but does not describe the geometry the bracket example produces, so check the output yourself.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page