hjemmesidekongen/expo-deployment
plugins/smedjen/skills/expo-deployment/SKILL.md
EAS Build, OTA updates, app store submission, and Expo deployment workflows.
development
Updated Apr 5, 2026
$ install --global
skillsauthnpx skillsauth add hjemmesidekongen/ai expo-deploymentInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 5, 2026, 5:28 PM18.2s3 files scanned
SKILL.md
- name:
- expo-deployment
- description:
- >
- user_invocable:
- false
- interactive:
- false
- model_tier:
- senior
- depends_on:
- []
- reads:
- []
- writes:
- []
- type:
- data_validation
- - name:
- secrets_not_in_app_config
- verify:
- Sensitive values are in EAS secrets or .env files, not hardcoded in app.json or app.config.js
- fail_action:
- Move secrets to EAS environment variables or local .env — never commit credentials
- on_fail:
- EAS configuration has issues that will cause build or submission failures — fix before triggering builds
- on_pass:
- EAS deployment configuration is valid
- origin:
- smedjen
- inspired_by:
- expo-skills-main
- ported_date:
- 2026-03-10
- iteration:
- 1
- changes:
- New discipline skill for smedjen
Expo Deployment
EAS (Expo Application Services) handles the full Expo deployment lifecycle: native builds in the cloud, OTA JavaScript updates, and app store submission.
EAS Build Overview
EAS Build runs cloud builds for iOS and Android without requiring local Xcode or Android Studio. Configuration lives in eas.json — one file, multiple profiles (development, preview, production). Each profile maps to a build type and distribution target.
Development builds replace Expo Go. They include your custom native code and connect to a local dev server. Preview builds go to internal testers (ad hoc / internal distribution). Production builds go to the stores.
OTA vs Native Update Decision
OTA update (EAS Update): JavaScript and assets only. No native code changes, no new SDK version, no new native dependencies. Fastest path — no review required, deploys in minutes.
Native build required: any change to app.json native fields (bundleIdentifier, package, permissions, splash screen), new native dependencies, SDK upgrade, or changes to app.config.js that affect native output.
Rule: if expo prebuild would produce a different output, you need a native build.
Submission Workflow
EAS Submit handles store upload after a successful EAS Build. It reads credentials from EAS and submits the artifact. Apple requires an App Store Connect API key; Google requires a service account JSON.
Submission is decoupled from builds — submit any build by ID: eas submit --platform ios --id <build-id>.
Key Rules
- Never use
expo publish(legacy) — useeas updatefor all OTA updates. runtimeVersionmust match between the build and the update. Mismatches cause silent update ignoring.- Environment variables for builds go through EAS secrets, not
.envfiles committed to git. - Channels map to branches — keep
productionchannel pointing only at production-ready branches. - Always test OTA updates on a preview build before pushing to production channel.
See references/process.md for eas.json profile details, EAS Update channels, versioning strategy, CI/CD integration, internal distribution, and anti-patterns.
Related Skills
hjemmesidekongen/brand-strategy
development
VerifiedTrustedCommunity
Creates a brand from scratch through market research and interactive sparring. Runs competitive research via Perplexity, then guides the user through positioning, audience, voice, values, and content pillars. Produces the full brand guideline set at .ai/brand/{name}/. Use when building a new brand, defining brand strategy for a product, or when /våbenskjold:create is invoked.
SKILL.mdUpdated Apr 5, 2026
hjemmesidekongen/brand-loader
testing
VerifiedTrustedCommunity
Loads brand guidelines from .ai/brand/{name}/ and makes them available to the current context. Progressive disclosure: L1 confirms brand exists, L2 loads summary, L3 loads specific files on demand. Use when a downstream skill or user needs brand context, or when /våbenskjold:apply is invoked.
SKILL.mdUpdated Apr 5, 2026
hjemmesidekongen/brand-evolve
documentation
VerifiedTrustedCommunity
Guided reinvention of an existing brand guideline. Loads current brand from .ai/brand/{name}/, identifies what to keep vs change, and walks the user through targeted evolution. Preserves brand equity while updating positioning, voice, or values. Use when refreshing a brand or when /våbenskjold:evolve is invoked.
SKILL.mdUpdated Apr 5, 2026
hjemmesidekongen/brand-audit
development
VerifiedTrustedCommunity
Codifies an existing brand from materials, samples, and references. Analyzes provided content to extract voice patterns, values, and positioning. Produces the same guideline format as brand-strategy. Use when a brand already exists but isn't documented, or when /våbenskjold:audit is invoked.
SKILL.mdUpdated Apr 5, 2026