context-engineering

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

Updated Jun 13, 2026
One-click install
npx skills add https://github.com/22Teikk/22Teikk-Agent-Skills-Hub --skill context-engineering-22teikk
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: context-engineering
Source: https://github.com/22Teikk/22Teikk-Agent-Skills-Hub/tree/main/core/skills/context-engineering
Command: npx skills add https://github.com/22Teikk/22Teikk-Agent-Skills-Hub --skill context-engineering-22teikk

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 (lost focus, degraded quality). This Skill provides a structured method for deciding what information an agent sees, when it sees it, and how it is organized across a session. ## Core Features & Use Cases - Five-Level Context Hierarchy: Structures context from persistent rules files (CLAUDE.md, .cursorrules, AGENTS.md) down through specs, source files, error output, and conversation history. - Digest Delegation Pattern: Delegates heavy codebase reading to subagents that return capped, structured summaries, keeping the main session's context window free for planning. - Confusion Management: Provides explicit patterns for surfacing spec conflicts, missing requirements, and ambiguity instead of silently guessing. - Use Case: When starting a new feature, you load only the relevant spec section, the files to modify, one existing pattern example, and a rules file — then verify the agent references real project APIs rather than invented ones. ## Quick Start Ask the agent to help you write a CLAUDE.md rules file covering your tech stack, build commands, 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 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: the files being modified, related tests, one existing pattern example, and relevant constraints. Loading more than roughly 5,000 lines of non-task-specific content degrades output quality.

When should I delegate codebase reading to a subagent?▼

Delegate when answering a question requires scanning more files than you can name up front, such as mapping a module or finding every usage of a pattern. Have the subagent return a capped digest of findings with path:line pointers instead of raw file contents.

Why does agent output quality degrade in long conversations?▼

Long sessions accumulate stale context that crowds out current instructions. 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?▼

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 which approach to take.