context-engineering

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

Updated May 13, 2026
One-click install
npx skills add https://github.com/sapatamuku-creator/mastersapatamuku --skill context-engineering-sapatamuku-creator
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: context-engineering
Source: https://github.com/sapatamuku-creator/mastersapatamuku/tree/main/releases/v2.7/.agents/skills/context-engineering
Command: npx skills add https://github.com/sapatamuku-creator/mastersapatamuku --skill context-engineering-sapatamuku-creator

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 systematic method for curating what the agent sees at each stage of a session. ## Core Features & Use Cases - Five-Level Context Hierarchy: Structures context from persistent rules files (CLAUDE.md, .cursorrules, AGENTS.md) down to per-iteration error output and conversation history. - Context Packing Strategies: Provides templates like the Brain Dump, Selective Include, and Hierarchical Summary for loading only task-relevant files and specs. - Confusion Management: Defines patterns for surfacing spec conflicts, missing requirements, and inline plans instead of silently guessing. - Use Case: When starting a new feature, you create a CLAUDE.md with your tech stack, commands, and conventions, then load only the relevant spec section and source files so the agent follows existing patterns instead of inventing new ones. ## Quick Start Ask the agent to create a CLAUDE.md rules file for this project covering the tech stack, build commands, code conventions, and boundaries before starting the next task.

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 at the project root covering tech stack, build and test commands, code conventions, and boundaries such as 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. Loading more than roughly 5,000 lines of non-task-specific content causes the agent to lose focus, so include only relevant files, spec sections, and one pattern example.

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

Cursor uses .cursorrules or .cursor/rules/*.md, 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 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 context before critical work.

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

It should surface the conflict explicitly with options rather than silently picking one interpretation. Present the spec requirement, the existing pattern, and possible resolutions, then ask the user which approach to take.