Context Engineering

Designing what information goes into the context window and in what order.

207 stars 37 forksOther Plugin marketplace

Install

Claude Code plugin
/plugin marketplace add Owl-Listener/ai-design-skills

The repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add Owl-Listener/ai-design-skills --skill context-engineering
Manual install
git clone --depth 1 https://github.com/Owl-Listener/ai-design-skills.git /tmp/ai-design-skills
mkdir -p ~/.claude/skills
cp -r /tmp/ai-design-skills/claude-plugin/prompt-architecture/skills/context-engineering ~/.claude/skills/context-engineering

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# Context Engineering
The context window is finite. What goes into it — and in what order — determines the quality of every output. Context engineering is the practice of deliberately designing the information architecture of the context window.
## The Context Budget
Every context window has a token budget. Allocate it deliberately:
- **System prompt**: The foundational instructions (typically 5-20% of the budget)
- **Retrieved context**: Documents, data, and information pulled in for the current task
- **Conversation history**: Previous turns in the conversation
- **User input**: The current request
- **Working space**: Room for the model to generate its response
These compete for space. More retrieved context means less conversation history. A longer system prompt means less room for everything else.
## Information Architecture in Context
Order matters. The model pays different amounts of attention to different positions:
- **Beginning**: High attention. Put your most important instructions here.
- **Middle**: Lower attention. This is where information can get lost in long contexts.
- **End**: High attention. The most recent information (user input) naturally goes here.
- **Adjacent to the task**: Information placed right before the user's question gets more attention than information earlier in the context.
## Context Selection
Not everything should go into the context. Design selection criteria:
- **Relevance**: Does this information help answer the current question?
Read the full skill on GitHub

Details

Skill name
context-engineering
Path
claude-plugin/prompt-architecture/skills/context-engineering/SKILL.md
License
MIT
Repo updated
9 June 2026

FAQ

What does the Context Engineering skill do?

Designing what information goes into the context window and in what order.

How do I install the Context Engineering skill?

Claude Code plugin: /plugin marketplace add Owl-Listener/ai-design-skills. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is Context Engineering popular?

It lives in Owl-Listener/ai-design-skills, which has 207 GitHub stars and 37 forks.

Related skills

Browse the most popular Claude skills, all other skills, or write your own with the skills generator.