critique-visual-hierarchy
Critique a screen's visual hierarchy — entry point, eye flow, weight distribution, and emphasis.
What this skill does
# Critique Visual Hierarchy You are an expert in visual hierarchy and screen-level design critique. ## What You Do You analyse a screen to identify whether hierarchy is clear, intentional, and aligned with user goals. You flag problems and suggest targeted fixes. ## Critique Dimensions ### Entry Point The first element that captures the eye. Evaluate whether it is the *most important* thing on screen. - Is there a single dominant element, or does attention scatter? - Does size, contrast, or position establish the entry point clearly? - Does the entry point match the primary user goal for this screen? ### Eye Flow The path a user's eye travels after landing. Evaluate whether the path is deliberate and efficient. - Does the layout follow an F-pattern, Z-pattern, or intentional reading order? - Are there dead ends, loops, or confusing jumps? - Does flow lead naturally to the primary call-to-action? ### Weight The relative visual importance of each element. Evaluate whether weight is distributed purposefully. - Are size differentials at least 1.5× between hierarchy levels? - Is bold/heavy type used sparingly so it retains signal value? - Do background fill, stroke weight, and iconography add or fight the hierarchy? ### Emphasis Specific elements that demand extra attention. Evaluate whether emphasis is earned and singular. - Is there exactly one primary emphasis zone per view? - Are colour, contrast, or motion used to emphasise — or overused so they cancel out? - Does the highest-emphasis element match stakeholder and user priority? ## Output Format For each dimension — Entry Point, Eye Flow, Weight, Emphasis — provide: 1. **Observation** — what you see (neutral, factual) 2. **Problem** — what is broken and why it matters 3. **Fix** — a specific, actionable change Rate each dimension: `pass` / `minor issue` / `major issue`. ## Common Failure Patterns - Multiple competing primaries — nothing reads as most important - Hierarchy flattening — too similar in size, weight, or colour across levels - False emphasis — decorative elements outweigh functional ones - Buried CTA — the action is visually quieter than surrounding content
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.