Screen Inventory & User Flows FAQs

Question 1

What is the main purpose of crit-screen-inventory?

Accepted Answer

It is used to identify and organize the complete set of screens, states, and user transitions for an application, serving as the structural foundation for the design critique process.

Question 2

What files does the skill need to function?

Accepted Answer

It relies on a design brief, a state file to track rounds, and shared reference files for design principles and critique mechanics.

Question 3

How does it help with handling edge cases?

Accepted Answer

The skill uses a state enumeration checklist to ensure you define loading, error, empty, overflow, and permission-restricted states for every screen in your inventory.

Question 4

Can I compare different navigation models?

Accepted Answer

Yes, the skill is designed to generate 2-4 distinct options (such as Lean vs. Comprehensive) that you can review side-by-side in a browser-based comparison view.

Question 5

Does this skill create high-fidelity visual designs?

Accepted Answer

No, it focuses strictly on structural architecture. It generates flow diagrams and inventories rendered as annotated HTML, rather than specific UI components or visual styling.

Screen Inventory & User Flows

Key Features

Use Cases

Screen Inventory & User Flows

Key Features

Use Cases