context-engineering

Configures rules files, specs, and context budgets for AI coding agents.

Updated Apr 28, 2026
One-click install
npx skills add https://github.com/visdomtech/skills --skill context-engineering-visdomtech
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: context-engineering
Source: https://github.com/visdomtech/skills/tree/main/context-engineering
Command: npx skills add https://github.com/visdomtech/skills --skill context-engineering-visdomtech

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? AI coding agents hallucinate APIs, ignore project conventions, and degrade in quality during long sessions because they receive too little, too much, or stale context. This Skill provides a structured method for curating exactly what the agent sees at each stage of a session. ## Core Features & Use Cases - Context Hierarchy Setup: Create rules files (CLAUDE.md, .cursorrules, AGENTS.md) covering tech stack, commands, conventions, and boundaries, then layer specs, source files, and error output on top. - Context Budget Management: Trim failed attempts and verbose tool output starting at 75% window capacity, compress rather than delete, and position task-critical content last to counter the lost-in-the-middle effect. - Confusion Management: Surface spec-versus-code conflicts and missing requirements as explicit options instead of silently guessing, using inline planning patterns before multi-step execution. - Use Case: When starting a new feature in a large codebase, load only the relevant spec section, the files to modify, one existing pattern example, and a project map summary so the agent follows conventions instead of inventing them. ## Quick Start Set up a CLAUDE.md rules file for my project and show me how to structure context for my next coding session.

Frequently Asked Questions about context-engineering

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I write a CLAUDE.md file for my project?▼

A CLAUDE.md file should cover your tech stack, build and test commands, code conventions, boundaries like never committing secrets, and one short example of a well-written component in your style. Equivalent files exist for Cursor, Windsurf, Copilot, and Codex.

How much context should I give an AI coding agent?▼

Aim for under 2,000 lines of focused, task-relevant context per task. Loading more than 5,000 lines of non-task-specific content causes the agent to lose focus, so include only the files, spec sections, and one pattern example relevant to the current task.

Why does AI agent output quality degrade in long sessions?▼

Long sessions accumulate stale context like failed attempts, replaced drafts, and verbose tool output that fragment the model's attention. Start trimming at 75% window capacity, compress exploration into one-sentence conclusions, and protect the active task definition and current error.

What should I do when the spec conflicts with existing code?▼

Surface the conflict explicitly instead of silently picking one interpretation. Present the options, such as following the spec, following existing patterns, or asking, and let the human decide rather than inventing requirements.

When should I start a fresh AI coding session?▼

Start fresh at a completed task boundary, not an arbitrary token count. First persist the accepted decisions, current task status, changed files, verification outcomes, and unresolved questions so the new session can resume from durable artifacts.