40 Best Kimi Prompts (2026)

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.

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 that was left unresolved.

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 and a slightly warmer one. Context they'll need: [BACKGROUND].

I've attached a document. Read it in full — you have the context window for it — 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.

Here's a task or request I've been given: [PASTE REQUEST]. Turn it into a clear, ordered checklist of concrete steps. For each step, note what "done" looks like and any input or decision I need from someone else. Flag the steps that are easy to forget, and put anything blocking at the top.

Turn on Thinking. I'm getting this error in [LANGUAGE / FRAMEWORK version]: [PASTE ERROR]. Here's the relevant code: [PASTE CODE]. Reason step by step 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. Verify your fix against the error before giving the final answer.

Explain what this code does to a developer new to [LANGUAGE / LIBRARY]: [PASTE CODE]. 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. Keep it concrete and skip the obvious lines.

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.

Turn on Thinking. Build [FEATURE] 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 any assumptions you made and how I'd test it. Verify the code meets each requirement before finishing.

I've attached a screenshot/mockup of a UI. Build it as a responsive [HTML + CSS / React] component that matches the layout, spacing, and typography as closely as you can. Use semantic markup, keep the CSS clean, and note anywhere you had to guess a value. Then list what I'd need to swap in real content or data.

Use Agent Mode. Build a [one-page / multi-page] website for [WHAT — e.g. my freelance service]. Audience: [WHO]. It needs these sections: [LIST]. Tone and style: [DESCRIBE]. Make it responsive, fast, and accessible, write real placeholder copy I can edit, and use a clean modern layout. When it's built, walk me through the structure and tell me exactly what to change to make it mine.

Use Agent Mode. Build a [10]-slide deck on [TOPIC] for [AUDIENCE / PURPOSE — e.g. an investor pitch]. Source material: [PASTE OR ATTACH]. One clear idea per slide, a strong title line on each, speaker notes underneath, and a logical arc from problem to ask. Keep the text tight and design it cleanly. Flag any slide where you're missing information from me.

Use Agent Mode with Thinking. Build a working prototype of [APP / TOOL] in [STACK]. Core features: [LIST THE MUST-HAVES]. Constraints: [DATA, DEPENDENCIES, LOOK]. Plan the build first and show me the plan, then implement it step by step, test as you go, and give me a runnable result plus setup instructions. Note any feature you cut for the prototype and why.

Use Agent Mode. I want to produce [DELIVERABLE — e.g. a launch kit: landing page, one-pager, and email sequence] for [PROJECT]. Context: [PASTE BRIEF]. Break this into sub-tasks, assign each to a specialized sub-agent, and coordinate them so the pieces are consistent in message and style. Show me the task breakdown, then deliver each part. Keep a single source of truth for the key facts.

Use Agent Mode. I do this repetitive task often: [DESCRIBE THE WORKFLOW STEP BY STEP, WITH INPUTS AND OUTPUTS]. Build me a reusable process or small tool that does it with minimal input from me. Show the steps it will take, handle the common edge cases I mention here: [EDGE CASES], and produce the output as [FORMAT]. Tell me what to paste in each time to run 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 you made. 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.

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 note the publication date next to each fact. End with what's still uncertain or contested.

Use Deep Research. Produce a thorough report on [QUESTION]. Cover: background, the key data and who's saying what, the main disagreements, and a clear bottom line. Pull from multiple independent sources, cite each with a link and date, and prefer primary sources. Structure it with headings, and end with a "what's still uncertain" section and 3 things I should verify myself.

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.

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.

I've attached a data file. Read it, then tell me: what the columns mean, the size and shape, the top patterns or trends, any outliers or data-quality issues, and the 3 findings that matter most for [MY GOAL]. Show the numbers behind each finding, and flag anything that would need more data to confirm. Don't invent values that aren't in the file.

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.

Turn on Thinking. 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.

Turn on Web search. Analyze [COMPETITOR] for me as of this month. Cover: their positioning, target customer, pricing, main strengths, obvious weaknesses, and where they're vulnerable. Then tell me three specific ways [MY COMPANY / PRODUCT] could differentiate. Cite sources with links, and separate confirmed facts from your inference.

Turn on Thinking. Help me price [PRODUCT / SERVICE]. Context: [COSTS, TARGET CUSTOMER, COMPETITORS, VALUE DELIVERED]. Propose 2-3 pricing models (e.g. tiers, usage, flat), lay out the trade-offs of each, and recommend one with the reasoning. Include the numbers, name the biggest risk in your recommendation, and suggest one experiment to test it cheaply.

Write a monthly [investor / client] update from these notes: [PASTE PROGRESS, METRICS, WINS, PROBLEMS, ASKS]. Structure it: TL;DR, key metrics, what went well, what didn't and what we're doing about it, and specific asks. Keep it honest and skimmable, lead with the numbers that matter, and don't spin the bad news. Target [LENGTH].

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.

I need to learn [SUBJECT / EXAM] by [DATE]. I can study [HOURS] per week and my current level is [LEVEL]. Build a week-by-week plan: what to cover each week, in what order, and which topics need the most time based on how hard or foundational they are. Include checkpoints to test myself and a lighter final week for review.

Quiz me on [TOPIC] at [LEVEL]. Ask one question at a time and wait for my answer before the next. After each answer, tell me if I'm right, correct any mistake with a short explanation, and adjust the difficulty based on how I'm doing. Keep going for [10] questions, then give me a summary of what I've got down and what to review.

Turn on Thinking. Be a Socratic tutor for [TOPIC / PROBLEM]. Don't give me the answer. Ask me guiding questions one at a time that lead me to work it out myself, and when I'm stuck, give the smallest hint that unblocks me rather than the solution. If I go wrong, ask a question that helps me see the mistake. Start now.

I need a [Google Sheets] formula/model 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). If a small helper column would make it cleaner, suggest it.

Use Agent Mode. Build me a spreadsheet to [PURPOSE — e.g. track a budget / plan a project]. Inputs I'll enter: [LIST]. Outputs I want: [LIST — totals, charts, summaries]. Set up the columns, add the formulas, and include a small summary section up top. Explain how to use it in three lines, and tell me which cells I edit versus which are calculated.

I've attached messy data. Clean it for me: fix inconsistent formats, standardize [DATES / NAMES / UNITS], flag duplicates and blanks, and reshape it into [DESIRED STRUCTURE — e.g. one row per record with these columns]. Return the cleaned table plus a short log of every change you made and anything you couldn't resolve without me deciding.

I've attached a file. Extract [WHAT YOU NEED — e.g. every date, name, and amount] and return it as a clean table with columns [COLUMN 1, COLUMN 2, ...]. Read the whole document, don't skip sections, and leave a cell blank rather than guessing if the value isn't stated. After the table, list anything ambiguous that you had to interpret.

I've attached a chart/screenshot of a metric. Tell me what it shows in plain English, the trend and any inflection points, what likely explains them, and what I should watch next. Then flag one way this chart could be misleading. If you need context I haven't given (time range, definitions), say what would sharpen the read.