Click to rate this post!
[Total: 0 Average: 0]
Adapting prompts for different platforms and devices for Generative AI prompt design
Below are examples from different domains, each illustrating how to adapt multi-platform prompts and devices when designing prompts for Generative AI.
Examples
- E-commerce Product Description
- Domain: E-commerce
- Task: Generating product descriptions
- Platform/Device: Mobile app and Web
- Prompt: "Write a short and engaging description for a pair of wireless earbuds, highlighting its main features. Make it concise for mobile users and more detailed for web users."
- Modified Prompt: "Write a short and engaging description for a pair of wireless earbuds, highlighting its main features. Make it concise for mobile users and more detailed for web users. Exemplar: Look at how we described the XYZ headphones last month. Negative Prompt: I don’t want to see any technical jargon in the mobile version, and please avoid making the web version too brief."
- Explanation: Here, the prompt is clear and specific, addressing the task of writing a product description. The context is set for an e-commerce setting, and the format is adapted for both mobile and web users. The tone is kept engaging to attract customers. The persona is that of a salesperson trying to highlight the product’s features. The formality level is casual, and the behavior expected is helpful and informative. The maturity level is professional, and there is an emphasis on consistency across both platforms.
- Educational Content Creation
- Domain: Education
- Task: Creating a lesson on photosynthesis
- Platform/Device: Tablet for students and Interactive Whiteboard for teachers
- Prompt: "Develop a lesson plan on photosynthesis, ensuring it’s interactive for students using tablets and comprehensive for teachers using an interactive whiteboard."
- Modified Prompt: "Develop a lesson plan on photosynthesis, ensuring it’s interactive for students using tablets and comprehensive for teachers using an interactive whiteboard. Exemplar: Use the structure we applied in the ABC lesson last semester. Negative Prompt: Please do not include any outdated information, and avoid making the tablet version too text-heavy."
- Explanation: Clarity is maintained with explicit instructions on what the content should include. The context is an educational setting, and the task is creating a lesson plan. The format is adapted for both tablets and interactive whiteboards. The tone is instructive, and the persona is that of an educator. The formality level is moderate, and the behavior expected is educational and engaging. The maturity level is suitable for a school setting, ensuring consistency in content across devices.
- Customer Support Response
- Domain: Customer Service
- Task: Responding to a customer query about a product
- Platform/Device: Email and Live Chat
- Prompt: "Draft a response to a customer asking about the features of our latest smartphone. Make it detailed for email replies and quicker, more direct for live chat responses."
- Modified Prompt: "Draft a response to a customer asking about the features of our latest smartphone. Make it detailed for email replies and quicker, more direct for live chat responses. Exemplar: Follow the tone we used in the DEF response last week. Negative Prompt: I don’t want to see any upselling in the live chat responses, and please avoid making the email replies too short."
- Explanation: The prompt is clear, requiring a response to a customer query. The context is customer service, and the task is responding to a product inquiry. The format is adapted for both email and live chat, with a tone that is helpful and polite. The persona is a customer support representative. The formality level is professional, and the behavior expected is responsive and informative. The maturity level is suitable for a customer service setting, ensuring consistency in responses across platforms.
- Social Media Post Creation
- Domain: Marketing
- Task: Creating a social media post for a new product launch
- Platform/Device: Instagram and Facebook
- Prompt: "Craft an engaging social media post announcing our new product launch. Make it visually appealing with a short caption for Instagram and provide more details for Facebook."
- Modified Prompt: "Craft an engaging social media post announcing our new product launch. Make it visually appealing with a short caption for Instagram and provide more details for Facebook. Exemplar: Look at how we announced the GHI product last month. Negative Prompt: Please do not use any clichés, and avoid making the Facebook post too similar to the Instagram post."
- Explanation: The prompt is specific, targeting the creation of a social media post. The context is marketing, and the task is announcing a new product. The format is adapted for both Instagram and Facebook, with a tone that is exciting and engaging. The persona is a social media marketer. The formality level is casual, and the behavior expected is promotional and engaging. The maturity level is suitable for a wide audience, ensuring consistency in the message across platforms.
- Enterprise Architecture
- Domain: Enterprise Architecture
- Task: Designing a comprehensive software system for a large organization
- Platform/Device: Desktop for architects and Mobile for field engineers
- Prompt: "Create a detailed software architecture plan for our entire organization. Ensure it’s very comprehensive and includes all layers of the architecture for desktop users, and provide a summarized version with quick access to key components for mobile users in the field."
- Modified Prompt: "Create a detailed software architecture plan for our entire organization. Ensure it’s very comprehensive and includes all layers of the architecture for desktop users, and provide a summarized version with quick access to key components for mobile users in the field. Exemplar: Similar to the architecture plan we did for the XYZ project last year, but updated with the new systems we’ve adopted. Negative Prompt: I don’t want to see overly technical jargon in the mobile version, and please avoid including outdated systems that we no longer use."
- Explanation: This prompt is clear, targeting the creation of an enterprise-level software architecture plan. The context is a large organization, and the task is to design a software system that encompasses all aspects of the enterprise. The format is adapted for both desktop and mobile users, with a tone that is professional and instructive. The persona is a software architect. The formality level is high, and the behavior expected is thorough and precise. The maturity level is advanced, ensuring consistency and clarity across platforms.
- Business Architecture
- Domain: Business Architecture
- Task: Mapping out business processes and their interaction with software systems
- Platform/Device: Web application for business analysts and Tablet for quick reviews
- Prompt: "Develop a business architecture map that outlines all our key business processes and how they interact with our software systems. Make it detailed and interactive for users on the web application, and provide a simplified, easy-to-navigate version for quick reviews on tablets."
- Modified Prompt: "Develop a business architecture map that outlines all our key business processes and how they interact with our software systems. Make it detailed and interactive for users on the web application, and provide a simplified, easy-to-navigate version for quick reviews on tablets. Exemplar: Use the format we applied in the ABC process mapping, ensuring all touchpoints are clearly marked. Negative Prompt: Please do not include any deprecated processes, and avoid making the tablet version too cluttered."
- Explanation: The prompt is specific, focusing on the creation of a business architecture map. The context is the intersection of business processes and software systems, and the task is to map out these relationships. The format is adapted for both web application and tablet users, with a tone that is clear and analytical. The persona is a business architect. The formality level is professional, and the behavior expected is analytical and precise. The maturity level is suitable for a business setting, ensuring consistency in the map across platforms.
- Technical Architecture
- Domain: Technical Architecture
- Task: Designing the technical infrastructure for a new software application
- Platform/Device: Desktop for in-depth planning and Smartphone for on-the-go decision making
- Prompt: "Create a technical architecture plan for our new software application, ensuring it’s detailed and includes all technical components for desktop users, and provide a quick reference guide with key technical decisions for smartphone users."
- Modified Prompt: "Create a technical architecture plan for our new software application, ensuring it’s detailed and includes all technical components for desktop users, and provide a quick reference guide with key technical decisions for smartphone users. Exemplar: Follow the structure we used for the DEF project, but with updated technology stacks. Negative Prompt: I don’t want to see any legacy systems in the plan, and please avoid making the smartphone version too technical."
- Explanation: The prompt is clear, targeting the creation of a technical architecture plan. The context is software development, and the task is to design the technical infrastructure for a new application. The format is adapted for both desktop and smartphone users, with a tone that is technical and precise. The persona is a technical architect. The formality level is high, and the behavior expected is detailed and accurate. The maturity level is advanced, ensuring consistency and clarity across platforms.
- Information or Data Architecture
- Domain: Information or Data Architecture
- Task: Designing a data management system for the organization
- Platform/Device: Desktop for data architects and Tablet for field data collectors
- Prompt: "Develop a data architecture plan that ensures efficient data management and accessibility across the organization. Make it comprehensive with all data layers included for desktop users, and provide a simplified version with quick data entry and retrieval options for tablet users in the field."
- Modified Prompt: "Develop a data architecture plan that ensures efficient data management and accessibility across the organization. Make it comprehensive with all data layers included for desktop users, and provide a simplified version with quick data entry and retrieval options for tablet users in the field. Exemplar: Use the GHI project as a reference, ensuring all data sources are integrated. Negative Prompt: Please do not include any deprecated data sources, and avoid making the tablet version too complex."
- Explanation: The prompt is specific, focusing on the creation of a data architecture plan. The context is data management within the organization, and the task is to design a system that ensures efficient data handling. The format is adapted for both desktop and tablet users, with a tone that is clear and data-centric. The persona is a data architect. The formality level is high, and the behavior expected is precise and efficient. The maturity level is advanced, ensuring consistency and clarity across platforms.
- Integration Architecture
- Domain: Integration Architecture
- Task: Designing a system to integrate various software applications
- Platform/Device: Desktop for architects and Mobile for integration testers
- Prompt: "Create an integration architecture plan that outlines how our various software applications will communicate and work together. Ensure it’s detailed and includes all integration points for desktop users, and provide a summarized version with key integration tests for mobile users."
- Modified Prompt: "Create an integration architecture plan that outlines how our various software applications will communicate and work together. Ensure it’s detailed and includes all integration points for desktop users, and provide a summarized version with key integration tests for mobile users. Exemplar: Look at the JKL project for inspiration, ensuring all APIs are documented. Negative Prompt: I don’t want to see any deprecated APIs, and please avoid making the mobile version too brief."
- Explanation: The prompt is clear, targeting the creation of an integration architecture plan. The context is software integration, and the task is to design a system that ensures seamless communication between different applications. The format is adapted for both desktop and mobile users, with a tone that is technical and precise. The persona is an integration architect. The formality level is high, and the behavior expected is thorough and accurate. The maturity level is advanced, ensuring consistency and clarity across platforms.
- Deployment Architecture
- Domain: Deployment Architecture
- Task: Planning the deployment of a new software application
- Platform/Device: Desktop for deployment planning and Smartphone for monitoring
- Prompt: "Develop a deployment architecture plan for our new software application, ensuring it includes all necessary components and steps for desktop users, and provide a real-time monitoring tool with key deployment status updates for smartphone users."
- Modified Prompt: "Develop a deployment architecture plan for our new software application, ensuring it includes all necessary components and steps for desktop users, and provide a real-time monitoring tool with key deployment status updates for smartphone users. Exemplar: Refer to the MNO project, ensuring all deployment stages are included. Negative Prompt: Please do not include any unnecessary deployment steps, and avoid making the smartphone version too detailed."
- Explanation: The prompt is specific, focusing on the creation of a deployment architecture plan. The context is software deployment, and the task is to plan the rollout of a new application. The format is adapted for both desktop and smartphone users, with a tone that is clear and directive. The persona is a deployment architect. The formality level is high, and the behavior expected is organized and precise. The maturity level is advanced, ensuring consistency and clarity across platforms.
Conclusion
In each of these examples, the prompt is tailored for multi-platforms and devices, ensuring clarity and relevance. Exemplars are provided to guide the Generative AI model, and negative prompts are included to specify what the user does not want to see.
Pro Tip
When designing prompts for different platforms and devices or multi-platforms, always think about who will use them and how. For a phone, keep prompts short and easy to tap. On a computer, you can add more details. Remember, the key is to make prompts clear and simple, so everyone can understand them, whether they are students, developers, or architects. This way, your prompts will be helpful and easy to use on any device.
FAQs
1. What is a multi-platform prompt?
A multi-platform prompt is a set of instructions or questions designed to work well on different devices like phones, computers, and tablets.
2. Why is it important to design prompts for different devices or multi-platforms?
Different devices have different screen sizes and ways people use them. Designing prompts for each device makes sure they are easy to read and use, no matter what device someone is using.
3. How do I make a prompt good for a phone?
Keep it short and simple. Make sure it’s easy to read on a small screen and easy to answer with just a few taps.
4. What should I consider for computer prompts?
You can include more details in computer prompts because the screen is bigger and people often use a keyboard to type their answers.
5. Can the same prompt work on all devices or multi-platforms?
Yes, but it’s best to adjust the prompt a bit for each device to make sure it’s as easy as possible for people to understand and respond to.
6. What are some common mistakes in prompt design?
Using long, complicated words or too much technical language can make prompts hard to understand, especially for younger people or those new to the topic.
7. How do I test if my prompt is good for all devices or multi-platforms?
Try using the prompt on different devices yourself, and maybe ask others, like friends or colleagues, to test it too and give feedback.
8. What’s the best way to keep prompts clear and simple?
Use everyday language and keep sentences short. Always think about if someone new to the topic can understand it easily.
9. Are there any tools to help design multi-platform prompts?
Yes, there are online tools and software that can help you create and test prompts on different devices.
10. How often should I update my prompts?
It’s good to review and update your prompts regularly, especially if there are new trends or changes in how people use devices.
Related Topics
Click to rate this post!
[Total: 0 Average: 0]