React Native
React Native is one of two mobile starters Tharas can create from nothing. Ask for a mobile app and this is what it reaches for by default.
From an idea to a running project#
Describe a mobile app and Tharas names the project, picks the stack, scaffolds a real starter, initialises the repository and registers it — then builds what you asked for against it.
Naming React Native explicitly answers the platform question, so the planner does not have to guess between mobile and web.
How a mobile project is verified#
A mobile app has no HTTP surface to probe, so the smoke stage that starts a service and requests its routes does not apply. The install and build steps are the whole gate, and they have to pass.
That is worth knowing rather than glossing over: verification on mobile is genuinely weaker than on a web service, because there is less to prove automatically.
Everything else still applies#
- Isolation
- Every task builds in its own branch and worktree, scope-checked, never in your checkout.
- Approval gates
- A specification first, and a ship gate that will not open a pull request without evidence.
- Self-healing
- A blocked task is diagnosed, researched and repaired before you are asked.
- Memory
- What Tharas learns about your app is indexed locally and queried by the next run.
Common questions
Can Tharas work in an existing React Native repository?
Yes. Scaffolding is for starting from nothing; adding an existing repository and indexing it is the normal path.
What about native Swift or Kotlin?
Tharas has no native Swift or Kotlin starter. Asking for one routes to a React Native scaffold, which is worth knowing before you start.