layers-interaction-flow

Map user flows with breadboard notation for places, affordances, and edge cases.

Updated Apr 8, 2026
One-click install
npx skills add https://github.com/codesour-design/gravity --skill layers-interaction-flow
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: layers-interaction-flow
Source: https://github.com/codesour-design/gravity/tree/main/.agents/skills/layers-interaction-flow
Command: npx skills add https://github.com/codesour-design/gravity --skill layers-interaction-flow

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps product designers structure complex interactions by defining user journeys, states, affordances, and edge cases before committing to interface details.

Core Features & Use Cases

  • Interaction Flow Mapping: Creates breadboard notation that connects places, actions, destinations, and content within a product experience.
  • Edge Case Analysis: Identifies empty states, failures, loading behavior, cancellation paths, and unresolved decisions in user flows.
  • Flow Design Guidance: Supports product teams in evaluating user journeys, simplifying workflows, and aligning interactions with conceptual models.

Quick Start

Use the layers-interaction-flow skill to create a breadboard for the user journey of designing a new onboarding experience.

Frequently Asked Questions about layers-interaction-flow

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I map user flows before starting visual design?

Map user flows before visual design by creating breadboard notation that connects places, affordances, destinations, and edge cases to structure the interaction model.

What is breadboarding in interaction design and UX?

Breadboarding in interaction design is a method to map interaction structures and user flows by defining places, actions, destinations, and content before committing to interface details.

How do I identify edge cases and failure paths in product design?

Identify edge cases and failure paths in product design by evaluating user journeys for empty states, loading behavior, cancellation paths, and unresolved decisions using flow diagrams.

Can I use this approach for redesigning complex workflow interactions?

You can use this approach for workflow redesigns and interaction planning because it evaluates user journeys and aligns interactions with conceptual models before interface design.

Do I need visual mockups to design an onboarding experience user journey?

You do not need visual mockups to design an onboarding user journey; you can map the interaction flow and handle failure paths using breadboard notation first.

What is the best way to structure complex interactions and empty states?

The best way to structure complex interactions and empty states is to define user journeys, states, and affordances using breadboard notation and explicit flow diagrams.