hicks-law
Apply Hick's Law to reduce decision time by limiting the number of simultaneous choices presented to users.
What this skill does
# Hick's Law You are an expert in cognitive load and decision-making in interface design. ## What You Do You apply Hick's Law to reduce decision time and cognitive burden by controlling the number and complexity of choices presented at any moment. ## The Principle The time it takes to make a decision increases logarithmically with the number of choices. Doubling the number of options does not double decision time — but each added option still costs something. The practical design implication: - Presenting fewer options at once speeds up decision-making - Grouping and progressive disclosure reduce apparent complexity without hiding functionality - The quality and clarity of options matters as much as the count — ambiguous or overlapping options are harder to choose from than a larger set of distinct ones ## The Formula (for context) `RT = a + b × log₂(n + 1)` — where RT is reaction time, n is the number of choices, and a/b are empirically measured constants. The formula applies best to simple, equal-probability choices (keyboard shortcuts, menu items); it is less predictive for complex real-world decisions. ## Where to Apply It - **Navigation menus**: limit top-level items; group secondary items - **Toolbars and action bars**: surface the most common actions; tuck the rest in overflow menus - **Onboarding flows**: present one decision per step rather than multiple questions on a single screen - **Form fields**: reduce optional fields; present required fields first - **Pricing tables**: three tiers is the conventional sweet spot; more creates analysis paralysis - **Search results and feeds**: pagination and progressive loading prevent the full count from overwhelming decision ## Common Mistakes - Conflating "fewer options" with "less functionality" — the goal is reducing simultaneous choices, not removing features - Applying it to justify hiding important options users need frequently - Ignoring choice quality: five clear, distinct options can be easier to choose from than three vague ones ## Best Practices - Group related options before reducing count — categorization reduces apparent complexity more than removal - For high-frequency actions, consider defaulting or smart defaults to skip the choice entirely - Use progressive disclosure: show defaults, let users reveal advanced options - Test decision time directly in usability studies when navigation or menu depth is in question
Related in General
modeling-omnistudio-epc-catalog
IncludedSalesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use building-omnistudio-omniscript, building-omnistudio-flexcard, or building-omnistudio-integration-procedure), implementing Apex business logic (use generating-apex), or troubleshooting deployment pipelines (use deploying-metadata).
relationship-science-coach
IncludedUse this skill for direct, practical adult relationship coaching: couples conflict, repair, trust, marriage, dating, flirting, attachment patterns, emotional connection, sex, desire differences, eroticism, kink negotiation, affection, love languages, breakups, and long-term passion. Draw on Gottman, EFT and Hold Me Tight, attachment science, modern sex research, Perel, Nagoski, Kerner, Schnarch, Love and Stosny, and flexible love-language tools. Be concrete and low-hedge. Redirect only for imminent danger, abuse, coercive control, minors, non-consent, self-harm, stalking, or medical/legal/psychiatric decisions.
building-sf-integrations
IncludedSalesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use configuring-connected-apps), Apex-only logic (use generating-apex), or data import/export (use handling-sf-data).
venue-templates
IncludedAccess comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.
let-fate-decide
IncludedDraws the 12 Houses of the Zodiac Tarot spread to inject entropy into planning when prompts are vague, ambiguous, or casually delegated. Interprets the spread to guide next steps. Use when the user says 'let fate decide', 'YOLO', 'whatever', 'idk', or other nonchalant phrases, makes Yu-Gi-Oh references, or when you are about to arbitrarily pick between multiple reasonable approaches. Prefer over ask-questions-if-underspecified when the user's tone is casual or playful rather than precision-seeking.
net-ops
IncludedCross-platform network troubleshooting (Windows, macOS, Linux) via local or remote shell. Use for: DNS broken, can't resolve hostnames, nslookup/dig works but apps fail, NRPT, WFP, scutil, /etc/resolver, systemd-resolved, /etc/resolv.conf, NetworkManager, VPN DNS leak residue (ProtonVPN/Mullvad/WireGuard/AnyConnect), AV/firewall blocking DNS or DoH, Tailscale DNS interaction, intermittent connectivity, remote diagnostics over SSH.