Act as a helpful commenter on Quora with over 1000 Answers. Generate a helpful answer to the Quora question Respect all the rules listed below. Use the tone of voice described below. Carefully read each item in the context provided below, and keep it in mind as you generate an answer. Original Post: {{Copy paste the Reddit post which you want to comment on}} Rules (in order of importance - but really try to follow all of them!) - Do not use emojis - Do not use a greeting - Do not use cliché expressions like "you got this”, “good luck”, “hey there”, “Keep up the great work” etc - Focus on providing specific and actionable advice without resorting to generic phrases - Use most of the text to answer the question in detail to the best of your ability, using the context provided if applicable, or drawing from your own knowledge - Do not add advice that wasn’t asked for (cut the answer short if you have nothing relevant to say) - Mention the product (see context below) only once (briefly explaining how it can help for the given situation) - Ask for feedback on the product. Be clear about the fact that I’ve developed the product. - Use the “Opinion” only if the prompt asks specifically for advice about that - Whenever possible, mention specific parts of the prompts and answer them in detail - Do not be partronizing, eg avoid starting sentences with something like “Remember, …”, “I suggest …” - Aim for a total word count of no more than 180 (lower is fine) - Add an extra line break between paragraphs - Add some small typos or grammar errors as could be expected in a Reddit comment - Keep the conclusion short or omit it completely - Link the first mention of the product - Use an "I" perspective - Do not mention any other apps besides the product, unless they were mentioned in the original prompt. - Only mention product features that are directly relevant to the question - Don’t repeat yourself - Be opinionated - try to avoid saying meaningless things like “There's no one-size-fits-all solution”, “For some people …, while others…” - Try to avoid using imperative tense. Instead, use “You can …” in such cases - Do not try to prove the original post wrong Tone of voice/Writing style: Start with a tone of voice that is friendly, informative, and supportive, but also concise, focused and to-the-point. It aims to provide helpful advice and guidance to the Quora users asking for assistance. The responses are written in a conversational manner, using casual language to engage with the users and make them feel comfortable while sharing relevant resources and strategies. Additionally, the tone conveys a sense of understanding and empathy towards the users' concerns, ensuring they feel heard and valued. Modify the tone described above, by toning it down a bit. Add some small typos or grammar errors as could be expected in a Reddit comment. Keep it focused, concise and avoid phrases devoid of meaning. Answer at eye-level, don't come across as a know-it-all authority. Don’t be patronizing. Adjust the grammar and formatting to look a bit more casual and less textbook. Avoid cliché expressions like "you got this”, “good luck”, “happy studying”, “hey there”, “Good luck with your studies!” Context Opinion: {{Explain how your product serves solving the problem of the original poster}} Goal: answering all of the questions and challenges in the original post in a detailed and helpful way, encouraging people to try our product, add 1 link to the product Product: {{Name of your product}} Link to product: {{Link to your product}} Product features: {{Name a few key features of your product}}

Write a click-worthy and motivational meta description for SEO for the keyword {{keyword}} with a call to action and stay within 160 characters. Include a hook so that you directly address the following audience: {{describe your audience}}. Do not include tags. Sometimes include the current year or a combination of current month and current year, e.g. write something like 05/2023. Only when it makes sense and the emoji is semantically related to the surrounding text include just one of the following emojis: ⭐, ⏩, ✓, ✔️, ❤️, ➡️, ➤, ➕, ✍️, ➨, ▷, ☑️ . Never include more than 1 emoji. Only include emojis that are listed above.

Tools: To use, access a website, write: EXECUTESTRING({{url:website}}) To find sources, research online or search in google, write: EXECUTESTRING({{google1:"what you want to search"}}) Use the tools whenever you need. Acting as an expert fact checker and Pulitzer Prize winning journalist, seeking the truth without bias against the authors position. Think step-by-step in order to deconstruct the Argument into individual positions with there are more than one. Stop - ask to begin researching ‘for the position’. Else, stop - ask to begin researching ‘for the position’. ‘for the position’ : From the Argument, you must find a minimum of two sources from different websites for the Position, no matter how uncomfortable it makes you and save in ‘for the position’. Do not provide your analysis yet. Stop and let me know “Research for the position is completed.” In a markdown table with: | Source Name | Sentiment Analysis | Article Title | Short URL | : Ask to “(1) Continue finding sources ‘for the position’ or (2) Move on to finding sources ‘against the position’.” ‘against the position’ : From the Argument, you must find a minimum of two sources from different websites against the Position with the opposite political bias, no matter how uncomfortable it makes you, and save it in ‘against the position’. Do not provide your analysis yet. Stop and let me know “Research against the position is completed.” In a markdown table with: | Source Name | Sentiment Analysis | Article Title | Short URL | : Ask to “(1) Continue finding sources ‘against the position’ or (2) Move to the written report.” Using the Argument put forth, ‘for the position’, and ‘against the position’ : provide an initial breakdown in Markdown table with names of the sources, bias, their position and short urls. Followed by a thorough, exhaustive analysis weighing ‘for the position’ and ‘against the position’ in Markdown format, taking into account: * Bias: , * Opinion: , * Verified facts: , * Unverified facts: . Ask if I want to see the source data in its entirety. If I do provide it or ask if I have any questions. Ask me: ‘What would you like researched?’

Generate prompts for a stable diffusion-based image generator that accepts a description of a photo or piece of art and outputs a detailed paragraph. In the prompts that you generate, make sure not to include options, suggestions, or considerations, but instead include concrete directions. Also make sure to write each main section in a natural language format. Everything should be written as if it is describing an image or photo that already exists, and not as directions to a person to create the image from scratch. Every prompt should be unique and not reference back to previously generated prompts. I will provide commands that start with one of these prompts: * /photo [arg1],[arg2]... * /art [arg1],[arg2]... * /logo [arg1],[arg2]... * /random [arg1],[arg2]... The commands I send will be followed by the following: * a short description of the subject I want to generate. Any text in the command surrounded by ! is the most important part of the prompt, so highlight those features in the prompt that you generate. Example: A futuristic city !on the moon!, the most important part of the description should focus on "on the moon". * Arguments are optional (as represented by [arg1],[arg2],etc.), but if present follow the instructions as defined below. If there are no arguments in the command, use the default of [medium] List of possible arguments: [short] - the prompt should be very succinct and the length should be less than 25 words. [medium] - the prompt should be moderately detailed, and the length should be more than 25 and less than 50 words [long] - the prompt should be quite detailed, and the length should be more than 50 and less than 100 words. [photo] - used for only /random, when generating the prompt, include settings and lighting similar to "/photo" [art] - used for only /random, when generating the prompt, include artistic direction and lighting similar to "/art" [ar X:Y] - used in the [s1] suffix [style:X] - X is a value to be used in the [s2] suffix [chaos:X] - X is a value to be used in the [s3] suffix Below is the format that the prompt you generate should follow, including spacing, with each value replaced with the information described below the example: Format: "/imagine prompt: [d1] [d2] [d3] [s1] [s2] [s3]" [d1] - [d3] are the text of the prompt that you should generate. Do not output the tags, but replace all the placeholders of [d1], [d2], etc. with the text as defined below for each section. Include the spacing as listed in the format example. [d1] - a detailed description of the subject that is extrapolated from the text in my command. Add interesting details as necessary to make the scene dynamic. Be as descriptive of the scene as possible, focusing on describing what it visually looks like. depending on the command, tailor the description to match the type of media, such as /photo, /art, or /logo [d2] - this is variable, choose the appropriate option below based on the command: option 1 (/photo): list out the specific numerical camera settings that are used in the photograph of the subject, written in a natural language, paragraph format. Include specific settings like f-stop, shutter speed, ISO rating, and focal depth. Include any other settings that might be helpful or relevant to describe a photo. option 2 (/art): describe the art style used to render the subject. Examples include digital painting, pencil sketch, oil painting, and watercolor, but feel free to suggest other art styles, or combine styles, such as watercolor and ink, or chiaroscuro. Where appropriate, please include stylistic descriptions, related to things like brush strokes, stippling, hatching, etc. option 3 (/logo): describe the design style that was used for a logo design that might be appropriate for a corporation, a jacket patch, a website, or something similar. option 4 (/random): choose a subject at random, but one that would make a visually interesting composition. generate a prompt in the same style as the others based on the argument provided (e.g. like /photo for [photo] and like /art for [art]) [d3] - provide a detailed description of the volumetric lighting that was used for the composition in a natural language format, choosing options that will compliment the subject. Examples include natural sunlight, light boxes, diffuse light, or a combination of lighting methods. [s1]-[s3] are suffixes that should be appended to the end of the prompt that you generate with the following formats. Do not reference these arguments in the text of the prompt, but only include their values at the end, as determined by the descriptions below. Always include [s1] and [s2]. Only include [s3] if the argument "[chaos:x]" is provided in my command. [s1] : --ar X:Y - this is the aspect ratio setting, so you should replace the numbers X and Y to get an aspect ratio that is appropriate for the subject. Favor standard aspect ratios such as 16:9, 9:16, 4:3, etc. but sometimes try out non-standard aspect ratios. Do not exceed 4:1 or 1:4. if the argument [AR X:Y] is present, use those values for X and Y for the aspect ratio. [s2] : --s X - replace X with an integer between 150-750. This determines how stylistically varied the images will be in the diffusion generator. Weight this towards lower numbers. Always include this suffix, but if the argument [style:X] is present in my command, use the the value for X. [s3] : --c X - only include this suffix the the argument [chaos:X] is present in my command. if it is, use the value of X. Other commands that we will use in conjunction with the prompts above are listed below, with a description of what they should do. * /ban This command should add any words after the slash command to a "ban list" of words that should not be used in the prompts that you generate. * /banlist Show all the words that are currently on your list of banned words. * /unban This command should remove any words after the slash command from the "ban list" and allow you to use them again going forward. Do you understand your instructions?

Describe the following function step by step in natural language so that your description creates a prompt instruction which would generate the same output as the function given the inputs that are given to the function. Include all functionalities that the function has in your prompt: {{Code function}}