Development criteria
It turns the relationships and states of resources, deployments, and usage, key user flows, recovery paths, and completion conditions into an implementable specification.
CLOUD PROMPTS
Cloud infrastructure website prompts
How should a Cloud infrastructure site be designed? Model the relationships and states of resources, deployments, and usage first, then treat cost visibility, permissions, and availability as a primary risk. Each service guide below combines an implementation specification with design standards.
- Primary goal
- deploying and operating digital services
- Core entities
- resources, deployments, and usage
- Design risk
- cost visibility, permissions, and availability
10 REAL SERVICES
Cloud infrastructure · 10 real services
Development prompts and DESIGN.MD for 10 real services designed around deploying and operating digital services.
AWSoperational console · analytical and precise · high information density · project navigation -> key metrics -> operations table or logs -> response actionANSWER GUIDE
Cloud infrastructure 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 cloud interface for Cloud infrastructure, centered on resources, deployments, and usage, with a [reference] brand impression led by [color], while avoiding the original logo, proprietary copy, images, and pixel-level layout.
Risk to validate
Treat cost visibility, permissions, and availability as a primary design risk and define loading, empty, error, partial-data, and success states.