context-engineering
Master the four operations of context engineering — Write, Select, Compress, Isolate. Manage token budgets, compaction strategies, and context partitioning to keep AI sessions sharp and efficient.
Install
With your agent
Install OMGSkills skill "rohitg00/pro-workflow:skills/context-engineering" into this agent's normal skills directory: call the OMGSkills MCP get_install_plan tool for your agent and run the script it returns (it installs only the pinned commit and verifies SKILL.md), and stop if MCP or the pin is unavailable. Do not overwrite or change existing skills without asking me.
Manual command
git clone https://github.com/rohitg00/pro-workflow /tmp/pro-workflow && ln -s /tmp/pro-workflow/skills/context-engineering ~/.claude/skills/context-engineeringFrom README
Context Engineering Four operations control everything about how context flows through an AI coding session. Master them and you control the quality of every response. The Four Operations Write — Persist Info Outside Context Move information out of the context window into durable storage so it survives compaction and session boundaries. Where to write: | Target | When | Example | |--------|------|---------| | CLAUDE.md | Permanent project rules | "Always use pnpm, never npm" | | NOTES.md / scratchpad | Working state for current task | Architecture decisions, open questions | | .claude/memory/ | Learnings and patterns | [LEARN] rules from corrections | | External files | Data too large for context | Test plans, migration checklists | Pattern — Scratchpad workflow: Select — Retrieve Relevant Info Pull the right information into context at the right time. Precision matters more than volume.
More from this repo
auto-setup
Auto-configure quality gates, hooks, and settings for a new project.
batch-orchestration
Decompose large-scale changes into independent units and spawn parallel agents in isolated worktrees.
bug-capture
Capture a user-reported defect as a durable GitHub issue written in the project's own domain language.