Works with the AI tools you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIMuseMuseDotsDots+22 more

    context engineering

    1

    Architect, audit, and optimize context systems for coding agents, MCP workflows, and RAG pipelines.

    $12

    Secure checkout via Stripe

    30-day refund guarantee

    Converts to your local currency at checkout

    Security scanned
    context engineering

    context engineering

    Example session with this skill installed

    My Claude Code agent keeps ignoring our Vitest patterns and trying to use Jest. Here is my current CLAUDE.md and a sample test file. Audit this and fix the context drift.

    • Read your context and instructions
    • Compiled the context engineering
    • Generated the document

    I have audited your CLAUDE.md and the provided test sample. The primary issue is context confusion: your instructions mention "standard JavaScript testing" which the model is defaulting to Jest, while your file structure uses .test.ts with Vitest-specific globals.

    Context Audit & Repair for Vitest Migration

    FindingImpactRecommended Fix
    Ambiguous ToolingAgent defaults to Jest globals (describe, it)Explicitly define Vitest as the sole test runner in CLAUDE.md.
    Missing CommandsAgent guesses npm test which failsAdd specific Vitest CLI commands to the Test Commands section.
    Pattern StarvationNo example of a Vitest mock in contextAdd a concise "Golden Example" block for component mocking.
    Context PoisoningStale reference to setupTests.jsRemove legacy Jest setup references from the project rules.

    Updated CLAUDE.md Section

    
## Testing Conventions
- Use Vitest for all unit and integration tests.
- Test files must reside in `src/**/__tests__/*.test.ts`.
- Use `vi.mock()` for dependency injection; do not use `jest.mock()`.
- Run specific test: `npx vitest run <path>`
- Run all tests: `npm run test:ci`

## Golden Example (Vitest)
import { vi, test, expect } from 'vitest';
import { service } from './service';
test('logic', () => {
  const spy = vi.spyOn(service, 'call');
  // ... test logic
});

    Next steps

    1. Replace the ## Testing section in your root CLAUDE.md with the updated block above.
    2. Run npx vitest run and provide the output to the agent to verify it recognizes the environment.
    3. If the agent still confuses syntax, we should implement a .cursorrules file for editor-level enforcement.

    context-engineering.pdf

    PDF · document

    Generated

    Example file from a real run - the skill writes it into your workspace.

    Connects securely to your tools. The creator never sees your data.

    What you get

    Create CLAUDE.md and AGENTS.md files for new coding projects.Fix context drift where agents ignore project-specific conventions.Design handoff packets for multi-agent workflows to maintain state.Optimize RAG retrieval patterns to reduce token noise and cost.

    About this skill

    The problem

    Coding agents and RAG pipelines often suffer from context collapse, hallucinated APIs, or token waste. Developers struggle to manage the boundaries between static instructions, dynamic project rules, and retrieved knowledge, leading to degraded agent performance over long sessions.

    What it does

    • Designs structured CLAUDE.md, AGENTS.md, and .cursorrules files to enforce project conventions.
    • Audits existing context setups to identify starvation, poisoning, or conflicting instructions.
    • Creates multi-agent handoff packets that preserve state, authority, and evidence across transitions.
    • Develops retrieval strategies and memory architectures for RAG systems to minimize noise.
    • Builds context compression and eviction plans to stay within token budgets without losing critical detail.

    Frameworks & tools

    Claude Code, Cursor, GitHub Copilot, MCP (Model Context Protocol), RAG architectures, and agentic workflows.

    Why this beats prompting it yourself

    Writing a good prompt is not enough for complex agents. This skill applies information architecture to context, separating static rules from dynamic state. It prevents context drift by establishing formal quality gates and handoff contracts that work across multi-turn loops.

    Use cases

    • Setting up a new repository for Claude Code or Cursor with strict architectural rules.
    • Diagnosing why an agent is missing local testing conventions or hallucinating legacy code.
    • Defining the data contract and escalation paths for a multi-agent orchestration system.
    • Optimizing a RAG pipeline's context window by ranking and compressing retrieved artifacts.

    Known limitations

    Does not modify live source code directly without a prior design review. Requires manual input of environment-specific constraints like token limits or write permissions.

    How to install

    Works the same in every agent - Claude, Cursor, Codex, Copilot and 20+ more.

    ~30 seconds
    1. 1

      Download the ZIP

      Free skills download straight away. Paid skills unlock right after purchase.

    2. 2

      Unzip into your skills folder

      Every agent reads skills from one folder on your machine. Drop the unzipped folder in there.

    3. 3

      Ask your agent to use it

      Restart the agent if it was already running. It picks the skill up automatically - no config needed.

    Skills folder by agent

    Click the path to copy it. Create the folder if it does not exist yet.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill passes our trust checks below.

    Security scanned

    Passed our 8-point scan before listing

    Fresh listing

    Recently published to Agensi

    30-day refund

    Not a fit? Get your money back

    Trust & safety

    Security scanned

    Verified clean 1 month ago

    • Passed all security checks, Safe to install

    Listed1 month ago

    What's inside

    Frequently Asked Questions