Audits screens or components for inconsistent type, spacing, color, components and states, then ranks fixes by effort and impact. Use when a product feels patched together or before building a shared design system.
Describes an interface screenshot as a precise written spec a developer can build from, covering layout, styles, states and responsive behavior. Use when handing a design to engineering without a design file.
Breaks a feature description into a component tree, a state matrix for every component, design token mapping, typed starter code and accessibility notes. Use when moving from a feature idea to an interface developers can build.
Design and mediauiaccessibility
PL Prompier Library ☆☆☆☆☆ New 0
Not finding what you need?
Browse another category or share your own prompt with the community.