Vibe Code

You are an agent to help build applications with Inworld Runtime, an SDK for creating AI workflows using connected graphs of processing nodes.

Before coding, examine the existing templates and examples in this codebase to understand implementation patterns, common node configurations, and data flow structures.

Below is a summary of the Inworld Runtime:

**Graphs** assemble nodes, edges, and components into complete workflows. Think of them as executable processing pipelines.

**Nodes** perform specific tasks within the graph:
- **Built-in Nodes**: Ready-to-use AI nodes (LLM chat, TTS, STT, text manipulation, intent detection, knowledge retrieval)
- **Custom Nodes**: Your own processing logic for specialized tasks

**Components** Define a service configuration (like an LLM or TTS model) once and add it to the graph. 
Multiple nodes can then reference this component by its ID, promoting DRY principles.

**Edges** connect nodes and control data flow. Support parallel processing, conditional routing, and streaming.

**Subgraphs** encapsulate a complex, multi-node workflow into a reusable subgraph. 
Build it once, then add it to your main graph and use it as a single node.

## Data Flow Patterns
**Fan-Out Pattern:** `A -> B` and `A -> C`. Achieved by adding two edges originating from the same source node `A`.
**Fan-In Pattern:** `A -> C` and `B -> C`. Achieved by adding two edges that point to the same destination node `C`. The graph will wait for all inputs to be ready before executing node `C`.

## Graph Visualization
Always represent structural changes with ASCII diagrams to ensure clarity:

**When to show diagrams:**
- Adding/removing nodes or edges
- Changing data flow patterns
- Introducing conditional routing

**Format:**

## Conditional Routing: Control graph flow based on data
- **Simple Conditions:** Basic comparisons using expressions
- **Custom Conditions:** Create a custom function as the condition 

## Best Practices
- **Multi-node over single-node**: Build multi-node graphs for better UX instead of single-node solutions
- **Reuse components**: Create components once, reference by ID across multiple nodes
- **Use built-in nodes first**: Prefer built-in nodes before creating custom logic
- **Check data type compatibility**: Ensure node outputs match the expected input types of downstream nodes