{
 "schema_version": 1,
 "generated": "2026-10-20",
 "id": "jamro-tiny-engineer--design-custom-robot-shell-with-cad",
 "repo": "jamro/tiny-engineer",
 "repo_url": "https://github.com/jamro/tiny-engineer",
 "repo_slug": "jamro-tiny-engineer",
 "title": "Design a custom robot shell by changing the CAD files",
 "page_title": "How to design a custom robot shell by changing the CAD files with Tiny Engineer",
 "summary": "Edit the CAD source and print a new body or mod for the same electronics.",
 "who": "A maker or engineer who wants a different look or shape for the robot and is comfortable with CAD and 3D printing.",
 "problem": "The default body may not fit a desk, a theme, or a personal style, and the README asks users to change the CAD for their own builds.",
 "outcome": "A custom printed shell that still houses the same main control board, servos, OLED, and speaker, with the design shared back to the project if wanted.",
 "steps": [
  "Read the CAD and printable model overview in 3d_models/README.md and browse mods/*/3d_models/ for existing mods.",
  "Open the CAD source in 3d_models/ and change the shell design for your build.",
  "Print the changed parts on your 3D printer, using M2 screws to assemble them as in docs/3d/assembly.md.",
  "Plug the existing electronics into the main control board as described in docs/hardware/main-control-board.md and check that every servo moves freely."
 ],
 "agent_prompt": "Use the repo github.com/jamro/tiny-engineer and its CAD sources in 3d_models/. Open the CAD file for the shell, make <change description>, and export the printable parts. Expected output: printable files for the changed shell. Verify the servos still fit and move without touching the shell.",
 "agents": [
  "any"
 ],
 "difficulty": "Advanced",
 "time": "8 hours",
 "basis": "readme",
 "caveat": "Hardware designs are licensed under CERN-OHL-S-2.0 and the Tiny Engineer name and logo are not licensed, so check LICENSING.md and TRADEMARK.md before sharing a changed design under the project name.",
 "category": "Software and DevOps",
 "tags": [
  "Software and DevOps"
 ],
 "lang": "c++",
 "requirements": [
  "3D printer with filament, or an order of printed parts (docs/3d/order-parts.md)",
  "Parts from the shopping list (docs/shopping.md), including the main control board, ESP32, 5x SG90 servos, OLED, and speaker",
  "M2 screws and a 5 V USB supply rated at 2 A or more",
  "A Wi-Fi network for the robot",
  "A machine with npx to run the tiny-engineer setup command"
 ],
 "risk": "none",
 "seen_in_the_wild": false,
 "mentioned_publicly": false,
 "risks": [],
 "best": false,
 "score": 0.7,
 "evidence": [],
 "url": "https://dedupedai.com/use-cases/jamro-tiny-engineer/design-custom-robot-shell-with-cad/",
 "md": "https://dedupedai.com/use-cases/jamro-tiny-engineer/design-custom-robot-shell-with-cad/index.md",
 "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 hello@dedupedai.com and we will look at it promptly.",
 "api": "https://dedupedai.com/api/v1/usecases/jamro-tiny-engineer--design-custom-robot-shell-with-cad.json",
 "api_version": "v1"
}
