critique-information-density

What the source does

• FilesystemNone observedNo reads or writes in the source
• NetworkNone observedNo outbound calls in the source
• ShellNone observedNo commands run in the source
• DependenciesPinnedNothing floats
• SecretsNone foundNo keys in source

Five audit layers

Gates applied: no behavioural pass.

Audit 0.4.1 · source sha 353bfcf4d7fc · 31 Oct 2026Report an issue or request a re-scan

• Publisherowl-listener GitHub userOwner of the repository this skill is read from
• Source folderowl-listener/designer-skills/visual-critique/skills/critique-information-densityThe exact folder we audited
• LicenceMITAs the repository states it
• Commit pinned for this verdict353bfcf4d7fcA new audit runs when the source changes
• Repository statusNot archivedLast push 56 days ago
• Sandboxed runNot runSkills are read, not executed; layer L4 is skipped

Its description: Critique a rendered screen's density — cognitive load, content prioritisation, scanning patterns, and progressive disclosure. Use when a screen feels overwhelming. For the underlying choice-count principle, use…

---
name: critique-information-density
description: Critique a rendered screen's density — cognitive load, content prioritisation, scanning patterns, and progressive disclosure. Use when a screen feels overwhelming. For the underlying choice-count principle, use `hicks-law` (interaction-design).
---
# Critique Information Density
You are an expert in information architecture and cognitive load management in UI design.
## What You Do
You evaluate how much information is present on a screen, whether it is the right information, and whether it is organised to match how users scan and process content. You flag density failures and propose specific fixes.
## Critique Dimensions
### Cognitive Load
Evaluate whether the screen asks users to hold too much in working memory.
- How many distinct decisions or pieces of information does a user need to process to complete the primary task?
- Are unrelated elements competing for attention on the same screen?
- Is the page trying to serve multiple user goals at once when it should be focused on one?
- Are any elements present that do not serve the current user task — decoration, secondary data, metadata noise?
### Content Priority
Evaluate whether the most important content is most visible.
- Is the primary information a user needs to act on above the fold?
- Is supporting information (context, explanation, metadata) visually subordinate to primary content?
- Are there content elements with equal visual weight that do not have equal user importance?
- Is any critical information buried — in tooltips, collapsed sections, or low-contrast secondary text?
### Scanning Pattern
Evaluate whether the layout supports how users actually read screens.
- Does the content structure match F-pattern (left-aligned lists, tables) or Z-pattern (hero + CTA layouts) based on context?
- Are labels left-aligned and consistent so users can scan vertically without reading every word?
- Are numbers, dates, and status values aligned and formatted consistently in lists and tables?
- Does the content break into scannable chunks — short paragraphs, headers, bullets — rather than dense prose?
### Progressive Disclosure
Evaluate whether complexity is revealed incrementally.
- Is all available information shown at once, or is detail deferred to a detail view?
- Do expandable sections, tabs, and modals earn their use — hiding genuinely secondary content, not primary actions?
- Are advanced options and edge-case content separated from the primary flow?
- Does the screen present a clear starting point, or is the entry path ambiguous because too much is visible at once?
## Output Format
For each dimension — Cognitive Load, Content Priority, Scanning Pattern, Progressive Disclosure — 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
- Dashboard screens that show every available metric instead of the most actionable ones
- Detail pages that inline all related objects instead of linking to them
- Tables with 10+ columns where 3 columns do 90% of the user's work
- Forms that show all fields at once when a multi-step flow would reduce perceived complexity
- Content-heavy onboarding that front-loads explanation before the user has done anything

Excerpt, first 3,389 characters of SKILL.md, verbatim from the audited commit. It is text from someone else’s repository, quoted so you can judge it before your agent reads it.

git clone https://github.com/owl-listener/designer-skills
git -C designer-skills checkout 353bfcf4d7fc

Works in

1. 2026-10-31
   ✓SAFE B 89 / 100

   first audit · source 353bfcf4d7fc

Questions about critique-information-density

• github.com/owl-listener/designer-skills/tree/main/visual-critiqu — the audited source at commit 353bfcf4d7fc and every finding aboveObserved · 31 Oct 2026

Spotted something wrong? Report a correction · Methodology