设计与多媒体

critique-information-density

owl-listener/de…r-skills

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).

  • 1760 次安装
  • 3200 星标
  • 收录于

安装命令

npx skills add https://github.com/owl-listener/designer-skills --skill critique-information-density

SKILL.md

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?