Collaboration

Agent-assisted design still happens inside a team. This page describes how designers collaborate using Git, pull requests, and shared review — without needing to become full-stack engineers.

Who does what

Role	Typical ownership
Designer	Brief, context artifacts, design.md, UI slices, design review, PR description
Engineer	Architecture, API integration, auth, performance, merge approval for risky areas
Design ops / MUXAI champion	Harness standards, wiki updates, skill recommendations
Security / platform	Governance policy, deploy targets, secrets

Designers can own frontend slices in the harness; escalate when work touches backend, auth, or production infra.

Iteration slice workflow

Repeat for each feature or screen:

1. Branch — create a feature branch (feature/settings-nav). Never commit directly to main for shared repos.
2. Build — implement shell first, then section content with tokens and components.
3. Preview — run npm run dev; confirm layout, states, and responsive behavior locally.
4. Design review — run the design-review skill or manual check against design.md.
5. Accessibility pass — keyboard focus, contrast, labels on forms; fix obvious gaps before PR.
6. Diff review — skim the Git diff; confirm no secrets, no unrelated files, no token drift.
7. Pull request — open PR with screenshots, Figma link, and what changed for reviewers.
8. Merge — after approval and green checks; delete branch when done.

Pull requests for designers

A good PR description includes:

• What — user-facing change in plain language
• Why — ties to brief or ticket
• Screenshots — before/after or mobile + desktop
• Figma — link to frame or file
• Review focus — “Please check spacing on nav” beats “please review”

You do not need to explain every line of code. You do need to show intent.

Async critique

• Post preview URL or screenshots in Slack/Teams with specific questions.
• Use PR comments for line-level feedback; resolve threads before merge.
• When design direction changes mid-PR, update design.md or context artifacts — not just the code.

Designer ↔ engineer handoff

To engineers: “This slice is UI-complete for happy path; needs API hook for save.” List open questions.

From engineers: API contracts (JSON shape), error states, loading behavior. Add to context artifacts so the agent stays aligned.

Figma ↔ code: Keep Figma as source for exploration; repo + design.md as source for implementation. Note when code intentionally diverges and why.

Design system contributions

When you add or change a shared component:

• Match existing tokens and naming in design.md
• Document the component in the design system (Figma + code)
• Get design-system owner review on PRs that touch shared primitives

Shared wiki maintenance

After each project cycle, if the team rediscovered something:

• Add a glossary term
• Update Setup or Workflow
• Propose a skill for the catalog

See Templates for starter files.