Priorities & Context

In a Stitch Workspace, a priority isn’t a one-off bug ticket like “change button color to blue.” It’s a standing design goal that tells Stitch what kind of UX improvements to look for across your application’s routes.

Workspace features require running stitch enable loop once on your machine. See Connect a Repository for setup.

Set your priority with the /stitch skill

When you onboard a repository with the /stitch skill, your agent offers to configure our standard Scale Interactive Visual Prototyping priority (ui-prototyping). You can also ask /stitch to set up or tailor a priority at any time:

Use the UI prototyping template from the terminal

The CLI includes a built-in template registry that creates your standing priority and calibrates your workspace’s remote analysis skills in one step:

stitch create priority --template ui-prototyping

Running stitch create priority --template ui-prototyping does two things at once:

• Creates your standing priority with CREATE_SUGGESTIONS autonomy so Stitch continuously proposes insights, solution specs, and Canvas design prompts.
• Syncs three workspace skills (design-synthesis, insight-guidelines, and assessment-guidelines) that steer Stitch’s backend research agents toward visual UI prototyping rather than generic code-quality lints.

If you want to target specific routes or workflows in your app, pass --objective alongside --template ui-prototyping so you customize the goal while keeping the UI prototyping skill calibration:

stitch create priority \
  --template ui-prototyping \
  --objective "Transform passive schedule and booking tables across /schedule and /venues into tactile, direct-manipulation surfaces."

Write outcome-focused objectives

The best priority objectives describe a durable UX outcome across multiple routes rather than a single closed task:

• Aim for outcomes: “Evaluate visual rhythm across /feed and /schedule so mobile schedule views are glanceable and tactile” or “Transform read-only booking summaries into direct-manipulation surfaces across /venues and /checkout.”
• Skip tiny tasks: One-line chores like “Fix table padding on /schedule” or “Add a filter dropdown” are faster to just edit directly than to run through workspace synthesis.

You can list, inspect, or update your active priorities whenever your focus shifts:

stitch find priorities
stitch edit priority <priority-id> --objective "..."
stitch delete priority <priority-id>

Attach supporting files and context

If you have product requirements, user research notes, or architecture docs that should inform your prototypes, attach them to your workspace.

Upload PDFs, images, or Markdown specs with stitch upload file:

stitch upload file ./specs/checkout-prd.pdf
stitch find files

Or add a quick note directly from the terminal with stitch create context:

stitch create context \
  --title "Checkout Flow Goals" \
  --description "Reduce guest checkout from four separate steps to a single focused view."

stitch find contexts