Set up with your coding agent

Open your coding agent in your app's repo and paste this prompt. It walks the agent through the CLI, your Featurama project and the SDK, wired into the navigation your app already has. You approve the purchase and hand over your agent token privately.

Setup prompt

You are my coding agent. Set up Featurama in my EXISTING mobile app, end to end. Inspect its framework, package manager, navigation and existing configuration first. Make the smallest appropriate changes; do not create a new app.

Official guides: https://featurama.app/docs/cli-agent-setup and https://featurama.app/docs/sdk-setup. Use the hosted API origin https://newapi.featurama.app (NOT the dashboard URL or the legacy api.featurama.app). A project key must come from that same origin.

1. If I have not done so, ask me to create/sign in to my account at https://featurama.app/register, verify my email and complete the lifetime checkout. Do not make a purchase on my behalf without explicit approval. I can create an agent token in https://featurama.app/settings. Arrange a private stdin/secret-manager handoff for that token; never request it in chat, print it, put it in shell arguments or commit it. If you cannot receive it safely, give me the CLI login command to run myself.
2. With Node.js 22+, use the SCOPED CLI, not the unrelated unscoped npx featurama package:
   npx -y @vibelabsdotto/featurama-cli@0.1.4 --help
   npx -y @vibelabsdotto/featurama-cli@0.1.4 context list
   npx -y @vibelabsdotto/featurama-cli@0.1.4 context add hosted --instance https://newapi.featurama.app --use
   npx -y @vibelabsdotto/featurama-cli@0.1.4 login --token-stdin
   npx -y @vibelabsdotto/featurama-cli@0.1.4 context verify hosted
   npx -y @vibelabsdotto/featurama-cli@0.1.4 projects list
   Reuse an existing context for that origin instead of adding a duplicate. Feed login through a private stdin stream, not an interactive prompt or command argument. Stop on authentication errors; do not try a token against another origin.
3. Reuse my existing Featurama project for this app if there is one. Otherwise, after confirming my lifetime access and asking for the app name, create it with projects create --name "<app name>" --technology expo (or reactNative for bare React Native). The create response contains the full project API key ONCE. Capture it privately; never paste it into chat/logs. An existing project's full key cannot be retrieved: do not rotate it without my approval. The agent token is for the CLI/MCP only and must NEVER ship in the app.
4. For React Native / Expo, install @vibelabsdotto/featurama-rn-expo and its documented peer dependencies using this app's package manager, then wire FeaturamaProvider and FeatureRequestsScreen into the existing navigation. Configure baseUrl: 'https://newapi.featurama.app' and the matching project API key using the app's configuration. Expo EXPO_PUBLIC_ values are bundled into the app, not secret storage; only put the project-scoped key there, never the agent token. For Swift, Flutter, Android or .NET MAUI, first read the SDK guide: these are source previews, not published packages. Do not invent an install command or claim release availability.
5. Run the app's existing checks and exercise the feedback screen if the environment allows it. Verify that the SDK uses the same API origin as the key. Report the changed files, real verification results and any manual steps or blockers. Do not deploy or rotate credentials without my approval.

The agent follows the same steps as these guides, if you want to check its work or do a step by hand: