lumolisted

# Lumo Mobile design intelligence for Claude Code. Lumo combines a curated rule set with a small toolkit of deterministic Python tools — so checks that need real math (WCAG luminance, OKLCH correction, AST diff, cross-platform parity) return facts, not LLM guesses. ## When to Use Use Lumo when the user request touches any of: - Accessibility / WCAG contrast questions on a colour pair or palette - Reviewing or auditing mobile UI code (Jetpack Compose, Android XML, SwiftUI, UIKit) - Comparing the same screen across iOS and Android for visual / behavioural parity (padding, animation timing, touch target, typography scale) - Applying cognitive-science rules to a layout: Fitts (target size × distance), Hick (choice count → decision time), Gestalt grouping, Nielsen heuristics - Choosing or validating colour tokens for a mobile design system - Detecting platform-specific anti-patterns (e.g. emoji as system icons, hardcoded hex in components, missing safe-area handling) ## When NOT to Use Skip Lumo entirely for: - Pure backend / API / database tasks - Non-mobile web design (use a web-focused skill instead) - Build / CI / dependency / version-bump tasks - Performance work that doesn't touch UI rendering - Tasks where the user has explicitly opted out of design feedback Do not invoke Lumo "just in case" the request might be design-adjacent. If the request doesn't match a trigger above and the user hasn't named a mobile UI concern, stay out. ## Tools Lumo ships with Py