Example uses and prompts

Each example says what to put on the canvas, what to select, and a prompt to start from. Use the prompt in Create spec to start a project, or in the workspace chat to ask about the canvas without changing any code.

Fix a bug from a report

Put the bug report on the canvas (paste the issue link, the screenshot and the error from the logs into a note), add the repository, select all of it and Create spec:

Fix the crash in the screenshot. The stack trace is in the note. Find the
cause, fix it, and add a test that fails without the fix. Do not change the
public API.

Build a feature from a sketch

Drop the mockup in, write the behaviour in a note as a checklist, select both with the repository:

Add bulk select to the asset grid as in the sketch. Shift-click selects a
range, the floating bar offers Move to folder and Delete, and Delete can be
undone for 8 seconds. Use the existing BulkActionBar component.

Build UI with the design system

Keep a pinned design system group (see tips) and select the screen you want built:

Build the settings page in the mockup with the components in the design
system group. No new colours or spacing values: use the tokens. Match the
mockup at desktop and phone widths.

Write up research without a repository

Projects do not need a repository. Select the interview notes, the survey export and the links:

Summarise the interviews into the five most common problems, with a quote
for each and how many people mentioned it. Put the numbers in a table and
write the result as findings.md.

At the end, Take files into the workspace… brings the write-up onto the canvas.

Get up to speed on a repository

Add the repository and ask in the workspace chat:

Explain how authentication works in this repository: where sessions are
created and checked, and which files I would change to add passkeys.

Review a pull request with context

Select the spec the work came from and the repository:

Review the open pull request against this spec. List every acceptance
criterion it does not meet yet and anything it changes that the spec does
not ask for.

Plan before building

When the work is big, ask for a plan first and keep it on the canvas:

Do not change any code yet. Read the repository and the notes, and write a
step-by-step plan for moving image uploads to the storage bucket, with the
risks of each step. Write it as plan.md.

Turn a meeting into tasks

Paste the meeting notes into a note, select it:

Turn these notes into a checklist of tasks, one line each, with the person
named next to it where the notes say who. Group them by area.