Interface Lab Library
Skills collect reusable local prompt techniques.
Local skills cover layout, motion, borders, shadows, WebGL, icons, and component treatments. Choose the techniques first, then combine them with systems and assets.
Prompt Skills
Local expression layer: layout, motion, borders, shadows, WebGL, and copy-ready prompt techniques.
Commerce Browse Cart Checkout Funnel
Design, audit, or implement retail ecommerce funnels from homepage/category/search, product-list filtering and sorting, PDPs, add-to-cart feedback, cart review, guest checkout, address validation, payment errors, and order confirmation.
Use for retail ecommerce, online stores, catalogs, PLPs, PDPs, carts, mini carts, checkout, guest checkout, shipping/pickup, payment, promo codes, order confirmation, and conversion optimization; use the food-commerce skill first for restaurant or food ordering.ProInteraction · 0ProFood Commerce Order Path
Design, audit, or implement food-commerce first viewports, menu cards, price proof, ingredient/nutrition evidence, cart state, and order-motion fallbacks.
Use for restaurants, cafes, drinks, bakeries, quick-service, takeaway, ghost kitchens, food-commerce, and food pop-up pages; inputs must include business type, primary conversion, first-viewport product object, menu data, price/proof signals, motion plan, and target viewports.ProInteraction · 0ProAI Generation Progress and Recovery
Define staged progress, cancel/retry, partial results, failure recovery, and status announcements for AI generation, transcoding, import, long-running jobs, and queues.
Inputs must include task type, estimated duration, whether percentage is knowable, stage list, queue status, cancel support, background continuation, retryability, and whether partial results can be shown.ProInteraction · 0ProMobile Action Density
Create action priority, touch target, safe-area, keyboard, and non-overflow rules for mobile toolbars, filters, bottom action bars, and long-label buttons.
Use for mobile top toolbars, bottom action bars, filter strips, bulk actions, detail-page action clusters, and long-label CTAs; inputs must include action list, frequency, destructive risk, text need, target viewports, and keyboard scenarios.ProInteraction · 0ProLibrary Search and Facet Flow
Design search, categories, facets, matched excerpts, empty states, and detail-return paths for knowledge, asset, template, component, and case libraries.
Inputs must include library type, item scale, primary user tasks, item metadata fields, filterable fields, sorting strategy, detail route, and whether the library is used by RAG/agents.ProInteraction · 0ProEmpty State Action Recovery
Design cause, copy, recovery actions, and frontend state contracts for first-use, no-results, filtered-empty, permission, configuration, failure, offline, and completed-empty states.
Inputs must include surface type, primary task, empty reason, user permission, current query/filter/loading/error state, available actions, copy tone, target viewports, and data source/error code.ProInteraction · 0ProLoading Skeleton State Contract
Design timing decisions, state machines, accessible feedback, and frontend contracts for loading, skeleton screens, inline loading, spinners, progress bars, optimistic updates, streaming placeholders, and refresh states.
Inputs must include surface type, operation type, expected duration, whether progress is measurable, whether stale content exists, duplicate-submit risk, cancel/retry/background capability, target viewports, and frontend state source.ProInteraction · 0ProCommand Palette Keyboard Flow
Define grouping, shortcuts, keyboard navigation, empty states, permissions, and mobile fallbacks for command palettes, quick-action menus, global search, and resource jumpers.
Inputs must include command sources, target users, command scale, global-search scope, executable vs navigational command distinction, permission model, shortcuts, mobile entry, and cmdk/shadcn usage.ProInteraction · 0ProMulti-Step Wizard Save and Resume
Design step indicators, draft saving, cross-step validation, review pages, resume entry, and submission confirmation for applications, onboarding, setup wizards, and import flows.
Inputs must include flow purpose, step list, linearity, fields/tasks per step, saveable content, identity/login requirements, timeout rules, cross-step dependencies, final-submit risk, and target devices.ProInteraction · 0ProNotification Inbox Triage
Define severity, persistence, actions, announcements, and archiving for toast, inline notification, banner, modal, notification center, and alert inbox systems.
Inputs must include message source, severity, task-blocking status, user-action need, auto-dismiss policy, history need, permission scope, frequency, and target devices.Pro