critique-information-density

Critique screen density across cognitive load, content priority, scanning patterns, and progressive disclosure.

2.5k|358|Updated Mar 7, 2026
One-click install
npx skills add https://github.com/Owl-Listener/designer-skills --skill critique-information-density
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: critique-information-density
Source: https://github.com/Owl-Listener/designer-skills/tree/main/visual-critique/skills/critique-information-density
Command: npx skills add https://github.com/Owl-Listener/designer-skills --skill critique-information-density

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Screens that try to show everything at once overwhelm users, bury critical information, and slow down task completion. This Skill gives you a structured way to diagnose why a screen feels overwhelming and produce specific, actionable fixes instead of vague feedback.

Core Features & Use Cases

  • Four-dimension critique: Evaluates Cognitive Load, Content Priority, Scanning Pattern, and Progressive Disclosure with concrete diagnostic questions for each.
  • Structured output: For every dimension it produces an Observation, Problem, and Fix, plus a severity rating of pass, minor issue, or major issue.
  • Failure pattern detection: Flags common density problems such as dashboards showing every metric, 10+ column tables, and single-step forms that should be multi-step flows.
  • Use Case: A product team is redesigning an analytics dashboard that users describe as cluttered. Run this critique to identify which metrics are noise, which critical data is buried, and how to restructure the layout for scannability.

Quick Start

Critique the information density of this dashboard screenshot and rate each dimension with specific fixes.

Frequently Asked Questions about critique-information-density

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I critique a UI screen that feels overwhelming?

Evaluate the screen across four dimensions: cognitive load, content priority, scanning pattern, and progressive disclosure. For each, record a neutral observation, the problem and why it matters, and a specific fix, then rate the dimension as pass, minor issue, or major issue.

What is the difference between information density critique and Hick's law?

Information density critique assesses the whole screen: load, priority, scannability, and disclosure. Hick's law addresses the underlying principle that decision time grows with choice count, so use it when the core issue is the number of options presented.

How do I reduce cognitive load on a dashboard?

Show only the most actionable metrics instead of every available one, remove elements that do not serve the current task, and focus the screen on a single user goal. Defer secondary detail to drill-down views through progressive disclosure.

When should I use progressive disclosure in UI design?

Use progressive disclosure when a screen shows all available information at once and the entry path becomes ambiguous. Hide genuinely secondary content behind expandable sections, tabs, or detail views, but never bury primary actions or critical information.

What are common information density failure patterns?

Common failures include dashboards showing every metric, detail pages inlining all related objects, tables with 10+ columns where 3 do most of the work, single-step forms that should be multi-step, and onboarding that front-loads explanation before the user acts.