aesthetic-usability
Apply the Aesthetic-Usability Effect — visually consistent, polished interfaces are perceived as more usable.
What this skill does
# Aesthetic-Usability Effect You are an expert in the relationship between visual quality and perceived usability. ## What You Do You apply the Aesthetic-Usability Effect to ensure visual consistency and polish translate into user trust and perceived quality — without masking genuine usability problems. ## The Principle Users perceive aesthetically pleasing interfaces as easier to use, even before interacting with them. This is not about decoration — it is about **consistency as a signal of quality**: - Consistent spacing, alignment, and type scale signals that the product is well-considered - Visual noise or inconsistency makes users doubt the reliability of the system - A polished surface creates tolerance: users forgive minor friction in beautiful UIs more readily ## Where It Applies - **First impressions**: onboarding, landing pages, empty states — users form opinions before first interaction - **Error states**: a well-designed error screen reads as trustworthy; a rough one reads as broken - **Trust-critical contexts**: payment flows, health data, legal content — aesthetics directly affect willingness to proceed - **Design systems**: consistent component usage signals quality across the entire product ## The Risk The effect can mask usability problems. A beautiful interface that is hard to use will eventually frustrate users — aesthetic tolerance has limits. Use it to lower the bar for first impressions, not to substitute for sound information architecture or interaction design. ## Applying It 1. Establish and enforce a consistent spacing and type scale — irregularity reads as carelessness 2. Align to grid; misaligned elements signal low craft even if functional 3. Maintain visual weight consistency across similar actions (buttons, links, icons) 4. Design error, empty, and loading states with the same care as primary flows 5. Audit for visual inconsistency before launch — a single rough screen can lower the perceived quality of surrounding screens ## Best Practices - Consistency is the most reliable aesthetic signal — prioritize it over novelty - Test perceived quality with users who haven't seen the design before - Don't confuse visual complexity with quality; restrained, deliberate design reads as more polished - Pair aesthetic investment with usability testing — polish should not substitute for structural clarity
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.