Build, Chat and Plan

The composer, the box under the chat, has three modes. The mode menu sits next to the send button and shows the current one.

Press ⌥P on a Mac, or Alt+P on Windows and Linux, to switch to the next mode. Yorki remembers the mode you chose for each project while the tab stays open.

Build

Build is the default. Describe a change and Yorki makes it: it writes the code, checks it, updates the preview and saves a new version.

If you send a request while a build is running, it waits in a queue and runs when the current one finishes. Queued requests can be moved up or down, or cancelled, until they start.

Chat

Chat is for thinking out loud. Ask how something in your app works, why something happens, or which of two ideas is better. Yorki reads your app's code to answer, but it never changes anything.

When a conversation ends with an idea you like, press Build this under the latest reply. Yorki then builds what you agreed on in the conversation.

Plan

Plan is for bigger changes, and for new apps you want to think through before the first build. Each reply contains a complete plan with the same seven parts: the goal, the decisions, the steps, the data the app keeps, the pages and flows, what is out of scope and any open questions.

Read the plan, then:

• Refine it. Send another message in Plan mode, such as "Drop the reviews page and add a waiting list." Yorki rewrites the plan.
• Implement it. Press Implement the plan. If the plan has open questions, Yorki asks them one at a time first, each with a recommended answer. Skip all uses the recommendations. Then the build starts.
• Set it aside. Press Skip. The plan stays in the chat, marked as set aside, and is not built.

A plan you implement stays in the chat, and Yorki records what it built in the project notes. Your specification is never changed by a plan: if a decision from it must always hold, write it into your specification yourself.

Which mode to use

• Build for a clear change: "Add a contact form to the about page."
• Chat for a question or a decision: "Should bookings need an account?"
• Plan for anything that touches several pages or the data your app keeps: "Add a members area with paid and free plans."