desktop-shell-maximize-gate

Verify shell chrome visibility across restored and maximized window states.

Updated Mar 16, 2026
One-click install
npx skills add https://github.com/BSchafer01/PanelNester --skill desktop-shell-maximize-gate
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: desktop-shell-maximize-gate
Source: https://github.com/BSchafer01/PanelNester/tree/main/.squad/skills/desktop-shell-maximize-gate
Command: npx skills add https://github.com/BSchafer01/PanelNester --skill desktop-shell-maximize-gate

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

When a desktop app owns its own chrome or hosts web UI content inside a native shell, maximizing the window can introduce regressions when returning to the restored state. This Skill provides a disciplined approach to gate those maximize-state fixes so restored-state behavior remains correct and visible, avoiding hidden layout shifts or clipping.

Core Features & Use Cases

  • Gate a maximize-state fix verification in desktop shells to ensure restored-state behavior is preserved.
  • Validate shell chrome and content layout across restored and maximized states, including titlebar, header, nav rail, active accents, and edge insets.
  • Use case: QA engineers reproduce bugs by cycling between restored and maximized states and verify visual integrity across routes.

Quick Start

Run a full maximize/restore cycle and compare shell chrome and content to ensure no clipping or regressions.

Frequently Asked Questions about desktop-shell-maximize-gate

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

FAQPage Schema
How do I prevent UI regressions when testing desktop shell maximize and restore state transitions?

To prevent maximize-state regressions, gate your fixes by cycling the window through restored and maximized states, verifying titlebar, header, nav rail, and content edges remain fully visible without clipping or hidden insets.

Why does my desktop shell chrome clip or hide insets after returning from a maximized state?

Shell chrome clipping after maximizing occurs because layout shifts alter edge insets. Validate the state transition cycle in both directions to identify where active accents or content edges become hidden during the restore.

What is the best way to verify shell chrome layout across restored and maximized window states?

The best way to verify shell chrome layout is to apply the same route in both restored and maximized states, checking the titlebar, header, nav rail, active accents, and content edges for visual integrity and accessibility.

Can I use visual validation to catch edge clipping during window maximize state transitions?

Yes, visual validation catches edge clipping by performing a full maximize and restore state transition cycle, comparing the shell chrome and content layout to ensure no hidden insets or regressions appear.

What should I check for when maximizing a desktop app causes hidden layout shifts in the restored state?

When maximizing causes restored-state layout shifts, check the titlebar, header, nav rail, active accents, and content edges. Conclude with a restored resize smoke check to validate target accessibility and prevent regressions.