context-engineering

To load project context for coding and debugging, curate relevant rules, specs, source files, evidence, and conversation history using a structured checklist to ensure all necessary information is available before making changes.

Gathering focused context for adding validation to an endpoint uses selective context patterns to collect only the specific rules, specs, and source files needed for that task, reducing errors and improving coding efficiency.

You need to load context for switching codebase areas when starting a new session or moving between different parts of a project, ensuring all relevant project context is verified and available before changing code.

Context engineering reconciles external instructions with Kandev conventions by applying structured context loading and verification, ensuring that all relevant information is available and aligned before coding or debugging.

Your code lacks the right project context because all necessary rules, specs, and source files were not loaded and verified before starting the debugging session, leading to errors and reduced efficiency.

Selective context patterns for addressing failed checks are limited to gathering focused context for specific tasks, meaning they may not capture the full project scope if broader codebase changes are required.