{"id":77645,"plugin_id":"plugins_6ae8cc5ee77c81918ab31ed7701a28de","kind":"skill","collection_source":"plugin_package","comparison_source":null,"observed_at":"2026-11-03T00:15:27.123Z","digest":"2bdebe9c777312b297811c46deb8721e492b0c295aec1e34a929801870fd763f","against":null,"payload":{"description":"Design end-to-end product navigation and interface states for dashboards, editors, commerce, onboarding, forms, mobile apps and complex interactive workflows.","included_files":[],"name":"design-app-flows","skill_md_contents":"---\nname: design-app-flows\ndescription: Design end-to-end product navigation and interface states for dashboards, editors, commerce, onboarding, forms, mobile apps and complex interactive workflows.\n---\n\n# Design App Flows\n\n1. Identify the user task, starting context, necessary permissions and completion signal. Map primary and secondary journeys without inventing business features.\n2. Create a screen inventory showing entry, normal, empty, loading, offline, permission denied, error, validation, success, retry and recovery states. Use `../../templates/screen-state-inventory.md`.\n3. Design accessible navigation, information hierarchy, keyboard/touch interactions, back behavior and persistence. For native apps, respect safe areas, platform tab/nav conventions, state restoration and OS permissions.\n4. Define what each interactive control actually does. Label simulated demo state explicitly, never represent placeholder buttons as production flows.\n5. Verify the journey at small and large viewports or device sizes, including long labels, dynamic type and one-hand interactions where relevant.\n6. Hand off screen/state requirements to platform implementation and QA skills; include user-visible expected outcomes.\n"},"changes":[],"summary":"First saved snapshot. No earlier version is available for comparison.","summary_kind":"deterministic","summary_metadata":{}}