Rules for designing ADHD-friendly interfaces. Use this when creating or refactoring UI components.
--- name: adhd-ui-optimizer-17226790e7ef description: Rules for designing ADHD-friendly interfaces. Use this when creating or refactoring UI components. --- # Goal Ensure the app remains "Low-Cognitive-Load" to prevent user overwhelm. # Instructions 1. **The Rule of One**: Every screen should have exactly ONE primary action button (e.g., "Log Dose"). 2. **Visual Hierarchy**: Use size and color to make the most important info (Time of next dose) 3x larger than secondary info. 3. **Contrast**: Use high-contrast themes but avoid "neon" colors that can cause sensory fatigue. 4. **Micro-copy**: Use "Action Labels." Instead of "Submit," use "I took it!" 5. **Feedback Loop**: Always provide immediate, dopamine-positive feedback (e.g., confetti, checkmarks) for completed actions. # Constraints - NEVER use pop-up ads or multiple competing notifications on one screen. - Avoid long paragraphs; use bullet points for medication info. - Minimize form fields; use smart defaults or steppers.--- name: adhd-ui-optimizer-17226790e7ef description: Rules for designing ADHD-friendly interfaces. Use this when creating or refactoring UI components. --- # Goal Ensure the app remains "Low-Cognitive-Load" to prevent user overwhelm. # Instructions 1. **The Rule of One**: Every screen should have exactly ONE primary action button (e.g., "Log Dose"). 2. **Visual Hierarchy**: Use size and color to make the most important info (Time of next dose) 3x larger than secondary info. 3. **Contrast**: Use high-contrast themes but avoid "neon" colors that can cause sensory fatigue. 4. **Micro-copy**: Use "Action Labels." Instead of "Submit," use "I took it!" 5. **Feedback Loop**: Always provide immediate, dopamine-positive feedback (e.g., confetti, checkmarks) for completed actions. # Constraints - NEVER use pop-up ads or multiple competing notifications on one screen. - Avoid long paragraphs; use bullet points for medication info. - Minimize form fields; use smart defaults or steppers.
Imported from the listed AgentSkill.sh category. Complete supplied package files and notices are retained. Required external tools and credentials are not installed. No bundled code was executed during import. Individual agent task behavior has not been tested.