| name | getting-started-with-design-work-in-strawberry |
| description | Help a designer audit a live interface for drift, understand who they are designing for, turn feedback into design themes, and present work. Use to choose a first design workflow and complete one real result. |
Getting Started with Design Work in Strawberry
Help the user finish one real piece of design work, then show them the workflow behind it.
The useful ground here is the built product rather than wherever the design is authored. Walking the
live interface, gathering the evidence a decision needs, capturing what a review actually decided,
and turning accepted work into something the people building it can follow.
Start with the live product
The most useful thing here is that the companion can open the real interface and move through it.
Use strawberry/design/audit-a-design-system to walk agreed pages and record where the built
interface has drifted from the system, across the states and breakpoints that matter.
Use strawberry/product-engineering/audit-a-product-flow when the question is whether the flow
works rather than whether it looks consistent.
Ground the work in evidence
Use strawberry/product-engineering/synthesize-customer-feedback to turn approved feedback into
source-linked themes, so a design argument rests on what users said rather than on whoever spoke
last in the review.
Use strawberry/marketing/research-an-audience when the user needs a sourced picture of who they
are designing for.
Keep decisions from evaporating in reviews
Design decisions are usually made in a room and then lost. Use
strawberry/operations/prepare-for-meetings to walk into a review with what was decided last time,
what has changed since, and the open questions that need answers. Use
strawberry/operations/debrief-a-meeting afterwards to capture what was actually decided, what is
still open, and who owns the next move, so the same discussion does not run twice.
Carry it into the work that follows
Use strawberry/product-engineering/write-a-product-spec when a design decision needs specifying
for the people building it, and strawberry/research-analysis/create-beautiful-slide-deck when the
work needs presenting to a room rather than reviewed in a file.
Keep what works
Preserve the accepted system, audit scope, states checked, and report format as a custom skill. Use
strawberry/operations/set-up-shared-team-workflow when the design team needs one shared method. A
Routine can re-walk agreed surfaces after each release and report only new drift, once scope and
review point are clear.
