Kimi K3 Prompt Generator

Build a production-ready [component name] in [React / Vue / Svelte] with TypeScript. Requirements: - Props: [list your props with types] - Behaviour: [describe what it does] - Edge cases to handle: [empty state, loading, error] - Styling: [Tailwind CSS / CSS Modules / styled-components] Deliver: 1. The complete component file 2. A TypeScript interface for props 3. Three usage examples showing different prop combinations 4. Any accessibility (ARIA) attributes needed

Diagnose this bug systematically. Work through every plausible cause before settling on the most likely one. Error: ``` [Paste error message or stack trace] ``` Relevant code: ``` [Paste the code] ``` Environment: [OS, runtime, package versions] Already tried: [list what you've attempted] Deliver: 1. Ranked hypothesis list (most → least likely) with one-line reasoning for each 2. The fix for the top cause — exact line changes 3. Steps to take if the top fix doesn't work 4. How to prevent this class of bug in future

I am pasting our entire codebase below (up to 1M tokens). Review it and identify: 1. ARCHITECTURE ISSUES — structural problems that will compound as the codebase grows 2. SECURITY VULNERABILITIES — any code that could be exploited (injection, insecure auth, exposed secrets) 3. PERFORMANCE HOTSPOTS — functions or patterns that will not scale 4. DEAD CODE — unused exports, imports, or entire files 5. MISSING TESTS — the 5 highest-risk paths with no test coverage For each finding: file, line number, one-sentence description, and the specific fix. [Paste codebase here]

Optimise this SQL query for maximum performance. Explain every change. Database: [PostgreSQL / MySQL / SQLite] Table sizes: [e.g. orders: 8M rows, users: 600K rows] Indexes that exist: [list them] Current query: ```sql [Paste your query] ``` Deliver: 1. The rewritten query 2. A bullet list of every change and why it helps 3. Any new indexes to create (exact CREATE INDEX statement) 4. The expected performance improvement (rough order of magnitude)

Synthesise the following research papers into a structured report for a technical audience. Papers: [paste abstracts, or full text if short enough] Topic: [the shared subject] Audience: [describe their background] Report structure: 1. CONSENSUS — what all papers agree on 2. CONTRADICTIONS — where they disagree and why 3. METHODOLOGY GAPS — weaknesses in the evidence base 4. PRACTICAL TAKEAWAYS — 3 actionable conclusions for someone working in this field 5. OPEN QUESTIONS — what research still needs to be done Target length: 600–800 words.

Help me choose between these architectural approaches for the following system. System: [describe what you're building] Scale targets: [users, requests/sec, data volume] Team size: [engineers, their expertise] Options: - Option A: [describe] - Option B: [describe] - Option C: [describe, or omit if only two] Deliver: 1. A weighted trade-off matrix (latency, operational complexity, cost, scalability, team fit) 2. Your recommendation with a clear rationale 3. The strongest argument AGAINST your recommendation 4. The first proof-of-concept I should build to validate the key assumption

I am attaching a screenshot of a UI. Convert it to clean, working [React / HTML+Tailwind / Vue] code. Instructions: - Match the layout as closely as possible - Use semantic HTML elements - Make it responsive (mobile-first) - Replace any real text with realistic placeholder text - Do not use inline styles — use utility classes After the code, add: - A list of any design decisions you made where the screenshot was ambiguous - Any accessibility improvements beyond what the screenshot shows [Attach screenshot]

Execute the following multi-step task. Before each step, state what you are doing and what information you need. Pause and ask if a decision requires my input. Task: [describe the goal, e.g. 'Analyse our Q3 support tickets, identify the top 5 recurring issues, draft a proposed fix for each, and create a prioritised roadmap'] Available context: [Paste your data, documents, or starting information] After all steps, write: 1. A one-paragraph executive summary of what you found 2. The single highest-priority action I should take this week 3. What you would do next if you had more time

Prove the following statement. Show every deduction explicitly — do not skip steps. Statement: [state the proposition to prove] Allowed axioms / theorems: [list any you want to restrict to, or say 'standard undergraduate mathematics'] Preferred proof style: [direct / contradiction / induction / construction] Format: - Number each step - State the rule or theorem applied at each step in parentheses - End with a clear QED statement If the statement is false, prove why and provide the correct version.

Write a competitive landscape brief for the following market. Our product: [one sentence description] Target customer: [describe] Competitors to analyse: [list 5–6 companies] For each competitor: - Their primary value proposition (one sentence) - Estimated customer profile - One thing they do better than us - One thing we do better than them - Their apparent pricing model End with: the white space in this market — what positioning is genuinely unclaimed that we could own in the next 12 months?

Design a RESTful API for the following system. Deliver a complete OpenAPI 3.1 YAML spec. System: [describe what the API controls] Key entities: [list them — e.g. users, orders, products] Auth: [bearer token / API key / OAuth2] Special requirements: [pagination, rate limiting, webhooks, etc.] For each endpoint include: - Method and path - Description - Request body schema with validation rules - Response schemas (200 and all error codes) - One curl example Also write a short README section explaining the authentication flow.

Generate a comprehensive test suite for the following function using [Jest / Vitest / pytest]. Function: ``` [Paste the function] ``` Cover: - Happy path (normal inputs) - Edge cases (empty, null, zero, negative) - Boundary conditions (min/max values) - Invalid inputs (wrong types, malformed data) - Async behaviour (if applicable) For each test: - Use a descriptive name: what scenario + what result - Follow AAA pattern (Arrange / Act / Assert) - Add a one-line comment explaining why this case matters

I am pasting a long document below. Extract the key information into a structured summary. Document type: [contract / research report / technical spec / meeting transcript / legal filing] My role: [describe who you are and what decision you need to make] Most important questions to answer: 1. [Your first question] 2. [Your second question] 3. [Your third question] Deliver: 1. A 200-word executive summary 2. Direct answers to my three questions with page/section references 3. Any critical information I did NOT ask about but should know 4. A list of any ambiguous or missing information [Paste document]

Analyse the chart or data table in the attached image. Context: [describe what the data is measuring, the time period, and the source if known] Decision I'm making: [describe what business or technical decision this data informs] Deliver: 1. The single most important trend in this data 2. The most surprising or counterintuitive finding 3. What the data does NOT tell me that I might wrongly assume 4. One sentence recommendation based on this data 5. What additional data I should collect to be more confident [Attach chart or table image]

Audit the following code for security vulnerabilities. Check against OWASP Top 10 and common patterns for this stack. Stack: [language, framework, database] Code: ``` [Paste the code] ``` For each vulnerability found: - Severity: Critical / High / Medium / Low - CWE number (if applicable) - Description: what is wrong and how it could be exploited - Fix: the specific code change needed - Prevention: how to avoid this class of issue in future End with a one-paragraph overall security assessment.

Migrate the following code from [source language/framework] to [target language/framework]. Source code: ``` [Paste the code to migrate] ``` Migration requirements: - Preserve all existing behaviour exactly - Follow [target framework]'s idiomatic patterns and conventions - Replace deprecated or unavailable APIs with the target ecosystem's equivalents - Add TypeScript types / type hints if the target language supports them After the migrated code: 1. A diff-style summary of what changed and why 2. Any behaviour differences I should test manually 3. Dependencies to add (exact package names and versions)

Write a 1,500-word technical article for [your publication / audience]. Topic: [your topic] Primary keyword: [must appear in H1, intro, and at least twice in body] Audience expertise level: [beginner / intermediate / senior engineer] Tone: [conversational / authoritative / tutorial-style] Structure: - H1 containing the primary keyword - 120-word intro that states the reader's problem and promises a specific takeaway - 4–5 H2 sections, each with a concrete example (not hypothetical) - Code snippets where relevant - 100-word conclusion with a single clear next step Do not use filler phrases or restate the intro in the conclusion.

Design a data pipeline architecture for the following use case. Data sources: [list them — databases, APIs, file uploads, streams] Data volume: [GB/day, rows/hour, or events/second] Output consumers: [dashboards, ML models, data warehouse, APIs] Latency requirement: [real-time <1s / near-real-time <5min / batch daily] Team: [engineers and their expertise with data tools] Deliver: 1. An architecture diagram described in text (source → transform → sink) 2. Tool recommendations for each layer with one-line rationale 3. The two biggest failure modes and how to mitigate them 4. A phased rollout plan: MVP (1 week) → production-ready (1 month)

Prepare me for a technical interview at [company type / stage] for a [role title] position. My background: [2–3 sentences on your experience] Role focuses on: [key responsibilities from the job description] Interview format: [coding round / system design / behavioural / all three] Deliver: 1. The 6 most likely technical questions for this specific role 2. A strong answer framework for each — key points to hit, not a full script 3. One system design question I should expect and a structured approach to answer it 4. The 3 questions I should ask the interviewer to signal strategic thinking 5. One weakness I should avoid mentioning given this role

Write a complete Product Requirements Document for the following feature. Feature: [name] Problem: [one sentence on the pain point] Target user: [describe] Success metric: [how will you know it worked?] PRD must include: 1. PROBLEM STATEMENT — 2 paragraphs: current pain and why it matters now 2. PROPOSED SOLUTION — what we are building (not how) 3. USER STORIES — 5 stories: 'As a [user], I want [goal], so that [reason]' 4. ACCEPTANCE CRITERIA — testable conditions for each user story 5. OUT OF SCOPE — 3 things explicitly NOT in v1 6. OPEN QUESTIONS — 3 undecided items and who owns each 7. TIMELINE — phases (discovery / build / launch) in sequence, no dates