Development criteria
It turns the relationships and states of identities, threats, and policies, key user flows, recovery paths, and completion conditions into an implementable specification.
CYBERSECURITY PROMPTS
How should a Cybersecurity site be designed? Model the relationships and states of identities, threats, and policies first, then treat false confidence, access control, and incident response as a primary risk. Each service guide below combines an implementation specification with design standards.
10 REAL SERVICES
Development prompts and DESIGN.MD for 10 real services designed around protecting identities, devices, and organizations.
ANSWER GUIDE
Choose the service whose core screen and repeated behavior most closely match the product you are building. Apply only information priority and state design, never the reference brand assets.
It turns the relationships and states of identities, threats, and policies, key user flows, recovery paths, and completion conditions into an implementable specification.
Start from A security interface for Cybersecurity, centered on identities, threats, and policies, with a [reference] brand impression led by [color], while avoiding the original logo, proprietary copy, images, and pixel-level layout.
Treat false confidence, access control, and incident response as a primary design risk and define loading, empty, error, partial-data, and success states.