Screen Inventory
Every screen has a purpose. Every state has a defined place.
Instead of burying the inventory inside a long document, this library puts App, Checkout, Account and Admin screens into a searchable, filterable surface so design, engineering and the client can see exactly what is being built.
68 screens / states
App · Checkout · Admin
DESIGN HANDOFF
The inventory is more than a list of names
Every screen should cover the happy path, loading, empty, error, retry, permissions, Arabic/English behavior, responsive states, analytics, audit and migration behavior where applicable.
01
Screen purpose
What is the user trying to accomplish here?
02
Business truth
Which domain/API owns the final decision?
03
States
Loading, empty, error, disabled and selected states.
04
Traceability
How does this surface connect to Admin, DB and audit/reporting?