progressive-disclosure-defaults-and-tucking

What problem does it solve?

This Skill solves the problem of cluttered UX and overwhelming settings pages by making deliberate editorial decisions about what should be shown by default versus tucked behind progressive disclosure.

Core Features & Use Cases

• Defaulting disclosure state: Decide when sections should start open or closed based on who needs it, when it’s needed, and how often it’s used.
• Primary placement vs. tucking criteria: Triage controls into always/usually/sometimes primary and candidates for secondary or tertiary disclosure, including “Advanced” and exception-driven content.
• Tucking dynamic content safely: Apply rules so errors and real-time changes aren’t hidden in collapsed UI, using affordance signals like badges and banners instead.

Quick Start

Use the skill to audit a Settings page or form layout and recommend which sections and controls should be primary, secondary (disclosed), or tucked deeper, including appropriate default open/closed behavior.