17.1K skills · sorted by relevance
Guide Expo SDK upgrades through dependency updates, diagnostics, configuration cleanup, and migration of deprecated packages. Includes checks for native project changes and guidance for moving audio and video code to replacement APIs.
Build React Native and Expo screens with guidance on navigation, state management, and data fetching. Apply patterns for long lists, validated forms, device features, and secure token storage when developing or reviewing mobile apps.
Build iOS and Android apps with React Native and Expo. Get guidance and typed component code for navigation, lists, animations, storage, and platform differences, with attention to scrolling performance and testing on both platforms.
Use when configuring or operating the native Salesforce Data Export Service (Setup → Data Export) — weekly or monthly CSV export, attachment inclusion, file-size split, the 48-hour download window, and the gap between this free utility and the paid Salesforce Backup and Restore product. Triggers: 'data export service', 'weekly export', 'export attachments', 'data export 48 hour download', 'data export missing objects', 'is weekly export a backup', 'bulk api 2.0 query job export', 'data loader extract batch', 'process-conf.xml export', 'incremental export systemmodstamp', 'export inventory retention owner'. NOT for the paid Salesforce Backup and Restore product (use that as a separate tool), NOT for Bulk API extraction (use data/bulk-api-patterns), NOT for HA/DR architecture (use architect/ha-dr-architecture).
The English summary is being prepared. Showing the original description.
Use when an admin or partner needs to package an Experience Cloud (Community) site as a reusable Lightning Bolt Solution for distribution — covers the export workflow from Experience Builder, what gets bundled (ExperienceBundle, custom apps, flow categories, theme, layouts, navigation menus) versus what does NOT (data, CMS content, files), choosing Bolt vs managed package vs unlocked package vs cloning a site, sandbox-to-production promotion, multi-org distribution, AppExchange listing as a Bolt, and template versioning via the LightningBolt metadata `versionNumber`. Triggers: 'turn this community into a reusable template', 'package an Experience Cloud site to ship to multiple orgs', 'export Experience Builder template for AppExchange', 'should we use a Bolt or a managed package for this community', 'create an industry-specific community starter', 'how do we version our partner portal template', 'distribute branded Experience site across business units'. NOT for general Experience Cloud site build, content, or member setup (use admin/experience-cloud-site-setup, admin/experience-cloud-cms-content, admin/experience-cloud-member-management). NOT for shipping Apex / LWC / data-model functionality as a product (use devops/managed-package-development, devops/second-generation-managed-packages, devops/unlocked-package-development). NOT for moving a single Experience site between sandbox and prod as a one-off (use devops/experience-cloud-deployment-admin, devops/cicd-for-experience-cloud).
The English summary is being prepared. Showing the original description.
Use SwiftUI interface components and appearance settings in an Expo SDK 55 app. The skill guides package installation, wrapping SwiftUI content in Host, and embedding React Native components within a SwiftUI layout.
Build or modify Expo native modules and views using Swift, Kotlin, and TypeScript. Guides scaffolding, native function bindings, events, lifecycle hooks, and configuration so Expo apps can use platform features or existing native SDKs.
Connect an Expo project to the Codex app Run button by creating a local launch script and action configuration. Start the development server from the app, view its logs, and optionally add platform-specific launch buttons.
Analyze Mixpanel data with Python to explore usage trends, conversion steps, returning users, and differences between user groups. Also manage business context documents that explain an organization's structure and goals to AI assistants.
Build app screens with Expo Router using guidance on layouts, navigation, native tabs, and animations. Includes implementation patterns for styling, adapting to screen sizes, and checking features in Expo Go.
Review JavaScript module usage and convert CommonJS code to ES modules using import/export. Inspect source code and browser execution, explain how unused code can be removed during builds, and describe how to verify changes.
Turn a research experiment plan into training and evaluation code, run a small setup check, and launch GPU experiments. Collect initial metrics and update progress records so the results are ready for further review.
Prepare a Python environment for Mixpanel analysis by installing required libraries and checking credentials and connectivity. Use it for first-time setup, missing dependencies, or guidance on service account and OAuth sign-in options.
Entry point and router for every Expo or EAS task. Load this skill first — before writing code and before choosing another expo-* / eas-* skill — when the request, PRD, or spec mentions Expo, EAS, Expo Go, or an expo-* package, or the project has an `expo` dependency in `package.json`. Within that gate it also covers app specs and designs to implement (tabs, stacks, maps, lists, navigation, building from a screenshot), and phrasings like 'implement a mobile app', 'make my app look native', 'add navigation', 'fetch some data', 'upgrade my SDK', 'add Expo to my existing native app', 'ship to the App Store', or 'I'm new to Expo, where do I start'. A fully specified request (SDK pinned, libraries named, layout given) still routes through here — the shared setup rules still apply. Do NOT load it when neither signal is present: a bare React Native project with no `expo` dependency is not Expo work. Detects the real goal, routes to the right expo-* / eas-* skill, and owns the shared setup rules.
The English summary is being prepared. Showing the original description.
Build an interactive page that explains a process as a machine viewed from an angle. A tested simulation keeps movement, numbers, and explanations consistent, while controls let readers step through operations and explore failures.
Structure mobile apps built with React Native and Expo. Covers navigation, state management, device feature integration, offline data synchronization, and performance practices, helping developers organize projects and account for differences between iOS and Android.
Turn a vague research direction into a focused proposal and a detailed experiment roadmap. This workflow connects method refinement with validation planning, producing review records, an experiment tracker, and a summary of what to run next.
Build and debug mobile apps for iOS and Android with React Native and Expo. Implement navigation, adapt screens to each platform, integrate native modules that access platform features, and improve list rendering, keyboard behavior, and memory use.
Build Android interfaces in Expo using Jetpack Compose components and modifiers, which control layout and appearance. The skill guides component selection, sizing, scrollable lists, and XML icons for SDK 55.
Prepare and deploy Expo apps to iOS and Android stores or the web using EAS, Expo's build and deployment services. Covers production builds, store submissions, beta distribution, preview deployments, and automated release workflows.
Translate existing code-explanation docs into another language, Chinese by default. Translates a whole `CODE_EXPLANATION/` folder into a parallel `CODE_EXPLANATION_<LANG>` copy (e.g. `CODE_EXPLANATION_ZH`), or a single file — either bilingually in place (English + translation interleaved) for small files or as a `<name>_<lang>.<ext>` sidecar copy for larger ones. Keeps filenames, code, identifiers, file paths, and technical terms in English — only the explanatory prose is translated. Use this skill whenever the user wants to translate, localize, or produce a non-English version of code-explanation / codebase documentation: phrases like "translate-explanation", "translate the code explanation", "translate the CODE_EXPLANATION folder", "localize these docs to Chinese", "make a Chinese version of the explanation", or naming any target language for the explanation files. Default to Chinese (ZH) when no language is specified.
The English summary is being prepared. Showing the original description.
A platform decision framework for experimentation. When to use Statsig vs PostHog vs GrowthBook vs Optimizely vs Amplitude vs Eppo vs Kameleoon. How to migrate between them. How to coordinate when multi-platform is genuinely warranted. The decisions that compound for years and the ones you can defer. Triggers on which experimentation platform, choose Statsig vs PostHog, evaluate experimentation tools, switch experimentation platform, migrate from Optimizely, consolidate experimentation tools, multi-platform experimentation, experimentation platform decision, ab test platform selection, feature flag platform vs experiment platform, warehouse-native experiments, vendor lock-in experimentation. Also triggers when a team is asking about cost, governance, or migration cost across experimentation tools, or when an evaluation is starting.
The English summary is being prepared. Showing the original description.
Running experiments out of the data warehouse instead of via dedicated experiment platforms. SQL-based assignment, exposure logging discipline, metric definitions in dbt models, statistical analysis in SQL or Python, variance reduction with CUPED, sequential testing, and the operational tradeoffs vs platforms like Statsig and Optimizely. Triggers on warehouse-native experimentation, run experiments in BigQuery, run experiments in Snowflake, dbt experiments, SQL t-test, CUPED variance reduction, exposure log, sample ratio mismatch, sequential testing, mSPRT, doubly robust estimation, build vs buy experimentation. Also triggers when the team is choosing between platform and warehouse, building warehouse-native experiment infrastructure, auditing one, or running an experiment with a custom metric the platform cannot handle.
The English summary is being prepared. Showing the original description.
Expo (React Native フレームワーク, Expo SDK 58 / EAS) のリファレンス。 Expo Router (file-based routing, expo-server, data loaders, +api.ts), app.json / app.config, config plugins, Expo Modules API, expo-* SDK, Expo UI, EAS Build / Update / Submit / Workflows, eas.json, expo-updates (OTA), CNG / prebuild, Expo CLI (npx expo), development build (dev-client), expo-notifications push。
The English summary is being prepared. Showing the original description.