nw-design-methodology

Featured

Apple LeanUX++ design workflow, journey schema, emotional arc patterns, and CLI UX patterns. Load when transitioning from discovery to visualization or when designing journey artifacts.

Web & Frontend 636 stars 68 forks Updated today MIT

Install

View on GitHub

Quality Score: 95/100

Stars 20%
93
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# Design Methodology (Apple LeanUX++) ## Design Workflow ``` 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?" ``` ### Phase 1: Journey Mapping (1-2 days) - Techniques: User journey mapping | goal-completion flow | step identification - Question: "What complete journey is the user trying to accomplish?" - Output: Journey map with steps, commands, and touchpoints ### Phase 2: Emotional Design (1 day) - Techniques: Emotional arc design | form follows feeling | transition analysis - Question: "How should the user FEEL at each step?" - Output: Emotional annotations on journey map ### Phase 3: TUI Prototyping (1-3 days) - Techniques: Progressive fidelity | ASCII mockups | TUI design patterns - Question: "What does each step look like?" - Output: TUI mockups for each journey step ### Phase 4: Integration Check (1 day) - Techniques: Shared artifact tracking | horizontal coherence | CLI vocabulary - Question: "Do all pieces connect properly?" - Output: Validated journey with integration checkpoints ## Journey Schema ```yaml schema_version: 1 journey: name: "{Goal Name}" goal: "{What user is trying to accomplish}" persona: "{User persona reference...

Details

Author
nWave-ai
Repository
nWave-ai/nWave
Created
9 months ago
Last Updated
today
Language
Python
License
MIT

Similar Skills

Semantically similar based on skill content — not just same category

Web & Frontend Listed

apple-design

Design rules for any user interface Claude creates or reviews (website, landing page, web or mobile app, dashboard, admin panel, component, artifact, prototype, game menu), translated from Apple's WWDC talks for the web - instant feedback, interruptible spring motion, gestures, materials and depth, typography, reduced motion, and the eight design principles (purpose, agency, familiarity, simplicity, craft). Use before writing any UI code, CSS, animation or layout, and when reviewing or polishing an interface, even if the request does not mention design.

1 Updated 5 days ago
titouannwtt
AI & Automation Featured

nw-discovery-methodology

Question-first approach to understanding user journeys. Load when starting a new journey design or when the discovery phase needs deepening.

636 Updated today
nWave-ai
Web & Frontend Featured

design-code-architecture

Guided journey from an app idea to a deliberate architecture: boundaries, domain model, data decisions, and resilience, making only the expensive-to-reverse decisions and deferring the rest. Orchestrates eight skills phase by phase - clean-architecture, domain-driven-design, system-design, ddia-systems, software-design-philosophy, release-it, pragmatic-programmer, 37signals-way - asking the user questions at every decision point and recording results in the project docs/ folder (ARCHITECTURE.md, DESIGN-CODE-ARCHITECTURE-PLAN.md) so the journey resumes across sessions. Use when the user wants to design a new app's architecture, choose boundaries and a domain model, decide monolith versus microservices, or says 'how should I structure this app'. If a codebase already exists, use remove-technical-debt (aged), improve-code-quality (fresh prototype), or architecture-optimization (slow but working); if unvalidated, run create-business or create-app first. For one framework in isolation, invoke that skill directly.

2,727 Updated 5 days ago
wondelai