Quality, safety, and responsible practice
Build quality and safety into the request — not as a final automated score.
Accessibility
Accessibility is not a final automated score. Build it into the request. At minimum:
- use semantic elements before custom containers;
- ensure every control has an accessible name;
- support keyboard operation and visible focus;
- maintain sufficient contrast;
- do not communicate meaning through colour alone;
- provide text alternatives for meaningful images;
- preserve usability at zoom and larger text sizes;
- use clear headings and labels;
- respect reduced-motion preferences;
- keep target sizes and spacing usable.
Responsive behaviour
Responsive design is not “make it mobile.” Specify how the composition should adapt:
- what stacks, wraps, collapses, scrolls, or disappears;
- maximum and minimum widths;
- how navigation changes;
- what happens to long labels and translated content;
- which information remains prioritised;
- how pointer and touch interactions differ.
Check the spaces between common device presets. Layouts often break between the screenshots everyone remembers to test.
States and edge cases
For each feature, consider:
- default;
- hover, focus, pressed, selected, and disabled;
- loading or progress;
- empty or first use;
- partial data;
- success and confirmation;
- recoverable error;
- blocking error;
- offline or unavailable service;
- permission denied;
- long, missing, or unexpected content.
Not every feature needs every state. The habit is to ask, not to blindly generate them all.
Privacy and security
- Never paste passwords, API secrets, private keys, production customer data, or identifiable research data into prompts.
- Store secrets in environment variables and keep
.envfiles out of Git. - A browser is public territory: anything shipped to frontend code can be inspected.
- Do not disable authentication or database protections just to make a demo work.
- Review dependency and data-permission choices before production use.
- Treat agent-suggested terminal commands as actions with real consequences; read them before approval.
Performance and motion
Motion should communicate change, relationship, or feedback — not prove that animation was installed.
Use Motion.dev for purposeful microinteractions and transitions. Prefer CSS for simple state changes. Consider a more specialised animation tool only when the experience genuinely needs complex sequencing.
Define a small motion system:
- quick feedback;
- standard transition;
- deliberate entrance;
- easing values;
- reduced-motion alternatives.
Avoid animating everything on page load. Protect reading, input, and navigation from delay. Optimise large images and videos, and test on less powerful devices.
Human review
Before sharing, ask:
- Does the product make a claim we cannot support?
- Did the AI introduce a pattern we did not choose?
- Is the interface technically working but experientially confusing?
- Are we presenting synthetic material as user evidence?
- Could sensitive data have entered the project or repository?
- Can another person understand the limitations of this prototype?