ls-design-mobilelisted

# L.S.Design Mobile Design for the target platform and usage context rather than treating mobile as a smaller desktop. ## Decision order User and repository requirements come first, followed by product and platform truth, accessibility and function, this specialist's guidance, then aesthetic defaults. ## Mode selection - For responsive web, preserve document semantics, browser behavior, zoom, reflow, and progressive enhancement. - For native or cross-platform apps, follow the target platform's navigation, safe-area, typography, input, feedback, and permission conventions. - When both are required, share product concepts and tokens while allowing platform-specific components and flows. ## Workflow 1. Inspect target platforms, minimum sizes, input modes, navigation model, safe areas, and existing component system. 2. Prioritize tasks and content for intermittent attention and constrained space. 3. Define navigation, screen hierarchy, primary actions, and state transitions before surface styling. 4. Design for realistic content, keyboard presence, text expansion, rotation if supported, and system appearance settings. 5. Test tap, keyboard, screen-reader, loading, offline, permission, empty, and error paths that the product uses. ## Quality bar - Keep controls comfortably operable and separated; use platform guidance and product testing rather than one universal pixel number. - Do not hide essential actions behind gestures without visible alternatives. - Avoid excessive