resonate-philosophy

Teach developers to write simple sequential Resonate workflows using yield* checkpoints.

6|Updated Jan 8, 2026

Search Tags:#best-practices #state-management #simplification #workflows #generators #durable #resonate

Ready to run

npx skills add https://github.com/resonatehq/resonate-skills --skill resonate-philosophy

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: resonate-philosophy
Source: https://github.com/resonatehq/resonate-skills/tree/main/resonate-philosophy
Command: npx skills add https://github.com/resonatehq/resonate-skills --skill resonate-philosophy

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Helps developers stop over-engineering Resonate workflows by shifting the mindset from distributed-systems patterns to simple, sequential code that leverages Resonate's built-in durability and coordination features.

Core Features & Use Cases

Reduce Complexity: Explains which common infrastructure patterns (status tables, retry wrappers, event buses, distributed locks) are unnecessary when using Resonate.
Resonate Best Practices: Describes relying on yield* checkpoints, built-in retries, crash recovery, and structured concurrency to make workflows durable.
Practical Scenarios: Guides refactoring workflows to generator-style implementations, removing redundant state duplication and simplifying error-handling across order processing, approvals, and external API orchestration.

Quick Start

Use the resonate-philosophy skill to refactor a workflow into simple generator-based steps and remove redundant retry and status-table logic.

Frequently Asked Questions about resonate-philosophy

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I simplify durable workflows and remove redundant retry wrappers?▼

To simplify durable workflows, refactor them into sequential generator functions using Resonate's yield* checkpoints. This leverages built-in retries and persistence, eliminating the need for external retry wrappers and status tables.

What infrastructure patterns are unnecessary when using Resonate for state management?▼

When using Resonate for state management, infrastructure patterns like status tables, retry wrappers, event buses, and distributed locks are unnecessary. Resonate's built-in durability and structured concurrency handle these concerns automatically.

How do I convert event-driven patterns into sequential generator-based workflows?▼

To convert event-driven patterns into sequential generator-based workflows, replace distributed-systems logic with Resonate's yield* checkpoints. Rely on its crash recovery and structured concurrency to manage order processing and external API orchestration.

Do I need a status database for Resonate workflows?▼

You do not need a status database for Resonate workflows. Resonate provides built-in persistence and crash recovery through yield* checkpoints, allowing you to eliminate external state duplication and redundant status tracking.

What is the best way to handle error-handling in durable workflows without over-engineering?▼

The best way to handle error-handling in durable workflows without over-engineering is to rely on Resonate's built-in retries. By using generator functions with yield* checkpoints, you avoid complex distributed locks and manual state duplication.

Why does my Resonate workflow have duplicated state management logic?▼

Your Resonate workflow likely has duplicated state management logic because it still relies on traditional distributed-systems patterns. Shifting to simple, sequential code with yield* checkpoints removes the need for external state duplication.