Build a LEGO Robot with Claude Code

Design, validate, and build a LEGO desk robot with Claude Code and Studio.

Introduction

30 Second Summary

A design on a screen can look perfect while hiding pieces that cannot connect. The truth arrives when the finished object has to stand on its own.

In this project, you will turn an idea for a walking desk robot into an LDraw model with Claude Code. BrickLink Studio will test the design before the physical build proves whether it really works.

What You'll Build

You'll place a physical robot on your desk in a walking pose with its matching digital render and printable instructions ready to show beside it.

By the end of this project, you'll have:

  • A 100-to-110-part robot that you can open and rotate as a complete digital model.
  • A validated Studio design with visible results for collisions, connectivity, stability, color availability, and price.
  • A photorealistic render, a printable PDF instruction booklet, and a BrickLink Wanted List that support the physical build.
  • Secret Mission: Give the robot a swappable facial expression using only part types and colors from its existing inventory.

Are there any prerequisites?

No previous LEGO inventory or digital design experience is required. You need a Mac running macOS 13.0+ with 4 GB+ RAM.

You also need an eligible paid Claude plan. Budget an estimated US$40-US$60 before shipping and tax if you are starting from nothing.

Before We Start

Before any tools enter the picture, lock in the personality or job your robot should have. Your reason for displaying a physical desk buddy gives every later design choice a clear direction.

Set Up the AI-to-Brick Workshop

Your robot moves from an AI-generated model to an independently checked digital build. That journey needs one shared workspace before design begins.

Claude Code handles the text-heavy draft in LDraw. BrickLink Studio supplies the independent checks around that draft.

In this step, get ready to:
  • Prepare Claude Code for authenticated terminal use.
  • Install the digital model tools inside one project folder.
  • Connect BrickLink to the finished workshop.
Install and authenticate Claude Code

Claude Code runs inside Apple Terminal on your Mac. Its first launch uses your browser to authenticate your account.

Claude Code requires eligible paid access because the free Claude plan does not include it. This starts recurring billing that you can cancel before renewal if one month is enough for your build.

Check the subscription cost

Claude Pro is the lowest individual option in this guide at US$20 when billed monthly. Check the renewal date before confirming your subscription.

  • Open the official Anthropic pricing page in your browser.
  • Select an eligible paid Claude plan.
  • Complete the subscription checkout with the account you want to use for Claude Code.

The version check below identifies the setup path your Mac needs. A missing-command result is an expected starting state.

  • Press Cmd+Space to open Spotlight.
  • Type Terminal into Spotlight.
  • Press Enter to open Apple Terminal.
  • Check whether Claude Code is already installed by running this command:
claude --version

What does this command check?

This asks the installed CLI to print its version. A version number confirms that your shell can find Claude Code.

✔️ I see version 2.1.318

Good. Claude Code 2.1.318 is ready for authentication.

ⓧ I see an older version

Your Mac can find Claude Code, but this workshop uses version 2.1.318.

  • Install the current native release by running this command:
curl -fsSL https://claude.ai/install.sh | bash

What does this command do?

This downloads Anthropic's native installer over HTTPS. Bash runs the installer on your Mac.

  • Close the current Terminal window after the installer finishes.
  • Press Cmd+Space to reopen Spotlight.
  • Type Terminal into Spotlight.
  • Press Enter to open a fresh Terminal window.
  • Verify the updated installation by running:
claude --version

What does this verification prove?

The fresh Terminal window loads the installed command into its shell environment. The output should contain version 2.1.318.

That update is complete. Your Mac now has the Claude Code version used throughout this workshop.

Still seeing the older version?

Close every Terminal window before opening a fresh one. An older window can keep using the command path it loaded before installation.

Check that the installer completed without a network interruption.

Help me update Claude Code on my Mac.

ⓧ Command not found

Claude Code has not been installed in the shell used by this Terminal window.

  • Install Claude Code by running the official native installer:
curl -fsSL https://claude.ai/install.sh | bash

What does this command do?

This downloads Anthropic's native installer over HTTPS. Bash runs the installer on your Mac.

  • Close the current Terminal window after the installer finishes.
  • Press Cmd+Space to reopen Spotlight.
  • Type Terminal into Spotlight.
  • Press Enter to open a fresh Terminal window.
  • Verify the installation by running:
claude --version

What does this verification prove?

A version number confirms that the fresh Terminal window can find Claude Code. The output should contain 2.1.318.

The installation is working. Claude Code is now available from Apple Terminal.

Claude Code still unavailable?

Confirm that the installer reached its completion message before you closed Terminal.

Check your internet connection if the installer stopped while downloading files.

Help me install Claude Code on my Mac.

The first interactive launch moves briefly to your browser for authentication. Terminal waits while you approve access.

  • Start the Claude Code authentication flow by running:
claude

What does this command do?

This opens an interactive Claude Code session in Terminal. The first launch begins the browser authentication flow.

  • Sign in through the browser with your paid Claude account.
  • Approve the authentication flow.
  • Return to Apple Terminal after the browser confirms access.

You should see an interactive Claude Code session in Terminal. That is the first part of your workshop working.

Authentication not completing?

Confirm that the browser is signed in with the same paid Claude account you activated earlier.

Return to Terminal after browser approval because the session continues there.

Help me complete Claude Code authentication.

  • Close this Terminal window after the authenticated session appears.
Install the brick design tools

Studio 2.0 for Mac gives you one place to open an LDraw model. It also supplies the checks that keep Claude's claims independent.

Why use Studio for this project?

A single design application keeps the model moving through one review loop.

  • Studio opens LDraw model files.
  • Studio checks collisions, connectivity, stability, colors, and prices.
  • Studio creates renders, instructions, and Wanted Lists.

macOS may ask for approval while the installer runs. Approving that request allows the desktop installation to finish.

  • Open the official Studio download page in your browser.
  • Download the latest Studio 2.0 build for Mac.
  • Select Downloads in the Finder sidebar after the download finishes.
  • Open the downloaded Studio installer.
  • Complete the macOS installation flow.
  • Press Cmd+Space to open Spotlight.
  • Type Studio into Spotlight.
  • Press Enter to open Studio.

You should see Studio's Welcome Screen. The digital building environment is now running.

Studio not opening?

Confirm that the installer finished before searching for Studio.

If macOS blocked the launch, review the security prompt that appeared during installation.

Help me open BrickLink Studio on my Mac.

The official LDraw Parts Library maps each .dat filename to part geometry. This project uses library release 2026-10.

  • Switch back to Finder.
  • Select Documents in the Finder sidebar.
  • Click File in the macOS menu bar.
  • Click New Folder.
  • Type Claude-LEGO-Robot as the folder name.
  • Press Return to create the folder.

Finder should now show Claude-LEGO-Robot inside Documents. This folder holds every model, report, render, and instruction file created later.

  • Download complete.zip from the official LDraw library.
  • Select Downloads in the Finder sidebar.
  • Double-click complete.zip to extract it.
  • Select the extracted ldraw folder.
  • Press Cmd+C to copy the folder.
  • Select Documents in the Finder sidebar.
  • Open Claude-LEGO-Robot.
  • Press Cmd+V to place ldraw inside the project folder.

The library must keep its original internal structure. Claude depends on those exact folders when it checks part references.

  • Open the copied ldraw folder in Finder.
  • Confirm that parts appears inside ldraw.
  • Confirm that LDConfig.ldr appears inside ldraw.

You should now have ~/Documents/Claude-LEGO-Robot/ldraw/parts plus ~/Documents/Claude-LEGO-Robot/ldraw/LDConfig.ldr. That completes the local parts reference your robot needs.

Missing the parts folder?

Confirm that you moved the extracted ldraw folder instead of the unopened complete.zip archive.

Keep every folder inside ldraw in its original location. Rearranging the library can make valid parts appear missing.

Help me fix my LDraw library folders.

Connect BrickLink and launch the workshop

The BrickLink marketplace carries the project from a digital inventory toward real parts. Registration is free, while a LEGO Account supplies the required account identity.

  • Open LEGO.com in your browser.
  • Create your LEGO Account.
  • Open the BrickLink website in your browser.
  • Start the BrickLink registration flow.
  • Use your LEGO Account when the registration flow requests it.
  • Complete the BrickLink registration.

Your LEGO Account now supports the BrickLink services used later for the Wanted List. The account labels can vary as the registration flow changes.

  • Switch back to Studio.
  • Sign in to BrickLink from Studio.
  • Complete the account approval in your browser if Studio opens it.
  • Return to Studio after approval.
  • Keep the Welcome Screen available.

Claude needs to start from ~/Documents/Claude-LEGO-Robot so it can inspect the local LDraw library. The final launch anchors every generated artifact to that folder.

  • Press Cmd+Space to open Spotlight.
  • Type Terminal into Spotlight.
  • Press Enter to open Apple Terminal.

Before you launch Claude Code, do you expect it to begin inside the folder that contains your LDraw library?

  • Move Terminal into the robot project folder and launch Claude Code by running:
cd ~/Documents/Claude-LEGO-Robot
claude

What do these commands do?

  • The first command moves Terminal into ~/Documents/Claude-LEGO-Robot.
  • The second command starts an interactive Claude Code session from that project folder.

You should see Claude Code open interactively in Terminal. It is now running from the folder that contains your robot workspace.

  • Switch to Finder.
  • Select Documents in the Finder sidebar.
  • Open Claude-LEGO-Robot.
  • Open ldraw.
  • Confirm that parts is present.
  • Confirm that LDConfig.ldr is present.
  • Switch to Studio.
  • Leave the signed-in Welcome Screen displayed.

Your workshop is ready. Claude Code can reach the official parts library, while Studio is waiting to open the model it creates.

The full design workspace is now connected. Next, you will delegate the first visual-first robot prototype to Claude Code.

Generate a Visual-First Prototype

Your AI-to-brick workshop is ready. Claude Code can create the model file while BrickLink Studio turns that text into a robot you can rotate.

A polished robot render can hide impossible connections. This step deliberately prioritizes the walking silhouette before any independent validation.

In this step, get ready to:
  • Delegate a 100-to-110-part robot prototype to Claude.
  • Open the prototype in Studio and save a photorealistic render.
Delegate the first LDraw draft to Claude

An LDraw model stores every brick as a text-based part reference. Claude can inspect your local parts library before generating those references.

  • Switch back to the Claude Code session from earlier.
  • Paste the design brief below into Claude Code:
Inspect ./ldraw/parts and ./ldraw/LDConfig.ldr before writing anything. Create prototype.ldr for a fixed-pose, non-motorized LEGO desk robot that looks as if it is walking. Use 100 to 110 type-1 part-reference lines, and reference only .dat filenames that actually exist under ./ldraw/parts. Use official colors from LDConfig.ldr and never use color 24 on a type-1 line. Keep most studs facing upward so Studio can divide the build into steps. Keep the robot no more than about 16 studs high and 10 studs wide. Build a recognizable head, torso, two arms, two legs, and two feet. Make the pose visually dynamic with most of the torso shifted over one narrow planted foot. Add a two-part antenna assembly exactly one plate height above the head without connecting it, as a visual placeholder. Insert 0 STEP after groups of roughly 4 to 6 parts. Before finishing, verify every referenced .dat filename against the local library and write design-report.md with the part count, unique part filenames, colors, dimensions assumed, and all known risks. Do not claim that the model is physically valid because Studio will test it next.

What does this brief control?

  • The ./ldraw/parts check keeps every part filename grounded in your installed library.
  • The ./ldraw/LDConfig.ldr check keeps the model within official color definitions.
  • The part count keeps the robot small enough for a desk-sized physical build.
  • The 0 STEP boundaries separate groups for later instruction work.
  • The design-report.md file records the prototype part count.
  • The report also lists unique filenames and colors.
  • The report records assumed dimensions and known risks.
  • The report leaves physical validity for Studio to test independently.
  • Submit the brief by pressing Enter.
  • Review Claude's completion message after it finishes generating the model.
  • Confirm the completion message names prototype.ldr.
  • Confirm the completion message names design-report.md.

You should see Claude report a prototype with 100 to 110 part references. It should also confirm that the referenced part filenames were checked against the local library.

Good progress. Your robot now exists as an LDraw model with a written record of its assumptions and risks.

Missing a prototype file?

If Claude stops before creating both files, tell it which artifact is missing. Ask it to continue from the original brief without changing the constraints.

If Claude reports that it cannot find the library, confirm its session is still open at ~/Documents/Claude-LEGO-Robot.

Help me finish the LDraw prototype and report.

Open and render the prototype

Studio converts the generated part references into a model you can inspect from every angle. This first pass checks the robot's appearance and walking silhouette.

  • Return to Studio's Welcome Screen from earlier.
  • Click Open file.
  • Select Documents in the file picker sidebar.
  • Open the Claude-LEGO-Robot folder.
  • Select prototype.ldr.
  • Click Open.
  • Rotate the model until its walking silhouette is clear.

Before you render it, ask yourself whether the image alone can reveal every hidden build problem.

  • Open the rendering workflow by clicking File.
  • Select Render image….
  • Select Photoreal as the render type.
  • Set the camera angle in Preview.
  • Start the render by clicking Render.
  • Save the image in the Claude-LEGO-Robot folder as prototype-render.png.
  • Keep the render preview open until Studio closes it automatically.

Studio shows a preview while it renders. The preview window closes automatically when the image is ready.

You should see a small robot with a recognizable head and body. Its narrow-footed stance should create a clear walking pose.

Your robot has made it from text to a visible walking pose you can show. Physical validity remains untested.

  • Leave the antenna and stance unchanged for the next audit.

Prototype not rendering correctly?

If Studio cannot open the model, confirm that you selected prototype.ldr from the Claude-LEGO-Robot folder.

If the robot is cropped, adjust the camera in Preview. Start the render again after the whole robot fits inside the frame.

Help me render my LDraw robot prototype in Studio.

Your visual-first prototype now has a model file, a design report, and a photorealistic render. Next, Studio will reveal what the polished image cannot prove.

Audit the Prototype in Studio

Your prototype-render.png proves the walking silhouette looks convincing. A polished render can still hide impossible connections.

Now BrickLink Studio becomes an independent checker for prototype.ldr. You will turn its visible evidence into an audit you can trust.

In this step, get ready to:
  • Run Studio's physical build checks.
  • Record unavailable part-color combinations.
  • Establish a Used USD pricing baseline.
Check collisions and color legality

Collision detection highlights overlapping pieces as wireframes. The Color Validator finds unavailable part-color combinations.

  • Click Collision in the Studio toolbar.

You'll see the Collision icon turn red. Any colliding part appears as wireframe.

  • Inspect the complete robot from several angles.
  • Record the wireframe findings here: your collision observations.

Why Collision Is Guidance

Studio documents that collision detection is not always exact. Treat each wireframe as guidance for the audit.

The physical build remains the final test.

  • Select the Color Validator tab next to the Steplist.

Any unavailable part-color combination appears as a Problem part.

  • Record each unavailable combination here: your Color Validator problems.
  • Leave Autofix unused.

Unsure What to Record?

If Collision shows no wireframes, record that Studio found no visible collision. If Color Validator shows no Problem parts, record that result too.

Ask for help interpreting the current Studio view.

Expose connectivity and stability problems

A connectivity check groups pieces that share physical connections. A stability check evaluates connections plus support against a flat surface.

Before you inspect connectivity, do you expect the polished robot to form one connected group? Studio is about to test that assumption.

  • Click Stability.
  • Select the Connectivity tab.

You'll see the main robot as one transparent group. You'll see the disconnected two-part antenna as a pink group.

  • Record the connectivity result here: your disconnected antenna observation.

You caught the exact gap the render concealed. The antenna remains a separate physical assembly.

Antenna Not Showing in Pink?

  • Confirm that the Connectivity tab is selected.
  • Rotate the model until the antenna is visible above the head.

Get help checking the connectivity view.

  • Select Stability to return to the summary.
  • Inspect the support zones beneath the robot.

You'll see red support zones where the stance lacks enough bottom support.

Pink highlights are cautions. Red highlights are warnings.

  • Record the unstable support areas here: your red stability zones.
  • Record the connection cautions here: your pink stability cautions.
  • Record the connection warnings here: your red stability warnings.

How to Read Stability Results

  • Transparent parts cause no reported stability problem.
  • Green support zones stand on a flat surface.
  • Pink highlights indicate connection cautions.
  • Red highlights indicate connection warnings.
  • Red support zones indicate insufficient bottom support.

Studio can flag pieces that are physically well connected. Record each category separately so Claude Code receives precise evidence.

Establish the price baseline

The BrickLink Price Guide gives the prototype a consistent comparison point. Used parts priced from current sale listings create the baseline for later revisions.

  • Open Edit in Studio's top menu.
  • Select Preferences….

You'll see Studio's pricing controls in the Preferences window.

  • Set Currency to USD.
  • Set Condition to Used.

The pricing preferences now show USD with Used parts selected.

  • Set the pricing basis to Current items for sale average.

You'll see Current items for sale average selected as the pricing basis.

Pricing data can take a few moments to load. That short wait is Studio collecting the available Price Guide values.

  • Open Model in Studio's top menu.
  • Select Model Info.
  • Wait for the part prices to finish loading.

You'll see the prototype's parts with their available price data.

  • Record the model subtotal here: your prototype subtotal.
  • Select a price column to sort the table.
  • Record the most expensive rows here: your highest-priced part-color combinations.
  • Record combinations with no listed price here: your unpriced part-color combinations.

What Does This Estimate Mean?

Studio calculates this average across sellers from all countries. Country selection does not filter the price data.

A missing price generally signals a nonexistent or extremely rare part-color combination.

Shipping affects the final checkout total. Tax plus seller minimums can raise it further.

Prices Not Loading?

  • Confirm that Studio remains signed in to BrickLink.
  • Return to Model Info after your internet connection is available.

Get help diagnosing missing Studio prices.

Before the final check, do you think the polished robot represents one connected assembly? Your next clicks test that prediction.

  • Dismiss the Model Info window.
  • Click Stability.
  • Select the Connectivity tab.

You'll again see the main robot as one transparent group. The disconnected antenna remains pink.

Strong work. Your attractive prototype now has independent evidence covering geometry, availability, stability, connectivity, and price.

Your prototype audit is complete. Next, you'll use these findings to turn the visual-first robot into a buildable desk buddy.

Repair and Verify the Robot

Your BrickLink Studio audit turned the prototype's hidden flaws into concrete evidence. The disconnected antenna proved that a polished render can still hide a separate physical assembly.

This step feeds that evidence back to Claude Code for a focused repair. Studio then acts as the independent referee for the revised LDraw model.

In this step, get ready to:
  • Use the recorded Studio audit to generate a corrected robot.
  • Repeat every independent Studio check until the final model passes.
  • Save the validated model files plus a photorealistic render.
Give Claude the Studio evidence

Claude needs the observations from your Studio audit. Each finding becomes a constraint for the corrected robot.

  • Switch back to the Claude Code terminal session from earlier.
  • Paste the repair brief below into Claude Code.
Revise prototype.ldr into desk-buddy-final.ldr using the Studio audit below. Attach the two-part antenna to the head with a legal connection instead of leaving a gap. Widen the feet, place both feet on the same ground plane, and redistribute the torso so the walking pose remains recognizable but the support zone is stable. Replace unavailable colors and expensive or unpriced part-color combinations using only filenames that exist in ./ldraw/parts. Preserve 100 to 110 total type-1 part references by swapping or redistributing parts rather than simply adding many parts. Keep the build mostly studs-up for automatic instructions. Recheck all referenced filenames, retain useful 0 STEP boundaries, and update design-report.md with the final count and every change made.

Studio collision findings:
Studio connectivity findings:
Studio stability findings:
Studio Color Validator findings:
Studio Model Info subtotal and expensive parts:

What Does This Brief Control?

  • The antenna constraint removes the deliberately floating group.
  • The stance constraints widen the support area while preserving the walking pose.
  • The parts constraints keep the model between 100 and 110 type-1 references.
  • The 0 STEP constraint retains useful boundaries for the instruction workflow.
  • The design-report.md requirement captures the final count plus the revision rationale.
  • Add each recorded Studio observation below its matching audit label.
  • Submit the completed brief to Claude Code.

Claude should create desk-buddy-final.ldr without replacing prototype.ldr. It should also update design-report.md with the final count plus every change.

  • Click the Finder icon in the macOS Dock.
  • Select Documents in the Finder sidebar.
  • Open the Claude-LEGO-Robot folder.
  • Confirm that desk-buddy-final.ldr appears beside the updated design-report.md.

That is the first repair loop complete. Your revised model now reflects evidence gathered outside Claude.

Final Model Missing or Incorrect?

  • Ask Claude to create desk-buddy-final.ldr if it edited prototype.ldr directly.
  • Ask Claude to revise the model if the report shows fewer than 100 or more than 110 type-1 references.
  • Ask Claude to check every referenced filename against ldraw/parts if Studio cannot load a part.

Share Claude's response plus the affected audit finding for focused help. Help me diagnose why Claude did not create the required final LDraw model.

Re-run every independent check

The revised file remains a proposal until Studio checks it.

Collision detection reveals visible overlaps. Connectivity reveals separate physical assemblies.

Stability tests the support zone. Color Validator flags unavailable part colors.

Before you run the checks, which prototype problems do you expect the evidence-driven revision to remove?

  • Return to Studio from earlier.
  • Open desk-buddy-final.ldr from the Claude-LEGO-Robot folder.
  • Turn on Collision in the Studio toolbar.

You should see the complete robot with no visible wireframe parts.

  • Click Stability.
  • Select the Connectivity tab.

You should see one transparent connected group. The antenna should no longer appear as a separate pink group.

  • Return to the Stability summary.

You should see green support zones with no red unstable zone.

  • Open the Color Validator tab beside the Steplist.

You should see no Problem parts in the final model.

Why Studio Remains the Referee

Studio documents Collision as guidance because its detection is not always exact. Studio also treats Stability conservatively.

Together, the checks provide evidence that is independent from Claude's geometry review. The physical build remains the final test.

A failed check gives Claude one focused problem to solve. Small revisions make each visible change easier to verify.

  • Return to Claude Code if any result still fails.
  • Give Claude the exact visible part or region from the failed check.
  • Request one focused revision for that finding.
  • Reopen the revised desk-buddy-final.ldr in Studio after Claude finishes.

Keep Each Revision Focused

Change one failed area at a time. This keeps a price fix from quietly breaking the stance or antenna connection.

  • Recheck Collision.
  • Recheck Connectivity.
  • Recheck Stability.
  • Recheck Color Validator.
  • Repeat the focused revision loop until all four checks pass.

You have closed the digital validation loop when every check reaches the expected state. The robot is now connected with stable support plus no known Color Validator problems.

Still Seeing a Failed Check?

  • Name the exact wireframe part if Collision still highlights a region.
  • Name each pink group if Connectivity still shows separate assemblies.
  • Describe the red support zone if Stability still marks the stance as unstable.
  • Record the affected part-color combination if a Color Validator Problem row remains.

Share the visible result for focused help. Help me turn this Studio validation failure into a precise Claude repair request.

Lock the final digital version

Studio's Used-parts average gives you a consistent pricing baseline. The average includes sellers from all countries, so checkout costs remain outside the target.

Before opening Model Info, do you think the repairs increased or reduced the prototype subtotal?

  • Open Model in Studio.
  • Select Model Info.
  • Wait for the final model prices to load.
  • Compare the Used-parts average with the US$40 target.

✔️ The Average Is US$40 or Less

Good result. The final design meets the parts-subtotal target before shipping plus tax.

ⓧ The Average Exceeds US$40

A few rare part-color combinations can dominate the estimate. A focused replacement can lower the average while preserving the validated structure.

  • Sort the Model Info table by price.
  • Record the highest-priced or unpriced rows here: the expensive or unpriced final-model rows.
  • Return to the Claude Code session from earlier.
  • Request lower-cost replacements for the expensive or unpriced final-model rows.
  • Reopen the revised desk-buddy-final.ldr in Studio.
  • Repeat the full Studio validation suite.
  • Reopen Model Info.
  • Confirm that the new Used-parts average is US$40 or less.

Once the average reaches the target, your final design has an affordable sourcing baseline. Shipping plus seller minimums still affect the later checkout total.

The validated model now needs durable files for editing, sharing, plus presentation.

  • Use Studio's save controls to save the validated model as desk-buddy-final.io inside Claude-LEGO-Robot.

You should see desk-buddy-final.io as the current Studio model.

  • Open File in Studio.
  • Select Export As.
  • Export the validated design as desk-buddy-final.ldr.
  • Keep the .mpd output if Studio creates a multi-part document.
  • Switch to Finder.
  • Return to the Claude-LEGO-Robot folder.
  • Confirm that desk-buddy-final.io plus desk-buddy-final.ldr are present.

Your editable Studio project plus validated LDraw export are now stored together.

  • Return to Studio.
  • Open File.
  • Select Render image….
  • Choose Photoreal.
  • Set the camera in Preview.

Photorealistic rendering can take a few minutes on a Mac. A longer wait here means Studio is still calculating the final image.

  • Click Render.
  • Save the finished image as desk-buddy-final.png inside Claude-LEGO-Robot.

Before checking the folder, which files do you expect to prove that the validated model plus presentation render are complete?

  • Switch to Finder.
  • Return to the Claude-LEGO-Robot folder.
  • Confirm that the folder contains desk-buddy-final.io, desk-buddy-final.ldr, desk-buddy-final.png, plus the updated design-report.md.

You should see the final Studio project, validated LDraw model, photorealistic render, plus revision report beside the retained prototype artifacts.

✔️ Awesome, I Have the Final Artifacts

Great. Keep the final files plus the original prototype together inside Claude-LEGO-Robot.

ⓧ I'd Like to Double Check the Final Artifacts

  • Studio shows no visible Collision wireframes, one connected group, green support zones, no red unstable zone, plus no Color Validator Problem parts.
  • The final design-report.md records a count between 100 and 110 plus the revision rationale.
  • The desk-buddy-final.ldr model has a connected antenna, grounded feet, stable support, available colors, plus useful 0 STEP boundaries.
  • The desk-buddy-final.io file preserves the validated Studio project.
  • The desk-buddy-final.png file presents the corrected robot as a photorealistic render.
  • The ldraw library remains unchanged with LDConfig.ldr plus the official parts directory intact.
  • The original prototype.ldr plus prototype-render.png remain as the pre-validation comparison.

That is the hardest loop closed: your robot now has independent evidence behind its design. Next, you will turn the validated model into instructions, a Wanted List, plus a physical desk buddy.

Publish, Source, and Build the Desk Buddy

Your corrected desk buddy now has a stable pose, legal connections, available colors, and a reviewed price estimate in BrickLink Studio. You have the digital evidence needed to move from validation to production.

A validated model is still a hypothesis until someone can follow its instructions, source its exact pieces, and make it stand. This step uses Instruction Maker, the BrickLink marketplace, and the physical build as three final checks.

In this step, get ready to:
  • Turn the validated model into buildable instructions.
  • Export a printable PDF booklet and create a reviewed Wanted List.
  • Obtain the parts and test the finished robot on a flat desk.
Turn the model into instructions

Instruction Maker converts the final model into a sequence that another person can follow. The mostly studs-up design gives Studio a simpler structure to divide into buildable steps.

  • In BrickLink Studio, return to the validated desk-buddy-final.io model from earlier.
  • Click Tool in the menu bar.
  • Click Instruction Maker.
  • Select Step Editor.
  • Select more than one part in the current step.
  • Click Divide into Steps in the toolbar above the parts list.

You'll see Studio allocate the selected parts across a generated build sequence.

Why Automatic Steps Fit This Model

Automatic division works best when studs face upward and the build remains together. Those constraints were part of the original design brief, so the generated sequence starts from useful structure.

The sequence still needs your judgment. A page can look orderly while asking the builder to place a piece that has no support.

  • Review the generated sequence from the first step to the last.
  • Select any part in the Step List that appears before it can connect to the assembly.
  • Drag the selected part within the Step List.
  • Drop the part when the blue line marks a buildable position.
  • Repeat the review until every intermediate assembly stays together.

Good progress. The sequence now describes a robot that can be assembled one connected section at a time.

  • Select Page Design in Instruction Maker.
  • Confirm that each step page includes a model image.
  • Confirm that each step page shows a step number.
  • Confirm that each step page includes a Parts List.
  • Save desk-buddy-final.io by pressing Cmd+S.

You'll see a print-ready sequence with model images, numbered steps, and the pieces required for each stage.

Export the booklet and create the Wanted List

The booklet makes the build portable beyond Studio. The Wanted List transfers the validated model into a sourcing checklist with quantities and purchasing limits.

  • Click the green Export button in Page Design.
  • Choose PDF as the export format.
  • Select all pages for the export.
  • Save the booklet as desk-buddy-instructions.pdf inside ~/Documents/Claude-LEGO-Robot.
  • Return to the Claude-LEGO-Robot folder in Finder.

You'll see desk-buddy-instructions.pdf beside the final model and render. Opening it should show every exported instruction page.

  • Return to Build mode in Studio.
  • Click Add to Wanted List.
  • Create a new list named Claude LEGO Robot.
  • Click Proceed to verify items.
  • Review the Condition choice for every item.
  • Review the Max Price choice for every item.
  • Review the Quantity for every item.
  • Click Add to Wanted List.

The Wanted List named Claude LEGO Robot now holds the pieces needed for the validated model. Your condition, maximum-price, and quantity choices are ready for the buying comparison.

Missing Pages or Wanted List Items?

  • Return to Page Design if the PDF is missing pages. Select all pages before exporting it again.
  • Compare the Wanted List quantities with desk-buddy-final.io before purchasing if the item count looks incomplete.

Get help checking the export or Wanted List.

Source the parts and complete the physical test

Studio's price baseline includes sellers from all countries, so it cannot predict your checkout total. The Buy workflow reveals the store combinations and extra costs that decide what you actually pay.

  • Use the BrickLink Buy workflow to compare store combinations for Claude LEGO Robot.
  • Compare each store's item subtotal.
  • Compare each seller's minimum order.
  • Choose the store combination that best fits your budget.

Payment is the moment real costs begin. Treat US$20-US$40 as a parts-subtotal target because shipping, tax, and seller minimums can raise the final total.

  • Review the shipping charge before payment.
  • Review the tax amount before payment.
  • Review every seller minimum before payment.
  • Review the final order total before payment.
  • Stop the order if the final total exceeds your budget.
  • Return to the previous model-revision workflow if expensive parts need replacements.
  • Repeat the independent Studio checks after any replacement.
  • Submit payment once the final order fits your budget.

You'll receive an order confirmation after the purchase is accepted. Keep the Wanted List available so you can compare the delivered quantities with the pieces you requested.

Delivery creates the longest pause in this project. Timing depends on the sellers and your destination, so the physical test begins after every required part arrives.

  • Sort the delivered parts against the quantities in Claude LEGO Robot.
  • Build the robot by following desk-buddy-instructions.pdf from the first page to the last.
  • Record any instruction step that creates a floating piece.
  • Record any connection that lacks enough clutch to stay together.
  • Compare the assembled stance with desk-buddy-final.png.

Before you let go, do you expect the real robot to remain connected and hold the same walking pose as the render?

  • Place the finished robot on a flat desk.
  • Remove your hands from the robot.

You'll see the 100-to-110-part desk buddy remain connected and stand in its intended walking pose without hand support.

You made the jump from an AI-generated model to a robot that stands on your desk. The physical result now backs the digital evidence.

Robot Leaning or Coming Apart?

  • Compare both feet with the matching instruction pages if the robot leans.
  • Check each loose piece's orientation against the model image if a connection separates.
  • Confirm that both feet sit fully on the same flat surface before judging the stance.

Help me diagnose a physical build problem.

Secret mission

Give the Robot a Swappable Mood

Your desk buddy already has one expression. Reuse its existing facial pieces to create a second mood that swaps in without dismantling the head, then document both configurations in the instruction booklet.

Clean Up Your Resources

Clean Up Your Resources

Choose whether to keep your robot workshop ready, pause your paid access, or remove the resources you no longer need. Claude Pro is the only recurring project cost.

Cost warning

Claude Pro costs US$20 when billed monthly, excluding tax. The subscription continues renewing until you cancel it.

Cancel before your next renewal date if you have finished using Claude Code. Your saved project remains on your Mac.

Resources you used:

  • Recurring Claude Pro subscription.
  • BrickLink Wanted List named Claude LEGO Robot.
  • Local project folder at ~/Documents/Claude-LEGO-Robot containing every digital artifact.
  • Physical Claude LEGO Robot with its original expression and alternate expression.

Keep everything running

No action is required. Choose this option if you plan to keep refining the model or designing more LEGO projects with Claude Code.

  • Keep your Claude Pro subscription active if you expect to use Claude Code before the next billing date.
  • Retain ~/Documents/Claude-LEGO-Robot for future design revisions.
  • Leave the Claude LEGO Robot Wanted List in BrickLink for future part replacements.
  • Keep the physical robot assembled for displaying or testing new facial arrangements.

Pause - I'll come back to this later

Pause the paid access while keeping your models, instructions, Wanted List, and physical robot. Claude Code requires an eligible paid plan when you resume.

  • Open the subscription management area in your Claude account.
  • Cancel Claude Pro before its next renewal.
  • Confirm that your account shows no future Claude Pro renewal.
  • Retain ~/Documents/Claude-LEGO-Robot on your Mac.
  • Keep the Claude LEGO Robot Wanted List in your BrickLink account.
  • Keep the physical robot assembled for your return.

Delete - I don't want to use this again

This option permanently removes the local project folder. Deleting the Wanted List does not undo completed BrickLink purchases.

  • Open the subscription management area in your Claude account.
  • Cancel Claude Pro before its next renewal.
  • Confirm that your account shows no future Claude Pro renewal.
  • Open the Wanted Lists area in your BrickLink account.
  • Select Claude LEGO Robot.
  • Delete the selected Wanted List.
  • Confirm that Claude LEGO Robot no longer appears among your Wanted Lists.
  • Disassemble the physical Claude LEGO Robot.
  • Sort the pieces back into storage.
  • Delete the local project folder by running this command in Terminal:
rm -rf ~/Documents/Claude-LEGO-Robot

What does this command remove?

This command permanently removes ~/Documents/Claude-LEGO-Robot. That folder includes the LDraw library, prototype, final model, report, renders, Studio project, and updated instruction booklet.

  • Check ~/Documents in Finder.

You should no longer see the Claude-LEGO-Robot folder.

Folder still visible?

  • Check that the command targets the exact path ~/Documents/Claude-LEGO-Robot.
  • Confirm that you ran the command in Terminal on the Mac that stores the project.

Get help with the cleanup command.

Nice Work!

Nice Work!

You did it! Your 100-to-110-part LEGO desk buddy now stands unaided in its walking pose after completing the full digital-to-physical workflow.

You've learned how to:

  • Direct Claude Code to turn a constrained design brief into a 100-to-110-part LDraw robot. Feed visible validation evidence back into each revision.
  • Run independent validation in BrickLink Studio. Expose collisions. Verify connectivity. Check desk stability. Confirm available colors. Review the parts estimate before sourcing.
  • Produce a photorealistic render. Export a printable PDF instruction booklet. Prepare a BrickLink Wanted List. Build the physical robot from the ordered parts.
  • Secret Mission: Reuse only part types and colors from the final Wanted List to create a swappable facial expression. Document both moods on one comparison page in desk-buddy-instructions.pdf.

Ready to quiz yourself?