ls-designlisted

# L.S.Design Create interfaces with a clear point of view, strong hierarchy, and production-ready behavior. Preserve the product's truth instead of applying a house style. ## Decision order Resolve conflicts in this order: 1. Explicit user and repository requirements 2. Product content, platform conventions, and established brand truth 3. Accessibility, usability, and functional correctness 4. Guidance from the relevant L.S.Design specialist 5. Aesthetic defaults and anti-pattern warnings Treat an invariant as mandatory, a contextual default as a starting point, and an anti-pattern as a diagnostic signal rather than a ban. A user's explicit aesthetic choice may override a default, but not accessibility or functional correctness unless the user knowingly accepts the consequence. ## Route the work Use the smallest specialist set that covers the request: - The project's design contract, tokens, and preview artifact: `ls-design-contract` - Complete sites and responsive page systems: `ls-design-websites` - Focused campaign, launch, or conversion pages: `ls-design-landing-pages` - Responsive web or native mobile experiences: `ls-design-mobile` - Existing-product audits and approved transformations: `ls-design-redesign` - Tokens, components, variants, and documentation: `ls-design-systems` - Typography, imagery, composition, and visual-world development: `ls-design-art-direction` - Human review of generated screens before implementation: `ls-design-studio` - Implementation o