Voltra
Build, review, refactor, configure, or debug Voltra code using Voltra JSX, Voltra JS APIs, and the Expo config plugin. Use when the user asks about charts,…
Install
Quick install
npx skills add https://github.com/callstackincubator/voltra/tree/HEAD/skills/voltranpx skills add callstackincubator/voltra --skill voltra --agent claude-codenpx skills add callstackincubator/voltra --skill voltra --agent cursornpx skills add callstackincubator/voltra --skill voltra --agent codexnpx skills add callstackincubator/voltra --skill voltra --agent opencodenpx skills add callstackincubator/voltra --skill voltra --agent github-copilotnpx skills add callstackincubator/voltra --skill voltra --agent windsurfMore install options
Shorthand — useful for multi-skill repos:
npx skills add callstackincubator/voltra --skill voltraManual — clone the repo and drop the folder into your agent's skills directory:
git clone https://github.com/callstackincubator/voltra.gitcp -r voltra/skills/voltra ~/.claude/skills/voltra
Build, review, refactor, configure, or debug Voltra code using Voltra JSX, Voltra JS APIs, and the Expo config plugin. Use when the user asks about charts,…
voltraby callstackincubator
Build, review, refactor, configure, or debug Voltra code using Voltra JSX, Voltra JS APIs, and the Expo config plugin. Use when the user asks about charts,…npx skills add https://github.com/callstackincubator/voltra --skill voltraDownload ZIPGitHub
Voltra
Use this as the single Voltra skill entrypoint. Keep all product-wide ground truth here and load references from references/ as needed.
Voltra-Wide Ground Truth
- Never generate native platform UI code for Voltra tasks. Use Voltra JSX and Voltra JS APIs.
- Do not generate Swift, Kotlin, Java, Objective-C, or platform XML unless the user explicitly asks to edit an existing Voltra-supported Android widget preview XML file.
- Always solve Voltra tasks through Voltra JavaScript or TypeScript APIs, JSX components, and the Expo config plugin first.
- If a task appears to require native code, first check whether Voltra already exposes a JS API or config option. Prefer that path.
- Do not scaffold native extension code manually. Voltra's config plugin owns native target setup.
- Do not use plain React Native primitives inside Voltra-rendered trees. Avoid
View,Text,Pressable,TouchableOpacity, and similar RN UI primitives for Live Activity or Android widget content.
- For iOS app code, import
Voltraand runtime APIs from@use-voltra/ios-client.
- For Android app code, import
VoltraAndroidand runtime APIs from@use-voltra/android-client.
- Keep iOS and Android authoring paths separate unless the user explicitly asks for a shared abstraction.
- Update config before writing registration-dependent UI code.
- Treat images as a Voltra concern, not a native-code concern. Prefer Voltra image props, Voltra asset directories, and Voltra preloading APIs.
- When guidance conflicts, prefer this skill's internal references first, then hosted docs on
use-voltra.dev.
- Use hosted docs on
https://use-voltra.devwhen deeper documentation is needed.
Reference Routing
Read only the references needed for the current task:
- Setup, install, Expo Dev Client,
expo prebuild:references/setup.md
app.json, app.config., plugin keys, widget registration, groupIdentifier, enablePushNotifications: references/app-config.md
- Exact plugin fields and widget registration schema:
references/plugin-schema.md
- iOS Live Activities, Dynamic Island, lock screen variants, supplemental activity families:
references/ios-live-activities.md
- Exact Live Activity variant shapes:
references/variant-shapes.md
- iOS Home Screen widgets, accessory widgets, scheduled widgets, widget timelines, widget families,
VoltraWidgetPreview,updateWidget,scheduleWidget,reloadWidgets,getActiveWidgets:references/ios-widgets.md
- Exact iOS widget families and fallback behavior:
references/widget-families.md
- Charts for iOS widgets, Live Activities, and Android widgets:
references/charts.md
- Android widgets, Android widget previews, pre-rendering, widget updates:
references/android-widgets.md
- Server-driven widgets,
serverUpdate, widget polling flows,createWidgetUpdateHandler,setWidgetServerCredentials,clearWidgetServerCredentials:references/server-driven-widgets.md
- Android component choices and widget API checklist:
references/component-mapping.md,references/runtime-api-checklist.md
- APNS, push tokens, push-to-start, channel IDs, server-rendered Live Activity payloads:
references/ios-server-updates.mdand usuallyreferences/ios-live-activities.md
- Exact APNS flow details:
references/push-flow.md
- Image handling for Voltra surfaces:
references/images.mdplus the target surface reference
Working Style
- Identify the target platform and surface first.
- Confirm the correct Voltra namespace and JS entrypoint.
- If the task involves charts, verify the public JSX props and platform behavior before writing code or docs.
- Update config before writing registration-dependent UI code.
- Read only the domain references needed for the task.
- Use Voltra APIs that already exist in the repo before inventing new abstractions.
- Keep answers scoped to the requested platform.
Reference Index
references/source-of-truth.md
references/images.md
references/setup.md
references/app-config.md
references/plugin-schema.md
references/ios-live-activities.md
references/variant-shapes.md
references/ios-widgets.md
references/widget-families.md
references/charts.md
references/android-widgets.md
references/server-driven-widgets.md
references/component-mapping.md
references/runtime-api-checklist.md
references/ios-server-updates.md
references/push-flow.md
More skills from callstackincubator
agent-deviceby callstackincubatorAutomate iOS and Android app interactions with snapshot-based discovery and selector-driven replay. Supports iOS simulators/devices and Android emulators/devices with session-bound automation, multi-tenant remote daemon mode, and device-scope isolation for QA workflows Core commands: snapshot for UI discovery with refs, press / fill / scroll for interactions, open / close for app lifecycle, install / reinstall for binary deployment Includes utilities for logging, network inspection,...dogfoodby callstackincubatorSystematically explore and test a mobile app on iOS/Android with agent-device to find bugs, UX issues, and other problems. Use when asked to dogfood, QA,…react-devtoolsby callstackincubatorInspect and profile React Native component trees from agent-device. Use for React Native performance, profiling, props, state, hooks, render causes, slow…react-devtoolsby callstackincubatorReact DevTools CLI for AI agents. Use when the user asks you to debug a React or React Native app at runtime, inspect component props/state/hooks, diagnose…githubby callstackincubatorGitHub workflow automation via gh CLI for pull requests, stacked PRs, and repository management. Provides stacked PR merge workflow: squash-merge the first PR, then rebase and update base branch for each subsequent PR in the chain Includes conflict detection and manual resolution prompts to prevent silent failures during multi-PR merges Covers core gh CLI operations: PR creation, status checks, squash/rebase merging, and branch management Optimized for low context usage by relying on gh CLI...github-actionsby callstackincubatorGitHub Actions workflow patterns for React Native iOS simulator and Android emulator cloud builds with downloadable artifacts. Use when setting up CI build…react-native-best-practicesby callstackincubatorStructured performance optimization reference for React Native apps covering FPS, bundle size, TTI, and memory. Organized into 9 JavaScript/React guides (profiling, lists, animations, memory), 9 native optimization guides (Turbo Modules, threading, profiling), and 9 bundling guides (tree shaking, code splitting, size analysis) Each reference follows a hybrid format with quick patterns/commands, impact ratings (CRITICAL/HIGH/MEDIUM), and deep-dive explanations with prerequisites and common...react-native-brownfield-migrationby callstackincubatorProvides an incremental adoption strategy to migrate native iOS or Android apps to React Native or Expo using @callstack/react-native-brownfield for initial…---
Source: https://github.com/callstackincubator/voltra/tree/HEAD/skills/voltra
Author: callstackincubator
Discovered via: mcpservers.org
SKILL.md source
--- name: voltra description: Build, review, refactor, configure, or debug Voltra code using Voltra JSX, Voltra JS APIs, and the Expo config plugin. Use when the user asks about charts,… --- # voltra Build, review, refactor, configure, or debug Voltra code using Voltra JSX, Voltra JS APIs, and the Expo config plugin. Use when the user asks about charts,… # voltraby callstackincubator Build, review, refactor, configure, or debug Voltra code using Voltra JSX, Voltra JS APIs, and the Expo config plugin. Use when the user asks about charts,… `npx skills add https://github.com/callstackincubator/voltra --skill voltra`Download ZIPGitHub ## Voltra Use this as the single Voltra skill entrypoint. Keep all product-wide ground truth here and load references from `references/` as needed. ## Voltra-Wide Ground Truth * Never generate native platform UI code for Voltra tasks. Use Voltra JSX and Voltra JS APIs. * Do not generate Swift, Kotlin, Java, Objective-C, or platform XML unless the user explicitly asks to edit an existing Voltra-supported Android widget preview XML file. * Always solve Voltra tasks through Voltra JavaScript or TypeScript APIs, JSX components, and the Expo config plugin first. * If a task appears to require native code, first check whether Voltra already exposes a JS API or config option. Prefer that path. * Do not scaffold native extension code manually. Voltra's config plugin owns native target setup. * Do not use plain React Native primitives inside Voltra-rendered trees. Avoid `View`, `Text`, `Pressable`, `TouchableOpacity`, and similar RN UI primitives for Live Activity or Android widget content. * For iOS app code, import `Voltra` and runtime APIs from `@use-voltra/ios-client`. * For Android app code, import `VoltraAndroid` and runtime APIs from `@use-voltra/android-client`. * Keep iOS and Android authoring paths separate unless the user explicitly asks for a shared abstraction. * Update config before writing registration-dependent UI code. * Treat images as a Voltra concern, not a native-code concern. Prefer Voltra image props, Voltra asset directories, and Voltra preloading APIs. * When guidance conflicts, prefer this skill's internal references first, then hosted docs on `use-voltra.dev`. * Use hosted docs on `https://use-voltra.dev` when deeper documentation is needed. ## Reference Routing Read only the references needed for the current task: * Setup, install, Expo Dev Client, `expo prebuild`: `references/setup.md` * `app.json`, `app.config.*`, plugin keys, widget registration, `groupIdentifier`, `enablePushNotifications`: `references/app-config.md` * Exact plugin fields and widget registration schema: `references/plugin-schema.md` * iOS Live Activities, Dynamic Island, lock screen variants, supplemental activity families: `references/ios-live-activities.md` * Exact Live Activity variant shapes: `references/variant-shapes.md` * iOS Home Screen widgets, accessory widgets, scheduled widgets, widget timelines, widget families, `VoltraWidgetPreview`, `updateWidget`, `scheduleWidget`, `reloadWidgets`, `getActiveWidgets`: `references/ios-widgets.md` * Exact iOS widget families and fallback behavior: `references/widget-families.md` * Charts for iOS widgets, Live Activities, and Android widgets: `references/charts.md` * Android widgets, Android widget previews, pre-rendering, widget updates: `references/android-widgets.md` * Server-driven widgets, `serverUpdate`, widget polling flows, `createWidgetUpdateHandler`, `setWidgetServerCredentials`, `clearWidgetServerCredentials`: `references/server-driven-widgets.md` * Android component choices and widget API checklist: `references/component-mapping.md`, `references/runtime-api-checklist.md` * APNS, push tokens, push-to-start, channel IDs, server-rendered Live Activity payloads: `references/ios-server-updates.md` and usually `references/ios-live-activities.md` * Exact APNS flow details: `references/push-flow.md` * Image handling for Voltra surfaces: `references/images.md` plus the target surface reference ## Working Style * Identify the target platform and surface first. * Confirm the correct Voltra namespace and JS entrypoint. * If the task involves charts, verify the public JSX props and platform behavior before writing code or docs. * Update config before writing registration-dependent UI code. * Read only the domain references needed for the task. * Use Voltra APIs that already exist in the repo before inventing new abstractions. * Keep answers scoped to the requested platform. ## Reference Index * `references/source-of-truth.md` * `references/images.md` * `references/setup.md` * `references/app-config.md` * `references/plugin-schema.md` * `references/ios-live-activities.md` * `references/variant-shapes.md` * `references/ios-widgets.md` * `references/widget-families.md` * `references/charts.md` * `references/android-widgets.md` * `references/server-driven-widgets.md` * `references/component-mapping.md` * `references/runtime-api-checklist.md` * `references/ios-server-updates.md` * `references/push-flow.md` ## More skills from callstackincubator agent-deviceby callstackincubatorAutomate iOS and Android app interactions with snapshot-based discovery and selector-driven replay. Supports iOS simulators/devices and Android emulators/devices with session-bound automation, multi-tenant remote daemon mode, and device-scope isolation for QA workflows Core commands: snapshot for UI discovery with refs, press / fill / scroll for interactions, open / close for app lifecycle, install / reinstall for binary deployment Includes utilities for logging, network inspection,...dogfoodby callstackincubatorSystematically explore and test a mobile app on iOS/Android with agent-device to find bugs, UX issues, and other problems. Use when asked to dogfood, QA,…react-devtoolsby callstackincubatorInspect and profile React Native component trees from agent-device. Use for React Native performance, profiling, props, state, hooks, render causes, slow…react-devtoolsby callstackincubatorReact DevTools CLI for AI agents. Use when the user asks you to debug a React or React Native app at runtime, inspect component props/state/hooks, diagnose…githubby callstackincubatorGitHub workflow automation via gh CLI for pull requests, stacked PRs, and repository management. Provides stacked PR merge workflow: squash-merge the first PR, then rebase and update base branch for each subsequent PR in the chain Includes conflict detection and manual resolution prompts to prevent silent failures during multi-PR merges Covers core gh CLI operations: PR creation, status checks, squash/rebase merging, and branch management Optimized for low context usage by relying on gh CLI...github-actionsby callstackincubatorGitHub Actions workflow patterns for React Native iOS simulator and Android emulator cloud builds with downloadable artifacts. Use when setting up CI build…react-native-best-practicesby callstackincubatorStructured performance optimization reference for React Native apps covering FPS, bundle size, TTI, and memory. Organized into 9 JavaScript/React guides (profiling, lists, animations, memory), 9 native optimization guides (Turbo Modules, threading, profiling), and 9 bundling guides (tree shaking, code splitting, size analysis) Each reference follows a hybrid format with quick patterns/commands, impact ratings (CRITICAL/HIGH/MEDIUM), and deep-dive explanations with prerequisites and common...react-native-brownfield-migrationby callstackincubatorProvides an incremental adoption strategy to migrate native iOS or Android apps to React Native or Expo using @callstack/react-native-brownfield for initial… --- **Source**: https://github.com/callstackincubator/voltra/tree/HEAD/skills/voltra **Author**: callstackincubator **Discovered via**: mcpservers.org
Related skills 6
caveman
Ultra-compressed communication mode. Cuts token usage ~75% by speaking like caveman while keeping full technical accuracy. Supports intensity levels: lite, full (default), ultra, wenyan-lite, wenyan-full, wenyan-ultra. Use when user says "caveman mode", "talk like caveman", "use caveman", "less tokens", "be brief", or invokes /caveman. Also auto-triggers when token efficiency is requested.
secure-linux-web-hosting
Use when setting up, hardening, or reviewing a cloud server for self-hosting, including DNS, SSH, firewalls, Nginx, static-site hosting, reverse-proxying an app, HTTPS with Let's Encrypt or ACME clients, safe HTTP-to-HTTPS redirects, or optional post-launch network tuning such as BBR.
readme-i18n
Use when the user wants to translate a repository README, make a repo multilingual, localize docs, add a language switcher, internationalize the README, or update localized README variants in a GitHub-style repository.
lark-shared
Use when first setting up lark-cli, running auth login, switching user/bot identity (--as), handling permission denied or scope errors, needing to update lark-cli, or seeing _notice in JSON output.
improve-codebase-architecture
Find deepening opportunities in a codebase, informed by the domain language in CONTEXT.md and the decisions in docs/adr/. Use when the user wants to improve architecture, find refactoring opportunities, consolidate tightly-coupled modules, or make a codebase more testable and AI-navigable.
paper-context-resolver
Optional RigorPilot helper for README-first deep learning repo reproduction. Use only when the README and repository files leave a narrow reproduction-critical gap and the task is to resolve a specific paper detail such as dataset split, preprocessing, evaluation protocol, checkpoint mapping, or runtime assumption from primary paper sources while recording conflicts. Do not use for general paper summary, repo scanning, environment setup, command execution, title-only paper lookup, or replacin...