context-engineering

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

Updated Aug 11, 2026
One-click install
npx skills add https://github.com/Kunj-Sharma03/agent-contextify --skill context-engineering-kunj-sharma03
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: context-engineering
Source: https://github.com/Kunj-Sharma03/agent-contextify/tree/main/templates/skills/context-engineering
Command: npx skills add https://github.com/Kunj-Sharma03/agent-contextify --skill context-engineering-kunj-sharma03

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 or too much unfocused context. 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 project for AI-assisted development, use this Skill to write a rules file covering tech stack, commands, conventions, and boundaries, then load only the relevant spec section and source files per task. ## Quick Start Ask the agent to set up a context rules file for your project covering the tech stack, build commands, code conventions, and boundaries before starting a new 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 rules file for my project?

A CLAUDE.md rules file should cover your tech stack, build and test commands, code conventions, boundaries, and one short example of a well-written pattern. Keep it concise since it loads into every session and shapes all agent output.

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

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

Why does my AI agent ignore project conventions?

Agents ignore conventions when those conventions are not written down anywhere they can read. Create a rules file such as CLAUDE.md, .cursorrules, or AGENTS.md documenting your conventions, since implicit knowledge does not exist for the agent.

What is the difference between CLAUDE.md, .cursorrules, and AGENTS.md?

They are equivalent persistent rules files for different tools: CLAUDE.md for Claude Code, .cursorrules or .cursor/rules for Cursor, .windsurfrules for Windsurf, AGENTS.md for OpenAI Codex, and .github/copilot-instructions.md for GitHub Copilot.

When should I start a fresh AI coding session?

Start a fresh session when switching between major features or when agent quality degrades as conversation history grows. Long conversations accumulate stale context, so summarize progress or compact deliberately before critical work.