context-engineering

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

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? AI coding agents produce poor output when they receive too little context (hallucinated APIs, ignored conventions) or too much context (lost focus, degraded quality). This Skill provides a structured methodology 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, .cursorrules, AGENTS.md) 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 context window. - Confusion Management: Defines explicit patterns for surfacing spec conflicts, missing requirements, and ambiguity instead of letting the agent silently guess. - Use Case: When starting a new feature, you load only the relevant spec section, the files to modify, one existing pattern example, and a constraints list, keeping focused context under 2,000 lines per task. ## Quick Start Ask the agent to help you create a CLAUDE.md rules file covering your tech stack, commands, conventions, and boundaries before starting your 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 set up a CLAUDE.md rules file for my project?▼

Create a CLAUDE.md file at your project root covering tech stack, build and test commands, code conventions, and boundaries like never committing secrets. Include one short example of a well-written component so the agent follows your style.

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

Aim for under 2,000 lines of focused context per task. Include only the files you will modify, related tests, one existing pattern example, and relevant constraints. Loading more than 5,000 lines of non-task-specific context degrades output quality.

What is the equivalent of CLAUDE.md for Cursor or 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 persistent project-wide rules.

Why does my AI agent ignore project conventions as the conversation gets longer?▼

Long conversations accumulate stale context that dilutes the original instructions. Start fresh sessions when switching major features, summarize progress periodically, and compact the conversation before critical work.

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 the human, and let the user decide before implementing.