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.
- If detailed examples are required, open
resources/implementation-playbook.md.
Phase 1: Architecture and API Design (Sequential)
1. Define Feature Requirements and API Contracts
- Use Task tool with subagent_type="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. Design System and UI/UX Consistency
- Use Task tool with subagent_type="ui-ux-designer"
- Prompt: "Create cross-platform design system for feature using API spec: [previous output]. Include:
- Component specifications for each platform (Material Design, iOS HIG, Fluent)
- Responsive layouts for web (mobile-first approach)
- Native patterns for iOS (SwiftUI) and Android (Material You)
- Desktop-specific considerations (keyboard shortcuts, window management)
- Accessibility requirements (WCAG 2.2 Level AA)
- Dark/light theme specifications
- Animation and transition guidelines"
- Context from previous: API endpoints, data structures, authentication flows
- Expected output: Design system documentation, component library specs, platform guidelines
3. Shared Business Logic Architecture
- Use Task tool with subagent_type="comprehensive-review::architect-review"
- Prompt: "Design shared business logic architecture for cross-platform feature. Define:
- Core domain models and entities (platform-agnostic)
- Business rules and validation logic
- State management patterns (MVI/Redux/BLoC)
- Caching and offline strategies
- Error handling and retry policies
- Platform-specific adapter patterns
Consider Kotlin Multiplatform for mobile or TypeScript for web/desktop sharing."
- Context from previous: API contracts, data models, UI requirements
- Expected output: Shared code architecture, platform abstraction layers, implementation guide
Phase 2: Parallel Platform Implementation
4a. Web Implementation (React/Next.js)
- Use Task tool with subagent_type="frontend-developer"
- Prompt: "Implement web version of feature using:
- React 18+ with Next.js 14+ App Router
- TypeScript for type safety
- TanStack Query for API integration: [API spec]
- Zustand/Redux Toolkit for state management
- Tailwind CSS with design system: [design specs]
- Progressive Web App capabilities
- SSR/SSG optimization where appropriate
- Web vitals optimization (LCP < 2.5s, INP ≤ 200ms)
Follow shared business logic: [architecture doc]"
- Context from previous: API contracts, design system, shared logic patterns
- Expected output: Complete web implementation with tests
4b. iOS Implementation (SwiftUI)
- Use Task tool with subagent_type="ios-developer"
- Prompt: "Implement iOS version using:
- SwiftUI with iOS 17+ features
- Swift 5.9+ with async/await
- URLSession with Combine for API: [API spec]
- Core Data/SwiftData for persistence
- Design system compliance: [iOS HIG specs]
- Widget extensions if applicable
- Platform-specific features (Face ID, Haptics, Live Activities)
- Testable MVVM architecture
Follow shared patterns: [architecture doc]"
- Context from previous: API contracts, iOS design guidelines, shared models
- Expected output: Native iOS implementation with unit/UI tests
4c. Android Implementation (Kotlin/Compose)
- Use Task tool with subagent_type="mobile-developer"
- Prompt: "Implement Android version using:
- Jetpack Compose with Material 3
- Kotlin coroutines and Flow
- Retrofit/Ktor for API: [API spec]
- Room database for local storage
- Hilt for dependency injection
- Material You dynamic theming: [design specs]
- Platform features (biometric auth, widgets)
- Clean architecture with MVI pattern
Follow shared logic: [architecture doc]"
- Context from previous: API contracts, Material Design specs, shared patterns
- Expected output: Native Android implementation with tests
4d. Desktop Implementation (Optional - Electron/Tauri)
- Use Task tool with subagent_type="frontend-mobile-development::frontend-developer"
- Prompt: "Implement desktop version using Tauri 2.0 or Electron with:
- Shared web codebase where possible
- Native OS integration (system tray, notifications)
- File system access if needed
- Auto-updater functionality
- Code signing and notarization setup
- Keyboard shortcuts and menu bar
- Multi-window support if applicable
Reuse web components: [web implementation]"
- Context from previous: Web implementation, desktop-specific requirements
- Expected output: Desktop application with platform packages
Phase 3: Integration and Validation
5. API Documentation and Testing
- Use Task tool with subagent_type="documentation-generation::api-documenter"
- Prompt: "Create comprehensive API documentation including:
- Interactive OpenAPI/Swagger documentation
- Platform-specific integration guides
- SDK examples for each platform
- Authentication flow diagrams
- Rate limiting and quota information
- Postman/Insomnia collections
- WebSocket connection examples
- Error handling best practices
- API versioning strategy
Test all endpoints with platform implementations."
- Context from previous: Implemented platforms, API usage patterns
- Expected output: Complete API documentation portal, test results
6. Cross-Platform Testing and Feature Parity
- Use Task tool with subagent_type="unit-testing::test-automator"
- Prompt: "Validate feature parity across all platforms:
- Functional testing matrix (features work identically)
- UI consistency verification (follows design system)
- Performance benchmarks per platform
- Accessibility testing (platform-specific tools)
- Network resilience testing (offline, slow connections)
- Data synchronization validation
- Platform-specific edge cases
- End-to-end user journey tests
Create test report with any platform discrepancies."
- Context from previous: All platform implementations, API documentation
- Expected output: Test report, parity matrix, performance metrics
7. Platform-Specific Optimizations
- Use Task tool with subagent_type="application-performance::performance-engineer"
- Prompt: "Optimize each platform implementation:
- Web: Bundle size, lazy loading, CDN setup, SEO
- iOS: App size, launch time, memory usage, battery
- Android: APK size, startup time, frame rate, battery
- Desktop: Binary size, resource usage, startup time
- API: Response time, caching, compression
Maintain feature parity while leveraging platform strengths.
Document optimization techniques and trade-offs."
- Context from previous: Test results, performance metrics
- Expected output: Optimized implementations, performance improvements
Configuration Options
- --platforms: Specify target platforms (web,ios,android,desktop)
- --api-first: Generate API before UI implementation (default: true)
- --shared-code: Use Kotlin Multiplatform or similar (default: evaluate)
- --design-system: Use existing or create new (default: create)
- --testing-strategy: Unit, integration, e2e (default: all)
Success Criteria
- API contract defined and validated before implementation
- All platforms pass the agreed observable behavior matrix; document intentional differences
- Performance metrics meet platform-specific standards
- Accessibility standards met (WCAG 2.2 AA minimum)
- Cross-platform testing shows consistent behavior
- Documentation complete for all platforms
- Measure code reuse only where useful; do not sacrifice native behavior to reach an arbitrary percentage
- User experience optimized for each platform's conventions
Platform-Specific Considerations
Web: PWA capabilities, SEO optimization, browser compatibility
iOS: App Store guidelines, TestFlight distribution, iOS-specific features
Android: Play Store requirements, Android App Bundles, device fragmentation
Desktop: Code signing, auto-updates, OS-specific installers
Initial feature specification: $ARGUMENTS
Example
User request:
Build and deploy the same feature consistently across web, mobile, and desktop platforms using API-first architecture and parallel implementation strategies.
Limitations
- Use this skill only when the task clearly matches the scope described above.
- Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
- Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.
1---2name: multi-platform-apps-multi-platform3description: Build and deploy the same feature consistently across web, mobile, and desktop platforms using API-first architecture and parallel implementation strategies.4metadata:5 source: https://skillmd.com/skills/sickn33/multi-platform-apps-multi-platform6 aas-risk: critical7 aas-source: community8 aas-date-added: '2026-02-27'9---1011# Multi-Platform Feature Development Workflow1213Build and deploy the same feature consistently across web, mobile, and desktop platforms using API-first architecture and parallel implementation strategies.1415[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.]1617## Use this skill when1819- Working on multi-platform feature development workflow tasks or workflows20- Needing guidance, best practices, or checklists for multi-platform feature development workflow2122## Do not use this skill when2324- The task is unrelated to multi-platform feature development workflow25- You need a different domain or tool outside this scope2627## Instructions2829- Clarify goals, constraints, and required inputs.30- Apply relevant best practices and validate outcomes.31- Provide actionable steps and verification.32- If detailed examples are required, open `resources/implementation-playbook.md`.3334## Phase 1: Architecture and API Design (Sequential)3536### 1. Define Feature Requirements and API Contracts37- Use Task tool with subagent_type="backend-architect"38- Prompt: "Design the API contract for feature: $ARGUMENTS. Create OpenAPI 3.1 specification with:39 - RESTful endpoints with proper HTTP methods and status codes40 - GraphQL schema if applicable for complex data queries41 - WebSocket events for real-time features42 - Request/response schemas with validation rules43 - Authentication and authorization requirements44 - Rate limiting and caching strategies45 - Error response formats and codes46 Define shared data models that all platforms will consume."47- Expected output: Complete API specification, data models, and integration guidelines4849### 2. Design System and UI/UX Consistency50- Use Task tool with subagent_type="ui-ux-designer"51- Prompt: "Create cross-platform design system for feature using API spec: [previous output]. Include:52 - Component specifications for each platform (Material Design, iOS HIG, Fluent)53 - Responsive layouts for web (mobile-first approach)54 - Native patterns for iOS (SwiftUI) and Android (Material You)55 - Desktop-specific considerations (keyboard shortcuts, window management)56 - Accessibility requirements (WCAG 2.2 Level AA)57 - Dark/light theme specifications58 - Animation and transition guidelines"59- Context from previous: API endpoints, data structures, authentication flows60- Expected output: Design system documentation, component library specs, platform guidelines6162### 3. Shared Business Logic Architecture63- Use Task tool with subagent_type="comprehensive-review::architect-review"64- Prompt: "Design shared business logic architecture for cross-platform feature. Define:65 - Core domain models and entities (platform-agnostic)66 - Business rules and validation logic67 - State management patterns (MVI/Redux/BLoC)68 - Caching and offline strategies69 - Error handling and retry policies70 - Platform-specific adapter patterns71 Consider Kotlin Multiplatform for mobile or TypeScript for web/desktop sharing."72- Context from previous: API contracts, data models, UI requirements73- Expected output: Shared code architecture, platform abstraction layers, implementation guide7475## Phase 2: Parallel Platform Implementation7677### 4a. Web Implementation (React/Next.js)78- Use Task tool with subagent_type="frontend-developer"79- Prompt: "Implement web version of feature using:80 - React 18+ with Next.js 14+ App Router81 - TypeScript for type safety82 - TanStack Query for API integration: [API spec]83 - Zustand/Redux Toolkit for state management84 - Tailwind CSS with design system: [design specs]85 - Progressive Web App capabilities86 - SSR/SSG optimization where appropriate87 - Web vitals optimization (LCP < 2.5s, INP ≤ 200ms)88 Follow shared business logic: [architecture doc]"89- Context from previous: API contracts, design system, shared logic patterns90- Expected output: Complete web implementation with tests9192### 4b. iOS Implementation (SwiftUI)93- Use Task tool with subagent_type="ios-developer"94- Prompt: "Implement iOS version using:95 - SwiftUI with iOS 17+ features96 - Swift 5.9+ with async/await97 - URLSession with Combine for API: [API spec]98 - Core Data/SwiftData for persistence99 - Design system compliance: [iOS HIG specs]100 - Widget extensions if applicable101 - Platform-specific features (Face ID, Haptics, Live Activities)102 - Testable MVVM architecture103 Follow shared patterns: [architecture doc]"104- Context from previous: API contracts, iOS design guidelines, shared models105- Expected output: Native iOS implementation with unit/UI tests106107### 4c. Android Implementation (Kotlin/Compose)108- Use Task tool with subagent_type="mobile-developer"109- Prompt: "Implement Android version using:110 - Jetpack Compose with Material 3111 - Kotlin coroutines and Flow112 - Retrofit/Ktor for API: [API spec]113 - Room database for local storage114 - Hilt for dependency injection115 - Material You dynamic theming: [design specs]116 - Platform features (biometric auth, widgets)117 - Clean architecture with MVI pattern118 Follow shared logic: [architecture doc]"119- Context from previous: API contracts, Material Design specs, shared patterns120- Expected output: Native Android implementation with tests121122### 4d. Desktop Implementation (Optional - Electron/Tauri)123- Use Task tool with subagent_type="frontend-mobile-development::frontend-developer"124- Prompt: "Implement desktop version using Tauri 2.0 or Electron with:125 - Shared web codebase where possible126 - Native OS integration (system tray, notifications)127 - File system access if needed128 - Auto-updater functionality129 - Code signing and notarization setup130 - Keyboard shortcuts and menu bar131 - Multi-window support if applicable132 Reuse web components: [web implementation]"133- Context from previous: Web implementation, desktop-specific requirements134- Expected output: Desktop application with platform packages135136## Phase 3: Integration and Validation137138### 5. API Documentation and Testing139- Use Task tool with subagent_type="documentation-generation::api-documenter"140- Prompt: "Create comprehensive API documentation including:141 - Interactive OpenAPI/Swagger documentation142 - Platform-specific integration guides143 - SDK examples for each platform144 - Authentication flow diagrams145 - Rate limiting and quota information146 - Postman/Insomnia collections147 - WebSocket connection examples148 - Error handling best practices149 - API versioning strategy150 Test all endpoints with platform implementations."151- Context from previous: Implemented platforms, API usage patterns152- Expected output: Complete API documentation portal, test results153154### 6. Cross-Platform Testing and Feature Parity155- Use Task tool with subagent_type="unit-testing::test-automator"156- Prompt: "Validate feature parity across all platforms:157 - Functional testing matrix (features work identically)158 - UI consistency verification (follows design system)159 - Performance benchmarks per platform160 - Accessibility testing (platform-specific tools)161 - Network resilience testing (offline, slow connections)162 - Data synchronization validation163 - Platform-specific edge cases164 - End-to-end user journey tests165 Create test report with any platform discrepancies."166- Context from previous: All platform implementations, API documentation167- Expected output: Test report, parity matrix, performance metrics168169### 7. Platform-Specific Optimizations170- Use Task tool with subagent_type="application-performance::performance-engineer"171- Prompt: "Optimize each platform implementation:172 - Web: Bundle size, lazy loading, CDN setup, SEO173 - iOS: App size, launch time, memory usage, battery174 - Android: APK size, startup time, frame rate, battery175 - Desktop: Binary size, resource usage, startup time176 - API: Response time, caching, compression177 Maintain feature parity while leveraging platform strengths.178 Document optimization techniques and trade-offs."179- Context from previous: Test results, performance metrics180- Expected output: Optimized implementations, performance improvements181182## Configuration Options183184- **--platforms**: Specify target platforms (web,ios,android,desktop)185- **--api-first**: Generate API before UI implementation (default: true)186- **--shared-code**: Use Kotlin Multiplatform or similar (default: evaluate)187- **--design-system**: Use existing or create new (default: create)188- **--testing-strategy**: Unit, integration, e2e (default: all)189190## Success Criteria191192- API contract defined and validated before implementation193- All platforms pass the agreed observable behavior matrix; document intentional differences194- Performance metrics meet platform-specific standards195- Accessibility standards met (WCAG 2.2 AA minimum)196- Cross-platform testing shows consistent behavior197- Documentation complete for all platforms198- Measure code reuse only where useful; do not sacrifice native behavior to reach an arbitrary percentage199- User experience optimized for each platform's conventions200201## Platform-Specific Considerations202203**Web**: PWA capabilities, SEO optimization, browser compatibility204**iOS**: App Store guidelines, TestFlight distribution, iOS-specific features205**Android**: Play Store requirements, Android App Bundles, device fragmentation206**Desktop**: Code signing, auto-updates, OS-specific installers207208Initial feature specification: $ARGUMENTS209210## Example211212**User request:**213214> Build and deploy the same feature consistently across web, mobile, and desktop platforms using API-first architecture and parallel implementation strategies.215216## Limitations217- Use this skill only when the task clearly matches the scope described above.218- Do not treat the output as a substitute for environment-specific validation, testing, or expert review.219- Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.