- Home
- Skills
- Agents & Orchestration
- Agentic Engineering Patterns Library
Works with the AI tools you already use
Agentic Engineering Patterns Library
The patterns that avoid them exist — they're just scattered across blog posts, papers, and other people's postmortems.
$24
Agentic Engineering Patterns Library
Example session with this skill installed
I have a legal assistant agent that needs to analyze 50+ documents and summarize them. It keeps losing context and forgetting the initial instructions. How should I restructure it?
- Read your context and instructions
- Compiled the agentic engineering patterns
- Generated the UI component
Symptom first: losing context and forgetting the initial instructions across 50+ documents is context saturation, not a reasoning failure — see context-patterns.md. Start with the pattern index (pattern-index.md): this is a high-volume, repeat-the-same-work task, so the orchestration family is a pipeline or a router over batches, not a subagent team. Apply the for-loop test from orchestration-patterns.md — if the documents don't need to talk to each other, a subagent team is the wrong answer and just adds latency and coordination cost. Keep the original instructions in a durable scratchpad rather than the live context, use progressive disclosure and compaction per batch, and watch what compaction silently drops. Because this runs many times, add idempotency and a checkpoint per batch (failure-and-recovery-patterns.md) so a mid-run failure doesn't restart everything. For quality, sample summaries for review weighted to the riskiest documents and verify against the source instead of trusting the agent's self-report (oversight-and-evaluation-patterns.md). Patterns rejected and why: subagent team (no inter-document dependency), and a single agent holding all 50 documents (guarantees the saturation you're already seeing). This is design guidance — you implement it in your own stack.
agentic-engineering-patterns-library.tsx
TSX · React component
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
About this skill
Most agent systems fail the same handful of ways: the single agent given twelve tools that picks the wrong one, the subagent team that was really a sequential job, the loop with no exit, the memory that poisons the next run, the agent that claims it's done and isn't. The patterns that avoid them exist — they're just scattered across blog posts, papers, and other people's postmortems. This is the reference: what holds up in production, when each pattern applies, when each is the wrong answer, and what it costs. It ships as seven reference files. A pattern index maps symptoms and requirements to the right family and sets the decision order, because getting decomposition wrong cannot be fixed downstream. Orchestration covers single agent, pipeline, router, planner-executor, subagent teams, supervisor, and iterative refinement — with the for-loop test that kills most fake multi-agent designs. Context covers progressive disclosure, retrieval, compaction and what it silently loses, scratchpads, isolation, memory hygiene, and the rent every token pays on every call. Tool design covers granularity, descriptions as the real interface, argument design that doesn't force the model to invent values, read/write separation, authorization gates, and error returns that teach instead of triggering blind retries. Failure and recovery covers budgets and stop conditions, loop detection on state rather than repetition, retry discrimination, checkpointing, visible degradation, the defined give-up, and idempotency for a world where everything runs twice. Oversight and evaluation covers approval gates versus approval fatigue, review sampling weighted to risk, verification over self-reports, golden sets, adversarial cases, judge bias and its mitigations, and trajectory evaluation. A final file covers composition — which combinations reinforce, which quietly fight — and works a full support-triage agent design end to end, including the patterns it rejects and why. It is a reference library and design aid, not a framework, runtime, or code generator: it doesn't install anything, run your agent, or write your tool implementations, and patterns are judgment aids rather than guarantees. Works with Claude Code, Cursor, Codex CLI, Gemini CLI, and any SKILL.md agent.
How to install
Works the same in every agent - Claude, Cursor, Codex, Copilot and 20+ more.
- 1
Download the ZIP
Free skills download straight away. Paid skills unlock right after purchase.
- 2
Unzip into your skills folder
Every agent reads skills from one folder on your machine. Drop the unzipped folder in there.
- 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
6 installs
Downloaded by developers to date
30-day refund
Not a fit? Get your money back
Trust & safety
Security scanned
Verified clean 2 months ago
- Passed all security checks, Safe to install