# Choose a starter kit once: the six checks that prevent a full rewrite later

Most rewrites do not start with bad code. They start with a starter kit that answered the wrong question. The kit demoed beautifully, the screens looked finished, and three months later the team discovers the navigation model fights deep linking, the auth layer cannot hold a refresh token, or the state layer collapses the moment offline support arrives. At that point nobody rewrites one file. They rewrite the app.

This post gives you a decision procedure for picking a starter kit you will still be happy with at version three. It is written for builders turning an AI-generated prototype into a shippable product, and every check below maps to a rewrite trigger seen in real production apps.

---

*This is an excerpt. Read the full post at [otf-kit.dev/blog/choose-starter-kit-without-rewrite](https://otf-kit.dev/blog/choose-starter-kit-without-rewrite) — full-stack kits your AI coding agent can actually ship to production. [Browse the kits →](https://otf-kit.dev)*