mobile-patterns
Skill0 starsChanged 5 months agoMITView on GitHub
Applies mobile app best practices — navigation, offline, push, performance, and platform conventions. Use when building or reviewing React Native, Flutter, or native iOS/Android features.
2 other projects use a version of this.
Adopted by
Most recently taken up by
- YosemiteCrew/Yosemite-Crewtheir own version, first seen Nov 1, 2026
- ngnthanhdev/claude_template_codetheir own version, first seen Aug 20, 2026
Other versions2 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 2
- YosemiteCrew/Yosemite-Crew★ 2ksame name
- ngnthanhdev/claude_template_code★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository68 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- .github/copilot-instructions.mdCopilot instructions
- .cursor/rules/engineering-skills.mdcCursor rule
- marketing-routerSkill
- accessibilitySkill
- agent-guardrailsSkill
- agent-memorySkill
- agent-verificationSkill
- autonomous-loopsSkill
- browser-checksSkill
- caching-strategySkill
- context-curationSkill
- contract-testingSkill
- data-modelingSkill
- decision-docsSkill
- dependency-hygieneSkill
- design-handoffSkill
- e2e-testingSkill
- experimentationSkill
- fault-recoverySkill
- feature-flagsSkill
- finops-budgetSkill
- git-flowSkill
- hardeningSkill
- i18n-l10nSkill
- idea-shapingSkill
- incident-responseSkill
- incremental-deliverySkill
- interface-designSkill
- launch-campaignSkill
- launch-readinessSkill
- llm-feature-engineeringSkill
- long-running-agentsSkill
- community-engagementSkill
- content-marketingSkill
- email-nurtureSkill
- growth-strategySkill
- paid-adsSkill
- referral-loopSkill
- seo-growthSkill
- social-distributionSkill
- micro-interactionsSkill
- migration-pathSkill
- observabilitySkill
- orchestrated-deliverySkill
- parallel-subagentsSkill
- perf-budgetSkill
- pipeline-opsSkill
- product-briefSkill
- product-discoverySkill
- product-groomingSkill
- react-patternsSkill
- resilienceSkill
- review-gateSkill
- simplifySkill
- skill-creatorSkill
- skill-harvestSkill
- skill-routerSkill
- source-firstSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 87
No error state on failed API
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Mobile Patterns
Mobile is not a narrow website — offline, battery, app store rules, and platform conventions matter. This skill covers cross-platform mobile delivery; web-specific UI stays in [[ui-craft]] and [[react-patterns]].
Pairs with [[ux-design]] for flows, [[test-first]] / [[e2e-testing]] for device tests, [[perf-budget]] for startup and jank, [[hardening]] for secure storage, and [[launch-readiness]] for store releases.
When to Use
- Building React Native, Flutter, or native mobile features
- Navigation, deep links, or app state issues
- Offline/sync behavior
- Push notifications
- App store submission prep
- Mobile performance (startup, list scroll, memory)
Skip for responsive web-only — use [[ui-craft]] and [[react-patterns]].
Process
1. Platform scope
Document:
- Framework — RN, Flutter, Swift, Kotlin
- Min OS versions — iOS / Android
- Offline requirement — read-only vs read-write offline
2. Navigation architecture
- One primary navigation pattern (tabs, stack, drawer — not all three)
- Deep links map to screens with auth guard
- Back behavior matches platform (Android back, iOS swipe)
- Modal vs push — modals for short tasks only
3. State and data
- API client with timeout/retry ([[resilience]])
- Optimistic UI where safe; rollback on failure
- Secure token storage (Keychain/Keystore — never AsyncStorage for secrets)
- Cache strategy for offline read ([[caching-strategy]])
4. Performance
| Area | Target |
| Cold start | <2s to interactive |
| List scroll | 60fps; virtualized lists |
| Images | Sized, cached, WebP where supported |
| Bundle | Monitor size per release |
Profile on real device, not simulator only.
5. Push and permissions
- Request permission in context — after user sees value
- Handle denied permission gracefully
- Payload → deep link to relevant screen
- Unsubscribe / notification settings in app
6. Release checklist
- Version/build number bumped
- Store screenshots and metadata ([[technical-writing]])
- Privacy nutrition labels / Data safety form accurate
- Crash reporting wired ([[observability]])
- Staged rollout (Play %) / TestFlight before 100%
Common Rationalizations
- "Mobile web is enough" — Push, offline, and store discovery need native/hybrid.
- "Works on my iPhone" — Test Android mid-range and small screens.
- "We’ll add offline later" — Network assumptions break on subway and flights.
Red Flags
- Secrets in plain storage
- WebView for entire app (store rejection risk)
- No error state on failed API
- Lists without virtualization (1000+ items)
- Push permission on first launch before value
Verification
- Navigation and deep links documented
- Token storage uses secure platform APIs
- Offline behavior defined and tested
- Performance checked on real device
- Store release checklist passed for ship
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.