Agent skill · wondelai
improve-app
Guided journey from a shipped app that works but feels rough to a product that fits the job, flows without friction, reads clearly, and persuades honestly. Orchestrates nine skills phase by phase - jobs-to-be-done, ux-heuristics, design-everyday-things, refactoring-ui, microinteractions, made-to-stick, influence-psychology, high-perf-browser, steve-jobs-design-review - asking the user questions at every decision point and recording results in the project docs/ folder (CUSTOMER.md, DESIGN.md, POSITIONING.md, IMPROVE-APP-PLAN.md) so the journey resumes across sessions. Use when the user wants to fix a clunky product, cut UX friction, sharpen in-app copy, or says ''the app works but feels rough''. Not for code, tests, or hardening - use improve-code-quality (fresh prototype) or remove-technical-debt (aged); no app yet, create-app; needs growth loops, grow-app; marketing-site friction, improve-website; one leaking flow, conversion-optimization. For one framework in isolation, invoke that skill directly.
What it needs
About 12k tokens when loaded.
What this skill does
Improve an App The app already ships and works — users, screens, a real flow — but the experience feels rough where it should feel effortless. Across nine phases this journey fixes what users feel, in evidence order: re-anchor on the job, remove friction, polish the look and the moments, sharpen the words, persuade honestly, and end with a review brutal enough to cut. It is interactive (the agent asks before deciding) and resumable (state lives in docs/). Code-level causes route out to the code journeys — this pass fixes the product experience. Core Principle Fix what users feel, in evidence order: re-anchor on the job the app is hired for, remove friction before polish, sharpen the words, persuade honestly, and end with a review brutal enough to cut. A prettier screen on a confusing flow loses users at the same rate — the order of the phases is the whole game. This skill sequences the phases, asks the decision questions, and records what you decide. The nine constituent skills carry the method — invoke them rather than improvising their frameworks. Journey Map Phase Skill Question it answers Artifact --- --- --- --- 1 jobs-to-be-done What job is the app hired for, and where does it underdeliver? Extends docs/CUSTOMER.md — GATE 2 ux-heuristics Where does the interface make users stop and think? Extends docs/DESIGN.md, docs/EXPERIMENTS.md 3 design-everyday-things Where do users act wrong because the design misled them? Extends docs/DESIGN.md, docs/EXPERIMENTS.md 4 refactoring-ui Does the app look as clear as it works? Extends docs/DESIGN.md, docs/EXPERIMENTS.md 5 microinteractions Does every action feel alive, or dead? Extends docs/DESIGN.md, docs/EXPERIMENTS.md 6 made-to-stick Do the in-app words land, or read as jargon? Extends docs/POSITIONING.md, docs/EXPERIMENTS.md 7 influence-psychology Do the paywall and upgrade moments persuade honestly? Extends docs/POSITIONING.md, docs/EXPERIMENTS.md 8 high-perf-browser Does the app feel fast where users touch it? Extends d …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills wondelai/improve-app--402029