domains / families / agent-tooling / context-fundamentals

context-fundamentals

combined

This skill should be used when the user asks to "understand context", "explain context windows", "design agent architecture", "debug context issues", "optimize context usage", or discusses context components, attention mechanics, progressive disclosure, or context budgeting. Provides foundational understanding of context engineering for AI agent systems. This skill should be used to explain or reason about the foundational concepts of context engineering: what context is, the anatomy of a context window, how attention mechanics work, the U-shaped attention curve, why context quality matters more than quantity, and the mental models needed to interpret every other context-engineering decision. Use this for conceptual explanation, onboarding, and background reading. Route operational work to the specialized skills: debugging attention failures goes to context-degradation, token-efficiency work goes to context-optimization, conversation summarization goes to context-compression, and project-shape decisions go to project-development.

When to use

• Designing new agent systems or modifying existing architectures
• Debugging unexpected agent behavior that may relate to context
• Optimizing context usage to reduce token costs or improve performance
• Onboarding new team members to context engineering concepts
• Reviewing context-related design decisions

When not to use

• Use this skill only when the task clearly matches the scope described above.
• Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
• Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.

Skill page

Conflict

The copies overlap heavily on the anatomy of context (system prompts, tools, retrieval, history, outputs) and the core definition of context. However, they disagree on scope and contain material steps the others lack. The muratcankoylan copy is a conceptual onboarding skill that explicitly routes operational work to other skills and introduces specific principles (U-shaped attention curve, position-aware placement, iterative curation). The foryourhealth111 and sickn33 copies are broader, covering operational topics like attention mechanics, position encoding, and the 83.9% tool output statistic, which the first copy omits. Crowning one would hide either the operational depth or the specific conceptual routing logic.