simplified-views
starsforks
How to install simplified-views?
owl-listener/inclusive-design-skills/simplified-views
$npx -y skills add Owl-Listener/inclusive-design-skills --skill simplified-viewsDesign simplified and reduced-complexity views of interfaces for users who need less visual noise and fewer options. Use when designing settings, dashboards, complex tools, or any interface that could benefit from a simpler mode. Triggers on: simplified view, simple mode, easy mo
SKILL.md
| 1 | # Simplified Views |
| 2 | |
| 3 | Design interfaces that offer a simpler version of themselves — fewer |
| 4 | options, less visual complexity, clearer paths — for users who need |
| 5 | or prefer reduced complexity. |
| 6 | |
| 7 | ## Who This Is For |
| 8 | |
| 9 | - People with cognitive disabilities who are overwhelmed by complex interfaces |
| 10 | - Older adults who prefer simpler, more predictable tools |
| 11 | - New users who don't need advanced features yet |
| 12 | - Anyone in a stressful or low-energy context |
| 13 | - People using assistive technology where less clutter means |
| 14 | faster navigation |
| 15 | |
| 16 | ## Core Principle |
| 17 | |
| 18 | The simplified view is not a lesser version. It's a focused version |
| 19 | that contains everything needed for the core tasks and nothing that |
| 20 | isn't. |
| 21 | |
| 22 | ## Design Patterns |
| 23 | |
| 24 | ### Feature Layering |
| 25 | - Identify core tasks (what 80% of users do 80% of the time) |
| 26 | - Show core features by default |
| 27 | - Advanced features accessible via "Show more" or "Advanced" |
| 28 | - Never require the advanced view to complete basic tasks |
| 29 | - The simplified view should feel complete, not stripped |
| 30 | |
| 31 | ### Progressive Complexity |
| 32 | - Start simple, let users add complexity as they need it |
| 33 | - Onboarding should begin in simplified mode |
| 34 | - Offer to increase complexity when the user demonstrates comfort |
| 35 | - "You might also want to try..." not "You're in basic mode" |
| 36 | - Never make users feel that simplified = inferior |
| 37 | |
| 38 | ### Dashboard Simplification |
| 39 | - Default dashboard: 3–5 key metrics, primary actions |
| 40 | - Full dashboard: all metrics, secondary actions, configuration |
| 41 | - Let users choose which cards/widgets to show |
| 42 | - Remember their choice across sessions |
| 43 | - Provide preset layouts: "Essential", "Detailed", "Custom" |
| 44 | |
| 45 | ### Navigation Simplification |
| 46 | - Simplified nav: top-level items only |
| 47 | - Full nav: all levels visible |
| 48 | - Both must reach all content — simplified may need more clicks |
| 49 | but each click should be obvious |
| 50 | - Breadcrumbs help users who take the longer path |
| 51 | |
| 52 | ### Form Simplification |
| 53 | - Show required fields only by default |
| 54 | - "Show optional fields" expands the form |
| 55 | - Smart defaults reduce decisions |
| 56 | - Break complex forms into steps in simplified mode, |
| 57 | show all fields on one page in advanced mode |
| 58 | |
| 59 | ## Implementation Approaches |
| 60 | |
| 61 | ### User-Controlled Toggle |
| 62 | - Visible setting: "Simplified view" / "Full view" |
| 63 | - Available in app settings AND on the page itself |
| 64 | - Preference remembered across sessions |
| 65 | - Clearly labelled — never hidden |
| 66 | |
| 67 | ### Responsive Simplification |
| 68 | - Automatically simplify at smaller viewports |
| 69 | - Mobile views are inherently simplified — embrace this |
| 70 | - Don't try to cram the desktop layout into mobile |
| 71 | |
| 72 | ### Role-Based Defaults |
| 73 | - New accounts start in simplified mode |
| 74 | - Power users can switch to full mode |
| 75 | - Admin accounts may need full mode by default |
| 76 | - Let users override role-based defaults |
| 77 | |
| 78 | ## Anti-Patterns |
| 79 | |
| 80 | - "Lite" versions that lack essential features |
| 81 | - Simplified modes that are clearly afterthoughts with broken layouts |
| 82 | - Forcing users to request simplified mode through support |
| 83 | - Patronising language ("Easy mode for beginners!") |
| 84 | - Removing access to content rather than reorganising it |
| 85 | |
| 86 | ## Assessment Questions |
| 87 | |
| 88 | 1. Is there a simplified view available for complex interfaces? |
| 89 | 2. Can core tasks be completed entirely in simplified mode? |
| 90 | 3. Is the toggle between modes easy to find and use? |
| 91 | 4. Does simplified mode feel complete, not stripped? |
| 92 | 5. Are user preferences for view mode remembered? |
People who liked this also viewed
6 picksType
- web-design-guidelinesReview UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "check accessibility", "audit design", "review UX", or "check my site against best practices".SkillsJul 2026
- lark-slides飞书幻灯片：创建和编辑幻灯片。创建演示文稿、读取幻灯片内容、管理幻灯片页面（创建、删除、读取、局部替换）。当用户需要创建或编辑幻灯片、读取或修改单个页面时使用。当用户给出 doubao.com 的 /slides/ URL/token 时，也应直接使用本 skill，不要因为域名不是飞书而回退到 WebFetch；路由依据是 URL 路径模式和 token，而不是域名。不负责：云文档内容编辑（走 SkillsJul 2026
- design-taste-frontendTaste-Skill - gives your AI good taste. stops the AI from generating boring, generic slop SkillsJul 2026
- ui-ux-pro-maxUI/UX design intelligence for web and mobile. Searchable local database with 84 styles, 192 color palettes, 74 font pairings, 192 product types, 98 UX guidelines, 104 icon entries, 16 GSAP motion presSkillsJul 2026
- caveman-helpQuick-reference card for all caveman modes, skills, and commands. One-shot display, not a persistent mode. Trigger: /caveman-help, "caveman help", "what caveman commands", "how do I use caveman".SkillsJul 2026
- codebase-designShared vocabulary for designing deep modules. Use when the user wants to design or improve a module's interface, find deepening opportunities, decide where a seam goes, make code more testable or AI-nSkillsJul 2026
