Tips

Give the agent the design system

An agent builds UI the way you show it. Keep the design system on the canvas as one group: a note listing the components and when to use them, a screenshot of the colour and spacing tokens, and a link to the live component catalogue (Yard's own is at /design-system). Pin the group so it goes along with every project, and say "use the components in the design system group" in the prompt.

Point at the exact thing

The less the agent has to guess, the better the result:

• A repository: select its block to give the agent the whole repository.
• Some lines: highlight them in the repository explorer and add a note saying what is wrong with them.
• One file: extract it onto the canvas as a block and select only that.
• In writing: type @ in a project's spec to mention a block, a file or a repository.

See pointing an agent at blocks.

Pin what is always true

Pin the blocks every conversation needs: the product brief, conventions, the design system. Pinned blocks go with every message and every new project. Keep pins few: a pin that is not always relevant is noise.

Group by piece of work

Gather everything about one feature (the note, mockups, research links) into a group. Selecting the group selects all of it, it moves as one, and the canvas stays readable as it grows. ⌘/Ctrl+G groups the selection.

Keep specs short and checkable

A good spec is a goal in a sentence or two and acceptance criteria that can each be checked: "Delete can be undone for 8 seconds", not "Deleting should feel safe". The agent ticks the criteria off as it meets them, so you see progress against what you asked for.

Workspace chat or a project?

• Ask in the workspace chat to explain, summarise or plan. It reads the canvas and the repositories; repositories can only be changed inside a project.
• Start a project when you want something built or written: it gets its own container and branches, and ends in pull requests or files.

Answer questions quickly

When an agent is missing context it stops and asks, and the project shows Needs your input. You are notified; answering in the project's chat lets it carry on.

Let history be your undo

Everything on the canvas, in notes and in specs is saved with history. Rearrange freely: you can see who changed what and revert from history.