Provide a professional design critique of this UI in Markdown: # Design Critique ## Score: X/10 ## Executive Summary [2-3 sentence overview of the design's effectiveness] ## What's Working Well ✓ - [Specific strength with example from the design] - [Another strength] - [Keep doing this] ## Critical Issues ✗ ### 1. [Issue Name] - Priority: High/Medium/Low **Problem:** [Describe what's wrong] **Impact:** [Why this matters for users] **Fix:** [Specific actionable solution]…
Design Critique
Get a structured, scored critique of any UI — strengths, critical issues, an accessibility audit, and a fix checklist.
· You bring UI screenshot· critique.md· checklist.md
A real run, unedited2 generations · $0.36 of walletBrand and inputs are fictional, made in Vmotif · 2026-09-24
Straight off the canvas.
Everything below is what this run returned, untouched.
- Design Critiquemarkdown
# Design Critique ## Score: 8/10 ## Executive Summary Fernway is a calm, cohesive trail-discovery dashboard with a strong brand voice, a clear three-column layout, and well-chosen earthy colors that fit the "quiet trails" promise. The main weaknesses are **redundancy and competing CTAs**. A repeated orange "Send to watch" button appears four times, and tags duplicate the active filters. There are also some **low-contrast secondary text and tags**, and a detail panel that mixes route data with unrelated personal stats. ## What's Working Well ✓ - **Strong brand-to-content alignment:** The fern logo, muted greens, and the headline *"Quiet trails near you / Scenic routes. Fewer crowds. A calmer run."* create an immediately understandable, emotionally consistent product. - **Map thumbnails as primary content:** Each card leads with a topographic map, a bold orange route line, and a scale bar. This lets runners compare route shape and terrain at a glance. - **Consistent card anatomy:** Title → location → key stats (distance, climb) → tags → description → actions. The pattern is identical across all three cards, which makes scanning effortless. - **Clear active filter state:** "Under 10 km" uses an orange outline and tint that distinguishes it from inactive chips. "Clear all" is also easy to find. - **Useful elevation profile:** The chart has labeled axes, a soft filled area, and a Min / Max / Total climb summary. It gives meaningful detail without overwhelming the user. - **Restrained color usage:** Orange is reserved for route lines, the active nav item, the active filter, and CTAs, so the palette stays disciplined. - Action Checklistmarkdown
# UI Improvement Checklist — Fernway "Quiet trails near you" ## Before You Start - [ ] Take a full-page screenshot of the current state at 1792×1008 and at 1440px width for comparison - [ ] Review with stakeholders which issues to prioritize. Flag these open questions: - Should selecting a card update the right-hand detail panel? - Should the "Your weekly mileage" widget stay on the Routes page? - [ ] Export the current color tokens (orange CTA, green chip, beige chip, gray chip, body gray) so contrast can be measured against exact hex values --- ## High Priority (Fix First) ### Layout & Structure
One stage, all at once.
What each stage reads, what it makes and what it cost on this run. Steps inside a stage don’t wait on each other, so they run side by side.
- 01
Design Critique & Action Checklist
Reads your inputsMakes 2 files
Or let your agent run it.
This run went through the Vmotif MCP server, the way Claude Code, Cursor or any MCP client drives it: seed the canvas, fill the inputs, run the graph.
create_canvas({ premade_workflow_id: "design-critique" })
update_canvas({ canvas_id, updates: [/* your inputs */] })
run_workflow({ workflow_id: canvas_id })MCP docs Get a point of view before you build — synthesized direction from references, or honest feedback on what exists.

