app-teardown
App teardown
Run a product teardown of the app in this repo: capture every screen as it actually renders, critique each screen and flow the way a senior product designer tears down a competitor, then lay each flow out on a /design canvas with the critique beside the screens. The screenshots are the evidence — every finding points at something visible in one.
This skill never edits app code. It reads, runs, captures and reports. All output goes in docs/teardown/.
1. Understand the product
Read the README, anything in docs/ (PRD.md, DEFINE.md, DESIGN.md if present), the package manifest, and the pricing or paywall code. Pin down who it's for, the job it does for them, and how it makes money. If any of the three can't be found, ask the user once before going on — critique without the job is decoration.
Done when: docs/teardown/product.md states audience, job and business model, each sourced to a file or to the user.
2. Map every screen
Inventory screens from the code, not by clicking around: routes (Next.js app/pages, React Router, Remix, SvelteKit), screens and navigators (Expo Router, React Navigation), SwiftUI/UIKit views, plus modals, sheets, dialogs and paywalls. Group them into flows — the sequence a user walks to get one thing done (first-run onboarding, sign-up/sign-in, the core loop, create/edit, upgrade, settings/account, cancel). A screen can sit in more than one flow.
For each screen, list the states worth capturing: empty, populated, loading, error, first-run vs returning, free vs paid.
Done when: docs/teardown/screen-map.md lists every flow with its screens in order and their states, and every route or screen file in the code is either in a flow or under "Not captured" with a reason.