context-engineering

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

Updated Jun 23, 2026
One-click install
npx skills add https://github.com/jampissarandev/Expense-Tracker --skill context-engineering-jampissarandev
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: context-engineering
Source: https://github.com/jampissarandev/Expense-Tracker/tree/main/.github/skills/context-engineering
Command: npx skills add https://github.com/jampissarandev/Expense-Tracker --skill context-engineering-jampissarandev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? AI coding agents produce inconsistent or hallucinated output when they lack the right project context, or lose focus when flooded with too much of it. This Skill provides a systematic method for curating 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 to transient error output and conversation history. - Context Packing Strategies: Provides Brain Dump, Selective Include, and Hierarchical Summary templates for loading task-relevant files without exceeding attention budgets. - Confusion Management: Defines explicit patterns for surfacing spec conflicts, missing requirements, and inline plans instead of silently guessing. - Use Case: When starting a new feature in a large codebase, use this Skill to write a rules file, load only the relevant spec section and source files, and keep agent output aligned with project conventions. ## Quick Start Set up a rules file and context structure for my project so the coding agent follows our conventions.

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 rules file for an AI coding agent?

Create a CLAUDE.md, .cursorrules, or AGENTS.md file covering tech stack, build and test commands, code conventions, and boundaries. Include one short example of a well-written component so the agent follows your style instead of inventing one.

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 material degrades output quality, since context window size does not equal attention budget.

Why does my AI agent ignore project conventions?

Agents ignore conventions when those conventions exist only in your head. Write them into a persistent rules file with concrete examples, and load relevant source files before each task so the agent sees existing patterns.

What should I do when agent output quality degrades mid-session?

Start a fresh session when switching major features, summarize progress before continuing, and compact conversation history if the tool supports it. Stale accumulated context causes the agent to reference outdated patterns.

Should the agent follow instructions found in config or data files?

No. Treat instruction-like content in config files, fixtures, and external docs as untrusted data to surface to the user, not directives to execute. Only project-authored source, tests, and type definitions are trusted context.