context-engineering

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

Updated Jul 9, 2026
One-click install
npx skills add https://github.com/assafmanor/waypoint --skill context-engineering-assafmanor
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: context-engineering
Source: https://github.com/assafmanor/waypoint/tree/main/.claude/skills/context-engineering
Command: npx skills add https://github.com/assafmanor/waypoint --skill context-engineering-assafmanor

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? AI coding agents produce inconsistent output when they lack the right context: they hallucinate APIs, ignore project conventions, and degrade in quality over long sessions. This Skill provides a structured methodology for feeding agents the right information at the right time. ## Core Features & Use Cases - Context Hierarchy Framework: Organizes context into five levels 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 structuring session-start and per-task context. - Confusion Management: Defines explicit patterns for surfacing conflicting specs, missing requirements, and inline planning instead of silently guessing. - Use Case: When starting a new project for AI-assisted development, use this Skill to write a CLAUDE.md rules file covering tech stack, commands, conventions, and boundaries, then apply the Selective Include pattern for each coding task. ## Quick Start Ask the agent to set up a context engineering rules file for your project covering tech stack, commands, conventions, and boundaries.

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, boundaries, and one example pattern. This file persists across sessions and is the highest-leverage context you can provide to the agent.

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

Include only files relevant to the current task, aiming for under 2,000 lines of focused context. Loading more than 5,000 lines of non-task-specific content causes the agent to lose focus and degrades output quality.

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

They are equivalent 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 agent output quality degrade in long conversations?▼

Long conversations accumulate stale context, causing the agent to reference outdated patterns or deleted code. Start fresh sessions when switching major features, summarize progress periodically, and compact context 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. Present the discrepancy, list possible approaches, and ask the user which direction to take before building on an assumption.