Kimi K3's long context is useful, but a large window is not a reason to send everything by default.
Treat context as a budget
Context is both capability and cost. Repository files, documentation, logs, screenshots, retrieval results, and chat history all compete for the same prompt budget.
Before a production workflow launches, decide which context is always needed, which context is optional, and which context should be retrieved only when the task requires it.
Keep stable prefixes stable
Stable system instructions, rubrics, repository maps, and policy text are easier to cache and review. Avoid rewriting the same stable block in slightly different ways across requests.
For coding tasks, include a concise project map first, then add the exact files needed for the requested change.
Watch multi-turn growth
Multi-turn conversations can grow quickly because previous messages become part of the next request. Summarize or reset when old turns stop helping the task.
Use logs to measure real input size. A context plan that looks clean in a demo can become expensive when used all day by a team.