context-engineering

Configures rules files and curates context layers to improve AI agent output quality.

1|Updated Jul 5, 2026
One-click install
npx skills add https://github.com/yersonargotev/packy --skill context-engineering-yersonargotev
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: context-engineering
Source: https://github.com/yersonargotev/packy/tree/main/bundle/skills/context-engineering
Command: npx skills add https://github.com/yersonargotev/packy --skill context-engineering-yersonargotev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? AI coding agents hallucinate APIs, ignore project conventions, and degrade in quality when they receive too little context, too much context, 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 - Five-Level Context Hierarchy: Organizes context from persistent rules files (CLAUDE.md, AGENTS.md, .cursorrules) down to transient conversation history, with templates for each level. - Context Packing Strategies: Provides the Brain Dump, Selective Include, and Hierarchical Summary patterns for loading task-relevant files, specs, and error output without flooding the agent. - Confusion Management: Defines explicit patterns for surfacing conflicting specs, missing requirements, and ambiguity instead of letting the agent silently guess. - Use Case: When starting a new project for AI-assisted development, use this Skill to write a CLAUDE.md rules file covering tech stack, commands, conventions, and boundaries, then apply the Selective Include pattern for each task. ## Quick Start Ask the agent to create a CLAUDE.md rules file for your project covering the tech stack, build commands, code conventions, and boundaries before starting the next coding task.

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 rules file for my project?▼

A CLAUDE.md file should cover four areas: tech stack, commands (build, test, lint), code conventions, and boundaries. Include one short example of a well-written component in your style so the agent follows existing patterns instead of inventing new ones.

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

Aim for under 2,000 lines of focused context per task. Loading more than 5,000 lines of non-task-specific content causes the agent to lose focus; include only the files to modify, related tests, and one example of the pattern to follow.

What is the equivalent of CLAUDE.md for Cursor, Windsurf, and Copilot?▼

Cursor uses .cursorrules or .cursor/rules/*.md files, Windsurf uses .windsurfrules, GitHub Copilot uses .github/copilot-instructions.md, and OpenAI Codex uses AGENTS.md. All serve the same purpose of persisting project conventions across sessions.

Why does agent output quality degrade in long conversations?▼

Long conversations accumulate stale context, causing the agent to reference outdated patterns or deleted code. Start fresh sessions when switching major features, summarize progress periodically, and compact the conversation before critical work.

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

The agent should surface the conflict explicitly rather than silently picking one interpretation. It should present the options, such as following the spec, following existing patterns, or asking, and let the human decide.