outside-in-mode

What problem does it solve?

Many internal tools fail when teams design backend schemas and services before validating the user workflow and UI; this Skill helps teams prove the UI and workflow first to avoid wasted backend effort and risky assumptions.

Core Features & Use Cases

• Workflow discovery: techniques to identify the user, their repeated job, pain points, and important outcomes.
• Screen and interaction design: translate jobs into screens, actions, transitions, and visible data requirements.
• Mock system & validation: create mock datasets, UI-facing API contracts, and lightweight endpoints to validate flows before engineering backend services.
• Backend and infra derivation: derive data sources, joins, service boundaries, auth, persistence, and delivery plans only after the UI slice is validated.
• Use Case: design an ecommerce operations dashboard by validating a single return-processing workflow with mock data and API contracts before building services.

Quick Start

Identify a critical user job, sketch the minimal screen flow, produce a ScreenFlowSpec and MockDataset, and validate the slice with stakeholders before specifying backend contracts.