flow-optimization
Flow Optimization
Flow is the state of complete immersion where users lose track of time and feel in control. Protecting it is a design responsibility.
Evidence Tiers
[Research] — Peer-reviewed studies, controlled experiments
[Expert] — Nielsen Norman Group, recognized UX authorities
[Case Study] — Documented examples from major products
[Convention] — Industry practice, limited formal validation
Multiple tags = stronger evidence: [Research][Expert]
Mixed findings noted as: [Research — Mixed]
Flow State Foundations
More from bfmcneill/agi-marketplace
psychology-foundations
Use when you need to understand WHY certain UX patterns work. Covers cognitive psychology, behavioral science, and neuroscience foundations that underpin satisfying experiences.
13progressive-disclosure
Use when designing interfaces with complex functionality, settings panels, or expert features. Covers layering information so beginners aren't overwhelmed and experts aren't held back.
7design-patterns
Use when refactoring code or designing flexible systems. Covers creational, structural, and behavioral patterns with Python examples.
6sveltekit-builder
Use when building SvelteKit apps with Svelte 5. Covers runes, SSR, forms, and stack patterns (Kysely, Better Auth, shadcn-svelte).
4agent-behavior
Use at the start of any coding session to establish activity tracking and working patterns. Defines how the agent should document its work and communicate progress.
3feedback-design
Use when building loading states, progress indicators, success confirmations, or error messages. Covers feedback loops and patterns that feel satisfying.
3