context-engineering

Configures rules files and curates context layers for AI coding agents.

Updated Jul 10, 2026
One-click install
npx skills add https://github.com/CodeCrafterAdi2006/Ink-and-Code --skill context-engineering-codecrafteradi2006
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: context-engineering
Source: https://github.com/CodeCrafterAdi2006/Ink-and-Code/tree/main/Skills/context-engineering
Command: npx skills add https://github.com/CodeCrafterAdi2006/Ink-and-Code --skill context-engineering-codecrafteradi2006

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? AI coding agents produce inconsistent output, hallucinate APIs, and ignore project conventions when they receive too little context or lose focus when flooded with too much. This Skill provides a structured methodology for curating exactly what an 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 through specs, source files, error output, and conversation history. - Context Packing Strategies: Provides templates like the Brain Dump, Selective Include, and Hierarchical Summary for loading focused, task-relevant context under 2,000 lines. - Confusion Management: Defines explicit patterns for surfacing spec conflicts, missing requirements, and inline planning instead of silently guessing. - Use Case: When starting a new feature in a large codebase, use this Skill to write a rules file covering 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 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 set up a CLAUDE.md rules file for my project?

Create a CLAUDE.md file 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?

Aim for under 2,000 lines of focused, task-relevant context per task. Loading more than 5,000 lines of non-specific context degrades output quality because context window size does not equal attention budget.

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, and AGENTS.md for OpenAI Codex. All define project-wide conventions loaded every session.

Why does my AI agent ignore project conventions?

The agent cannot follow conventions it has never seen. If rules are not written in a persistent rules file, they effectively do not exist, so the agent invents APIs and patterns instead of matching your codebase.

When should I start a fresh session instead of continuing?

Start a fresh session when switching between major features or when conversation history grows long and stale. Accumulated context causes the agent to reference outdated patterns and deleted code.

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

Do not silently pick one interpretation. Surface the conflict explicitly with the spec statement, the contradicting code location, and concrete options, then ask which approach to take before implementing.