Forge Studio →

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.

01

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:

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.

Two fields, either works

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…WhenYou get
New design
the form above
You know roughly what you want to buildStraight to a printable model in your workspace
The assistant
a chat
You're figuring out the electronics tooA 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.

02

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:

  1. 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.
  2. 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."

You
A weather station housing, about 90 mm across, with a small OLED window.
F
Recognises weather station → builds a louvered radiation shield over a sensor base, sizes the shield to 90 mm, cuts an OLED window, and lists the BME280 sensor, screen, MCU and battery as parts to buy.
You named the type; the shield, louvers, and vents came free. You only spent words on what was specific to you.
Why it matters

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.

03

Anatomy of a good prompt

A strong prompt has up to five parts. Only the first is required; add the rest as they apply.

the object · rough size · what goes inside / on it · colours · how it mounts / finish
You
A desk enclosure roughly 100 × 70 × 40 mm for an ESP32 and a 0.96" OLED, in matte black, wall-mounted with a soft, rounded look.
F
Object → a designed instrument case. Size → 100×70×40. Inside → an ESP32 socket + an OLED bezel on top. Colour → black. Mount/finish → wall ears + softly rounded corners.

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.

Rule of thumb

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.

The vocabulary
04

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 · sconceAn articulated desk lamp — weighted base, raked arm, tilting shade
speaker · boombox · sound barA sealed cabinet with a tuned bass port, amp bay, and grille
gridfinity · storage bin · parts tray · desk organiserA modular storage bin + baseplate (with compartments if you ask)
clock · wall clock · timepieceA round clock — case, dial, numerals, hands, movement
watch · wristwatchA small watch case with strap lugs + a crown
speedometer · gauge · dashboard · instrument clusterAn arc-scale gauge, or several gauges on a fascia panel
fan · desk fan · blowerA ducted fan — rotor, finger-safe guards, stand with a driver bay
sign · light box · LED name plate · edge-litA backlit sign (spell a word, or shape it to a logo)
handheld · retro console · Game Boy · pocket gameA clamshell handheld — screen window, buttons, 18650 bay
weather station · radiation shield · Stevenson screenA louvered outdoor sensor housing + display
gearbox · reduction · reducer · gear trainA printable spur-gear reduction — housing, cover, pinion + gear
camera slider · dolly · linear railA dovetail rail + sliding carriage with ¼-20 mounts
planter · plant pot · smart planterA self-draining pot with a plant-monitor pocket + saucer
wall mount · tool holder · pegboard · tool rackA 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 · chassisA full RC vehicle — drive, steering, wheels, a body shell
robot arm · gripper · manipulatorA 3-DOF servo arm with a gripper on a bench
rover · line-follower · hexapod · walkerA 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.

05

Saying dimensions

Give sizes in millimetres, in plain words. All of these read cleanly:

"about 120 mm across" "roughly 100 × 70 × 40 mm" "a 3.5-inch screen" "a 2-inch driver" "tall, around 40 cm" "a snug fit for a 65 × 56 mm board"

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.

You don't set walls

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.

06

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:

You
A wall clock — green case, white face, black numbers, red hands.
F
Colours each component separately and assembles a multi-colour 3MF — open it in an AMS/multi-material slicer and it prints pre-painted, one plate.
Say it like a painter

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.

Worked examples — simple to advanced
07

Simple objects

The whole-design types make one-liners powerful. Name it, add a detail or two, done.

You
A 2×1 gridfinity bin, 3 units tall, split into two compartments.
F
A Gridfinity bin (42 mm cells, 7 mm height units) with a divider and a matching baseplate it locks into.
You
A table clock with Roman numerals I to XII and minute marks, cream face, black hands.
F
A round clock on a stand (because you said "table," not "wall"), full Roman numeral ring, 48 minute divisions, cream dial, black hands, sized for a quartz movement.
"table / desk / standing" → a foot to stand on. "wall" → a keyhole to hang. The word picks the mount.
You
A heart-shaped light-box sign that spells "HOME" and glows.
F
A backlit sign whose outline follows the shape, letters thinned to a glowing membrane, with an LED channel, wiring cavity, switch, and a printed translucent back — no bought acrylic needed.
08

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.

You
An enclosure for an Arduino Nano, a 16×2 LCD, and a USB-C jack — rugged, screwed shut.
F
Mounts the Nano on standoffs, sets the LCD into a bezel (on top, so it prints in one piece), bores a USB-C port, and joins the lid with M3 corner screws because you said "rugged / screwed."
Forge carries 40+ named part sockets — MCUs, displays, sensors, batteries, relays, chargers. Naming the part is enough.
Quantities count

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.

09

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.

You
A carrier deck with three bays in a row — a 2S battery pack, a controller board, and a temp/humidity sensor — all under a rounded shell.
F
A peg-grid plate carrying three spaced, non-overlapping bays sized to each payload, with a box cover auto-fitted over the whole thing.
Words that build a system: carrier / deck / rack / bay / module / row / housed / under a shell.

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.

Housed or open?

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.

10

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.

You
A red RC pickup on a grey chassis, 35 mm wheels, with head and tail lamps, a USB charge slot, and a spare tyre on the tailgate.
F
A driveable pickup: N20 gearmotor + gear reduction + articulated steering + real wheels, a red pickup body on a grey chassis, white/red lamps, a wall-aware USB slot over the board, and a rear-door spare.
Body styles: pickup · truck · saloon · bus · buggy · lowboy · excavator. Say "SG90 servo" and it fits the common 9g servo.
Word matters

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.

Going further
11

Grounding with files

Uploads make Forge exact instead of approximate. All are optional, under "Ground it with your files."

UploadWhat it doesHow 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 standoffsName the part; the datasheet grounds its true dimensions
Big one

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.

12

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.)

You
Make it 5 mm taller and move the USB-C to the left wall.
F
Grows the height by 5 mm, relocates just the USB-C port, leaves everything else byte-for-byte the same, and shows you the exact diff.

Good refinement phrases are small and concrete:

"make the case green" "add ventilation" "add a second bay" "make it 5mm taller" "move the display to the top" "round the corners" "switch the lid to screws"
Refine vs recompile

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").

13

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 partsPut accessories on the vehicle (lamps, spare tyre, charge slot) — a chassis builds alone
Mention a board but don't upload it, expecting exact mountsEither upload the board file, or just name the part and let its socket mount it
Specify wall thickness or tolerancesGive outside size or payload only; Forge sets print-safe walls from the material
Need two of something but write it onceSay the count — "2× sensor" or "keypad (2)"
Want a front-panel display on a one-piece printExpect 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.

14

Trigger-word cheat sheet

Keep this nearby. The left words route to a ready-made design; the right words tune it.

Name the design

lampspeakerclockwatch gauge / speedometerdashboardfan gridfinity / storage binsign / light boxhandheld weather stationgearboxcamera slider planterwall mount / tool holderdevice case RC car / truck / pickuprobot armroverhexapod

Tune it

mount · wall · DIN rail · solar clock · wall vs table/desk numerals · Roman · 1–12 · minute marks lid · snap · screws · hinge · slide finish · soft/rounded · boxy · bevel sealed · weatherproof housed vs open / bare car · pickup/truck/saloon/bus/buggy/lowboy/excavator car · lamps · spare tyre · charge slot servo · SG90 / 9g count · "2×" · "(2)" colour per part · "green case, white face"
One sentence to remember

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.