Experience Design

Plugin experience-design from marketplace agent-ready-repo in eugenelim/agent-ready-repo. Commands read from the repo's manifest — today.

Skills (13)

• content-design

  Use when someone asks what a surface should communicate or how its copy should feel before final words are written, or when a team needs a cross-surface brand register. Runs in three modes: message and narrative structure for a content brief; per-surface acquisition copy goals for a copy-direction r

• creative-direction

  Use when someone says a digital surface should feel premium, calm, playful, or otherwise has a vibe but no shared visual direction. Also use when refining or amending an existing direction, or when inheriting it into a new section, component, or feature. Produces ranked aesthetic goals and, when due

• design-principles

  Use when a design team asks for durable rules that turn journey evidence and opportunity pains into consistent decisions across sprints. Produces 3–5 named design principles, each with rationale and an arbitration test. Use `creative-direction` for visual goals, `design-system` for token taxonomy, a

• design-review

  Use when someone asks to critique an existing rendered screen, flow, or mockup for usability, quality-floor, clarity, and aesthetic-fit problems. Produces a severity-rated findings list grounded in the actual artifact. Use `creative-direction` to name a new visual direction, `information-architectur

• design-system

  Use when an approved aesthetic direction or an existing product system exists and someone asks what the design system should actually be — the typography, color, spacing, shape, depth and motion decisions a build can implement. Produces a project-specific system: relationships plus the concrete valu

• experience-status

  Use when someone asks where the current experience-design thread stands, which design artifacts exist, what is missing, or which design skill comes next. Reads the configured design output and returns a read-only orientation; it never writes files or performs the missing design work. Product or port

• information-architecture

  Use when someone asks what goes where on a screen or flow, in what order, or how a genre-specific surface helps people understand, navigate, decide, or act. Produces IA and layout specs for general screens and flows plus analytical dashboards/reports/monitoring; conversion landing, home, pricing, an

• interaction-design

  Use when someone asks how one screen or component should respond to actions, validate input, transition, recover, or feel in use. Produces behavioral and state specifications for the interaction. Use `information-architecture` for hierarchy, `user-flow` for cross-screen routes, and `creative-directi

• journey-mapping

  Use when a team asks what an end user goes through across an experience, from one meaningful outcome to the next. Produces a customer journey map of stages, actions, touchpoints, emotions, pains, and opportunities, adjusted for the relevant platform. Use `service-blueprint` for backing services, `us

• process-mapping

  Use when a team asks how an internal business operation works today or should work tomorrow across actors and handoffs. Produces a SIPOC scope, swimlane map, as-is/to-be flow, and pain-and-waste register. Use `journey-mapping` for the customer's experience, `service-blueprint` to connect a journey t

• service-blueprint

  Use when someone asks what people, services, and systems support each step of an existing customer journey. Produces a service blueprint across evidence of service, frontstage, line of visibility, backstage, and support. Use `journey-mapping` to discover the customer path first, `user-flow` for scre

• user-flow

  Use when an approved customer journey needs to become screens, transitions, failure paths, and navigation routes. Produces a complete screen sequence plus one self-contained brief per screen and a whole-flow walk-through. Use `journey-mapping` to understand the journey first, `interaction-design` fo

• ux-writing

  Use when shaping the actual words a user reads in a product's UI — characterizing the UI copy voice (how the brand register applies to UI states), writing recurring UI-state microcopy (error, empty, button, label), or reviewing copy before it ships. Triggers on "what should this error say", "write t

Subagents (1)

• experience-reviewer

  Design-time / experience ONLY — a forked-context, read-only reviewer for design artifacts: a customer journey, a screen flow + its per-screen briefs, an aesthetic direction, or a generated screen. Reviews against: grounded aesthetic fit, platform fit, cross-brief coherence, quality floor (handle-all

Hooks (1)

• SessionStart

  python3 "${CLAUDE_PLUGIN_ROOT}/.claude-plugin/scripts/install-marker.py" --install-route claude-plugins

Similar plugins