context-engineering

Configures rules files and curates context layers to improve agent output quality.

Updated Sep 5, 2026
One-click install
npx skills add https://github.com/nntoan/ultra-omp --skill context-engineering-nntoan
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: context-engineering
Source: https://github.com/nntoan/ultra-omp/tree/main/packages/proflow/skills/context-engineering
Command: npx skills add https://github.com/nntoan/ultra-omp --skill context-engineering-nntoan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? AI coding agents hallucinate APIs, ignore project conventions, and degrade in quality when they receive too little context or are flooded with irrelevant information. This Skill provides a structured method for curating exactly what the agent sees at each stage of a session. ## Core Features & Use Cases - Five-Level Context Hierarchy: Organizes context from persistent rules files (CLAUDE.md, AGENTS.md, .cursorrules) down to transient conversation history, with templates for each level. - Context Packing Strategies: Provides Brain Dump, Selective Include, and Hierarchical Summary patterns for loading task-relevant files, specs, and error output without flooding the context window. - 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, load only the relevant spec section, the files to modify, one existing pattern example, and the specific test error output, keeping focused context under roughly 2,000 lines per task. ## Quick Start Ask the agent to set up a CLAUDE.md rules file for this project covering the tech stack, 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. Include only the files being modified, related tests, one existing pattern example, and the specific error output, rather than loading entire specs or large file sets.

What is the equivalent of CLAUDE.md for Cursor or GitHub Copilot?▼

Cursor uses .cursorrules or .cursor/rules/*.md files, GitHub Copilot uses .github/copilot-instructions.md, Windsurf uses .windsurfrules, and OpenAI Codex uses AGENTS.md. All serve the same purpose of persistent project-wide rules.

Why does agent output quality degrade in long conversations?▼

Long conversations accumulate stale context referencing outdated patterns or deleted code. Start fresh sessions when switching major features, summarize progress periodically, and compact the conversation before critical work.

When should an AI agent ask instead of guessing on requirements?▼

The agent should stop and ask when the spec conflicts with existing code or when a requirement is missing with no precedent in the codebase. It should surface the ambiguity with concrete options rather than silently picking an interpretation.