tzurot-architecture

What problem does it solve?

Designing and maintaining a scalable microservices architecture requires clear boundaries, communication patterns, and a shared understanding of responsibilities. This Skill outlines Tzurot v3's architectural principles, guiding you in making informed design decisions.

Core Features & Use Cases

• Clear Service Boundaries: Define the distinct responsibilities of bot-client (Discord interface), api-gateway (HTTP API + Job Queue), and ai-worker (AI processing + Memory).
• Shared Code Management: Understand what belongs in common-types (types, utilities, shared services) to prevent duplication and ensure consistency across the monorepo.
• Data Flow & Interaction Patterns: Trace the journey of a Discord message through the entire microservices stack to an AI response, clarifying inter-service communication.
• Anti-Patterns from v2: Learn from past mistakes, avoiding over-engineering, excessive abstraction layers, and complex dependency injection containers.

Quick Start

Use the tzurot-architecture skill to determine which microservice should handle a new feature that involves both Discord interactions and AI processing, ensuring clear separation of concerns.