A starter kit and UI library for building custom design apps with AI.
761
stars
20
commits
TypeScript
primary language
Sep 11, 2026
updated
Toolcraft is an open-source starter kit and UI library for building custom design apps with AI. Use it to create small creative products, internal utilities, interactive experiments, and tools tailored to your workflow.
It works with any AI agent (Codex, Claude, Cursor).
Built by Pixel Point.
Website · Examples · YouTube video · Blog post
Your AI agent can handle setup for you. Start with a prompt, or use the CLI below.
Open an empty project folder in Codex, Claude Code, Cursor, or another AI coding agent. Copy the prompt below and replace the text in brackets with your idea. The agent handles setup for you—no terminal commands to type.
Install any missing prerequisites, including Node.js and npm. Set up Toolcraft
with `npx --yes @pixel-point/toolcraft create --yes`,
then build [describe your tool] and start a local dev server.
Run this command in your terminal:
npx @pixel-point/toolcraft create
Follow the prompts, then open the generated project in your AI coding agent. Describe the tool you want to build and ask the agent to start a local preview:
Build an app that applies an ASCII effect to an uploaded image and start a local preview.
Toolcraft works best for apps that combine a visual canvas with a focused set of controls, such as:
Use Toolcraft only when a custom app would solve your task faster or better than Figma or another design tool. First consider what your existing software can do, including its AI features, and account for the time needed to build the app.
For example, you might be developing a brand’s visual language around procedural graphics. Managing hundreds of small layers and repeatedly applying effects or adjustments can become cumbersome in Figma. With a custom app, you decide which controls and parameters to include, how the design responds to them, and which export options you need, including video. You can build a repeatable workflow for producing consistent brand assets in batches, then keep expanding it as your ideas evolve. You can also share the app with your client so they can create new assets on their own.
It depends on what you want to build. You can usually expect a first working result 30–60 minutes after your initial prompt. More complex tasks, such as reverse engineering a reference, combining multiple WebGL effects, or building 3D tools, can take longer.
Toolcraft isn’t a magic tool that lets you create anything instantly. It gives you the workspace, AI guardrails, and skills to make the process smoother and improve your chances of getting the result you want.
At Pixel Point, we often spend 1–3 days on a single app and go through 30–50 iterations with AI, sometimes more, before reaching a version that matches what we envisioned.
Toolcraft uses port 3002 for the local development environment by default. If it’s busy on the first launch, it picks the next available port and remembers it for your project.
After creating the app, your AI agent will usually give you a URL like http://localhost:3002 that you can open in your browser. If it doesn’t, simply ask your agent to start the dev server or give you the local URL.
No. In general, $20/month plans aren’t suitable for meaningful work. Use a plan that costs at least $100/month.
No. It’s a batch of files copied into a folder of your choice when you use the command-line tool or ask an agent to do it for you. Those files contain the starter, component library, and AI harness that help you build your own design apps faster and better.
Yes.
Yes. Toolcraft is completely free, open-source software licensed under MIT. You’re free to use it in commercial projects, modify it, and distribute it to your clients.
Yes. The starter in this repository uses the MIT license, which allows commercial use, modification, and distribution. You can build tools for paid client work and use them in your business.
You can use Codex, Claude Code, Cursor, or another coding agent that can read and edit project files, run commands, and follow the project's instructions. Open the project in your agent and describe what you want to build. Toolcraft includes instructions and skills to guide the work.
Yes. Browse the example apps, open the one you want to start from, and click Clone with CLI on its page to copy the setup command. Ask your agent to run it, or paste it into your terminal. For example:
npx @pixel-point/toolcraft@latest create --template prism-flow
Your new project starts with that example's design and features, which you can then change with your agent.
Yes. Your agent can prepare the app for publishing and help you deploy it to a web host of your choice. It can run pretty much anywhere and can be easily deployed to Cloudflare, Vercel, or Netlify.
Yes. Your AI agent helps build and change the app. The generated app can run independently. You can keep using it after cancelling your AI subscription. If you add features that call an AI service, those features still need access to that service.
Files you import into a Toolcraft app are processed in your browser. Toolcraft does not send them anywhere else, since it isn’t a cloud service.
src/app — product schema, acceptance coverage, and performance configurationsrc/routes — application routes and Toolcraft compositionsrc/toolcraft/runtime — state, commands, canvas, panels, timeline, and export runtimesrc/toolcraft/ui — Toolcraft controls and interface componentsdocs/toolcraft — local rules and reference docs for AI agentse2e — browser acceptance and performance testsThis repository contains the standalone starter produced by the Toolcraft CLI. The runtime and UI source are included directly instead of being hidden behind a package, so generated projects can be inspected and changed when needed.
npm install # Install dependencies
npm run dev # Start the local app
npm run test # Run unit and contract checks
npm run verify:quick # Run the normal development checks
npm run verify:final # Run the complete functional gate
npm run build # Create a production build
TypeScript
67.6%
JavaScript
32.1%
A starter kit and UI library for building custom design apps with AI.
761
stars
20
commits
TypeScript
primary language
Sep 11, 2026
updated
Toolcraft is an open-source starter kit and UI library for building custom design apps with AI. Use it to create small creative products, internal utilities, interactive experiments, and tools tailored to your workflow.
It works with any AI agent (Codex, Claude, Cursor).
Built by Pixel Point.
Website · Examples · YouTube video · Blog post
Your AI agent can handle setup for you. Start with a prompt, or use the CLI below.
Open an empty project folder in Codex, Claude Code, Cursor, or another AI coding agent. Copy the prompt below and replace the text in brackets with your idea. The agent handles setup for you—no terminal commands to type.
Install any missing prerequisites, including Node.js and npm. Set up Toolcraft
with `npx --yes @pixel-point/toolcraft create --yes`,
then build [describe your tool] and start a local dev server.
Run this command in your terminal:
npx @pixel-point/toolcraft create
Follow the prompts, then open the generated project in your AI coding agent. Describe the tool you want to build and ask the agent to start a local preview:
Build an app that applies an ASCII effect to an uploaded image and start a local preview.
Toolcraft works best for apps that combine a visual canvas with a focused set of controls, such as:
Use Toolcraft only when a custom app would solve your task faster or better than Figma or another design tool. First consider what your existing software can do, including its AI features, and account for the time needed to build the app.
For example, you might be developing a brand’s visual language around procedural graphics. Managing hundreds of small layers and repeatedly applying effects or adjustments can become cumbersome in Figma. With a custom app, you decide which controls and parameters to include, how the design responds to them, and which export options you need, including video. You can build a repeatable workflow for producing consistent brand assets in batches, then keep expanding it as your ideas evolve. You can also share the app with your client so they can create new assets on their own.
It depends on what you want to build. You can usually expect a first working result 30–60 minutes after your initial prompt. More complex tasks, such as reverse engineering a reference, combining multiple WebGL effects, or building 3D tools, can take longer.
Toolcraft isn’t a magic tool that lets you create anything instantly. It gives you the workspace, AI guardrails, and skills to make the process smoother and improve your chances of getting the result you want.
At Pixel Point, we often spend 1–3 days on a single app and go through 30–50 iterations with AI, sometimes more, before reaching a version that matches what we envisioned.
Toolcraft uses port 3002 for the local development environment by default. If it’s busy on the first launch, it picks the next available port and remembers it for your project.
After creating the app, your AI agent will usually give you a URL like http://localhost:3002 that you can open in your browser. If it doesn’t, simply ask your agent to start the dev server or give you the local URL.
No. In general, $20/month plans aren’t suitable for meaningful work. Use a plan that costs at least $100/month.
No. It’s a batch of files copied into a folder of your choice when you use the command-line tool or ask an agent to do it for you. Those files contain the starter, component library, and AI harness that help you build your own design apps faster and better.
Yes.
Yes. Toolcraft is completely free, open-source software licensed under MIT. You’re free to use it in commercial projects, modify it, and distribute it to your clients.
Yes. The starter in this repository uses the MIT license, which allows commercial use, modification, and distribution. You can build tools for paid client work and use them in your business.
You can use Codex, Claude Code, Cursor, or another coding agent that can read and edit project files, run commands, and follow the project's instructions. Open the project in your agent and describe what you want to build. Toolcraft includes instructions and skills to guide the work.
Yes. Browse the example apps, open the one you want to start from, and click Clone with CLI on its page to copy the setup command. Ask your agent to run it, or paste it into your terminal. For example:
npx @pixel-point/toolcraft@latest create --template prism-flow
Your new project starts with that example's design and features, which you can then change with your agent.
Yes. Your agent can prepare the app for publishing and help you deploy it to a web host of your choice. It can run pretty much anywhere and can be easily deployed to Cloudflare, Vercel, or Netlify.
Yes. Your AI agent helps build and change the app. The generated app can run independently. You can keep using it after cancelling your AI subscription. If you add features that call an AI service, those features still need access to that service.
Files you import into a Toolcraft app are processed in your browser. Toolcraft does not send them anywhere else, since it isn’t a cloud service.
src/app — product schema, acceptance coverage, and performance configurationsrc/routes — application routes and Toolcraft compositionsrc/toolcraft/runtime — state, commands, canvas, panels, timeline, and export runtimesrc/toolcraft/ui — Toolcraft controls and interface componentsdocs/toolcraft — local rules and reference docs for AI agentse2e — browser acceptance and performance testsThis repository contains the standalone starter produced by the Toolcraft CLI. The runtime and UI source are included directly instead of being hidden behind a package, so generated projects can be inspected and changed when needed.
npm install # Install dependencies
npm run dev # Start the local app
npm run test # Run unit and contract checks
npm run verify:quick # Run the normal development checks
npm run verify:final # Run the complete functional gate
npm run build # Create a production build
TypeScript
67.6%
JavaScript
32.1%