Describe it. Your agent designs it.

Write a brief. The coding CLI you already have designs it as real files in a folder you own, with a live preview beside the conversation. No account, no subscription.

v1.19.0 · macOS and Windows · free tier, then Pro once for $29

Design the redesigned 1devtool.com homepage described in brief.md at the project root. Read it fully first; it fixes the copy, the exact section list …

Claude Code · Fable 5.140 min
devtool-homepage/index.html
The 1devtool.com hero: the headline “The only dev tool you need in the AI era.”, a Download Free button, and a real screenshot of the 1DevTool workspace below.
1devtool.com homepage Website

  • One-time purchase
  • Local-first
  • Bring your own agent
  • Your files, your folder
  • Built by one founder

Runs on the agent you already pay for.

1DesignTool finds the coding CLIs on your PATH and drives them: Claude Code, Codex, Cursor Agent and thirteen more. No new account, no API key to paste. Your agent talks to its own provider the way it always does.

The Agents page in Settings: a list of installed coding CLIs with version and path, each marked Ready or Not installed, including Claude Code, Codex, Grok Build, Cursor Agent, OpenCode, Antigravity, Qwen Code, Kimi Code, Amp, Devin, Cline and Hermes Agent.
Settings → Agents lists what it found on this machine.
  • Claude CodeReady
  • CodexReady
  • Cursor AgentReady
  • Grok BuildReady
  • OpenCodeReady
  • AntigravityReady
  • Qwen CodeNot installed
  • Kimi CodeReady
  • AmpNot installed
  • DevinReady
  • ClineNot installed
  • Hermes AgentReady
  • Pi
  • Oh My Pi
  • Kiro CLI
  • Aider

Ready and Not installed are from one machine’s Settings → Agents. Pi, Oh My Pi, Kiro CLI and Aider are found the same way.

Twelve things it made.

Recent work from real runs, most of it the sites, app screens and store listings behind StoicSoft’s own apps. Open one to read the exact prompt, or open the result itself.

Nineteen types, each with its own output.

The best run of each, from the brief to the files it handed back.

1,930 free 3D models, all made here.

Game-ready GLB props, vehicles, characters and scenes, each built by a coding agent with the 3D object template. Named parts, real knobs to remix, a clean export. Free for commercial use, no sign-up.

collections
116collections
visual styles
9visual styles
triangles, every part named
29.9Mtriangles, every part named
for three.js, Blender, Godot, Unity
GLBfor three.js, Blender, Godot, Unity
Windmill5,500 tris · drag to orbit
A real run, start to finish. The preview updates on every save.

One run, brief to gate, in six steps.

  1. BriefYou write it in the composer, or your agent sends it over MCP.
  2. DirectionOne of 17 visual directions, with generated tokens, a signature move and rules with numbers.
  3. Plandesign-plan.md first: headline, primary action, sections, the bold moment.
  4. Tokenstokens.css: every color, size and space the page may use.
  5. Buildindex.html lands first and grows section by section. Before it exists, the “Design so far” card draws the saved plan in the design’s own tokens.
  6. GatePlan found, lint, audit, contrast, contact sheet. Pass or fail, nothing in between.

Steer it like you would steer a designer.

Point at the preview and say what to change. Ask for options. Roll back. Every control below is a real screen from the app.

Click an element in the preview and say what to change. The comment pins to a selector and goes to the agent with the next turn.

Pin 1 on the hero row, Pin 2 on the headline, one button to send both.

Checked like a design team, not a chat.

Every run picks one of 17 visual directions, writes its plan before any HTML, and ends at a gate that says pass or fail.

  1. plandesign-plan.md found, bold moment named
  2. lint0 hard-coded colors, 0 off-scale sizes
  3. audit1440×900 and 390×844: no overflow, text ≥ 12px
  4. contrastevery text pair ≥ 4.5:1
  5. sheeta contact sheet of every viewport
  6. verdictPASS
A Design council card listing its stages: Requirements freeze done, Building with grok, Automatic checks, Evidence capture, Visual, UX, Copy and Rights reviews, Merging reviews, Repairing findings, Final verdict; review round 1 of 3.
The council, for big jobs. Visual, UX, copy and rights reviewers pass over the evidence independently. Findings merge, repairs run.
The Design knowledge page: a review queue with three proposed cards (a direction, a lesson and a flow), each with Accept and Reject buttons, and an inbox of files waiting to be learned.
It learns, and you approve. Lessons, dropped-in examples and extracted house styles become proposed cards. Nothing changes a future run until a person accepts it.

Design on your real screens. Then let your agent call it.

Your codebase, not just artifacts.

  • Link a repoand design on its real screens. Build mode shows the screen’s UI tree.
  • Every edit is verifiedapplied to your code and checked, or rolled back with a reason.
  • An isolated branchholds the work. You review it before you adopt it.
Build mode on a linked repo, on its own branch.
A 'Changes on 1design/shop-worktrees' dialog: one commit, 'Make the header sticky', two files changed, with the diff of src/App.tsx shown.
Review the branch.
The 'Adopt this folder?' sheet for a react + vite repo: dev server URL, dev command, and the option to edit on an isolated branch with linked node_modules and .env.
Adopt it on your terms.

Your agent can drive it over MCP.

1DesignTool runs an MCP server, onedesigntool. An agent in another app, Claude Code in a terminal for example, can create projects, start design turns, screenshot the preview, run the gate and apply verified edits. Access is granted per credential and per project in Settings → MCP.

› project_create  name: "Launch page" · type: web
✓ project created  a folder on your disk
› design_generate  prompt: "A launch page for a coffee subscription — hero, three blends, pricing"
✓ run started      watch the preview
› preview_screenshot  viewport: 390×844
✓ screenshot saved
› run_gate
✓ PASS
› apply_and_verify  "Tighten the headline to two lines"
✓ applied, verified
Three windows side by side: a terminal running a design_generate call over MCP, 1DesignTool showing the run and its design checks, and an iPhone simulator displaying the resulting habit-tracker app.
A terminal, the studio and a simulator, one design turn.

This page was designed by a coding agent calling those tools.

One of twelve. They hand work to each other.

1DesignTool is one of the StoicSoft desktop apps. Each is bought once and runs on its own, and they pass work along.

“Send to 1VideoTool” turns a design into video material.

StoicSoft bundles that include 1DesignTool, one-device prices
BundleAppsPriceStore
The Builder Stack1DevTool1DesignToolStoicBrowser1AIVault$69Builder Stack
The Studio Stack1VideoTool1AudioTool1DesignTool1FileTool$69Studio Stack
The Launch Stack1DesignTool1ShowcaseTool1VideoTool1MarketingTool$69Launch Stack
StoicSoft CompleteAll twelve paid appsStoicSoft$199Complete

One-device prices. A StoicSoft bundle key (SS-…) activates 1DesignTool Pro in the same key field.

Free forever. Pro once.

A real free tier, then one payment. No subscription, no account, and your files stay yours.

Free, forever

$0

  • 300 prompts
  • Unlimited projects
  • 3 versions per project
  • 4 variants
  • 3 design systems
  • Unlimited code export
  • 50 renders, watermarked
  • Live preview
  • Codebase projects
  • Your own agent CLIs
  • Works offline
Download free

Pro, one-time

$29 for 1 machine

  • Every free cap lifted: prompts, versions, variants, design systems, renders
  • No watermark
  • 12 months of updates included
  • Keep your licensed version forever
  • Tied to you, not the hardware
  • A StoicSoft bundle key unlocks it too
Buy Pro — $29

Honest answers.

Which agents does it work with?

Sixteen coding CLIs: Claude Code, Codex, Cursor Agent, Grok Build, OpenCode, Antigravity, Qwen Code, Kimi Code, Amp, Devin, Cline, Hermes Agent, Pi, Oh My Pi, Kiro CLI and Aider. 1DesignTool detects the ones already on your PATH. No API keys and no credits: your existing subscription does the designing.

Does it need the internet?

The app works offline: projects, previews, templates, design systems and the design kit all live on your machine. What touches the network is the agent CLI you chose (only while it runs), license checks (Lemon Squeezy), update checks (GitHub), stock-asset fetches (Openverse, Wikimedia, unDraw) and optional analytics, off by default. There is no 1DesignTool account and no cloud project storage.

Where do my files go?

Into a project folder on your disk: HTML, CSS and JS, plus GLB, STL and the other formats the 3D, CAD and sprite types produce. The live preview reads that folder. Export is the folder.

What do the free caps mean?

Free is 300 prompts, unlimited projects, 3 versions per project, 4 variants, 3 design systems, unlimited code export and 50 watermarked renders. Pro removes every cap and the watermark.

Windows SmartScreen warned me. Is that expected?

It can happen. Windows builds are not signed, so SmartScreen may warn the first time you open the installer. Choose “More info”, then “Run anyway”.

What happens after the 12 months of updates?

You keep your licensed version forever. Pro includes 12 months of updates; after that, the version you have keeps working.

Can my own agent drive it?

Yes. 1DesignTool runs an MCP server named onedesigntool with tools such as project_create, design_generate, preview_screenshot, run_gate and apply_and_verify. You grant access per credential and per project in Settings → MCP.

Is there a Linux build?

Not today. 1DesignTool is for macOS and Windows.

Describe the first one tonight.

Free, on your machine, with the agent you already have.

A doodle of a capybara soaking in a hot spring, drawn on a sheet of paper
doodle 1 of 22 — the agent draws while it works

Résumé

Iris Halvorsen

A print-ready résumé for Iris Halvorsen, senior frontend engineer, with a serif name, a profile paragraph, an experience column and an expertise sidebar.

Devin · gate PASS

A senior engineer's résumé — real serif typography, eight years of design-systems work, print-ready.

The prompt

Make a résumé: a senior frontend engineer résumé — 8 years, design-systems focus.
Open the result