Agentic AI Atlasby a5c.ai
OverviewWikiGraphFor AgentsEdgesSearchWorkspace
/
GitHubDocsDiscord
iiRecord
Agentic AI Atlas · expo/skills
page:docs-reference-repos-expo-skills-researcha5c.ai
Search record views/
Record · tabs

Available views

II.Record viewspp. 1 - 1
overviewarticlejsongraph
II.
Page JSON

page:docs-reference-repos-expo-skills-research

Structured · live

expo/skills json

Inspect the normalized record payload exactly as the atlas UI reads it.

File · wiki/docs/reference-repos/expo/skills/research.mdCluster · wiki
Record JSON
{
  "id": "page:docs-reference-repos-expo-skills-research",
  "_kind": "Page",
  "_file": "wiki/docs/reference-repos/expo/skills/research.md",
  "_cluster": "wiki",
  "attributes": {
    "nodeKind": "Page",
    "sourcePath": "docs/reference-repos/expo/skills/research.md",
    "sourceKind": "repo-docs",
    "title": "expo/skills",
    "displayName": "expo/skills",
    "slug": "docs/reference-repos/expo/skills/research",
    "articlePath": "wiki/docs/reference-repos/expo/skills/research.md",
    "article": "\n# expo/skills\n\n- **GitHub**: https://github.com/expo/skills\n- **Stars**: 1,675\n- **License**: MIT\n- **Last pushed**: 2026-04-10\n- **Topics**: (none)\n- **Source**: gh-search\n\n## Description\n\nOfficial AI agent skills from the Expo team for building, deploying, and debugging Expo apps. Packaged as a Claude Code marketplace plugin with 12 skills covering the full Expo development lifecycle. Fine-tuned for Opus models per Expo's documentation.\n\n## Archetype\n\n**claude-plugin** -- Ships as a Claude Code marketplace plugin (`.claude-plugin/marketplace.json`) with 4 plugin entries (1 active `expo`, 3 deprecated aliases). Also installable via `bunx skills add`.\n\n## Structure\n\n- `.claude-plugin/marketplace.json` -- Claude Code marketplace manifest (name: `expo-plugins`)\n- `plugins/expo/skills/` -- 12 skill directories:\n  - `building-native-ui/` -- Native UI components\n  - `expo-api-routes/` -- API routes\n  - `expo-cicd-workflows/` -- CI/CD with EAS\n  - `expo-deployment/` -- App Store/Play Store/web deployment\n  - `expo-dev-client/` -- Development client setup\n  - `expo-module/` -- Native module development\n  - `expo-tailwind-setup/` -- Tailwind CSS integration\n  - `expo-ui-jetpack-compose/` -- Android Jetpack Compose UI\n  - `expo-ui-swift-ui/` -- iOS SwiftUI integration\n  - `native-data-fetching/` -- Data fetching patterns\n  - `upgrading-expo/` -- SDK version upgrades\n  - `use-dom/` -- DOM components\n- `CLAUDE.md` -- Claude Code instructions\n- `CONTRIBUTING.md` -- Contribution guidelines\n\n## Key Capabilities\n\n- Full Expo development lifecycle: build, deploy, upgrade, debug\n- Platform-specific UI: SwiftUI (iOS), Jetpack Compose (Android), DOM components (web)\n- EAS (Expo Application Services) CI/CD integration\n- Native module development patterns\n- SDK upgrade workflows\n\n---\n\n## Processes\n\n### 1. Mobile App Deployment Process\n\n- **Placement**: `specializations/mobile/` (domain-specific)\n- **Description**: Multi-step mobile app deployment workflow extracted from the `expo-deployment` and `expo-cicd-workflows` skills. Generalizable beyond Expo to any React Native or mobile deployment pipeline.\n- **Steps**:\n  1. Detect platform targets (iOS, Android, web)\n  2. Validate build configuration and signing credentials\n  3. Run pre-deployment checks (version bump, changelog, asset optimization)\n  4. Breakpoint: confirm deployment targets and release channel\n  5. Build for each platform\n  6. Run platform-specific validation (App Store guidelines, Play Store policies)\n  7. Breakpoint: review build artifacts before submission\n  8. Submit to stores / deploy to web\n  9. Monitor submission status\n  10. Verify deployment success\n- **Generalizability**: Medium. The workflow pattern (build -> validate -> submit -> monitor) is universal for mobile apps, but Expo-specific details would need abstraction.\n\n### 2. SDK/Framework Upgrade Process\n\n- **Placement**: `specializations/shared/` (cross-domain, applies to any framework upgrade)\n- **Description**: Multi-step framework upgrade workflow extracted from the `upgrading-expo` skill. The pattern of version detection -> breaking changes analysis -> incremental migration -> verification is universal.\n- **Steps**:\n  1. Detect current SDK/framework version\n  2. Identify target version and all intermediate versions\n  3. Fetch breaking changes and migration guides for each version hop\n  4. Analyze codebase for affected patterns\n  5. Breakpoint: present migration plan with estimated effort\n  6. Apply migrations incrementally (version by version)\n  7. Run tests after each version hop\n  8. Breakpoint: review test results and manual verification items\n  9. Final validation and cleanup\n\n## Plugin Ideas\n\n### 1. Mobile Deployment Plugin\n\n- **Category**: CI/CD Integration\n- **Plugin name**: `mobile-deployment`\n- **Description**: Orchestrates mobile app builds and store submissions with breakpoints for review. Wraps EAS Build, Fastlane, or native CLI tools.\n- **install.md approach**: Detect mobile build toolchain (EAS, Fastlane, Xcode, Gradle), configure signing credentials, set up store API keys\n- **Key features**:\n  - Multi-platform build orchestration (iOS + Android + web)\n  - Store submission with guideline pre-checks\n  - Build artifact review breakpoints\n  - Version management and changelog generation\n- **Integration surface**: commands (`deploy:mobile`, `deploy:build`), hooks (`pre-commit` for version validation), breakpoint rules\n\n## Skipped\n\n- Individual skill content is Expo-specific instruction text, not orchestratable\n- The Claude Code plugin marketplace format is already well-understood by babysitter\n- Native UI skills (SwiftUI, Jetpack Compose) are reference material, not processes\n\n## Library Mapping\n\n| Extractable Process | Library Status | Action | Existing Path | Target Placement |\n|-------------------|----------------|--------|---------------|------------------|\n| Mobile App Deployment Process | NEW | Multi-platform mobile deployment with store submission workflow | - | specializations/mobile/mobile-app-deployment.js |\n| SDK/Framework Upgrade Process | NEW | Universal framework upgrade with breaking changes analysis | - | specializations/shared/framework-upgrade-process.js |\n| EAS CI/CD Integration Pattern | NEW | Expo Application Services CI/CD automation patterns | - | specializations/devops-sre-platform/eas-cicd-integration.js |\n| Native Module Development Workflow | NEW | Cross-platform native module development and integration | - | specializations/mobile/native-module-development.js |\n| Platform-Specific UI Integration | NEW | SwiftUI/Jetpack Compose integration patterns for cross-platform apps | - | specializations/mobile/platform-specific-ui-integration.js |\n| Mobile Build Configuration Management | NEW | Build configuration and signing credentials management workflow | - | specializations/devops-sre-platform/mobile-build-configuration.js |\n\n## Plugin Marketplace Mapping\n\n| Plugin Idea | Marketplace Status | Action | Existing Plugin | Target Placement |\n|-------------|-------------------|--------|-----------------|------------------|\n| Mobile Deployment | NEW | Multi-platform mobile build and store submission orchestration | - | plugins/a5c/marketplace/blueprints/mobile-deployment/ |\n| Framework Upgrade Automation | NEW | SDK/framework upgrade with breaking changes analysis and incremental migration | - | plugins/a5c/marketplace/blueprints/framework-upgrade-automation/ |\n",
    "documents": []
  },
  "outgoingEdges": [],
  "incomingEdges": [
    {
      "from": "page:docs-reference-repos",
      "to": "page:docs-reference-repos-expo-skills-research",
      "kind": "contains_page"
    }
  ]
}

Shortcuts

Back to overview
Open graph tab