aexol-studio/mobile-routing-expo-router
examples/new/mobile/.opencode/skills/mobile-routing-expo-router/SKILL.md
Expo Router conventions for route groups, native headers, and starter navigation
$ install --global
skillsauthnpx skillsauth add aexol-studio/axolotl mobile-routing-expo-routerInstall 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: Mar 29, 2026, 12:02 PM38.0s1 file scanned
SKILL.md
- name:
- mobile-routing-expo-router
- description:
- Expo Router conventions for route groups, native headers, and starter navigation
Mobile Routing (Expo Router)
Goal
Keep navigation predictable, native, and reusable.
Source of truth notes
- Ratio-scaling guidance is maintained in
mobile/AGENTS.md. - If route-level UI needs scaling decisions, reference that file instead of introducing duplicated policy here.
- Keep this skill additive and concise; do not copy canonical global policy text.
QC evidence contract (routing scope)
- For routing changes, report exact route files touched and why.
- Confirm interactive header/CTA elements preserve
testIDwhere applicable. - Include baseline-vs-introduced violation classification in results.
Route Conventions
- Use route groups for app domains:
app/(tabs)/...app/(auth)/...
- Keep root composition in
app/_layout.tsx. - Put shared header option factories in
src/components/navigation/.
Header Rules
- Use native stack options factory (
createNativeHeaderOptions) for consistent options. - Baseline options from factory:
headerShadowVisible: false,headerBackTitleVisible: false. - Keep root group headers hidden in
app/_layout.tsxfor(tabs)and(auth)entries. - Set route titles explicitly per screen/group (no implicit defaults).
- Keep titles aligned with current code baseline (e.g. tabs index
Axolotl, auth sign-inSign in) unless scope explicitly includes i18n/title refactor.
Route File Pattern
- Route file should compose screen and hook/template.
- Avoid inline API and heavy business logic in route files.
Starter Checklist
- Root layout with providers and stack
- Tabs layout with at least one tab
- Auth stack layout with at least one screen
Related Skills
aexol-studio/mobile-starter-architecture
tools
VerifiedTrustedCommunity
Baseline architecture for Axolotl mobile starter (Expo Router + reusable blocks)
27SKILL.mdUpdated Mar 27, 2026
aexol-studio/mobile-i18n-dev-translate
development
VerifiedTrustedCommunity
i18n baseline and dev-translate setup for Expo mobile starter
27SKILL.mdUpdated Mar 27, 2026
aexol-studio/mobile-graphql-react-query-zeus
development
VerifiedTrustedCommunity
Starter data layer pattern with React Query + Zeus for Expo app
27SKILL.mdUpdated Mar 27, 2026
aexol-studio/mobile-components
tools
VerifiedTrustedCommunity
Reusable native component and template patterns for starter implementation
27SKILL.mdUpdated Mar 27, 2026