Agent skill · software engineering · rmyndharis
multi-platform-apps-multi-platform
Build and deploy the same feature consistently across web, mobile, and desktop platforms using API-first architecture and parallel implementation strategies.
Why this skill is useful
Adds detailed API design and cross-platform architecture patterns that the AI wouldn't reliably generate on its own.
What it needs
About 5k tokens when loaded. Last updated 2026-08-02. 1,255 stars on the source repository.
What this skill does
Multi-Platform Feature Development Workflow Build and deploy the same feature consistently across web, mobile, and desktop platforms using API-first architecture and parallel implementation strategies. [Extended thinking: This workflow orchestrates multiple specialized agents to ensure feature parity across platforms while maintaining platform-specific optimizations. The coordination strategy emphasizes shared contracts and parallel development with regular synchronization points. By establishing API contracts and data models upfront, teams can work independently while ensuring consistency. The workflow benefits include faster time-to-market, reduced integration issues, and maintainable cross-platform codebases.] Use this skill when Working on multi-platform feature development workflow tasks or workflows Needing guidance, best practices, or checklists for multi-platform feature development workflow Do not use this skill when The task is unrelated to multi-platform feature development workflow You need a different domain or tool outside this scope Instructions Clarify goals, constraints, and required inputs. Apply relevant best practices and validate outcomes. Provide actionable steps and verification. Phase 1: Architecture and API Design (Sequential) 1. Define Feature Requirements and API Contracts Use Task tool with subagenttype="backend-architect" Prompt: "Design the API contract for feature: $ARGUMENTS. Create OpenAPI 3.1 specification with: RESTful endpoints with proper HTTP methods and status codes GraphQL schema if applicable for complex data queries WebSocket events for real-time features Request/response schemas with validation rules Authentication and authorization requirements Rate limiting and caching strategies Error response formats and codes Define shared data models that all platforms will consume." Expected output: Complete API specification, data models, and integration guidelines 2. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills rmyndharis/multi-platform-apps-multi-platform