agentic-engineering-experience

Start by translating product goals into step-by-step user journeys with clear route and page purposes. This Skill produces an experience map covering navigation, content hierarchy, and states, which the Design phase then turns into visual screens.

A page behavior contract should cover the page's purpose, navigation entry and exit points, loading, error, and empty states, and accessibility behavior. It describes behavior in plain language while staying separate from visual styling decisions.

No. It deliberately stops before creating visual screens or writing frontend code. Its output is an experience map and page contracts that feed into the separate Design and frontend engineering phases.

Use the experience phase whenever page purpose, navigation, or state behavior is not yet agreed upon. Skipping it risks inconsistent states and rework; it is most valuable for new flows or products with multiple routes and user roles.

It is one phase in the agentic-engineering pipeline, reading the project blueprint and core skill map, then handing its experience map and page contracts to the Design phase. It optionally coordinates with frontend-ui-engineering and taste-design skills when relevant.