npx claudepluginhub nwave-ai/nwave --plugin nwThis skill uses the workspace's default tool permissions.
```
Guides user journey discovery through phased questions on goals, mental models, emotions, artifacts, errors, and integrations. Generates iterative draft sketches for validation.
Designs end-to-end user-facing experiences: task flows, workflows, navigation, onboarding, settings, search, collaboration, checkout, dashboards, notifications, error recovery. Handles cross-platform adaptation, accessibility, interaction specs.
Designs user flows and screen structures using StyleSeed UX patterns like progressive disclosure, hub-and-spoke navigation, and information pyramids. For onboarding, checkout, dashboards, and multi-screen features.
Share bugs, ideas, or general feedback.
PHASE 1 PHASE 2 PHASE 3 PHASE 4
Journey Mapping Emotional Design TUI Prototyping Integration Check
| | | |
v v v v
"What's the flow?" "How should it feel?" "What does it look?" "Does it connect?"
journey:
name: "{Goal Name}"
goal: "{What user is trying to accomplish}"
persona: "{User persona reference}"
emotional_arc:
start: "{Initial emotional state}"
middle: "{Journey emotional state}"
end: "{Final emotional state}"
steps:
- id: 1
name: "{Step Name}"
command: "{CLI command or action}"
tui_mockup: |
+-- Step N: {Name} -----------------------------------------+
| {ASCII representation of CLI output} |
| ${variable} <-- tracked artifact |
+------------------------------------------------------------+
shared_artifacts:
- name: "{artifact_name}"
source: "{single source of truth file}"
displayed_as: "${variable}"
consumers: ["{list of places this appears}"]
emotional_state:
entry: "{How user feels entering step}"
exit: "{How user feels after step}"
integration_checkpoint: |
{What must be validated before proceeding}
gherkin: |
Scenario: {Step description}
Given {precondition}
When {action}
Then {observable outcome}
And shared artifact "${variable}" matches source
integration_validation:
shared_artifact_consistency:
- artifact: "{name}"
must_match_across: [1, 2, 3]
failure_message: "{Integration error description}"
Start: Anxious/Uncertain | Middle: Focused/Engaged | End: Confident/Satisfied Use when: Complex multi-step operations
Start: Curious | Middle: Exploring | End: Delighted Use when: Learning new features
Start: Frustrated | Middle: Hopeful | End: Relieved Use when: Fixing issues or debugging
tool [noun] [verb] or tool [verb] [noun]crafter agent create or crafter create agentResponsive: print something in <100ms | Progress: show for long operations | Transparent: show what is happening | Recoverable: clear errors with suggested fixes
Implement --help on every command | Make help discoverable | Provide contextual suggestions
Three artifact types produced:
journey-{name}-visual.md): ASCII flow diagram with emotional annotations and TUI mockups per stepjourney-{name}.yaml): Machine-readable journey definition following schema abovejourney-{name}.feature): Testable acceptance scenarios from each journey stepAll artifacts go to docs/feature/{feature-id}/discuss/.