Every pattern page should follow a uniform structure. That way the wiki is not just a collection of articles — it becomes a knowledge base that can be searched, compared, and have its navigation auto-generated.
Page frontmatter
YAML
title: Supervisor / Manager
description: A primary agent plans, routes, and synthesizes; specialists execute subtasks.
category: Control
difficulty: medium
production_readiness: high
related_patterns:
- agents-as-tools
- graph-workflow
- generator-critic
Page sections
- Definition
- Structure (Mermaid)
- When to use
- When not to use
- How to implement
- Minimal pseudocode
- Recommended trace events
- Common failure modes
- Implementation checklist
- References
Pattern metadata
TypeScript
export type PatternMeta = {
slug: string;
title: string;
category: "control" | "information" | "decision" | "environment" | "protocol";
difficulty: "easy" | "medium" | "hard";
productionReadiness: "low" | "medium" | "high";
latencyCost: "low" | "medium" | "high";
tokenCost: "low" | "medium" | "high";
bestFor: string[];
avoidWhen: string[];
related: string[];
};
Suggested site layout
Text
docs/
├─ index.md
├─ taxonomy.md
├─ decision-matrix.md
├─ patterns/
│ ├─ index.md
│ ├─ supervisor-manager.md
│ ├─ handoff-router.md
│ └─ ...
├─ implementation/
│ ├─ production-runtime.md
│ ├─ orchestrator.md
│ ├─ observability.md
│ └─ safety-guardrails.md
└─ reference/
├─ glossary.md
└─ references.md