recursica-skill-screen-priority

Rank content by the user's workflow, then apply the inverted triangle: broadest, most widely applicable content at the top in the largest treatment, becoming more granular and persona-specific toward the bottom. Priority is expressed through position or size.

There is no cap on distinct pieces of information; dozens or hundreds can be correct for enterprise work. The real test is whether the screen supports the investigations and actions the user came to perform, not a count threshold.

Rarely-used forms like create, import, or configure should never hold permanent screen space. Keep a visible trigger on the page and open the form on demand in a modal or panel, so frequent tasks keep the permanent regions.

No, meaning must never ride on color alone. Carry hierarchy with typography, position, white space, maximum widths, layout balance, and imagery where the content supports it.

The application uses one scrollbar: the user scrolls the browser from anywhere while sticky regions stay put. Inner scrolling regions force cursor placement before the wheel works, which is treated as a failure; the only possible exception is a full-viewport table.

A screen is complete when it meets the user's needs against their workflow and mental model, and the simplification pass is done: unnecessary content removed via the removal test and labels made as concise as possible, with simplification always the last step.