do-integrate

Generate API handlers, mappers, routes, and outbox configs for Go backends.

1|Updated Mar 8, 2026
One-click install
npx skills add https://github.com/viqueen/claude-go-playground --skill do-integrate
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: do-integrate
Source: https://github.com/viqueen/claude-go-playground/tree/main/.claude/skills/do-integrate
Command: npx skills add https://github.com/viqueen/claude-go-playground --skill do-integrate

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the complex process of integrating new business logic (domains) into the existing server architecture, ensuring consistency and reducing manual wiring errors.

Core Features & Use Cases

  • Automated Code Generation: Creates API handlers, mappers, and route files for both Connect-RPC and gRPC backends.
  • Outbox Integration: Sets up event mapping for asynchronous processing via River.
  • Configuration Updates: Modifies server setup files to register the new domain and its components.
  • Use Case: After developing the core business logic for a new 'user' domain, use this Skill to automatically generate all the necessary boilerplate code to expose it via the API and handle background tasks.

Quick Start

Use the do-integrate skill to wire the 'content' domain into the 'connect-rpc-backend' project.

Frequently Asked Questions about do-integrate

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

FAQPage Schema
How do I automate domain integration into a Go backend server?

Automate domain integration by generating API handlers, mappers, route files, and outbox event configurations. This process wires new business logic directly into the cmd/server setup files, ensuring architectural consistency across Connect-RPC and gRPC frameworks without manual boilerplate.

What is the best way to generate Connect-RPC and gRPC boilerplate for a new domain?

Generating Connect-RPC and gRPC boilerplate for a new domain involves creating API handlers and route files concurrently. This approach ensures proper wiring within server setup files while adhering to established layer rules and architectural conventions for both frameworks.

How does outbox event configuration work with domain logic integration?

Outbox event configuration sets up event mapping for asynchronous processing via River during domain integration. It automatically generates the necessary outbox configurations alongside API handlers, ensuring background tasks are properly wired into the server architecture.

Can I use this approach to wire domain logic into an existing server setup?

Yes, you can wire domain logic into an existing server setup by modifying server setup files to register the new domain and its components. It automatically updates the cmd/server configuration to integrate new handlers, mappers, and routes seamlessly.

What are the limitations of automating API handler and route generation?

Automating API handler and route generation relies on established architectural conventions and layer rules. It requires the target Go backend to follow specific Connect-RPC or gRPC structural patterns, meaning projects with non-standard architectures may not integrate correctly.