Live at ataturkseven.com
Describe the board. Get a placed, routed, checked PCB.
TND Studio turns a written spec into a netlist with real footprints, places the parts, autoroutes both copper layers under your design rules and checks the result. Then you keep going in a live 2D/3D editor with an AI layout assistant, and export to KiCad.
- Library parts
- —
- Boards
- —
- Placed parts
- —
- Routed tracks
- —
- Saved versions
- —
- Stored files
- —
Counted live from the site's MySQL database.
Everything between the idea and the fab files
Each of these runs on this server today. Sign in to use the ones that act on boards.
-
Live
Spec → netlist agent
Write the board in markdown. Claude proposes a netlist using real footprints; checks catch unknown footprints, missing pads, shorts and dangling nets, and the agent fixes them — up to three rounds.
-
Live
Automatic placement
A clean netlist becomes a board: parts packed in connectivity order inside an outline sized to fit, ready to open in the studio.
-
Live
Two-layer autorouter
A* maze router with 45° routing and vias, obstacles inflated by clearance and track width, power tracks necked down at fine-pitch pads. Results are previewed before they're applied.
-
Live
Copper DRC
Track, via and pad clearance at any rotation, shorts, minimum track width, via drill and annular ring, board-edge clearance and copper keepouts — plus courtyard, edge and netlist checks.
-
Live
2D/3D studio
Move, rotate, flip and add parts, edit pad nets, draw tracks and vias, undo and redo — on desktop or phone — with a three.js 3D view of the same board.
-
Live
AI layout assistant
Ask for changes in plain words. Proposals are dry-run against the checks, sent back if they make things worse, and previewed before you apply them.
-
Live
Overnight runs
Schedule autoroute passes, AI edits or design reviews per board. Cron runs them while you're away and the proposals wait for review in the studio.
-
Live
Project file system
Folders and files kept on this server with every version and a trash: board snapshots (JSON + KiCad), datasheets, fab outputs and notes. Metadata in MySQL, contents stored once per hash.
-
Live
MySQL persistence & KiCad
Every version of every board is stored and restorable; edits from the editor, the AI, the terminal or phpMyAdmin all sync. Import and export
.kicad_pcbwith placement, nets, tracks and vias.
The pipeline
- 01
Write the spec
Interfaces, parts you care about, constraints. Markdown, no schematic.
- 02
Netlist
The agent picks footprints and pads; the checks send problems back until it's clean.
- 03
Place
Parts land on a board sized for them, grouped by the nets they share.
- 04
Route
The autorouter connects both layers under the board's design rules.
- 05
Check & refine
DRC, the AI assistant and the 2D/3D editor — then export to KiCad.
See the board the way the enclosure will
The 3D view follows every edit live: part heights, through-hole drills, copper on both sides, the selected net lit up. Tap a part in 3D and it's selected in the editor.
Component library
Curated parts with vetted alternatives, notes from real designs and manufacturer datasheets — served from MySQL, with placement counts taken from the boards themselves.
| Part | Category | Alternatives | Used | Datasheet |
|---|---|---|---|---|
| Loading the library… | ||||
Try the spec pipeline
Runs on the site owner's Claude account, so it needs a signed-in session. A clean netlist can become a board — optionally autorouted — that opens in the studio.
The netlist, check results and each fix round will appear here.
Status
What works, and where the edges are — kept honest.
Working now
- Spec → netlist agent with footprint and pad checks, and spec → placed board
- Two-layer autorouter with design rules; copper, placement and netlist DRC
- Live 2D/3D studio, AI layout assistant, undo/redo and full version history in MySQL
- Component library API with search, categories and signed-in editing
- Overnight autoroute, AI and review runs with proposals to review
- KiCad
.kicad_pcbimport and export - Project file system with folders, version history, trash and board snapshots
Not yet
- Copper pours and zones, differential pairs and length tuning
- Rip-up and reroute — dense fine-pitch areas can be left partly unrouted
- Schematic capture and Gerber output (export to KiCad to plot)
- The Rust backend in the repo is behind the hosted Node server