caiolombello/caio-frontend
Frontend design, implementation and AI interface workflows
Use with frontend-design when designing or reviewing AI-native web interfaces: chat, copilots, generative editors, agent runs, tool activity, citations, or streamed artifacts. Owns model-state UX, user control, trust, cost/latency disclosure, and business-value evidence; not implementation code.
Use when creating, redesigning, polishing, or reviewing user-facing web UI: layout, visual direction, typography/color/spacing, states, responsiveness, accessibility, or design systems. Owns the visual quality bar and a screenshot-critique loop; pair with frontend-development for production code.
Use before implementing, changing, or fixing authorized production web UI code — components, routes, forms, interactions, state, or client data flow — in the project's stack or a minimal new one. Pair with frontend-design for visual decisions and screenshot QA. Not disposable experiments (throwaway-prototype), diagnosis-only work, or final PR review.