AI Agent Skills Included with Instamobile React Native Apps

Instamobile React Native app packages include local AI agent skills that help your coding assistant understand the app, set it up, customize it, test it, and prepare it for release.

The skills live inside each downloaded app package under:

.agents/skills/

They are designed to work with AI coding agents that can read local project files, including Codex, Claude Code, Cursor, Windsurf, and similar tools.

How To Use Them

Open the downloaded app folder in your AI coding environment. Then ask the agent to use the skill that matches the task.

Examples:

• "Use dopebase-local-setup to run this app locally."
• "Use dopebase-firebase-setup to replace the demo Firebase project."
• "Use dopebase-theme-branding to rebrand the app with my logo and colors."
• "Use dopebase-security-rules to review Firestore and Storage access."
• "Use dopebase-store-release to prepare the Android and iOS store builds."

If your agent needs an explicit skill path, tell it to read:

.agents/skills/<skill-name>/SKILL.md

Then describe the task you want it to complete.

Included Skills

Skill name	Use it for	What it helps with
dopebase-app-orientation	First pass through the app package.	Locating src/, src/core, native folders, Firebase folders, safe edit points, and the commands to run before changing code.
dopebase-local-setup	Getting the app running locally.	Installing dependencies, starting Metro, running iOS and Android, fixing CocoaPods, Gradle, Android Studio, Xcode, simulator, and device startup issues.
dopebase-firebase-setup	Moving from demo Firebase credentials to your Firebase project.	Replacing google-services.json and GoogleService-Info.plist, enabling Auth providers, deploying rules and Functions, seeding data, and validating register/login/media flows.
dopebase-env-config	Managing app configuration and keys.	Auditing API keys, bundle identifiers, package names, Firebase config files, staging values, production values, local secrets, and native rebuild requirements.
dopebase-data-model	Understanding or changing app data.	Tracing list/detail screens, Firestore collections, document fields, seed data, CRUD flows, filters, search, backend schemas, indexes, and permission behavior.
dopebase-auth-social-login	Configuring authentication and account flows.	Email/password login, registration, logout, password reset, Apple Sign In, Google Sign-In, Facebook Login, OAuth clients, deep links, redirects, and account deletion.
dopebase-security-rules	Reviewing backend access before production.	Firestore rules, Storage rules, ownership checks, media upload limits, App Check, rate limits, cost controls, public data exposure, and role-based access.
dopebase-theme-branding	Rebranding the app for your product.	App name, icon, splash screen, colors, logo, fonts, onboarding, empty states, store screenshots, support links, privacy links, and layout checks after copy changes.
dopebase-smoke-test-debug	Testing the app before delivery or release.	Fresh install launch, login, navigation, list/detail screens, create/edit flows, media upload, logout, screenshots, native logs, crash triage, and release-readiness checks.
dopebase-store-release	Preparing App Store and Google Play builds.	Android AAB, iOS archive, signing, version bumps, upload keystores, TestFlight, Play testing, permissions, Data Safety, privacy policy, screenshots, and release metadata.

Recommended Workflow After Download

1. Open the app package in your AI coding environment.
2. Start with dopebase-app-orientation so the agent understands the project structure before editing.
3. Run dopebase-local-setup to install dependencies and launch the app.
4. Use dopebase-firebase-setup and dopebase-env-config to connect your own backend and app identifiers.
5. Use dopebase-theme-branding to customize the product for your brand.
6. Use dopebase-data-model, dopebase-auth-social-login, and dopebase-security-rules when changing backend behavior or user flows.
7. Run dopebase-smoke-test-debug before sharing the app with testers.
8. Use dopebase-store-release when preparing App Store or Google Play builds.

Example Prompts

Use these prompts from the app root:

Use dopebase-app-orientation and explain the safest places to customize this app.

Use dopebase-firebase-setup. I created a new Firebase project and want this app
to use it for Auth, Firestore, Storage, and Functions.

Use dopebase-theme-branding. Replace the default branding with my app name,
primary color, logo, icon, and splash screen.

Use dopebase-smoke-test-debug. Run through the app like a tester and list any
release-blocking issues.

Use dopebase-store-release. Prepare the Android AAB and iOS TestFlight checklist
for this app.

Working With Any AI Agent

The skills are plain markdown workflows that work across different AI coding tools. A good agent should be able to:

• read the matching SKILL.md;
• inspect the app files before editing;
• make focused code or config changes;
• run local commands when needed;
• report what changed and what still needs your credentials or account access.

This keeps the workflow close to the app package. The agent sees the actual source files, native configuration, Firebase files, README, and release checklists while it works.

Related Docs

• React Native App File Structure
• React Native App Dependencies
• React Native App Setup Guides
• Firebase Production Checklist
• React Native App Release Checklist