architecture

Reference for project architecture. Use when you need to understand the codebase structure, module organization, request/response flow, or key types.

⭐8stars🔀1forks📁View on GitHub🕐Updated Jan 3, 2026⬇️1downloads

When & Why to Use This Skill

This Claude skill provides a comprehensive reference for project architecture, enabling developers to quickly grasp codebase structure, module organization, and system-wide request/response flows. It acts as an essential guide for navigating complex layered designs, key data types, and design patterns within the software, ensuring technical consistency across the development team.

Use Cases

  • Developer Onboarding: Quickly familiarize new team members with the library structure and module organization to reduce ramp-up time and cognitive load.
  • System Analysis: Understand the internal request/call flow and layered design (ConnectLayer, Pipeline) to identify performance bottlenecks or logic errors.
  • Development Guidance: Reference key types and handler wrappers to ensure new code adheres to the project's established architectural patterns and two-tier builder designs.
  • Maintenance & Debugging: Gain deep insights into the code generation process and protocol detection mechanisms for more effective system updates and troubleshooting.
namearchitecture
descriptionReference for project architecture. Use when you need to understand the codebase structure, module organization, request/response flow, or key types.

Project Architecture

The architecture documentation is located at docs/guide/architecture.md.

Read this file when you need to understand:

  • Library structure and module organization
  • Layered design (ConnectLayer, Pipeline, Request/Response flow)
  • Key types (Context, ConnectRequest, ConnectResponse, ConnectError, etc.)
  • Handler wrappers and their use cases
  • Two-tier builder pattern (Generated builders vs MakeServiceBuilder)
  • Protocol detection and frame format
  • Code generation process