improve-app

Orchestrate a nine-phase product improvement journey with persistent documentation tracking.

Updated Jul 31, 2026
One-click install
npx skills add https://github.com/fsolla/teqo --skill improve-app
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: improve-app
Source: https://github.com/fsolla/teqo/tree/main/.agents/skills/improve-app
Command: npx skills add https://github.com/fsolla/teqo --skill improve-app

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill addresses the gap between a functional, shipped application and a truly refined user experience by systematically identifying and removing friction, clarifying messaging, and optimizing performance.

Core Features & Use Cases

  • Evidence-Based UX Audits: Uses a nine-phase framework to audit everything from core job-to-be-done alignment to micro-interactions and performance.
  • Resumable Journey Tracking: Maintains state across sessions using a dedicated documentation folder, ensuring continuity in complex product improvement projects.
  • Use Case: Use this when your app works but feels clunky, users are dropping off at key conversion points, or the interface feels amateur and confusing.

Quick Start

Invoke the improve-app skill to begin an audit of your current application and generate a project improvement plan.

Frequently Asked Questions about improve-app

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I conduct a UX audit for a shipped application to improve conversion rates?

To conduct a UX audit for a shipped application, you need a multi-phase framework evaluating core job-to-be-done alignment, micro-interactions, and performance to systematically identify friction and optimize conversion honesty.

What is the best way to track progress on a complex product improvement project across sessions?

The best way to track product improvement progress is maintaining persistent documentation in a dedicated docs folder, recording phase status, key decisions, and experiment backlogs to ensure continuous journey tracking.

When do I need a systematic product design optimization process for my app?

You need a systematic product design optimization process when your app functions but feels clunky, users drop off at key conversion points, or the interface feels amateur and confusing.

Does this UX heuristic evaluation method require external dependencies or specific frameworks?

This UX heuristic evaluation method requires no external dependencies, relying solely on a persistent docs folder to track the nine-phase framework status, decisions, and experiment backlogs.

How do I fix confusing messaging and micro-interactions in my current product?

To fix confusing messaging and micro-interactions, apply a systematic product improvement journey that refines interface clarity, removes friction, and polishes micro-interactions based on evidence-based UX audits.

What are the limitations of using a nine-phase framework for application optimization?

A limitation of using a nine-phase framework for application optimization is the overhead of maintaining persistent documentation in a docs folder, which is required to track phase status and experiment backlogs.