mobile-platform-operations
Cross-platform mobile operations orchestration for app icons, mobile RBAC, SaaS planning, Play Store review, and operational mobile delivery assets.
Best use case
mobile-platform-operations is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Cross-platform mobile operations orchestration for app icons, mobile RBAC, SaaS planning, Play Store review, and operational mobile delivery assets.
Teams using mobile-platform-operations should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/mobile-platform-operations/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How mobile-platform-operations Compares
| Feature / Agent | mobile-platform-operations | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Cross-platform mobile operations orchestration for app icons, mobile RBAC, SaaS planning, Play Store review, and operational mobile delivery assets.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Mobile Platform Operations Acknowledgement: Shared by Peter Bamuhigire, techguypeter.com, +256 784 464178. <!-- dual-compat-start --> ## Use When - Planning or reviewing mobile delivery assets that span Android/iOS operations, app packaging, custom icons, RBAC, SaaS companion planning, or Google Play readiness. - The task references `mobile-custom-icons`, `mobile-rbac`, `mobile-saas-planning`, or `google-play-store-review`. - A mobile project needs operational documentation, app-store evidence, or cross-platform implementation coordination. ## Do Not Use When - The task is platform implementation only; use `android-development`, `ios-development`, or `kmp-development`. - The task is only report UI; use `mobile-reports`. - The task is iOS-only App Store release; use `ios-quality-and-release`. ## Required Inputs - Target platforms, app distribution channels, icon/asset constraints, auth/RBAC model, SaaS backend assumptions, release timeline, and store policy obligations. ## Workflow 1. Load platform implementation skills first: `android-development`, `ios-development`, or `kmp-development`. 2. Choose the operations concern: icon assets, mobile RBAC, SaaS planning, or Play Store review. 3. Load only the relevant reference below. 4. Produce the operational artifact, checklist, implementation guidance, or review evidence required for launch. ## Quality Standards - Operational mobile work must be traceable: asset names, permissions, store evidence, release notes, and backend/API assumptions should be explicit. - RBAC and SaaS plans must keep backend authority, offline behaviour, and platform UX states clear. - Store review guidance must include privacy, permissions, policy risk, testing, and rollback notes. ## Anti-Patterns - Treating store review, icons, and RBAC as last-minute polish. - Shipping mobile apps without documented backend contracts and offline/error-state expectations. - Using icon libraries where a project explicitly requires custom PNG assets. ## Outputs - Mobile operations checklist, app asset manifest, RBAC matrix, SaaS companion app plan, Play Store review checklist, or release evidence. ## References - `references/mobile-custom-icons.md` for custom PNG icon naming, asset directories, and tracking. - `references/mobile-rbac.md` for Android/cross-platform permission gates and offline authorization caches. - `references/mobile-saas-planning.md` for native mobile SaaS planning documents and implementation sequencing. - `references/google-play-store-review.md` for Android Play Store policy, testing, listing, and submission readiness. <!-- dual-compat-end -->
Related Skills
ios-platform-capabilities
iOS platform capability orchestration for biometrics, Bluetooth printing, push notifications, native PDF export, and production networking.
gis-platform-engineering
Use when implementing GIS maps, spatial data services, maps integrations, geocoding, spatial APIs, or PostGIS-backed geospatial platforms. Load absorbed GIS mapping, maps integration, and PostGIS backend references as needed.
kubernetes-platform
Use when running Kubernetes as a platform team — bootstrapping self-managed clusters on Debian/Ubuntu, designing multi-tenant RBAC, enforcing Pod Security and resource quotas, and operating cluster lifecycle (upgrades, certs, etcd, ingress, cert-manager, metrics-server). Self-managed first, cloud-managed second.
postgresql-operations
Use when administering, tuning, backing up, restoring, monitoring, or troubleshooting PostgreSQL production systems. Load the absorbed PostgreSQL administration and performance reference files for operational runbooks, query tuning, vacuum, replication, and incident response.
mysql-operations
Use when administering, tuning, backing up, restoring, monitoring, or troubleshooting MySQL production systems. Load absorbed MySQL administration and query-performance reference files for operational runbooks, indexes, replication, and incident response.
ai-agent-commercial-operations
Use when pricing, billing, refunding, recognizing revenue, or packaging commercial terms for agentic AI services and outcomes.
web-app-security-audit
Use when auditing a PHP/JavaScript/HTML web application for security vulnerabilities. Covers configuration, authentication, authorization, input validation, XSS, API security, HTTP headers, and dependency scanning. Produces a severity-rated audit...
vibe-security-skill
Use when designing or reviewing security for a web application, API, or multi-tenant SaaS — produces threat model, abuse case list, auth/authz matrix, and secret handling plan; covers OWASP Top 10 2025 and the AI-code-generation blind spots. Neighbours — api-design-first owns auth model fields, deployment-release-engineering owns secret rotation choreography, ai-security and llm-security own model-specific threats.
network-security
Use when designing, hardening, or auditing network-layer security for self-managed Debian/Ubuntu SaaS infrastructure — firewalls (nftables/UFW), WAF (ModSecurity + OWASP CRS), VPN (WireGuard, OpenVPN, IPsec), TLS/PKI ops, IDS/IPS (Suricata, Fail2ban), zero-trust, SSH hardening, DDoS mitigation, DNS security. Complements web-app-security-audit (app layer) and cicd-devsecops (secrets/CI).
linux-security-hardening
Use when hardening a Debian/Ubuntu server — user/group/sudo hardening, file permission audits, PAM password policy + MFA, AppArmor mandatory access control, auditd system call logging, kernel sysctl hardening, file integrity monitoring (AIDE), rootkit detection (rkhunter/chkrootkit), unattended security patching, GRUB + UEFI + LUKS boot security, and CIS benchmark compliance.
dpia-generator
Generate a Data Protection Impact Assessment (DPIA), Uganda DPPA 2019-compliant. Use when producing or reviewing a data protection impact assessment, a privacy impact assessment, when uganda-dppa-compliance flags [DPIA-REQUIRED], or when processing large-scale or sensitive personal data for a new feature.
code-safety-scanner
Scan any codebase for 14 critical safety issues across security vulnerabilities, server stability (500 errors), and payment misconfigurations. Use when auditing code before deployment, reviewing AI-generated code for production readiness, or...