Microscale Forge · For everyone using the Studio
Say what you want. Get a printable thing.
Forge Studio builds real, 3D-printable designs from a description. This guide teaches the one skill that matters: turning a design in your head into a prompt Forge nails on the first try.
The Studio at a glance
When you start a new design, the Studio asks for a few things. Only the first (or the second) is required — everything else sharpens the result:
2S 14500 battery · ESP32-C3 controller · motor driver
The first build takes about 30–60 seconds. It lands in your workspace — a 3D preview you can spin, downloadable files (STEP, STL, 3MF), a chat box to refine it, and full version history. Your description becomes the project's prompt: you can edit it and recompile any time.
Describe your design is for the shape and intent ("a weatherproof case for my sensor, wall-mounted"). Your components is a plain parts list, one per line, when you mostly care about housing specific hardware. Fill in either — one is enough — or both: the description sets the form, the list guarantees nothing gets dropped.
Two ways to start a design
The Studio home offers two front doors. Pick by what you have in hand:
| Start with… | When | You get |
|---|---|---|
| New design the form above | You know roughly what you want to build | Straight to a printable model in your workspace |
| The assistant a chat | You're figuring out the electronics too | A conversation that lands on a real, orderable parts list — then generates the design from it |
The assistant is the electronics-first path: it opens with "What do you want to build?" and works best when your first message says what it does, how it's powered, your skill level, and a budget — for example, "a battery-powered outdoor soil-moisture sensor with WiFi, beginner, around ₦15,000." It searches the catalog, builds a bill of materials, and hands off to the Studio with Add 3D-printed enclosure. Everything else in this guide is about the design prompt itself, which both paths share.
How Forge reads you
This is the mental shift that makes everything click. Forge is not sculpting freehand from your words. It does two things, in order:
- Picks a design type from what you name — a lamp, a clock, an RC truck, an enclosure, a gridfinity bin. There are 30-plus engineered types, each a complete product.
- Fills in the numbers — dimensions, colours, which parts go where — from the specifics you gave, using sensible defaults for anything you left out.
So the single most important move is to name the object first, then add specifics. "A desk lamp" already gives you a weighted base, a raked arm, and a tilting shade. Now you just adjust: "a tall desk lamp, matte black, with a wide shade."
If you describe a lamp as "a stick with a cone on top," Forge has to guess. If you say "a desk lamp," it uses the real, print-tested lamp design and your adjectives tune it. Name the thing, then describe it.
Anatomy of a good prompt
A strong prompt has up to five parts. Only the first is required; add the rest as they apply.
You don't need all five, and you don't need to be exact — "about," "roughly," "a little taller" all work. Forge fills gaps with defaults and you refine from there. The parts you do name are the parts you control.
Be specific about what you care about; stay vague about what you don't. Every number you give is a number Forge won't have to guess — but a good default beats a wrong guess, so don't invent dimensions you don't actually need.
Words that name a design
Because Forge picks a type from your words, knowing the words that land is the whole game. Say any of these and you get the matching engineered design. (A fuller list is the cheat sheet at the end.)
| Say something like… | …and you get |
|---|---|
| lamp · light · task light · sconce | An articulated desk lamp — weighted base, raked arm, tilting shade |
| speaker · boombox · sound bar | A sealed cabinet with a tuned bass port, amp bay, and grille |
| gridfinity · storage bin · parts tray · desk organiser | A modular storage bin + baseplate (with compartments if you ask) |
| clock · wall clock · timepiece | A round clock — case, dial, numerals, hands, movement |
| watch · wristwatch | A small watch case with strap lugs + a crown |
| speedometer · gauge · dashboard · instrument cluster | An arc-scale gauge, or several gauges on a fascia panel |
| fan · desk fan · blower | A ducted fan — rotor, finger-safe guards, stand with a driver bay |
| sign · light box · LED name plate · edge-lit | A backlit sign (spell a word, or shape it to a logo) |
| handheld · retro console · Game Boy · pocket game | A clamshell handheld — screen window, buttons, 18650 bay |
| weather station · radiation shield · Stevenson screen | A louvered outdoor sensor housing + display |
| gearbox · reduction · reducer · gear train | A printable spur-gear reduction — housing, cover, pinion + gear |
| camera slider · dolly · linear rail | A dovetail rail + sliding carriage with ¼-20 mounts |
| planter · plant pot · smart planter | A self-draining pot with a plant-monitor pocket + saucer |
| wall mount · tool holder · pegboard · tool rack | A gridfinity wall plate + a clip-in holder |
| case / box / enclosure for my <project> | A designed instrument case — bezel, buttons, knobs, connectors |
| RC car · truck · pickup · buggy · chassis | A full RC vehicle — drive, steering, wheels, a body shell |
| robot arm · gripper · manipulator | A 3-DOF servo arm with a gripper on a bench |
| rover · line-follower · hexapod · walker | A driving or walking robot base |
If nothing matches, Forge composes a bespoke system from scratch — bays on a carrier plate, or coaxial round parts. You're never limited to the named types; they're just the fast path.
Saying dimensions
Give sizes in millimetres, in plain words. All of these read cleanly:
You can dimension by the thing rather than the box: "a case for a Raspberry Pi 4," "sized for a 2S 14500 pack," "fits a 56 mm clock movement." Forge knows common part footprints and sizes the housing around them with the right clearances.
Never specify wall thickness, clearances, or tolerances — Forge sets those from the material so the part actually prints. Give the outside size or the payload; leave the engineering to the engine.
Colour & material
The Material and Colour pickers set the whole-part default. Materials: PLA, PLA (Matte), PETG, ABS, TPU. Colours include Black, White, Red, Blue, Gray, Green, Yellow, and translucent options.
But you can also name colours in the prompt, per part — and that's how you get a multi-colour print. Forge reads each colour onto the piece you attached it to:
Attach the colour to the noun — "a navy cabinet with a black grille," "an orange body on a grey chassis." Named prompt colours override the picker, so the picker is just your fallback for anything you didn't call out.
Simple objects
The whole-design types make one-liners powerful. Name it, add a detail or two, done.
Housing electronics
Name the boards and modules and Forge mounts each on the right socket — real standoffs, and a cutout for the connector. You don't place anything; you list it.
If you need more than one, say so plainly — "2× relay" or "keypad (2)". Forge places a separate instance for each, and won't merge or drop duplicates.
Prefer the components list field for a pure parts box — one item per line. Each line becomes a mounted, cut-out bay, and every bought part lands on your BOM automatically.
A multi-part system
When several parts share one build, describe the arrangement — a row of bays on a carrier, optionally housed under a shell. This is the "custom parts assembled into a system" case.
For a dashboard, describe the gauges and where they sit: "an instrument cluster with a clock on the left and a 0–120 speedometer on the right." Forge lays them on a fascia panel, each seated in its own bored opening.
Say "housed," "enclosed," "under a shell," or "with a body" to add a cover. Say "open," "bare," "exposed," or "a rack/tray" to leave the payload accessible. For anything that moves — a robot arm, a fan rotor — leave it uncovered.
Vehicles & robots
An RC vehicle is one rich object — name the body style and the details, nothing else. The real drivetrain, steering, and wheels come with it.
For a spare wheel, say "spare tyre" — that's the switch that adds one. Don't describe a vehicle plus loose extra parts ("a truck and two boxes"): an RC chassis builds alone. Put accessories on it (lamps, charge slot, spare), not beside it.
Robots follow the same one-object rule: "a rover / line-follower" builds a two-wheel driving base; "a hexapod walker" builds a six-legged body; "a robot arm with a gripper" puts a 3-DOF arm on a bench beside its controller bay.
Grounding with files
Uploads make Forge exact instead of approximate. All are optional, under "Ground it with your files."
| Upload | What it does | How to prompt with it |
|---|---|---|
| PCB file .kicad_pcb · .step · Gerber .zip | Lands connector cutouts and mounting standoffs exactly where your board's holes and ports actually sit | "An enclosure for this board" — Forge sizes the box to it and places everything itself |
| Panel / layout image png · jpg · webp | Reads the relative layout — what control/port goes where — from a photo, mockup, or labelled sketch | "Lay out the front like this image" |
| Component datasheet pdf · image | Reads the part's measured body, mounting holes, and connectors, and mounts it on real standoffs | Name the part; the datasheet grounds its true dimensions |
Only set up a "hosted PCB" by uploading a board file. If you just mention a board in text without uploading it, Forge mounts it via its named socket instead (which is what you want) — a fabricated host would give you an empty box with no standoffs. Upload the file, or name the part; don't half-do it.
Refining by chat
You rarely nail everything first try — and you don't have to. Once a design lands, the workspace has a refine box: "Ask for a change — make it 5mm taller, move the USB-C to the left wall, add vents on the lid." Type a change in plain English and Forge revises only that, keeping the rest identical, then re-renders. (You refine from any finished version.)
Good refinement phrases are small and concrete:
Refine tweaks the design you're looking at — small, surgical, keeps everything else. Editing the inputs (the prompt or components list) and recompiling re-runs the whole thing from changed source. Use refine for adjustments; edit-and-recompile for a rethink.
Every turn is a saved version you can revert to and branch from — so experiment. One change per message reads most reliably; stack a couple if they're related ("taller and move the port").
Pitfalls & fixes
| If you… | Do this instead |
|---|---|
| Describe a shape instead of naming it ("a stick with a cone") | Name the object ("a desk lamp"), then adjust with adjectives |
| Ask for an RC car plus loose extra parts | Put accessories on the vehicle (lamps, spare tyre, charge slot) — a chassis builds alone |
| Mention a board but don't upload it, expecting exact mounts | Either upload the board file, or just name the part and let its socket mount it |
| Specify wall thickness or tolerances | Give outside size or payload only; Forge sets print-safe walls from the material |
| Need two of something but write it once | Say the count — "2× sensor" or "keypad (2)" |
| Want a front-panel display on a one-piece print | Expect it on top (lid) — a wide display can't print bridging a vertical wall; Forge moves it and tells you |
| Cover a moving part (arm, fan rotor) | Leave it open — say "uncovered" or just don't ask for a shell |
Most first drafts are 80% right. The fastest path to 100% is a generate, a look at the preview, and two or three small refine messages — not one perfect mega-prompt.
Trigger-word cheat sheet
Keep this nearby. The left words route to a ready-made design; the right words tune it.
Name the design
Tune it
Name the object, give the sizes and parts you care about, attach colours to the pieces, say how it mounts — then refine. That's the whole method.