I am going to paste my entire codebase below. Using your 1M context window, read it completely before answering any questions.
After reading, answer the following:
1. [QUESTION 1 — e.g. where is the authentication logic?]
2. [QUESTION 2 — e.g. what happens if the database connection fails?]
3. [QUESTION 3 — e.g. which parts are most fragile?]
Do not guess or infer from partial reading. Read everything first.
Codebase: [PASTE ENTIRE CODEBASE]
Build the following frontend component. Optimise for clean, production-ready code — not for demo or prototype.
Framework: [REACT / VUE / SVELTE / VANILLA]
Component: [DESCRIBE IN DETAIL — what it shows, what it does, how it interacts]
Design system: [TAILWIND / MUI / CUSTOM — describe constraints]
Accessibility: [WCAG level required]
Performance constraints: [ANY SPECIFIC REQUIREMENTS — lazy load, virtual scroll, etc.]
Edge cases to handle: [LIST STATES — empty, loading, error, empty results, max items]
Write the complete, working component. Include prop types/interfaces. No placeholder comments — every section should be implemented.
[K3 is ranked #1 on SWE Marathon — use this prompt for long-horizon coding tasks]
I have a multi-step coding task that requires planning and execution across multiple files. Work through this autonomously.
Task: [DESCRIBE THE FULL FEATURE OR FIX]
Repository structure: [DESCRIBE KEY FILES AND THEIR PURPOSE]
Acceptance criteria: [EXACTLY WHAT THE FINISHED WORK MUST DO]
Do not touch: [FILES TO LEAVE UNCHANGED]
Test requirements: [WHAT TESTS ARE NEEDED]
Step 1: State your implementation plan with the files you will modify and the changes to each.
Step 2: Implement each change in full — no stubs, no TODOs.
Step 3: Write the required tests.
Step 4: Summarise what you changed and why.
[K3 tops Design Arena — use for UI component work]
Build a [COMPONENT NAME] with the following variants and states. Match the design system exactly.
Design system: [DESCRIBE — colors, spacing scale, typography, border radius]
Variants needed: [LIST — e.g. primary/secondary/ghost, small/medium/large]
States: [DEFAULT, HOVER, FOCUS, DISABLED, LOADING, ERROR]
Props interface: [DESCRIBE WHAT THE COMPONENT SHOULD ACCEPT]
Behaviour: [DESCRIBE INTERACTIONS — click, keyboard, animations]
Output: complete component code, prop types, and a usage example showing all variants and states. Production-ready, no placeholder logic.
Implement the following full-stack feature. I will paste the relevant codebase context below.
Feature: [DESCRIBE IN DETAIL]
Frontend: [FRAMEWORK AND KEY FILES]
Backend: [FRAMEWORK AND KEY FILES]
Database: [DB AND SCHEMA RELEVANT TO THIS FEATURE]
API contract: [ENDPOINTS, METHODS, PAYLOAD SHAPES]
Auth/permissions: [WHO CAN DO WHAT]
Implementation order:
1. Database schema changes (if any)
2. Backend API endpoint(s)
3. Frontend component(s) and data fetching
4. Tests (unit + integration if possible)
Write all four in full. No stubs.
Codebase context: [PASTE RELEVANT FILES]
[USE K3 ALLEGRETTO+ — $0.30/M cached input saves cost on repeated context]
I am starting a development session. Load the following project context — I will ask multiple questions and make multiple requests in this session. You should hold this context throughout.
Project context (cache this): [PASTE YOUR FULL PROJECT CONTEXT — architecture, key files, patterns, constraints]
Context loaded. Now:
Request 1: [YOUR FIRST CODING REQUEST]
After completing Request 1, wait for my next request. Do not restate the context — use it implicitly.