context-engineering

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

10|1|Updated Jul 29, 2026
One-click install
npx skills add https://github.com/flowing-abyss/obsidian-local-fonts --skill context-engineering-flowing-abyss
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: context-engineering
Source: https://github.com/flowing-abyss/obsidian-local-fonts/tree/main/.ai/skills/context-engineering
Command: npx skills add https://github.com/flowing-abyss/obsidian-local-fonts --skill context-engineering-flowing-abyss

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. - Confusion Management: Defines explicit patterns for surfacing conflicting specs, missing requirements, and ambiguity instead of letting the agent guess. - Use Case: When starting a new feature in a large codebase, use this Skill to write a rules file covering tech stack 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 Set up a CLAUDE.md rules file for my project and show me how to structure context for my next 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 file should cover your tech stack, build and test commands, code conventions, and boundaries such as never committing secrets. Include one short example of a well-written component in your style so the agent follows existing patterns.

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 about 5,000 lines of non-specific context causes the agent to lose focus, so include only the files, spec sections, and one pattern example relevant to the current task.

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.

Why does my AI agent ignore project conventions as the conversation gets longer?

Long conversations accumulate stale context that dilutes the rules. 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?

The agent should surface the conflict explicitly with options rather than silently picking one interpretation. It should present the discrepancy, list possible approaches, and ask which direction to take before building on an assumption.