Development criteria
It turns the relationships and states of services, applications, and cases, key user flows, recovery paths, and completion conditions into an implementable specification.
GOVERNMENT PROMPTS
Public services website prompts
How should a Public services site be designed? Model the relationships and states of services, applications, and cases first, then treat accessibility, plain language, and evidence as a primary risk. Each service guide below combines an implementation specification with design standards.
- Primary goal
- access to government services and information
- Core entities
- services, applications, and cases
- Design risk
- accessibility, plain language, and evidence
10 REAL SERVICES
Public services · 10 real services
Development prompts and DESIGN.MD for 10 real services designed around access to government services and information.
ANSWER GUIDE
Public services How to choose a prompt
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.
Design criteria
Start from A portal interface for Public services, centered on services, applications, and cases, with a [reference] brand impression led by [color], while avoiding the original logo, proprietary copy, images, and pixel-level layout.
Risk to validate
Treat accessibility, plain language, and evidence as a primary design risk and define loading, empty, error, partial-data, and success states.