2.8K 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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
Build Kotlin database access with JetBrains Exposed, a library that maps database records to code. Apply examples for queries, transactions, reusable connections, schema migrations, and repository interfaces that separate database operations from business logic.
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.
Set up Tailwind CSS v4 in Expo using react-native-css and NativeWind v5. Configure styling across iOS, Android, and Web, create components that accept CSS class names, and define shared themes with platform-specific fonts and colors.
Create and edit EAS workflow YAML files to automate builds and deployments for Expo projects. Check required settings, job dependencies, and dynamic values against the latest schema, which defines the accepted configuration.
Create server endpoints in Expo Router and deploy them with EAS Hosting. Use them to keep API keys off the client, validate incoming data, access databases, proxy external services, and receive webhook notifications.
Use Nexscope (Search Intelligence Framework) data to analyze ASIN traffic source composition and exposure distribution, covering current period/previous period/newly entered/exited period comparisons. Trigger when the user mentions ASIN traffic sources, traffic structure analysis, organic traffic vs paid traffic share, exposure score breakdown, period comparison, new/exited traffic keywords, competitor traffic analysis, SP ad keyword count, brand ad exposure, Amazon's Choice exposure, editorial recommendation exposure, Top Rated exposure, video ad exposure, organic search exposure ratio, PPC traffic sources, promotional deal traffic sources, recommendation slot structure breakdown, ASIN traffic analysis, traffic sources, organic traffic share, ad traffic share, exposure analysis, traffic structure, period-over-period comparison, keyword churn, Nexscope. Even if the user does not explicitly mention "Nexscope", if their need involves analyzing an ASIN's traffic sources, exposure channel distribution, cross-period comparison, or competitor traffic structure comparison, this skill should also be triggered.
The English summary is being prepared. Showing the original description.
Add a lightweight iOS App Clip to an Expo app so people can launch it from a website URL. Covers domain association, website launch cards, permissions, TestFlight submission, and App Clip metadata.
Build development clients for Expo apps that use custom native code. Covers local and cloud builds, device installation, TestFlight distribution, and connecting installed clients to a local development server.
Bring existing React web components and browser-only libraries into Expo apps with DOM components. Render them in a WebView, an embedded browser view, on native platforms and directly on the web to support gradual migration.
Use this skill when the user is doing hands-on DOCA Telemetry Exporter programming on a host where DOCA is installed — defining a doca_telemetry_exporter_schema and event types, creating sources, picking a publish surface (typed events / opaque events / the metrics counter-gauge-histogram API / OTLP logs / NetFlow), walking the schema-then-source lifecycle, or debugging DOCA_ERROR_* failures from the exporter API. Trigger even when the user does not explicitly mention "DOCA Telemetry Exporter" or "doca_telemetry_exporter_*" — typical implicit phrasings include "publishing counters from my DOCA app", "BAD_STATE when I report an event", "consumer/DTS sees nothing but my report succeeded", "how do I export NetFlow/IPFIX records", or "should I link the exporter or the telemetry service". Refuse and route elsewhere for the receiving DOCA Telemetry Service (DTS), plain stdout logging via doca_log, or real-time event subscription back into the app via doca-comch — those belong to other skills.
The English summary is being prepared. Showing the original description.