ecosystem-mobile
Skill7 starsChanged 43 days agoMITView on GitHub
Route mobile app work — pre-release audits, store submission, feature architecture, crash investigation — through the right fth-skills mobile skills in order. Use when the user wants to audit an app before launch, ship to the App Store or Play Store, build deep links, push, offline or onboarding features, fix crashes, or asks which mobile skills to use.
In this repository83 other files it gives its agents.
- AGENTS.mdAGENTS.md
- accessibility-enforcerSkill
- access-policy-designerSkill
- adaptive-guardSkill
- agent-reviewerSkill
- anti-ai-slop-designSkill
- api-mock-designerSkill
- api-observability-plannerSkill
- app-store-reviewerSkill
- ask-first-act-laterSkill
- assumption-checkerSkill
- auth-flow-designerSkill
- b2b-founder-roadmapSkill
- brand-name-labSkill
- breaking-change-detectorSkill
- changelog-generatorSkill
- checkpoint-guardianSkill
- claude-style-codingSkill
- claw-integration-designSkill
- context-compressorSkill
- contract-first-designerSkill
- coolify-orchestratorSkill
- crash-analystSkill
- data-lineage-tracerSkill
- data-maskerSkill
- deep-link-architectSkill
- design-intelligenceSkill
- design-md-enforcerSkill
- ecosystem-apiSkill
- ecosystem-databaseSkill
- ecosystem-orchestrationSkill
- ecosystem-productSkill
- ecosystem-reasoningSkill
- ecosystem-securitySkill
- ecosystem-webSkill
- error-recoverySkill
- fth-design-crafterSkill
- geo-auditorSkill
- geo-optimizerSkill
- index-advisorSkill
- jev-orchestratorSkill
- mastermind-loggerSkill
- memory-ledgerSkill
- migration-strategistSkill
- mobile-perf-auditorSkill
- mobile-security-auditorSkill
- multi-brain-debateSkill
- multi-brain-expertsSkill
- multi-brain-scoreSkill
- multi-brainSkill
- offline-sync-designerSkill
- onboarding-designerSkill
- output-criticSkill
- parallel-plannerSkill
- pgbouncer-architectSkill
- plan-hardenerSkill
- plan-implement-verify-recoverSkill
- proje-analizcisiSkill
- project-analyzerSkill
- project-focus-firstSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
6 rules. About 0 are common, 2 are distinctive, and 4 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
4
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 34
Follow this protocol whenever this ecosystem is invoked.
- Very specific: line 40
Execute: Run steps in order. Steps that share a parallel group are independent and may run concurrently (@parallel-planner).
- Very specific: line 41
Gates: Before any destructive, irreversible, or production-impacting action, stop at @checkpoint-guardian, or ask for explicit confirmation …
- Very specific: line 42
Failures: When a step misses its *Done when*, hand off to @error-recovery.
- Very specific: line 43
State: Keep a run log (workflow id, step, status, artifact).
- Distinctive: line 46
Skip this protocol: when the user names one specific skill (invoke it directly) or asks a quick factual question that needs no workflow.
≈ “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 Ecosystem
This skill is the entry point of its ecosystem. It chooses a workflow, checks which member skills are installed, runs them in order with explicit handoffs, and degrades gracefully when a member is missing. The workflow map lives in references/workflows.json; the handoff format lives in references/handoff-contract.md.
Catalog
<!-- BEGIN GENERATED: ecosystem-catalog (generated from the ecosystem workflow map by build_ecosystems.py — do not edit by hand) -->Domain: Mobile App Domain — Architect, audit, release, and monitor iOS, Android, React Native, and Flutter apps.
Philosophy: Mobile apps live under store guidelines, limited battery and memory, and unreliable networks. Never ship a feature that regresses performance, security, or accessibility.
| Skill | Role | Handoff artifact |
@accessibility-enforcer | Audits VoiceOver/TalkBack support and WCAG mobile criteria. | inline handoff block |
@mobile-perf-auditor | Diagnoses cold start, frame drops, memory, battery, and bundle size. | inline handoff block |
@mobile-security-auditor | Audits against OWASP Mobile Top 10: storage, network, runtime defenses. | inline handoff block |
@app-store-reviewer | Checks App Store and Play Store guideline compliance and metadata. | inline handoff block |
@release-orchestrator | Plans versioning, changelogs, beta tracks, and staged rollouts. | inline handoff block |
@deep-link-architect | Designs Universal Links and App Links with fallbacks. | inline handoff block |
@push-notification-planner | Designs APNs/FCM payloads, permission timing, and routing. | inline handoff block |
@offline-sync-designer | Designs local-first storage, conflict resolution, and background sync. | inline handoff block |
@onboarding-designer | Designs first-run experience, permission sequencing, and empty states. | inline handoff block |
@crash-analyst | Symbolicates and analyzes crash reports to a root cause and fix. | inline handoff block |
<!-- END GENERATED: ecosystem-catalog -->Router Protocol
<!-- BEGIN GENERATED: ecosystem-router (generated from the ecosystem workflow map by build_ecosystems.py — do not edit by hand) -->Follow this protocol whenever this ecosystem is invoked.
- Match. Compare the request with each workflow's When phrases. Pick one workflow, or route straight to a single member skill when the request is narrow. If two workflows fit equally, ask one question to choose. If the request belongs to another domain, use the ecosystem index in
@ecosystem-orchestration. - Preflight. Find out which step skills are installed: check the skills your host lists, or run
python <skill-dir>/scripts/install_all.py --status --workflow <id>(<skill-dir>is the folder containing thisSKILL.md). Show a short plan: step, skill, installed or missing, condition, expected artifact. - Missing skills never block. Offer once: (a) install them —
install_all.py --workflow <id>prints the commands and only runs them with--executeafter the user agrees; or (b) continue in fallback mode — perform the step yourself using its Does and Done when columns and label that outputfallback. - Conditions. Skip optional steps whose condition does not hold, and say which steps you skipped and why.
- Execute. Run steps in order. Steps that share a parallel group are independent and may run concurrently (
@parallel-planner). Pass artifacts as described inreferences/handoff-contract.md. Check each step's Done when before moving on. - Gates. Before any destructive, irreversible, or production-impacting action, stop at
@checkpoint-guardian, or ask for explicit confirmation when it is not installed. - Failures. When a step misses its Done when, hand off to
@error-recovery. Without it, retry once with a changed approach, then report the blocker with evidence instead of guessing. - State. Keep a run log (workflow id, step, status, artifact). Record it with
@memory-ledgerwhen installed, and write a@session-transferhandoff if the run will continue in another session. - Finish. Summarize artifacts, skipped steps, open risks, and the most relevant next workflow.
Skip this protocol when the user names one specific skill (invoke it directly) or asks a quick factual question that needs no workflow.
<!-- END GENERATED: ecosystem-router -->Workflows
<!-- BEGIN GENERATED: ecosystem-workflows (generated from the ecosystem workflow map by build_ecosystems.py — do not edit by hand) -->1. Pre-Release Audit Flow (mobile-pre-release-audit)
When: “audit the app before launch”; “is the app ready”; “review mobile app quality”
| # | Skill | Does | Done when | Condition | Parallel group |
| 1 | @accessibility-enforcer | Audit screen reader labels, touch targets, and contrast. | No critical accessibility issue remains open. | — | audit |
| 2 | @mobile-perf-auditor | Audit startup, rendering, memory, and bundle size. | Key metrics are within the stated budgets. | — | audit |
| 3 | @mobile-security-auditor | Audit storage, transport, secrets, and runtime defenses. | No critical OWASP Mobile finding remains open. | — | audit |
2. Production Release Flow (mobile-release)
When: “ship to the stores”; “prepare the release”; “submit to App Store or Play Store”
| # | Skill | Does | Done when | Condition | Parallel group |
| 1 | @app-store-reviewer | Check guidelines, privacy disclosures, and store metadata. | No rejection-risk item remains open. | Run the Pre-Release Audit Flow first | — |
| 2 | @release-orchestrator | Bump versions, write notes, and plan beta and staged rollout. | Rollout stages, halt criteria, and notes are ready. | — | — |
| 3 | @checkpoint-guardian | Confirm before submitting to the stores or widening a rollout. | User explicitly approved the submission. | — | — |
3. Feature Architecture Flow (mobile-feature-architecture)
When: “build a mobile feature”; “add deep links”; “add push notifications”; “make the app work offline”
| # | Skill | Does | Done when | Condition | Parallel group |
| 1 | @deep-link-architect (optional) | Design URL schema, association files, and in-app routing. | Links open the right screen on both platforms with a web fallback. | Feature needs deep links | feature |
| 2 | @push-notification-planner (optional) | Design payloads, permission timing, and tap routing. | Payload, permission, and analytics plan exist. | Feature needs push notifications | feature |
| 3 | @offline-sync-designer (optional) | Design local storage, optimistic UI, and conflict resolution. | Every entity has a sync and conflict policy. | Feature must work offline | feature |
| 4 | @onboarding-designer (optional) | Design first-run flow and permission sequencing. | Aha moment, permissions, and empty states are defined. | Feature changes first-run experience | feature |
4. Post-Launch Monitoring Flow (mobile-post-launch)
When: “fix crashes”; “investigate app issues”; “analyze crash reports”
| # | Skill | Does | Done when | Condition | Parallel group |
| 1 | @crash-analyst | Symbolicate, isolate the exception, and propose a fix. | Root cause and fix are identified. | — | — |
| 2 | @mobile-perf-auditor (optional) | Profile the regression when the root cause is performance (ANR, OOM, jank). | Performance fix is verified. | Root cause is performance-related | — |
| 3 | @release-orchestrator (optional) | Plan a hotfix release. | Hotfix version and rollout plan exist. | — | — |
Direct handoffs
@push-notification-planner→@deep-link-architect: Notification taps must open a specific screen.@mobile-security-auditor→@auth-flow-designer: Findings involve token storage or backend auth design.@offline-sync-designer→@sqlite: Local storage is SQLite-based.
<!-- END GENERATED: ecosystem-workflows -->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.