limrun-expo-development
Develop Expo Apps on Limrun
Remote Expo development requires matching native builds, Metro routes, and device launch URLs. This skill guides Limrun setup and iteration without rebuilding for every JavaScript change.
Установить с помощью моего Агента
Скопируйте этот запрос в своего Агента. Он содержит каноническую страницу Skill и манифест.
Review the Skillstore skill "limrun-expo-development" from https://skillstore.io/skills/limrun-inc-limrun-expo-development.md and its manifest at https://skillstore.io/api/skills/limrun-inc-limrun-expo-development/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.Ваш Агент по-прежнему должен показать план и запросить все подтверждения, требуемые политикой безопасности.
Ресурсы для AI-агентов
Используйте эти ссылки, когда AI-агенту, crawler или script нужен чистый контекст вместо полной страницы.
Протестировать
Использование «limrun-expo-development». Our Expo app gained a native dependency. Can we reuse its uploaded Debug asset?
Ожидаемый результат:
- The documented workflow requires a fresh Debug build after native dependency changes.
- Build and upload the updated asset before reinstalling it on the remote device.
- Reopen the development-client URL and verify the app before continuing Metro iteration.
Использование «limrun-expo-development». The Android app stopped loading JavaScript after reconnecting its tunnel.
Ожидаемый результат:
- The ADB tunnel port changes after reconnecting.
- Use the new loopback serial to restore Metro port forwarding for the selected emulator.
- Open the development-client URL again and confirm the rendered app through a screenshot.
Использование «limrun-expo-development». I need a preview that still works after stopping Metro.
Ожидаемый результат:
- Use a Release build instead of the Debug development client.
- Upload the platform-specific build asset and prepare its Limrun console preview link.
- The preview uses the Release asset and does not require a running Metro process.
Аудит безопасности
Средний рискAll 141 static findings are false positives involving Markdown formatting, scoped development commands, expected networking, and a dotenv reference. One semantic finding identifies public Metro exposure in the Expo tunnel fallback without an access-control or consent check. No evidence found of prompt injection, credential theft, or malicious reconnaissance.
Подтверждённые проблемы безопасности (1)
Факторы риска
⚙️ Внешние команды (50)
🌐 Доступ к сети (9)
🔑 Переменные окружения (1)
Поделиться и цитировать этот отчет
Делитесь версионным отчетом об оценке, нейтральным значком, встраиваемой карточкой и цитатами. Skillstore публикует доказательства, не решая, безопасен ли этот Skill.
Копировать ссылку на отчёт
https://skillstore.io/skills/limrun-inc-limrun-expo-development/audits/1?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportЗначок Markdown
[](https://skillstore.io/skills/limrun-inc-limrun-expo-development?utm_source=security_passport_badge)Значок HTML
<a href="https://skillstore.io/skills/limrun-inc-limrun-expo-development?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/limrun-inc-limrun-expo-development/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Встраиваемая карточка
<iframe src="https://skillstore.io/embed/skills/limrun-inc-limrun-expo-development.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>Академические ссылки (APA · BibTeX · CFF)
Цитата APA
limrun-inc. (2026). limrun-expo-development security audit report (audit version 1) [Author version unspecified]. Skillstore. https://skillstore.io/skills/limrun-inc-limrun-expo-development/audits/1Цитата BibTeX
@techreport{limrun-inc-limrun-inc-limrun-expo-development-2026,
author = {limrun-inc},
title = {limrun-expo-development security audit report (audit version 1)},
institution = {Skillstore},
year = {2026},
number = {1},
url = {https://skillstore.io/skills/limrun-inc-limrun-expo-development/audits/1},
note = {Author version unspecified}
}CITATION.cff
cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "limrun-expo-development security audit report (audit version 1)"
version: "unspecified"
type: report
authors:
- name: "limrun-inc"
date-released: "2026-10-15"
url: "https://skillstore.io/skills/limrun-inc-limrun-expo-development/audits/1"
identifiers:
- type: other
value: "skillstore:limrun-inc-limrun-expo-development:audit:1"
description: "Skillstore immutable audit report identifier"
Оценка Skillstore
Почему такая оценка Достоверность доказательств: СреднийЧто вы можете построить
Iterate on an Expo Feature
Connect an existing Expo app to a remote Limrun device and use Metro for JavaScript and TypeScript changes.
Investigate Remote Runtime Failures
Check native build freshness, development-client links, tunnel state, screenshots, and app logs when an Expo app fails to load.
Prepare an Independent Demo
Build a Release asset and prepare a Limrun preview link that does not depend on a running Metro server.
Попробуйте эти промпты
Inspect this Expo project for Limrun development readiness. Identify its SDK, app identifiers, launch scheme, and development-client dependency before changing files.
Set up this Expo app on a Limrun iOS simulator. Check Debug asset freshness, connect Metro, and verify the development-client launch.
Diagnose this Expo app after an Android tunnel reconnect. Target the explicit instance, refresh ADB reverse, and verify rendering through a screenshot.
Review native dependency changes, rebuild affected Limrun Debug assets, verify Metro iteration, then prepare Release preview links. Request approval before any public tunnel.
Лучшие практики
- Check the Expo SDK version and native dependency changes before deciding whether a Debug asset is reusable.
- Use explicit device instance IDs and keep Metro ports, tunnel routes, and launch URLs consistent.
- Prefer private tunnel routes, require approval before public exposure, and stop development servers and tunnels when iteration ends.
Избегать
- Reusing a Debug asset after native dependencies or native configuration change.
- Treating an empty Android accessibility tree as proof that the app failed to render.
- Starting a public Expo tunnel without checking access restrictions and approving development data exposure.
Часто задаваемые вопросы
Does this skill support both iOS and Android?
Do JavaScript changes require another native build?
Is expo-dev-client required?
Can I use local simulators instead of Limrun?
What should I check after an Android tunnel reconnect?
Can a final preview work without Metro?
Сведения для разработчиков
Автор
limrun-incЛицензия
MIT
Ревизия Skillstore
r1
Примечание о версии
Автор не указал версию.
Ссылка
4c558a97877f5e236b640596f721cb13399b82f2
Актуальность поддержки
15.10.2026
Использование
0 загрузок · 0 просмотров
Структура файлов
📄 SKILL.md