Complete guide for building beautiful apps with Expo Router. Covers fundamentals, styling, components, navigation, animations, patterns, and native tabs.
The English summary is being prepared. Showing the original description.
Publish NowStack Mobile production surfaces. Use for Convex prod, web deploy, production env sync, and coordinating iOS/Android release skills.
The English summary is being prepared. Showing the original description.
See how to installReview the instructions the agent will receive before you install.
web-app/ production build/deploy preparation.ns-ios-deploy-app, ns-deploy-android-app, and ns-generate-store-screenshots.This skill does not submit App Store or Google Play builds directly. Use the dedicated store skills for that. </scope>
<preflight> Run/read:git status --short --branch
git remote -v
npx convex --version
npx convex env list --prod || true
cd web-app && npm run typecheck
cd web-app && npm run build
cd mobile-app && npx tsc --noEmit
Read:
site-config.tsconvex/http.tsconvex/auth.tsconvex/storage/web-app/package.jsonmobile-app/package.json.agents/rules/auth-payments-storage.md.agents/rules/store-release.md
</preflight>
<env_rules>
.env, .env.local, .env.production, store keys, App Store .p8, Google service account JSON, Stripe secrets, or R2 secrets.<web_deploy>
Web deploy is owned by the ns-web-deploy skill — run it; do not duplicate its steps here. It covers the full one-shot flow: the mandatory nitro Vite plugin (without it Vercel ships a SPA and every route 404s), web-app/vercel.json running convex deploy so the backend ships with the frontend, npm run setup:vercel (deploy key + Root Directory = web-app), and deploying from the repo root with --archive=tgz or a push to main.
Non-negotiables to assert before declaring the web surface done:
npm run check-setup passes the "web-app/vercel.json" AND "web-app nitro plugin" checks.CONVEX_DEPLOY_KEY (Production) is set so the backend never drifts behind the frontend.convex deploy running AND Generated .vercel/output/nitro.json./, /privacy, /cgv, /support) returns 200, not 404 — a SPA-404 regression only surfaces on the live routes, not in the build.See ns-web-deploy and docs/production-checklist.md stage 2 for the step-by-step.
</web_deploy>
<mobile_handoff> Before declaring production complete:
ns-generate-store-screenshots if store screenshots are missing or stale.ns-ios-deploy-app for TestFlight/App Store Connect (asc workflow).ns-deploy-android-app for Google Play (gpc workflow).site-config.ts.
</mobile_handoff><success_criteria>
web-app typecheck/build pass.No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Complete guide for building beautiful apps with Expo Router. Covers fundamentals, styling, components, navigation, animations, patterns, and native tabs.
The English summary is being prepared. Showing the original description.
Routes general Convex requests to the right project skill. Use when the user asks which Convex skill to use or gives an underspecified Convex app task.
The English summary is being prepared. Showing the original description.
Use when optimizing Convex database read bandwidth, documents-read cost, query indexes, full-table scans, function-level usage dashboard findings, or code that uses .filter(), unbounded .collect(), N+1 reads, or expensive reactive Convex queries.
The English summary is being prepared. Showing the original description.
Build reusable Convex components with isolated tables and app-facing wrappers. Use for defineComponent, app.use, ComponentApi, or shared backend modules.
The English summary is being prepared. Showing the original description.
Plan safe Convex schema and data migrations. Use for widen-migrate-narrow rollouts, backfills, breaking field changes, table splits, or failed schema deploys.
The English summary is being prepared. Showing the original description.
Audit Convex performance for hot reads, write contention, subscriptions, function limits, OCC conflicts, latency, read amplification, and expensive reactive queries.
The English summary is being prepared. Showing the original description.