Your AI companion for Abstract.

Make version review about the decision, not a hunt for pixels.

A reviewer can see that a design changed without knowing why it changed, which requirement it addresses, or whether it accidentally altered a state that was already approved. Scrolling between versions is not a substitute for a clear review record.

Strawberry can compare the Abstract work visible in the tab with the brief and feedback you provide. It can prepare a review note that describes meaningful changes, related rationale, decisions still needed, and places where a human should inspect the design directly.

Turn scattered comments into a review that someone can close.

Feedback often arrives as tiny comments from different people, each reacting to a different moment in the product flow. A designer should not need to infer whether those comments conflict, repeat each other, or require a product decision rather than a cosmetic tweak.

With the comments and supporting tabs available, Strawberry can organise feedback by theme, screen, severity, and decision owner. It can preserve the original context while producing a review agenda that makes closure possible.

Give engineering a handoff that includes the edge cases.

A polished primary screen is not a complete handoff.

Engineering needs the states, behaviours, missing content, responsive considerations, and decisions that are easy to explain live but easy to lose when the link gets shared asynchronously.

Strawberry can prepare a handoff brief from the visible Abstract materials and the associated ticket or specification. It can name the final references, note uncertainties, and collect questions for the designer before implementation begins.

Save the review ritual that keeps design work moving.

Design teams revisit the same questions every week: which versions need a decision, what feedback is blocking progress, which handoffs are incomplete, and what changed since the last review? A standard private brief makes that meeting shorter and the follow-through clearer.

Once the format works for your team, save the Abstract review prompt as a Strawberry skill. A routine can prepare the agenda before the critique, while design edits, publishing, and branch decisions remain the responsibility of the people who own the work.

Frequently asked questions