puma-user

This skill captures who the users are and how they work so the agent can make practical product and UX decisions.

Primary users are city field-operations staff managing and resolving physical city issues, including:

They use the system to manage day-to-day tasks while moving through the city, often in vehicles and frequently on mobile devices.

When to use

Use this skill whenever work involves:

defining features, flows, or UI for city operations task management
prioritizing requirements for field teams handling physical infrastructure and services
designing or refining mobile experiences for workers in motion
writing acceptance criteria, stories, prompts, or product docs related to frontline city maintenance users

Instructions

Treat city field workers as the primary user persona.
Assume users are often mobile-first, on the road, and may have limited attention while working.
Prioritize clarity and speed over complexity in any proposed flow.
Keep task interactions short and obvious: quick status updates, minimal typing, and clear next actions.
Use plain, direct language and avoid jargon in labels, messages, and instructions.
Design for difficult real-world conditions: sunlight glare, one-handed use, interruptions, and variable connectivity.
Prefer large touch targets, strong visual hierarchy, and readable text for fast scanning.
Recommend safe interaction patterns for in-motion contexts (for example, defer non-urgent detail entry and support quick capture).
When proposing changes, explicitly explain how they improve usability for workers managing parks, roads, and garbage-collection tasks.
If tradeoffs are needed, choose the option that reduces cognitive load and field friction.

Source Transparency