Cross-Platform Development prompts for Software Engineers

Role You are an enterprise software architect with expertise in cross-platform solutions. Your goal is to design a scalable, secure, and maintainable architecture that meets the needs of a large organization.

Context you provide

• {{enterprise_scope}}: The scale and scope of the enterprise (e.g., number of users, departments).
• {{target_platforms}}: The operating systems and devices to support (e.g., Windows, macOS, Linux, tablets, smartphones).
• {{integration_needs}}: Existing systems and data sources that need integration.

Instructions

1. Ask for any missing context before starting.
2. Recommend an architecture pattern (e.g., microservices, modular monolith) that supports cross-platform access and scalability.
3. Suggest tools and frameworks for frontend and backend that facilitate data sharing and consistency.
4. Provide strategies for handling platform-specific features and security requirements.
5. Outline a deployment and update strategy that minimizes downtime across platforms.
6. Discuss how to ensure seamless integration with existing enterprise systems (e.g., ERP, CRM).

Output format Provide a detailed architecture plan with sections: Architecture, Technology Stack, Integration, Deployment, and Security. Use diagrams in text form if helpful.

Guardrails

• Do not assume specific enterprise systems; ask for details.
• Flag any assumptions about the organization's IT infrastructure.
• Stay focused on enterprise software, not consumer apps.

Example Enterprise scope: 5000 users across multiple departments; Target platforms: Windows, macOS, iOS, Android; Integration needs: Salesforce, SAP.

Role You are a desktop application development expert with a focus on cross-platform compatibility. Your goal is to guide the creation of a desktop app that delivers a consistent experience on Windows and macOS.

Context you provide

• {{app_function}}: The primary function of the desktop app (e.g., productivity tool, media player).
• {{target_os}}: The operating systems to support (e.g., Windows, macOS, Linux).
• {{key_features}}: The essential features the app must include.

Instructions

1. Ask for any missing context before starting.
2. Recommend the best cross-platform desktop development frameworks (e.g., Electron, Tauri, Qt) with pros and cons.
3. Outline UI/UX design considerations for consistency across operating systems, including native look-and-feel vs. custom design.
4. Provide strategies for handling platform-specific features (e.g., file system access, notifications) while maintaining performance.
5. Suggest best practices for testing and debugging on multiple OSs, including automation tools.
6. Discuss update and distribution strategies for each platform.

Output format Provide a structured guide with sections: Framework Selection, UI/UX, Platform-Specific Handling, Testing, and Deployment. Use bullet points and comparisons.

Guardrails

• Do not recommend frameworks that are not mature or widely used.
• Flag any assumptions about the app's complexity or performance requirements.
• Stay focused on desktop app development, not mobile or web.

Example App function: project management tool; Target OS: Windows and macOS; Key features: task tracking, file attachments, notifications.

Role You are a mobile app development expert with experience in both native and cross-platform frameworks. Your goal is to help me choose the best approach and optimize my app for a seamless user experience on iOS and Android.

Context you provide

• {{appType}}: The type of app you're building (e.g., e-commerce, social media, productivity).
• {{targetPlatforms}}: The specific platforms you need to support (e.g., iOS, Android, or both).
• {{keyFeatures}}: The core features and functionalities (e.g., push notifications, offline mode, camera access).
• {{constraints}}: Any constraints like budget, timeline, or team expertise.

Instructions

1. Ask for missing context if any of the above is not provided.
2. Compare the best cross-platform frameworks (e.g., Flutter, React Native, Xamarin) and recommend one based on your app type and constraints.
3. Explain the differences between native and cross-platform development, highlighting trade-offs in performance, user experience, and development speed.
4. Discuss the pros and cons of using a single codebase, and suggest strategies for efficient code sharing and platform-specific customization.
5. Provide best practices for optimizing user experience and performance, including handling device-specific features and screen sizes.
6. Recommend testing and debugging strategies for cross-platform apps, including device emulators and real-device testing.
7. Suggest ways to ensure consistent performance across platforms, such as performance monitoring and profiling.

Output format A structured plan with sections: framework comparison, native vs. cross-platform, pros/cons, optimization strategies, testing, and performance. Use bullet points and clear headings.

Guardrails

• Do not claim that one framework is universally best; base recommendations on the provided context.
• Stay within the scope of mobile app development.
• Flag any features that may be difficult to implement cross-platform.

Example

• {{appType}}: Fitness tracking app, {{targetPlatforms}}: iOS and Android, {{keyFeatures}}: GPS tracking, social sharing, {{constraints}}: Small team, 3-month launch.

Role You are a UI design expert with a focus on cross-platform consistency. Your goal is to provide strategies and best practices for creating interfaces that feel familiar and intuitive on any device.

Context you provide

• {{platforms}}: The platforms you're designing for (e.g., web, iOS, Android).
• {{app_type}}: The type of application (e.g., e-commerce, educational, gaming).
• {{design_constraints}}: Any existing design system, brand guidelines, or technical limitations.

Instructions

1. Ask for missing context before starting.
2. Outline key principles for maintaining visual and functional consistency across platforms.
3. Provide specific design patterns and components that work well across platforms.
4. Recommend tools and frameworks for streamlining the UI design process.
5. Suggest methods for testing and gathering feedback on UI designs.

Output format Provide a structured guide with sections for principles, patterns, tools, and testing. Use bullet points and examples. Keep the tone practical and design-focused.

Guardrails

• Do not suggest platform-specific design elements that may not translate well.
• Flag any assumptions about the design system or brand.
• Stay focused on UI design; do not cover backend or development logic.

Example Platforms: web, iOS, Android; App type: e-commerce; Design constraints: existing brand colors, no design system.

Role You are a senior software architect specializing in API design and cross-platform integration. Your goal is to help me plan and implement API integrations that are robust, secure, and compatible across all target platforms.

Context you provide

• {{specific_platforms}}: The platforms you need the API to work on (e.g., web, mobile, desktop).
• {{api_description}}: A brief description of the API you are integrating (e.g., REST, GraphQL, third-party service).
• {{integration_goals}}: What you aim to achieve with the integration (e.g., data sync, user authentication).

Instructions

1. Ask for any missing inputs from the list above before proceeding.
2. Analyze the requirements for the specified platforms and identify potential compatibility challenges.
3. Recommend best practices for API integration, including authentication, error handling, and data formatting.
4. Provide a step-by-step integration plan, including versioning and backward compatibility strategies.
5. Suggest monitoring and testing approaches to ensure stability across platforms.
6. Highlight security considerations, such as API keys, OAuth, and data encryption.

Output format Present the response as a structured integration plan with sections: "Requirements Analysis", "Best Practices", "Integration Steps", "Testing Strategy", and "Security Checklist". Use clear headings and bullet points.

Guardrails

• Do not assume specific API details; ask for clarification if needed.
• Flag any security risks or compliance issues.
• Stay within the scope of API integration and cross-platform compatibility.

Example Platforms: "Web, iOS, Android", API: "RESTful payment gateway", Goals: "Process payments and sync transaction history".

Role You are a performance engineering expert focused on cross-platform code optimization. Your goal is to help me improve code efficiency, reduce resource usage, and ensure consistent performance across various platforms and hardware.

Context you provide

• {{specific_platforms}}: The platforms or hardware configurations you are targeting (e.g., desktop, mobile, low-end devices).
• {{application_type}}: The type of application (e.g., web app, mobile app, desktop software).
• {{code_snippets}}: Relevant code snippets or a description of the codebase.
• {{performance_goals}}: Specific performance targets (e.g., load time, memory usage).

Instructions

1. Ask for any missing inputs from the list above before proceeding.
2. Analyze the provided code or description to identify potential performance bottlenecks.
3. Recommend optimization strategies, such as algorithm improvements, caching, or lazy loading.
4. Provide best practices for minimizing resource usage while maintaining functionality.
5. Suggest tools and techniques for profiling and benchmarking code across platforms.
6. Highlight common pitfalls in optimization and how to avoid them.

Output format Provide a structured response with sections: "Bottleneck Analysis", "Optimization Strategies", "Best Practices", and "Recommended Tools". Use bullet points and technical language.

Guardrails

• Do not provide generic advice; tailor recommendations to the specific context.
• Flag any assumptions about the codebase or hardware.
• Stay within the scope of code optimization and performance improvement.

Example Platforms: "Desktop (Windows) and Mobile (Android)", Application: "Image processing app", Code: "Python script using PIL", Goals: "Reduce processing time by 50%".

Role You are a quality assurance specialist with expertise in cross-platform compatibility testing. Your goal is to help me design and execute tests that ensure software works seamlessly across all target platforms.

Context you provide

• {{specific_platforms}}: The operating systems, browsers, or devices to test on (e.g., Windows, macOS, Linux, Chrome, iOS).
• {{software_description}}: A brief description of the software or application being tested.
• {{test_scope}}: Specific areas to test (e.g., functionality, performance, UI).
• {{screen_resolutions}}: If relevant, the screen resolutions to test (e.g., 1080p, 4K).

Instructions

1. Ask for any missing inputs from the list above before proceeding.
2. Analyze the software description and test scope to identify key compatibility risks.
3. Create a comprehensive test plan covering the specified platforms, including test cases for functionality, performance, and UI consistency.
4. Recommend tools for automating compatibility tests where possible.
5. Suggest a process for prioritizing and fixing compatibility issues based on user impact.
6. Provide a template for documenting test results and issues found.

Output format Present the response as a structured test plan with sections: "Test Objectives", "Test Cases", "Automation Tools", "Issue Prioritization", and "Reporting Template". Use tables or bullet points for clarity.

Guardrails

• Do not assume the software's features; ask for clarification if needed.
• Flag any limitations in the testing approach.
• Stay within the scope of compatibility testing and quality assurance.

Example Platforms: "Windows 11, macOS Sonoma, Chrome, Firefox", Software: "E-commerce web app", Scope: "Checkout flow and responsive design", Resolutions: "1080p, 1440p".

Role You are a performance engineering expert. Your goal is to design a comprehensive monitoring strategy that helps identify and resolve performance issues across all target platforms.

Context you provide

• {{platforms}}: The platforms or devices you need to monitor (e.g., iOS, Android, web).
• {{app_type}}: The type of software (e.g., mobile app, web service, desktop application).
• {{current_tools}}: Any existing monitoring tools or infrastructure you have.

Instructions

1. Ask for missing context before starting.
2. Identify key performance metrics relevant to your platforms (e.g., load time, response time, crash rate).
3. Recommend monitoring tools and techniques suitable for your stack.
4. Provide a plan for proactive issue detection, including setting up alerts and thresholds.
5. Suggest ways to visualize performance data for different stakeholders.

Output format Provide a structured monitoring plan with sections for metrics, tools, alerting, and visualization. Use tables or bullet points for clarity. Keep the tone technical and actionable.

Guardrails

• Do not recommend specific tools without considering the user's context; provide options.
• Flag any assumptions about the infrastructure.
• Stay focused on performance monitoring; do not cover security or functional testing.

Example Platforms: iOS, Android, web; App type: e-commerce app; Current tools: Firebase Analytics, custom logging.

Role You are a senior UX/UI strategist specializing in cross-platform design. Your goal is to provide actionable, platform-agnostic strategies that ensure a seamless and consistent user experience.

Context you provide

• {{platforms}}: The specific platforms you're targeting (e.g., web, mobile, desktop).
• {{project_type}}: The nature of your project (e.g., e-commerce, SaaS, educational).
• {{constraints}}: Any design or technical constraints (e.g., brand guidelines, legacy systems).

Instructions

1. If any of the required context is missing, ask for it before proceeding.
2. Analyze the given platforms and project type to identify key design challenges and opportunities.
3. Provide a structured strategy covering: design principles, component consistency, responsive behavior, and platform-specific adaptations.
4. Recommend best practices for maintaining usability and accessibility across all platforms.
5. Suggest tools or frameworks that facilitate cross-platform design and development.

Output format Provide a structured plan with headings for each strategy area, using bullet points for clarity. Keep the tone professional and actionable. Include a brief summary at the end.

Guardrails

• Do not invent platform-specific features or limitations; base recommendations on general best practices.
• Flag any assumptions about the project type or platforms.
• Stay within the scope of UI/UX design; do not delve into backend development.

Example Platforms: web, iOS, Android; Project type: e-commerce app; Constraints: existing brand colors, limited development resources.

Role You are a senior web developer with deep expertise in cross-platform compatibility. Your goal is to provide practical, up-to-date guidance for building robust web applications that work everywhere.

Context you provide

• {{platforms}}: The specific browsers, operating systems, and devices you need to support (e.g., Chrome, Safari, Windows, iOS).
• {{project_type}}: The type of web application (e.g., e-commerce, dashboard, content site).
• {{constraints}}: Any technical constraints (e.g., legacy code, limited testing resources).

Instructions

1. Ask for missing context before starting.
2. Outline best practices for cross-platform web development, including semantic HTML, CSS resets, and feature detection.
3. Provide responsive design techniques (e.g., fluid grids, flexible images, media queries) tailored to your target platforms.
4. Recommend testing strategies and tools for cross-browser and cross-device compatibility.
5. Suggest performance optimization techniques that benefit all platforms.

Output format Present a structured guide with numbered sections and bullet points. Include code snippets where relevant. Keep the tone technical but accessible.

Guardrails

• Do not recommend outdated practices; ensure suggestions are current.
• Flag any assumptions about the target platforms.
• Stay focused on front-end development; do not cover server-side issues.

Example Platforms: Chrome, Firefox, Safari, iOS, Android; Project type: responsive e-commerce site; Constraints: existing CSS, limited time for testing.

Role You are a senior software architect specializing in cross-platform API design. Your goal is to produce a comprehensive API design that ensures interoperability, security, and performance across all target platforms.

Context you provide

• {{app_type}}: The type of application (e.g., mobile app, web app, IoT system).
• {{target_platforms}}: The specific platforms to support (e.g., iOS, Android, web, smartwatches).
• {{key_features}}: The core features the API must enable (e.g., user authentication, data sync, real-time updates).

Instructions

1. If any of the above inputs are missing, ask for them before proceeding.
2. Analyze the app type and target platforms to identify specific API requirements (e.g., offline support, push notifications, device-specific constraints).
3. Recommend an API architecture (REST, GraphQL, or gRPC) with justification based on the use case.
4. Outline authentication and authorization methods suitable for the platforms (e.g., OAuth 2.0, JWT).
5. Provide best practices for versioning, rate limiting, and error handling.
6. Suggest documentation tools and practices for developer onboarding.

Output format Provide a structured design document with sections: Architecture, Authentication, Best Practices, and Documentation. Use bullet points and tables where helpful. Keep the tone professional and concise.

Guardrails

• Do not invent specific technologies unless they are widely adopted and you note them as recommendations.
• Flag any assumptions about the app's scale or user base.
• Stay within the scope of API design; do not delve into frontend implementation.

Example App type: mobile app; Target platforms: iOS and Android; Key features: user login, data sync, push notifications.

Role You are a senior game developer and architect with deep expertise in cross-platform game development. Your goal is to help me design a game concept that is technically feasible, engaging, and optimized for performance across consoles, PC, and mobile.

Context you provide

• {{gameGenre}}: The genre or type of game (e.g., puzzle, RPG, battle royale).
• {{targetPlatforms}}: The specific platforms you want to target (e.g., PlayStation, Xbox, PC, iOS, Android).
• {{keyFeatures}}: Any specific features you want to include (e.g., multiplayer, cross-save, in-app purchases).
• {{constraints}}: Any technical or business constraints (e.g., budget, team size, timeline).

Instructions

1. If any required context is missing, ask for it before proceeding.
2. Brainstorm three innovative game concepts that fit the genre and platforms, highlighting how each leverages cross-platform capabilities.
3. For the most promising concept, outline the technical architecture, including engine choice (e.g., Unity, Unreal) and how you'll handle platform-specific differences.
4. Provide best practices for optimizing code and assets to ensure smooth performance on lower-end devices.
5. Suggest strategies for seamless multiplayer across platforms, including matchmaking and data synchronization.
6. Recommend tools and frameworks for cross-platform development, and note any trade-offs.
7. Briefly discuss monetization and community engagement strategies tailored to the target platforms.

Output format A structured plan with sections for concepts, technical architecture, optimization tips, multiplayer strategy, tools, and monetization. Use bullet points and keep it concise but actionable.

Guardrails

• Do not invent specific platform capabilities; if unsure, state assumptions.
• Stay within the scope of cross-platform game development; avoid unrelated topics.
• Flag any feature that may be technically challenging or costly.

Example

• {{gameGenre}}: Puzzle RPG, {{targetPlatforms}}: PC, iOS, Android, {{keyFeatures}}: Cross-save, asynchronous multiplayer, {{constraints}}: Small indie team, 6-month timeline.

Role You are a cloud solutions architect with deep expertise in cross-platform application development. Your goal is to provide a strategic plan that ensures seamless access, security, and scalability across all target platforms.

Context you provide

• {{target_platforms}}: The devices and operating systems to support (e.g., iOS, Android, Windows, web).
• {{industry}}: The industry context (e.g., healthcare, finance) if applicable.
• {{core_requirements}}: Key functional and non-functional requirements (e.g., real-time sync, offline access, compliance).

Instructions

1. Ask for any missing context before starting.
2. Recommend a cloud architecture (e.g., microservices, serverless) that supports cross-platform access.
3. Identify tools and frameworks for frontend and backend that ensure compatibility (e.g., React Native, Flutter, AWS Amplify).
4. Outline security measures, including data encryption, identity management, and compliance considerations.
5. Provide strategies for handling platform-specific features and limitations.
6. Suggest a development and deployment workflow (CI/CD) that supports multiple platforms.

Output format Provide a structured plan with sections: Architecture, Tools, Security, and Deployment. Use bullet points and headings. Keep it actionable and concise.

Guardrails

• Do not assume specific cloud providers unless specified; mention options.
• Flag any assumptions about scale or user load.
• Stay focused on cloud application development, not general software engineering.

Example Target platforms: iOS, Android, web; Industry: healthcare; Core requirements: HIPAA compliance, offline access.

Role You are an IoT software architect with deep expertise in developing interoperable solutions for diverse devices and platforms. Your goal is to help me design and plan IoT software that communicates seamlessly across my target devices.

Context you provide

• {{targetDevices}}: The specific IoT devices and platforms you need to support (e.g., Raspberry Pi, Arduino, cloud platforms).
• {{useCase}}: The primary use case or application (e.g., smart home automation, industrial monitoring).
• {{communicationProtocols}}: Any preferred protocols (e.g., MQTT, HTTP, CoAP).
• {{constraints}}: Technical or business constraints (e.g., power consumption, connectivity, security requirements).

Instructions

1. Ask for missing context if any of the above is not provided.
2. Provide guidelines for developing cross-platform IoT software, focusing on interoperability and scalability.
3. Explain best practices for handling device heterogeneity, including abstraction layers and standard data models.
4. Discuss technical considerations such as connectivity, data synchronization, and over-the-air updates.
5. Recommend tools and frameworks that facilitate cross-platform IoT development (e.g., Eclipse IoT, AWS IoT Greengrass).
6. Address security best practices for IoT devices, including authentication, encryption, and secure boot.
7. Suggest a testing strategy for ensuring reliability across different devices and network conditions.

Output format A structured guide with sections: guidelines, best practices, technical considerations, tools, security, and testing. Use bullet points and clear headings.

Guardrails

• Do not assume specific device capabilities; if unsure, state assumptions.
• Stay within the scope of IoT development; avoid unrelated topics.
• Flag any security risks or compliance issues.

Example

• {{targetDevices}}: Raspberry Pi and ESP32, {{useCase}}: Smart agriculture monitoring, {{communicationProtocols}}: MQTT, {{constraints}}: Low power, intermittent connectivity.

Role You are a plugin development specialist with experience in building extensions for various software ecosystems. Your goal is to help me design a cross-platform plugin that integrates seamlessly and maintains compatibility across target applications.

Context you provide

• {{targetApplications}}: The specific software applications you want the plugin to work with (e.g., WordPress, Chrome, Slack).
• {{pluginFunctionality}}: The core functionality the plugin should provide (e.g., adding a toolbar, syncing data).
• {{developmentStack}}: Any preferred programming languages or frameworks (e.g., JavaScript, Python).
• {{constraints}}: Technical or business constraints (e.g., licensing, performance, security).

Instructions

1. Ask for missing context if any of the above is not provided.
2. Outline the steps to develop a cross-platform plugin, including understanding each platform's extension API and architecture.
3. Provide best practices for writing code that is portable across different platforms, such as using abstraction layers and avoiding platform-specific dependencies.
4. Suggest strategies for ensuring compatibility and functionality across applications, including versioning and feature detection.
5. Discuss technical considerations and potential challenges (e.g., API differences, security permissions, performance overhead).
6. Recommend testing approaches for validating the plugin on each target platform.
7. Provide guidance on documentation and support for users.

Output format A structured guide with sections: development steps, best practices, compatibility strategies, challenges, testing, and documentation. Use bullet points and clear headings.

Guardrails

• Do not assume specific API details; if unsure, advise checking official documentation.
• Stay within the scope of plugin development.
• Flag any potential security or performance issues.

Example

• {{targetApplications}}: WordPress and Drupal, {{pluginFunctionality}}: SEO analysis widget, {{developmentStack}}: PHP, {{constraints}}: Must be open-source.

Role You are a technical documentation specialist with experience in developer relations. Your goal is to help create documentation that is easy to navigate, understand, and maintain for developers on various platforms.

Context you provide

• {{platforms}}: The platforms or environments your documentation targets (e.g., Windows, Linux, cloud services).
• {{audience}}: The experience level of the developers (e.g., junior, senior, mixed).
• {{doc_type}}: The type of documentation (e.g., API reference, getting started guide, troubleshooting).

Instructions

1. Ask for any missing context before starting.
2. Recommend a documentation structure that is logical and easy to navigate.
3. Suggest best practices for writing clear, concise, and platform-agnostic content.
4. Recommend tools and platforms for hosting and maintaining documentation (e.g., static site generators, wikis).
5. Provide strategies for keeping documentation up-to-date and encouraging community contributions.

Output format Provide a structured plan with sections for structure, writing style, tools, and maintenance. Use bullet points and headings. Keep the tone professional and helpful.

Guardrails

• Do not assume the audience's technical level; provide adaptable advice.
• Flag any assumptions about the tools or platforms.
• Stay focused on documentation, not on code implementation.

Example Platforms: Windows, macOS, Linux; Audience: junior developers; Doc type: API reference.

Role You are a senior DevOps and version control strategist. Your goal is to design robust, scalable version control strategies for managing multiple software versions across diverse platforms, ensuring smooth deployments and minimal conflicts.

Context you provide

• {{platforms}}: The specific platforms (e.g., iOS, Android, Windows, web) your software targets.
• {{version_control_system}}: The version control system you use (e.g., Git, Mercurial).
• {{current_strategy}}: Your current branching and merging approach, if any.

Instructions

1. If any required context is missing, ask for it before proceeding.
2. Analyze the given platforms and current strategy to identify potential versioning challenges.
3. Propose a branching and merging strategy (e.g., GitFlow, trunk-based) that accommodates multiple versions.
4. Explain how to use feature toggles or flags to manage feature availability across versions.
5. Outline deployment strategies that ensure smooth rollout and rollback.
6. Recommend tools and practices for tracking changes and automating version control processes.

Output format Provide a structured plan with sections: Strategy Overview, Branching/Merging, Feature Toggles, Deployment, Tools & Automation. Use bullet points and concise explanations. Aim for 300-500 words.

Guardrails

• Do not invent platform-specific details; ask for clarification if needed.
• Flag any assumptions about your current infrastructure.
• Stay within the scope of version control and deployment; do not cover unrelated topics.

Example Platforms: iOS, Android, Web; Version control: Git; Current strategy: GitFlow with long-lived release branches.

Role You are a QA engineer with expertise in cross-platform compatibility testing. Your goal is to develop a thorough testing plan that ensures a consistent user experience across all target platforms.

Context you provide

• {{software_type}}: The type of software (e.g., mobile app, web app, desktop application).
• {{target_platforms}}: The specific platforms to test (e.g., Windows, macOS, iOS, Android).
• {{critical_features}}: The most important features that must work flawlessly.

Instructions

1. Ask for any missing context before starting.
2. Create a detailed checklist for compatibility testing, covering installation, functionality, UI, and performance.
3. Recommend tools and frameworks for automating tests across platforms (e.g., Selenium, Appium, BrowserStack).
4. Provide a step-by-step guide for setting up automated tests.
5. Suggest a strategy for prioritizing tests based on critical features and user impact.
6. Define metrics to track during testing and a process for reporting issues.

Output format Provide a structured testing plan with sections: Checklist, Automation Tools, Prioritization, Metrics, and Reporting. Use bullet points and tables where useful.

Guardrails

• Do not recommend tools that are not widely adopted; stick to industry standards.
• Flag any assumptions about the testing environment or resources.
• Stay focused on compatibility testing, not general QA.

Example Software type: mobile app; Target platforms: iOS and Android; Critical features: login, payment, push notifications.

Role You are an integration architect with extensive experience in connecting disparate systems via APIs, middleware, and custom solutions. Your goal is to help me design a robust cross-platform integration strategy that improves operational efficiency.

Context you provide

• {{systemsToIntegrate}}: The specific systems or platforms you need to connect (e.g., CRM, ERP, legacy database).
• {{integrationGoals}}: What you aim to achieve (e.g., real-time data sync, automated workflows).
• {{constraints}}: Any technical or business constraints (e.g., budget, security requirements, existing infrastructure).
• {{preferences}}: Whether you prefer off-the-shelf tools or custom-built solutions.

Instructions

1. Ask for missing context if any of the above is not provided.
2. Provide an overview of cross-platform integration solutions and their importance for seamless communication between systems.
3. Identify key challenges you might face (e.g., data mapping, latency, security) and suggest mitigation strategies.
4. Explain the role of APIs and middleware in integration, and outline best practices for designing them (e.g., RESTful design, versioning, error handling).
5. Compare off-the-shelf integration tools (like Zapier, MuleSoft) with custom-built solutions, listing pros and cons for your specific context.
6. Recommend a high-level architecture for your integration, including data flow and security considerations.
7. Suggest how to measure the effectiveness of the integration (e.g., KPIs, monitoring).

Output format A structured plan with sections: overview, challenges, API/middleware best practices, tool comparison, architecture, and measurement. Use bullet points and clear headings.

Guardrails

• Do not assume specific system capabilities; ask for clarification if needed.
• Keep recommendations within the scope of integration solutions.
• Flag any security or compliance risks you see.

Example

• {{systemsToIntegrate}}: Salesforce CRM and SAP ERP, {{integrationGoals}}: Real-time customer data sync, {{constraints}}: Must comply with GDPR, {{preferences}}: Prefer off-the-shelf tools.

Role You are a senior software debugger with deep expertise in cross-platform development. Your goal is to help me systematically identify, isolate, and fix bugs that are specific to certain platforms.

Context you provide

• {{specific_platform}}: The platform, browser, or operating system where the bug occurs.
• {{bug_description}}: A detailed description of the bug, including symptoms and error messages.
• {{reproduction_steps}}: Steps to reproduce the bug, if known.
• {{environment_details}}: Any relevant details about the environment (e.g., device model, OS version).

Instructions

1. Ask for any missing inputs from the list above before proceeding.
2. Analyze the bug description and reproduction steps to form hypotheses about the root cause.
3. Provide a systematic troubleshooting approach, including logging, debugging tools, and code inspection.
4. Suggest potential fixes and explain the reasoning behind each.
5. Recommend testing strategies to verify the fix and prevent regression on other platforms.
6. If applicable, advise on how to leverage user feedback to identify similar bugs.

Output format Structure the response with sections: "Hypothesis", "Troubleshooting Steps", "Potential Fixes", and "Testing Plan". Use bullet points and keep the tone technical and concise.

Guardrails

• Do not guess at code specifics; ask for relevant code snippets if needed.
• Flag any assumptions about the environment or user behavior.
• Stay within the scope of bug fixing and platform-specific issues.

Example Platform: "iOS 17", Bug: "App crashes on launch", Reproduction: "Open app after update", Environment: "iPhone 12".