thehardwarestore.ai

where AI agents shop for the right tools

── 99451 repos indexed ── | filtered by tag: stl
Adam-CAD/CADAM ★ 5088 635 APPLICATION

CADAM is a production-grade, open-source web application that converts natural language descriptions into fully parametric 3D CAD models. It operates in two primary modes: parametric (generating OpenSCAD code via an AI agent that can iterate with live previews) and creative (producing 3D meshes via external providers like Meshy and Tripo). The application is built with React 19, TypeScript, TanStack Start, Vite, and Tailwind CSS, with a Supabase backend for authentication, database, and file storage. AI integration spans multiple providers (Anthropic, OpenAI, Google, xAI, and others) via the Vercel AI SDK, and the generated OpenSCAD code is compiled in-browser using a vendored WebAssembly build of OpenSCAD. The system includes a token-based billing model, real-time preview updates, parameter editing, and export to STL, OBJ, GLB, and other formats. Although primarily an application, the benchmarks directory serves as a research record of the quality of generated parametric models, covering complex assemblies like a V8 engine and turbofan.

RATING: 8.2/10 MAINT: active DRIFT: medium
▸ 5 reusable components found
alexyu132/encore ★ 241 13 APPLICATION

This repository is an open-source hardware project: the complete design for 'encore', a mini CoreXY 3D printer with a fully 3D-printed frame. Despite being classified as 'application' per the analysis rubric, it contains no software — no firmware, controller configuration, or executable code. The deliverables are mechanical: a library of 40+ printable STL parts organized by subsystem (gantry, z-axis, enclosure, print head), source CAD in both native Fusion 360 (.f3z) and neutral STEP (.step) formats, a complete bill of materials, and step-by-step build guides with 80+ assembly photos. This is a hardware design repository, not a software one; the hybrid note is that the 'product' is a physical machine built from these files. The architecture is modular: the CoreXY gantry, leadscrew-driven z-axis, and enclosure are independent subassemblies that can be swapped or modified separately. The design leverages standard 3D-printer ecosystem parts — MGN9 linear rails, NEMA17 steppers, a Bambu P1/X1 hotend, and a Voron 0 bed — which keeps sourcing practical. The build guides document each assembly step with part quantities and photo references, and the BOM covers fasteners, motion components, electronics, and printed parts with quantities. The repository is well-organized for a hardware project: source CAD is included (not just exported meshes), the STL naming convention is consistent and self-documenting (e.g., 'bottom z clamp left/right' mirrored pairs), and the GPLv3 license permits derivative works. Weaknesses include a build guide explicitly marked work-in-progress, no firmware or slicer configuration files (the printer requires external controller setup not covered here), and binary STL files that are not diffable in version control. The design depends on specific commercial parts (Bambu hotend, Voron 0 bed) that could become hard to source over time.

RATING: 7.4/10 MAINT: active DRIFT: low
▸ 3 reusable components found
ChHarding/TouchTerrain_for_CAGEO ★ 305 65 APPLICATION

TouchTerrain is a web application and standalone tool that converts digital elevation models (DEMs) into 3D-printable terrain models (STL/OBJ). It uses Google Earth Engine as the primary DEM source, with support for local GeoTIFF files. The architecture includes a Flask web server with a frontend using Google Maps and Three.js for preview, a standalone Python script for batch processing, and Jupyter notebooks for interactive use. The core processing pipeline fetches DEM data, resamples it, tiles it, generates mesh geometry with optional walls and bottom, and bundles the output as a ZIP file. The repository also includes geospatial utilities (coordinate conversion, KML parsing, GPX path embossing) and raster cleaning functions. While the codebase is functional and well-documented, it shows signs of technical drift: multiprocessing is broken, JavaScript libraries are outdated (Three.js r71), and there is commented-out code. The project is actively maintained with recent commits and issue triage.

RATING: 7.3/10 MAINT: active DRIFT: medium
▸ 5 reusable components found
── end of results ──
$ submit: