Agent workflow: go wide, remix, repeat

Agents accelerate exploration and implementation; they do not own product judgment. Native or production-like code is a prototype medium until evidence, review, and tests make it shippable.

Required artifacts

1. Purpose brief: human outcome, audience, context, constraints, non-goals, risks, and do-not-build boundary.
2. Divergence board: 6–10 named directions with materially different hierarchy, interaction, density, tone, or motion — not color variants.
3. Decision log: selected, rejected, and remixed parts with reasons tied to purpose and rules.
4. Realistic content set: audience-specific names, values, imagery shapes, locale lengths, and sensitive-content cases.
5. State matrix: empty, loading, partial, error, offline, permission denied, destructive, very long, very large, multilingual, RTL, large type, reduced motion, narrow, wide, interrupted, and restored.
6. Key-moment playground: explicit controls for springs/easing, phases, stagger, friction/inertia, offsets, type, color, haptic/audio timing, and state. Record the selected values and intent.
7. Review evidence: representative-user feedback, accessibility review, device/browser checks, and performance/failure results.
8. AI risk assessment: data flow, uncertainty, foreseeable misuse, safeguards, edit/undo, consequence-based confirmation, escalation, and feature-removal threshold.

Loop

Go wide

Prompt with the actual problem, audience, constraints, and desired feeling. Demand independently previewable alternatives. Reject cosmetic duplicates.

Remix

Name why a promising part works, combine compatible strengths, remove redundant ideas, and retain provenance. Never copy a reference's protected expression or brand identity; extract the general problem-solving principle.

Repeat

Introduce realistic content and hostile states, test with people, then tune the few moments that carry product character. Return to divergence if the concept, not the polish, is weak.

Acceptance gate

Do not call a generated interface refined when only one direction or happy path exists, content is placeholder text, consequential behavior lacks risk review, or human/accessibility evaluation is absent.

Source: Create UI prototypes using agents in Xcode, WWDC26, observed 2026-07-13. Workflow wording and acceptance criteria are AwesomeDS's transferable synthesis.