Skip to main content

​
Start a fresh project

  1. Open Mistle and choose New Project.
  2. Pick or confirm your Projects Home folder (defaults to ~/mistle-projects/) and give the project a simple name.
  3. Mistle creates that folder and opens the guided Project Setup chat for you.

​
What Create a Project does

  • Confirms what you’re building with a few short questions so Mistle can learn your intent.
  • Determines the tech stack your use case needs, then scaffolds it.
  • Sets up and installs the tech stack in place.
  • Writes a summary in docs/overview.md that can be used for feature development reference.

​
Prompting Tips

You only need to provide as much details as is required to enable Mistle to determine a starting tech stack. If there is insufficient details, Mistle will ask clarifying questions. It is also okay to provide more details upfront.

​
Example prompts

Create a meme generator that turns text into image using Nano Banana

Create a Telegram bot that extracts data from invoices using Google's Flash model

Create a voiceover app that turns typed scripts into audio clips with Deepgram

​
What goes behind the scenes

  • What happens: Mistle captures your answers, maps them to use-case patterns, and selects the stack your scenario needs. The Web default pairs the Cloudflare Workers runtime with React Router v7, Turbo, pnpm, and mise.
  • Why it matters: template choices match your app type and auth needs so you do not start with extra rewiring.
  • What happens: Mistle pulls the template from its registry, seeds the repo at the root, renames the worker in apps/app/wrangler.jsonc, and pins config and package versions to the template.
  • Why it matters: keeps the layout consistent across projects and aligns Wrangler routing with your project name.
  • What happens: runs mise trust && mise install to install the toolchain (Node, pnpm, Wrangler, Turborepo) via mise, then runs pnpm install to wire workspace dependencies.
  • Why it matters: reproducible versions and one-time dependency install before you touch code.
  • What happens: wires Better Auth email/password by default (or a no-auth variant) and pre-binds Cloudflare D1, KV, and R2 for data and storage in the Worker runtime.
  • Why it matters: opinionated defaults for identity and state let you ship sooner and swap providers later with less plumbing.
  • What happens: writes your intent to docs/overview.md, initializes git, makes the initial commit, and calls end_setup so the workspace is ready.
  • Why it matters: you start with a clean history and a snapshot of the choices made during setup.