temporal-patternslisted

Catalog of Temporal's official, battle-tested Workflow design patterns (Saga, Continue-As-New, Signal-with-Start, Entity Workflow, Fan-Out, Fairness, Local Activities, Approval, and ~30 more) by problem domain, with a problem-to-pattern routing map and live links to each pattern's canonical page. Use WHENEVER working with Temporal design patterns in any mode: writing or reviewing Workflow/Activity code (pick the right named pattern and fetch its page before coding), answering customer or teammate questions on how to solve a problem in Temporal (map it to a pattern, explain tradeoffs), or building slides, decks, or enablement (exact names, domain groupings, canonical descriptions). Trigger even when the user never says "pattern" — e.g. "how do I do human approval in a workflow", "my history is getting too big", "undo earlier steps when a later one fails", "don't overwhelm the downstream API", "one tenant is starving the others". Trigger just as much when the problem is framed by use case or industry rather tha
dustinruehle/temporal-patterns-skill · ★ 1 · AI & Automation · score 75

Install: claude install-skill dustinruehle/temporal-patterns-skill

# Temporal Design Patterns Temporal's durable-execution primitives compose into a catalog of proven, named design patterns. Reaching for a named pattern beats inventing a Workflow shape: the pattern already encodes the failure handling, the history-growth control, and the edge cases someone else already hit. This skill exists so that — whether coding, answering a question, or building a deck — you select from the catalog first and pull canonical detail on demand. ## The one rule that makes this skill work **The catalog below is an index, not the implementation.** Each pattern has a canonical markdown page. Select the pattern from memory using the index and routing map here; **fetch the pattern page before writing implementation code or asserting specifics** (guarantees, limits, SDK support, exact mechanics). Do not reconstruct pattern code from memory — the pages are the source of truth and stay current as SDKs change. This matters most for customer-facing work, where a confident-but-stale detail is worse than a fetched, verified one. ### URL construction (deterministic) - Full index: `https://docs.temporal.io/design-patterns.md` - Any pattern: `https://docs.temporal.io/design-patterns/{slug}.md` - Example: `https://docs.temporal.io/design-patterns/saga-pattern.md` The `{slug}` for every pattern is in the catalog tables below. Append `.md` for the clean, token-cheap version (drop it for the human-readable web page to share with a customer). If fetching isn't available