@build-launch/expo-push-skill
v1.0.3
Published
Installer for the Expo Push Notifications guide skill across different AI agents
Maintainers
Readme
@build-launch/expo-push-skill
A CLI tool to install Skills that guides AI agents and developers to configure Expo Push Notifications (iOS/Android) with best practices.
AI agents are extremely powerful at writing code, but setting up mobile push notifications involves external consoles (Firebase, Expo dashboard).
This skill teaches your AI agent the correct, secure workflow for configuring push notifications in your project and also guide you through the setup process.
🚀 Quick Start
Run the installer via npx in the root of your Expo project:
npx @build-launch/expo-push-skill⚙️ How It Works
When you run the command, it prompts you for:
- AI Agent / Development Tool: Choose your preferred agent (e.g., Antigravity, Claude Code, Cursor, Windsurf, Cline/Roo Code, or Custom Copilot instructions).
- Installation Scope:
- Local: Install directly in your current project (e.g.,
.agents/skills/or project-level rules). - Global: Install in your home directory config (e.g.,
~/.gemini/config/or~/.clauderules) so it applies across all your projects.
- Local: Install directly in your current project (e.g.,
The CLI then copies the optimized, step-by-step setup guide to the appropriate rules/skills folder.
🧭 Setup Guide Sequence
Once installed, your AI agent will guide you through the following setup steps in the correct order:
- Dependency Installation: Installing
expo-notificationsandexpo-device. - Expo Credentials & Firebase FCM V1 Key Link: Generating the service account key and linking it on the Expo dashboard.
- Firebase Project and Android App Registration: Registering the package name on the Firebase Console and downloading
google-services.json. - Configure EAS Environment Variables: Setting up the
google-services.jsonfile as a secret environment variable on Expo Dev. - Convert Configuration: Safe conversion of
app.jsonto a dynamicapp.config.ts. - Update Configuration: Referencing the Google services file dynamically using the secret environment variable.
- Update
.gitignore: Appending credentials to.gitignoreto prevent secret leakage. - Testing/Verification: A step-by-step verification process using the Expo Notification Tool.
📄 License
MIT
