← Browse

@zidong-llc/upgrading-expo

B

Base de conocimiento y herramientas para agentes de IA.

skillclaude

Install

agr install @zidong-llc/upgrading-expo --target claude

Writes 1 file into .claude/skills/, pinned to git-fc131b59.

  • .claude/skills/upgrading-expo/SKILL.md

Document


name: upgrading-expo description: "Upgrade Expo SDK versions" risk: safe source: "https://github.com/expo/skills/tree/main/plugins/upgrading-expo" date_added: "2026-02-27"

Upgrading Expo

Overview

Upgrade Expo SDK versions safely, handling breaking changes, dependencies, and configuration updates.

When to Use This Skill

Use this skill when you need to upgrade Expo SDK versions.

Use this skill when:

  • Upgrading to a new Expo SDK version
  • Handling breaking changes between SDK versions
  • Updating dependencies for compatibility
  • Migrating deprecated APIs to new versions
  • Preparing apps for new Expo features

Instructions

This skill guides you through upgrading Expo SDK versions:

  1. Pre-Upgrade Planning: Review release notes and breaking changes
  2. Dependency Updates: Update packages for SDK compatibility
  3. Configuration Migration: Update app.json and configuration files
  4. Code Updates: Migrate deprecated APIs to new versions
  5. Testing: Verify app functionality after upgrade

Upgrade Process

1. Pre-Upgrade Checklist

  • Review Expo SDK release notes
  • Identify breaking changes affecting your app
  • Check compatibility of third-party packages
  • Backup current project state
  • Create a feature branch for the upgrade

2. Update Expo SDK

# Update Expo CLI
npm install -g expo-cli@latest

# Upgrade Expo SDK
npx expo install expo@latest

# Update all Expo packages
npx expo install --fix

3. Handle Breaking Changes

  • Review migration guides for breaking changes
  • Update deprecated API calls
  • Modify configuration files as needed
  • Update native dependencies if required
  • Test affected features thoroughly

4. Update Dependencies

# Check for outdated packages
npx expo-doctor

# Update packages to compatible versions
npx expo install --fix

# Verify compatibility
npx expo-doctor

5. Testing

  • Test core app functionality
  • Verify native modules work correctly
  • Check for runtime errors
  • Test on both iOS and Android
  • Verify app store builds still work

Common Issues

Dependency Conflicts

  • Use expo install instead of npm install for Expo packages
  • Check package compatibility with new SDK version
  • Resolve peer dependency warnings

Configuration Changes

  • Update app.json for new SDK requirements
  • Migrate deprecated configuration options
  • Update native configuration files if needed

Breaking API Changes

  • Review API migration guides
  • Update code to use new APIs
  • Test affected features after changes

Best Practices

  • Always upgrade in a feature branch
  • Test thoroughly before merging
  • Review release notes carefully
  • Update dependencies incrementally
  • Keep Expo CLI updated
  • Use expo-doctor to verify setup

Resources

For more information, see the source repository.

Repository README

Describes Zidong-LLC/BIBLIOTECA as a whole, which may contain artifacts other than this one. Where this artifact had no useful description of its own, its summary was taken from here.

BIBLIOTECA

Base de conocimiento y herramientas para agentes de IA. Mas de 1000 skills organizados por tematica, herramientas de productividad, y material de referencia.

Estructura

BIBLIOTECA/
├── skills/                # Motor de skills (1007 skills en 21 categorias)
│   ├── skills/            # Las skills organizadas por tematica
│   │   ├── cloud-azure/        (120)  SDKs y servicios Azure
│   │   ├── automation-tools/   (110)  Automatizacion: Zapier, n8n, CRMs, Apify
│   │   ├── code-quality/        (80)  Review, debugging, testing, refactoring
│   │   ├── web-frontend/        (71)  React, Angular, Next.js, UI/UX, web quality
│   │   ├── ai-ml/               (65)  ML, LLMs, RAG, data science, voice AI
│   │   ├── marketing-seo/       (62)  SEO, CRO, copywriting, ads, growth
│   │   ├── context-claude/      (57)  Context engineering, MCP, memoria, Claude
│   │   ├── devops-cicd/         (53)  Docker, K8s, Terraform, deployment
│   │   ├── web-backend/         (53)  Node, FastAPI, Django, APIs, pagos
│   │   ├── programming-languages/(47) Python, JS, Rust, Go, Java, Bash
│   │   ├── security-offensive/  (39)  Pentesting, red team, exploits
│   │   ├── business-product/    (38)  Producto, startups, analisis de mercado
│   │   ├── security-defensive/  (37)  Auditorias, compliance, hardening
│   │   ├── ai-agents/           (33)  Frameworks de agentes, multi-agente
│   │   ├── documentation/       (30)  Wikis, docs, Office, technical writing
│   │   ├── architecture-patterns/(28) DDD, microservicios, CQRS, C4
│   │   ├── databases/           (19)  PostgreSQL, SQL, NoSQL, Prisma
│   │   ├── desktop-embedded/    (16)  Extensions, bots, firmware, desktop
│   │   ├── mobile/              (14)  iOS, Android, Flutter, React Native
│   │   └── game-dev/            (9)   Unity, Godot, Unreal, shaders
│   ├── web-app/           # App web para explorar skills
│   ├── scripts/           # Scripts de build y validacion
│   ├── data/              # Indices JSON (catalog, aliases, bundles)
│   ├── docs/              # Guias detalladas
│   └── CATALOG.md         # Indice completo de skills
│
├── estructuras-de-prompts/ # System prompts, patrones y templates
│   ├── system-prompts-filtrados/      Prompts por empresa (Anthropic, OpenAI, Google, xAI)
│   ├── prompts-de-herramientas-ia/    Prompts de 35+ herramientas (Cursor, Devin, Replit...)
│   └── templates/                     Plantillas de estructura para nuevos proyectos
│
├── tools/                 # Herramientas
│   ├── claude-supermemory/    Plugin de memoria persistente para Claude
│   └── cli/                   Firecrawl CLI (web scraping para LLMs)
│
└── references/            # Material de referencia
    ├── public-apis/           Directorio de APIs publicas
    └── repos-referencia/      Repos de ejemplo y best practices

Uso rapido

# Explorar skills por categoria
ls skills/skills/web-frontend/
ls skills/skills/ai-ml/

# Buscar un skill especifico
grep -r "nombre" skills/data/catalog.json

# Regenerar el catalogo
cd skills && node scripts/build-catalog.js

# Lanzar la web app de skills
cd skills && npm start

Trustgrade B

  • passBody integrity

    Whether the stored document is plausibly the kind of file the artifact declares, rather than something fetched by mistake.

  • passType matchnot applicable to this artifact type

    Whether the artifact is really the kind of thing its metadata claims it is.

  • passFreshness

    How long since the source repository was last pushed to.

  • passPrompt injection

    Scans the artifact's own text for instructions aimed at your agent rather than at you.

  • warnLicenseno SPDX license detected

    Whether the source repository declares an SPDX license permissive enough to redistribute.

How the grade is calculated

Each check contributes 0 points when it passes, 1 when it warns, and 2 when it fails. The total maps to a letter:

  • Aevery check passed
  • Bone warning
  • Ctwo warnings
  • Dprompt injection or body integrity failed, or three warnings
  • Fone of those failed, and something else is wrong

These are automated hygiene checks, not a security audit, and not a dependency or vulnerability scan. A grade of A means nothing was flagged — not that the artifact is safe.

Versions

  • git-fc131b59879e2026-07-31