Development criteria
It turns the relationships and states of tasks, schedules, and routines, key user flows, recovery paths, and completion conditions into an implementable specification.
PRODUCTIVITY PROMPTS
Productivity website prompts
How should a Productivity site be designed? Model the relationships and states of tasks, schedules, and routines first, then treat priority clarity and notification fatigue as a primary risk. Each service guide below combines an implementation specification with design standards.
- Primary goal
- planning time and completing focused work
- Core entities
- tasks, schedules, and routines
- Design risk
- priority clarity and notification fatigue
10 REAL SERVICES
Productivity · 10 real services
Development prompts and DESIGN.MD for 10 real services designed around planning time and completing focused work.
ANSWER GUIDE
Productivity 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 productivity interface for Productivity, centered on tasks, schedules, and routines, with a [reference] brand impression led by [color], while avoiding the original logo, proprietary copy, images, and pixel-level layout.
Risk to validate
Treat priority clarity and notification fatigue as a primary design risk and define loading, empty, error, partial-data, and success states.