Studio

Building with LiTT

Building with LiTT is a conversation with a tight feedback loop: describe what you want, watch LiTT build it, check the preview, and iterate. Here are real prompts that work — and the loop that ties them together.

The loop: build → verify → preview → deploy

1. 1

   Build

   You send a mission in chat. LiTT plans the work, edits real project files, and runs terminal commands — installing packages, building, and testing as needed.
2. 2

   Verify

   LiTT runs checks against the work: typechecks, linters, tests, or a build step, depending on the project. If something fails, LiTT sees the error and fixes it — you'll see the retry in the activity timeline.
3. 3

   Preview

   You open the Preview tab and click through the running project. This is the moment of truth: does it look right, does it behave right?
4. 4

   Deploy

   When the preview looks right, the Deploy action prepares the project to go live. Deployment may ask for your approval first — nothing ships without you.

Then the loop repeats: every follow-up message — “make the headline bigger,” “add a pricing section” — goes through build → verify → preview again. Small loops beat big-bang requests: ten short iterations land better than one enormous prompt.

Example prompts that work

Copy these patterns and adapt them. The formula is simple: what it is + who it's for + what it must include.

What makes a good mission

• Be concrete about the outcome. “A landing page for my bakery with a menu and contact form” beats “make me a website.”
• Name the audience and the vibe. “For busy parents, clean and calm” gives LiTT design direction it can't guess.
• List must-haves. Sections, pages, or features you know you need — LiTT fills in the rest.
• One mission, one outcome. “Build the landing page” first; “now add a blog” second. Short loops, better results.
• Point at problems precisely. “The menu overlaps the hero on my phone” is actionable; “it looks weird” is a guessing game.

Verifying LiTT's work

Trust, but verify — LiTT makes it easy:

• Preview tab — click through the running project yourself. If it works here, the build is real.
• Code tab — read the actual files. Every edit is visible; nothing is hidden behind the chat.
• Activity timeline — see which files changed and which commands ran, in order.
• Terminal — run your own checks. litt check-style verification from the CLI works on the same project files.

When LiTT gets stuck

If a build error repeats or the preview won't start:

• Paste the error into chat: “I'm seeing this error: … — what does it mean and how do we fix it?”
• Ask LiTT to explain its plan before continuing.
• Check the terminal for the raw output — sometimes the full log shows what the summary didn't.
• As a last resort, ask LiTT to revert the last change and try a different approach.

Persistent issues are covered in Troubleshooting.