ux-flows

Included with Lifetime

$97 forever

Use when writing UX flow docs for a design team, cleaning up meeting notes into user journeys, or when someone asks for user-facing flow documentation. Triggers on "UX flows", "user flows", "design handoff", "clean up these flows", or preparing specs for a UI/UX team.

Design

What this skill does

# UX Flows

Turn meeting notes and technical specs into clean UX flow docs for design teams.

## Process

1. **Identify the audience** — these docs are for UI/UX designers. They need to know what the user does and what states matter. They do NOT need database fields, implementation details, or layout prescriptions.

2. **Strip implementation details** — remove all references to: table names, column names, status enums, API calls, database behavior, FK relationships, record creation logic. Translate technical states into user-facing language.

3. **Strip layout prescriptions** — remove references to: "left panel", "sidebar", "footer buttons", "split layout", "modal vs page". The design team decides how to arrange screens. Describe what happens, not where things go.

4. **Keep edge cases and states** — the design team DOES need to know: what states exist, what warnings to surface, what happens when things go wrong, what's optional vs required. Describe these in user terms.

5. **Ask clarifying questions** — challenge assumptions in the source material. Common issues: coupling scheduling with readiness, requiring fields that should be optional, prescribing flows that should be flexible.

## Output

Write to `docs/plans/YYYY-MM-DD-<topic>-ux-flows.md`. Target ~1 page. Structure as numbered flows with entry points, user actions, and key states.

## Principles

- **Describe what, not how** — "user sets a target date" not "date picker component with timezone selector"
- **Decouple orthogonal concerns** — if two things are independent (e.g. scheduling and readiness), present them as independent indicators, not a combined state
- **Everything optional by default** — question any flow that forces the user through steps. Can they skip? Come back later? Do things in any order?
- **States in user language** — "Needs attention" not `status = invalid`. "3/5 channels ready" not `posts.where(status: 'ready').count`
- **Edge cases as bullets, not flows** — disconnecting with scheduled posts, deleted assets, partial failures — describe the user impact in a sentence, don't diagram the backend cascade

Files: 1

Size: 2.4 KB

Complexity: 7/100

Category: Design

Source: https://github.com/franchiseai/claude-code-plugins/tree/main/plugins/ux-flows/skills/ux-flows

Related in Design

contribute

Included

Local-only OSS contribution command center. Auto-refreshes the user's in-flight PR and issue state on invoke so conversations start with full context — no need to brief Claude on what's in flight. Helps the user find issues to contribute to on GitHub, builds per-repo dossiers of what each upstream expects (CLA, DCO, branch convention, AI policy, draft-first, review bots, issue templates), runs deterministic gates before any external action so AI-assisted contributions don't reach maintainers as slop. State is markdown-only: candidate files at ~/.contribute-system/candidates/, repo dossiers at ~/.contribute-system/research/, append-only event log at ~/.contribute-system/log.jsonl. No database, no cloud calls. Use when the user asks about their PRs / issues / contributions, wants to find new work to take on, claim an issue, build/refresh a repo's dossier, or draft a Design Issue or PR. Trigger with "/contribute", "what's my PR status", "find a contribution", "claim issue X", "draft a Design Issue for Y", "refresh dossier for Z".

Designscripts

architectural-analysis

Included

User-triggered deep architectural analysis of a codebase or scoped subtree across eight modes — information architecture, data flow, integration points, UI surfaces, interaction patterns, data model, control flow, and failure modes. This skill should be used when the user asks to "diagram this codebase," "map the architecture," "show the data flow," "give me an ERD," "trace control flow," "find the integration points," "verify the layout pattern," "audit the UX architecture," or any similar request whose primary deliverable is mermaid diagrams plus cited reports under docs/architecture/. Dispatches haiku/sonnet sub-agents in parallel for per-mode exploration, then verifies every citation mechanically before any node lands in a diagram. Not for one-off prose explanations of code (use code-explanation) or for high-level system design from scratch (use system-design).

Designscripts

mcp

Included

Model Context Protocol (MCP) server development and tool management. Languages: Python, TypeScript. Capabilities: build MCP servers, integrate external APIs, discover/execute MCP tools, manage multi-server configs, design agent-centric tools. Actions: create, build, integrate, discover, execute, configure MCP servers/tools. Keywords: MCP, Model Context Protocol, MCP server, MCP tool, stdio transport, SSE transport, tool discovery, resource provider, prompt template, external API integration, Gemini CLI MCP, Claude MCP, agent tools, tool execution, server config. Use when: building MCP servers, integrating external APIs as MCP tools, discovering available MCP tools, executing MCP capabilities, configuring multi-server setups, designing tools for AI agents.

Designscripts

react-native-skia

Included

Design, build, debug, and optimise high-polish animated graphics in React Native or Expo using @shopify/react-native-skia, Reanimated, and Gesture Handler. Use when the user wants canvas-driven UI, shaders, paths, rich text, image filters, sprite fields, Skottie, video frames, snapshots, web CanvasKit setup, or performance tuning for custom motion-heavy elements such as loaders, hero art, cards, charts, progress indicators, particle systems, or gesture-driven surfaces. Also use when the user asks for fluid, glow, glass, blob, parallax, 60fps/120fps, or GPU-friendly animated effects in React Native, even if they do not explicitly say "Skia". Do not use for ordinary form/layout work with standard views.

Designscripts

plaid

Included

Product Led AI Development — guides founders from idea to launched product. Six capabilities: Idea (discover a product idea), Validate (pressure-test the idea against fatal flaws, problem reality, competition, and 2-week MVP feasibility), Plan (vision intake + document generation), Design (translate image references into a design.md spec), Launch (go-to-market strategy), and Build (roadmap execution). Use when someone says "PLAID", "plaid idea", "help me find an idea", "product idea", "idea from my business", "idea from my expertise", "plaid validate", "validate my idea", "pressure-test", "is this idea good", "find fatal flaws", "validate the problem", "plan a product", "define my vision", "generate a PRD", "product strategy", "plaid design", "design from image", "translate image to design", "create design.md", "extract design tokens", "plaid launch", "go-to-market", "launch plan", "GTM strategy", "launch playbook", "plaid build", "build the app", "start building", or "execute the roadmap".

Designscripts

nextjs-framer-motion-animations

Included

Adds production-safe Motion for React or Framer Motion animations to Next.js apps, including reveal, hover and tap micro-interactions, whileInView, stagger, AnimatePresence, layout and layoutId transitions, reorder, scroll-linked UI, and lightweight route-content transitions. Use when the user asks to add, refactor, or debug Motion or Framer Motion in App Router or Pages Router codebases, especially around server/client boundaries, reduced motion, LazyMotion, bundle size, hydration, or route transitions. Avoid for GSAP-style timelines, WebGL or 3D scenes, heavy scroll storytelling, or CSS-only effects unless Motion is explicitly requested.

Designscripts