ui-ux-workflowlisted

Docs-only conceptual UI/UX workflow for one bounded experience, surface, or journey. Use to produce an assessment, low-fi wireframe, mid-fi direction, user/data/operation flows, state transitions, a reusable downstream prompt, and a thin read-only preview handoff. Do not use for implementation-ready component contracts, code generation, browser-backed audit evidence, or a full interactive prototype.
bohewu/agents_pipeline · ★ 1 · Web & Frontend · score 77

Install: claude install-skill bohewu/agents_pipeline

# UI/UX Workflow Produce an approval-oriented concept for one bounded experience. Keep the output useful for review without drifting into engineering specifications or implementation. Read the durable protocol when exact bundle mapping, schema pairing, or the full template catalog is needed: `../../protocols/UI_UX_WORKFLOW.md`. For communication-first diagnosis or microcopy, pair with `../ui-communication-designer/SKILL.md`. For implementation after approval, use `../frontend-aesthetic-director/SKILL.md`. For browser evidence and scoring, use `$run-ux` with suitable browser tooling. ## Boundary This skill may produce: - a scoped assessment - low-fi structure - mid-fi visual and content direction - user, data, and operation flows - conceptual state transitions - a provider-neutral prompt export - a thin, external or read-only preview handoff Redirect implementation-ready layouts, component/API contracts, acceptance criteria, framework output, editable prototypes, live integrations, and final branded visual design to a later workflow. ## Choose the Output Depth Use a compact concept when the user asks one bounded question, such as choosing a layout, clarifying a state, or sketching a short flow. Include only the sections necessary to decide that question and state the next handoff. Use the durable v1 bundle when the user asks for a complete conceptual handoff, a versioned artifact, or all flows/states. In that case use these exact headings in order: 1. `Project UI/UX