40 Best Qwen Prompts (2026)

Switch to Thinking mode. I'm deciding between [OPTION A] and [OPTION B]. Context: [YOUR SITUATION, CONSTRAINTS, WHAT MATTERS MOST]. Work through it step by step: lay out the real trade-offs, the second-order consequences of each path, and the assumptions I might be wrong about. Then give a recommendation with a confidence level, and name the one piece of new information that would change your answer.

Switch to Thinking mode. Solve this problem and show every deduction: [PASTE PROBLEM]. Track the constraints as you go, state each inference and why it follows, and rule out options explicitly. Before the final answer, check that it satisfies every constraint in the problem. If more than one solution fits, say so and list them all.

Switch to Thinking mode. Here's a problem I can't pin down: [DESCRIBE SYMPTOMS, WHAT YOU'VE TRIED, RELEVANT DATA OR LOGS]. Reason from symptoms to likely root causes. Rank the causes by probability, give the evidence for each, and tell me the single cheapest test to confirm or rule out the top one. Keep what you know separate from what you're inferring.

Switch to Thinking mode. Here's my plan: [PASTE PLAN]. Act as a sharp skeptic. Work step by step through the ways this fails: hidden assumptions, weak links, single points of failure, and second-order effects I haven't considered. For each risk, rate likelihood and impact and suggest a concrete mitigation. Be blunt — I'd rather hear it now.

I'm choosing between these options: [LIST OPTIONS]. My criteria, most important first: [LIST CRITERIA]. Build a weighted decision matrix: score each option 1-5 on each criterion, apply the weights, and total them. Show the table, explain any score that isn't obvious, and give the winner. Then tell me which single criterion, if I've misjudged its weight, would flip the result.

Switch to Thinking mode. I'm getting this error in [LANGUAGE / FRAMEWORK version]: [PASTE ERROR]. Here's the relevant code: [PASTE CODE]. Reason through the likely root cause, give me the corrected code, and explain what was wrong in two sentences. If more than one cause is possible, rank them by likelihood, then verify your fix against the error before the final answer.

Explain what this code does to a developer new to [LANGUAGE / LIBRARY]: [PASTE CODE OR ATTACH FILE]. Give a one-paragraph overview, then a block-by-block walkthrough of the tricky parts, and call out any bugs, edge cases, or performance concerns you notice. Skip the obvious lines and keep it concrete.

Write thorough unit tests for this function using [TEST FRAMEWORK]: [PASTE FUNCTION]. Cover the happy path, edge cases, invalid inputs, and boundary conditions. Explain in one line what each test verifies, and flag any behavior in the function that looks like a bug or is ambiguous enough to need a spec decision.

Refactor this code for readability and maintainability without changing behavior: [PASTE CODE]. Improve naming, reduce nesting, and extract logic where it helps. Return the refactored version, then a short bullet list of what you changed and why. Keep it idiomatic for [LANGUAGE] and don't add dependencies.

Switch to Thinking mode. Build [FEATURE OR APP] in [LANGUAGE / STACK]. Requirements: [LIST REQUIREMENTS]. Constraints: [PERFORMANCE, DEPENDENCIES, STYLE]. First outline your approach and the key decisions, then write the full, runnable code with comments on the non-obvious parts. List your assumptions and how I'd test it. Verify the code meets each requirement before finishing. (For a full front end, use Web Dev to generate and preview it.)

You are a writer for [AUDIENCE]. Write a [1,200]-word blog post titled "[TITLE]" from this outline: [PASTE OUTLINE]. Keep the tone practical and direct, lead each section with the takeaway, use short paragraphs and concrete examples, and avoid clichés and filler. Output in clean Markdown with H2 sections and a two-line intro.

Rewrite the text below to be clearer and more direct without losing meaning. Cut filler, fix weak verbs, and keep my key terms. Target a [confident but plain] tone at a [general professional] reading level. Return the rewrite first, then a short bullet list of the main changes. Text: [PASTE TEXT]

You are writing a cold outreach email from me ([MY ROLE] at [MY COMPANY]) to [PROSPECT ROLE] at [PROSPECT COMPANY]. Goal: [GOAL]. Keep it under 90 words, open with a specific reason I'm reaching out to them (not a template), state one clear value point, and end with a low-friction ask. Give me three subject-line options.

Generate 12 headline options for [PIECE / PRODUCT] aimed at [AUDIENCE]. Mix angles: benefit-led, curiosity, contrarian, number-led, and how-to. Keep each under 65 characters, avoid hype words, and label the angle of each. Then pick your top three and say why they'd perform best.

Write a [500]-word [genre] scene. Setup: [WHO, WHERE, WHAT'S AT STAKE]. Point of view: [FIRST / THIRD], tense: [PAST / PRESENT]. Show, don't tell; let the tension build through action and dialogue rather than narration; end on a beat that pulls the reader forward. Match this voice: [DESCRIBE OR PASTE A SAMPLE]. Avoid clichés and purple prose.

Translate the text below from [SOURCE LANGUAGE] into [TARGET LANGUAGE]. Preserve the tone and register ([e.g. formal, warm, marketing]), keep names, product terms, and numbers exact, and adapt idioms so they read naturally to a native speaker rather than translating them word for word. Return the translation, then flag any phrase where a choice was tricky and give an alternative. Text: [PASTE TEXT]

Localize this copy for [TARGET MARKET / LOCALE], don't just translate it. Adapt currency, units, date formats, examples, and cultural references so it feels native to [TARGET LANGUAGE] readers in that market. Keep the brand voice [DESCRIBE]. Return the localized version, then a short note on what you changed for the market and why. Copy: [PASTE COPY]

Build a bilingual glossary for [DOMAIN — e.g. fintech, medical devices] between [LANGUAGE A] and [LANGUAGE B]. Extract the key terms from this material: [PASTE OR ATTACH SOURCE]. For each term give: term in A, preferred term in B, a one-line definition, and a usage note or common mistranslation to avoid. Output as a table and keep the preferred terms consistent for reuse.

Translate these subtitles from [SOURCE LANGUAGE] into [TARGET LANGUAGE], keeping the SRT timestamps unchanged: [PASTE SRT]. Keep each line short enough to read on screen (aim for [42] characters per line, max two lines), preserve the speaker's tone, and split or condense lines so the timing still works. Return valid SRT.

I wrote this in English as a non-native speaker. Polish it to sound natural and fluent while keeping my meaning and voice — don't make it more formal than it needs to be. Fix grammar, word choice, and awkward phrasing. Return the polished version, then a short list of the recurring mistakes so I can learn them. Text: [PASTE TEXT]

Run Deep Research on [TOPIC / QUESTION]. I need a structured report covering: the current state, the main viewpoints and who holds them, the key data and where it comes from, and where things are heading. Resolve conflicts between sources and say which side the evidence favors. Cite every source with a link and note the date. End with what's still uncertain and the open questions worth watching.

Turn on Web Search. Research [TOPIC / QUESTION] and write me a brief as of this month. Cover the current state, the main viewpoints, and where things are heading. Cite every source with a link, prefer primary and recent sources, and put the publication date next to each fact. End with what's still uncertain or contested.

Turn on Web Search. Find the main sources on [QUESTION] and compare what they say. Build a table: Source | Key claim | Evidence given | Date | Link. Then tell me where the sources agree, where they conflict, and which claim is best supported. Flag any source that looks weak or out of date. Cite every source with a link.

I've attached a document. Read it in full, then give me: a 3-sentence summary, the 5 most important points as bullets, any conclusions or recommendations it makes, and anything it leaves unanswered or assumes without evidence. Ground every point in the document only; if something isn't in it, say so rather than filling the gap.

Turn on Web Search. Fact-check this claim: "[CLAIM]". Find the original source, what the primary evidence actually says, and how credible outlets have covered it. Rate it True / Misleading / False / Unproven with a short reason. Cite every source with a link, and separate what's confirmed from what's still uncertain.

Turn these meeting notes into a clean summary: [PASTE NOTES]. Output three sections: Decisions made, Action items (as a table with Owner, Task, Due date), and Open questions. Keep it tight, don't invent details that aren't in the notes, and flag anything left unresolved.

You are a pragmatic startup advisor. Draft a one-page plan for this idea: [DESCRIBE IDEA]. Cover: the problem, the target customer, the offer, how it makes money, the first three steps to validate it cheaply, and the biggest risk. Be blunt about weaknesses. Output as clear sections, no filler.

Switch to Thinking mode. Write a one-page strategy memo on [DECISION / QUESTION]. Context: [BACKGROUND, GOALS, CONSTRAINTS, DATA]. Lay out 2-3 real options, the trade-offs of each, and a clear recommendation with the reasoning. Name the key assumption the recommendation rests on and what would have to be true for it to hold. Keep it tight and executive-ready.

Here's everything on my plate this week: [PASTE LIST]. Act as a sharp chief of staff. Sort it by impact and urgency, tell me the three things that actually move the needle, what to delegate or drop, and lay it out as a simple day-by-day plan. Call out anything that looks like busywork.

Write a job description for a [ROLE] at [COMPANY / TYPE OF COMPANY]. Context: [TEAM, LEVEL, KEY RESPONSIBILITIES, MUST-HAVE SKILLS, LOCATION / REMOTE]. Keep it concrete and honest about the day-to-day, avoid buzzwords and inflated requirements, and separate must-haves from nice-to-haves. Output: a two-line summary, Responsibilities, Requirements, and What we offer. Keep it under 400 words.

I've attached a CSV. Use Code Interpreter to analyze it. First describe the columns and row count, then answer: [YOUR QUESTIONS — e.g. what drives [METRIC], top segments, trends over time]. Show the key numbers in a table, note anything surprising or any data-quality issues you hit, and include the Python you ran so I can reproduce it.

I need a [Google Sheets / Excel] formula to [GOAL]. My data is laid out like this: [DESCRIBE COLUMNS]. Give me the formula, explain what each part does, and note common ways it could break (blank cells, text vs numbers, ranges that grow). If a small helper column would make it cleaner, suggest it.

Using Code Interpreter, make a chart from the attached data. I want to show [WHAT YOU WANT TO COMMUNICATE — e.g. the trend in X by month]. Pick the chart type that fits, label the axes and units clearly, and keep it clean. Then tell me in one or two sentences what the chart shows and any caveat I should mention when I present it.

Switch to Thinking mode and use Code Interpreter. With the attached data, I want to know whether [HYPOTHESIS — e.g. group A differs from group B on [METRIC]]. Choose the right statistical test and say why it fits, state the assumptions and check them, run it, and report the result with the effect size and a plain-English interpretation. Flag anything that would make the result unreliable.

Use Code Interpreter to clean the attached dataset. Handle: missing values, duplicates, inconsistent formats (dates, casing, units), and obvious outliers. Tell me each decision you made and why before you apply it, don't drop data silently, and return the cleaned file plus a short changelog of what you fixed and how many rows it touched.

Turn on Web Search. Plan a [NUMBER]-day trip to [DESTINATION] for [WHO] with a budget of [BUDGET]. We like [INTERESTS] and want to avoid [DISLIKES]. Give a day-by-day itinerary with realistic timing, group nearby stops to cut travel, and note current prices and opening hours where you can with links. Add one rainy-day backup and one splurge option.

I have these ingredients: [LIST]. Plan [NUMBER] meals for [PEOPLE] using mostly what I have, adding as few new items as possible. For each meal give a short ingredient list, quick steps, and rough time. Respect these needs: [DIET / ALLERGIES / DISLIKES]. At the end, give me a short shopping list of only the extras I'd need.

Help me write a message to [WHO] about [SITUATION]. My goal is [GOAL] and I want to sound [TONE — e.g. firm but kind]. Keep it honest and clear, don't over-apologize or ramble, and leave the door open for a good response. Give me two versions: a shorter one and a slightly warmer one. Context they'll need: [BACKGROUND].

Explain [CONCEPT] to me. First give the one-sentence core idea, then build it up with a concrete everyday analogy, then a worked example, then the common misconception people have. Assume I know [YOUR CURRENT LEVEL]. End with two questions I could answer to check I actually understood it.

Switch to Thinking mode. Here's my monthly income and spending: [PASTE NUMBERS OR CATEGORIES]. My goal is [GOAL — e.g. save X, pay down debt]. Analyze where the money goes, flag the categories that look high for my goal, and suggest a realistic adjusted budget with specific numbers. Show your reasoning and don't recommend cuts too painful to stick to. This is general guidance, not financial advice.