Get better answers from Kimi with prompts that work. Copy any of 36 ready-made prompts for research, writing and coding, build your own with the prompt builder, and learn which Kimi mode to use for each job.
Most weak answers come from vague prompts. Give Kimi these five things and the first answer is far more likely to be useful.
Who should Kimi be?
“You are a careful market analyst.”
What exactly do you want?
“Compare the 3 best note-taking apps.”
Who is it for, and what's the situation?
“For a 10-person design team on a $50 monthly budget.”
What should the answer look like?
“A table, then a 5-line summary.”
How should Kimi make it reliable?
“Cite sources and flag anything you're unsure of.”
Pick a category or search, copy a prompt, and replace the [brackets] with your details. Each card shows the best place to run it.
Showing all 36 prompts
Research [topic] for [audience]. Answer these questions: [question 1], [question 2], [question 3]. Prefer sources from the last [12 months], cite every claim, and end with a short section called 'What we still don't know'.
Compare [option A], [option B] and [option C] for [use case] in a table: price, key features, pros, cons and best fit. Cite a source for every number and flag anything you couldn't confirm.
Find [10] peer-reviewed studies on [topic] published since [year]. For each, list the authors, year, method, sample size and main finding. Then summarise where the studies agree and disagree.
Estimate the size of the [market] in [region] for [year]. Use two methods, top-down and bottom-up, list every assumption with its source, and give a low, base and high range.
Read the attached [report]. Give me a one-paragraph summary, the 7 key findings with page numbers, and 3 questions I should ask the authors.
Fact-check this text: [paste text]. For each claim, say true, false or unclear, give a source, and explain your verdict in one line.
Research these [5] competitors in parallel: [names]. For each, find pricing, target customers, recent launches and customer reviews. Merge everything into one comparison table and a 5-point summary.
Compare the [3] attached documents. Make a table of what each says about [topic 1], [topic 2] and [topic 3], highlight any contradictions, and quote the exact sentence with its page number.
Explain [concept] at three levels: for a 12-year-old, for a university student and for an expert. Use one real-world example at each level.
Prepare a one-page briefing on [company] before my meeting: what they do, recent news, leadership, financial highlights and 5 smart questions to ask. Cite your sources.
Analyse the attached spreadsheet. Describe the data, find the 5 most important trends, make 2 charts that show them, and list any data-quality problems you notice.
I'm choosing between [option A] and [option B] for [goal]. List the criteria that matter, score both from 1 to 5 on each with reasons, and tell me what would change your recommendation.
Write a [1,200]-word blog post about [topic] for [audience]. Start with an outline for my approval. Use short paragraphs and subheadings, and end with one clear takeaway.
Rewrite this to be clearer and about 30% shorter, keeping my meaning and tone: [paste text]. Then list the main changes you made.
Write a [friendly / firm] email to [who] about [situation]. My goal is [what I want]. Keep it under [120] words, with a clear subject line and one specific ask.
Rewrite this message in three tones: formal, friendly and very brief. [paste message]
Act as a tough editor. Review my draft for structure, clarity and argument. Give your top 5 fixes in order of impact, with an example rewrite for each. [paste draft]
Give me 10 headline options for an article about [topic] for [audience]: 3 straightforward, 3 curious, 3 benefit-led and 1 bold. Mark your top pick and say why.
Turn this article into a LinkedIn post under 200 words, 3 X posts and an Instagram caption. Keep every fact accurate and end each with a question to start discussion. [paste or attach article]
Create a [10]-slide presentation on [topic] for [audience]. One idea per slide, a strong title on each, simple charts where useful, and speaker notes. Use [currency and units] throughout.
Turn these meeting notes into a clean report: summary, decisions, action items with owners and dates, and open questions. [paste notes]
Translate this into [language] for readers in [country]. Keep the meaning, adapt idioms and units, and list any phrases that don't translate well. [paste text]
Write a [500]-word [genre] short story for [audience] about [idea]. Include a twist and end on a hopeful note.
Write a product page for [product] aimed at [customer]: a headline, 3 benefit bullets, a short FAQ and a call to action. Plain words, no hype, no claims I haven't given you.
Take a look at this project's directory structure and briefly describe what each directory is for. Then explain how a request flows from the entry point to the database.
Add [feature] in [file or module]. Follow the existing code style, write unit tests for normal and edge cases, run the tests and summarise what you changed.
This test is failing: [paste error]. Find the root cause, fix the code rather than the test, run the full test suite again and explain the bug in two sentences.
Plan first, don't edit yet: how would you split [file] into smaller modules without changing behaviour? List the steps and risks, then wait for my approval.
Review this diff like a senior engineer: [paste diff]. List bugs, security issues, performance problems and missing tests in order of severity, with line numbers and suggested fixes.
Write tests for [function or file] using [framework]. Cover normal cases, edge cases and errors, with clear names and one behaviour per test.
Explain what this code does, step by step, for a [junior] developer. Then point out anything risky or confusing. [paste code]
Write a [PostgreSQL] query that [goal]. Tables: [schema]. Explain how it works and suggest indexes if it would be slow on [number] rows.
Convert this [Python] code to [TypeScript], keeping the behaviour identical. Use idiomatic patterns and list anything that doesn't map cleanly. [paste code]
Build this screenshot as a responsive [React + Tailwind] component. Match the layout, spacing and colours, use semantic HTML and make it accessible.
Write a [bash] script that [task]. Make it safe to run twice, add comments, and show an example run with expected output.
Write a README for this project: what it does, how to install and run it, configuration, usage examples and how to contribute. Keep it short and check every command against the code.
No prompts match. Try another word, or build your own.
Fill in what you can. Your prompt updates as you type, ready to copy into Kimi.
Three vague prompts rewritten with a goal, details, a format and a check.
The same prompt can work better in a different mode. Match the job to the right place in Kimi.
| Your job | Best place in Kimi | Why |
|---|---|---|
| Quick questions, rewrites, emails | Chat | Fast answers. Turn thinking down or off for speed. |
| Hard reasoning, maths, decisions | Thinking | K3.1 Pro thinks step by step. Use high or max effort. |
| Cited reports from many sources | Deep Research | Searches, reads and writes a cited report, typically in 10–25 minutes. |
| Many items researched at once | Agent Swarm | Splits big jobs across many sub-agents in parallel. |
| Presentations, documents, sheets, websites | Slides, Docs, Sheets, Websites | Built-in agents create the file for you, ready to edit and export. |
| Coding in a real project | Kimi Code | Reads, edits and tests your code. Press Shift-Tab for Plan mode. |
| Files and folders on your computer | Kimi Work | Type / for Skills and @ to add files, then let it work in your folders. |
Agent tasks such as Deep Research, Agent Swarm and Slides use agent credits. Learn more: how to use Kimi, Kimi Code, Kimi Work and creating presentations.
Kimi K3.1 Pro reads about a million tokens. Attach full reports, contracts or codebases instead of summarising them yourself.
Ask for a source for every number and page numbers for document answers, so you can check them quickly.
Say the currency, units and date range you want. Testers found Kimi can otherwise mix currencies in slides.
Add 'Ask me up to 3 questions before you start' for big or unclear jobs. It saves rewrites.
Use low thinking effort for simple jobs and max for hard ones. Max is slower and uses more credits.
Ask for an outline or plan first, approve it, then the full piece. For code, use Plan mode.
End with 'Check your answer against my requirements and list anything you missed'.
Save prompts that work and reuse them with new [brackets]. Kimi Work can turn them into Skills.