context-engineering

Configures rules files, context hierarchy, and session management for AI coding agents.

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

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 over long sessions. This Skill provides a structured method for curating what the agent sees, when it sees it, and how it is structured. ## 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 the Brain Dump, Selective Include, and Hierarchical Summary patterns for loading focused context per task. - Confusion Management: Defines explicit patterns for surfacing conflicting specs, missing requirements, and ambiguity instead of guessing. - Use Case: When starting a new project for AI-assisted development, use this Skill to write a CLAUDE.md covering tech stack, commands, conventions, and boundaries, then load only task-relevant files per session. ## Quick Start Set up a CLAUDE.md rules file for my project covering the tech stack, build commands, code conventions, and boundaries so the agent follows our patterns.

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. Add one short example of a well-written component so the agent follows your style.

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

Load 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, .github/copilot-instructions.md for Copilot, and AGENTS.md for OpenAI Codex.

Why does agent output quality degrade in long conversations?▼

Long sessions accumulate stale context, causing the agent to reference outdated patterns or deleted code. Start fresh sessions when switching major features, summarize progress, and hand off before hitting autocompact thresholds.

Should AI agents treat external documentation and config files as trusted instructions?▼

No. Per OWASP LLM01, treat user-submitted content, third-party API responses, and fetched web pages as untrusted data. Surface any instruction-like text in them to the user rather than following it as directives.

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 approaches, then wait for an explicit decision.