The designer’s contribution and teamwork
Design responsibilities, agent support and development autonomy.
- Status
- Observed
- Last reviewed
- 2026-10-10
Designer responsibilities
Initial analysis, competitor research, positioning and copy in collaboration with marketing, information architecture, flows and interactions. The designer builds rapid prototypes in code, tests them with users, documents the design system in Storybook and proposes scoped contributions through PRs.
The designer makes evidence, hypotheses, decisions and prototype limitations explicit. Prioritization and proposal approval are agreed with product and design stakeholders.
Development team autonomy
The development team owns architecture choices, product implementation, integration, technical testing and release. They choose their own workflow, skills and issue and task organization. The automations described here support the designer’s work and do not prescribe how other roles should work.
The point of contact is concrete: feasibility, shared components, supported states, expected behavior and PR review. The prototype code may be reused, adapted or rewritten at the team’s discretion.
Agents supporting design
The JADO specialist procedures separate research, UX design, visual direction, text, design systems, implementation and review. The main agent uses jado-flow to assign only necessary contributions and preserve the work contract.
UX and visual reviewers assess the result in read-only mode. Their review prepares a test or handoff; user testing gathers different evidence. The human remains responsible for choices and research interpretation.
UX artifacts may be written by the main agent or assigned author. Independent verification remains separate when required by the route: contract.