Using Ring Developer Specialists

When to use

• Need deep expertise for specific technology (Go, TypeScript)
• Backend local runtime / docker-compose → ring:backend-go or ring:backend-ts
• Frontend with design focus → ring:ui-designer
• Frontend UI development (React/Next.js) → ring:frontend
• Frontend from product-designer specs → ring:ui-engineer
• Helm chart creation/maintenance → ring:helm
• Backend tests / coverage / TDD → ring:backend-go or ring:backend-ts
• Frontend test strategy → ring:qa-frontend
• Backend health/logging/tracing → ring:backend-go or ring:backend-ts
• Agent/prompt quality evaluation → ring:prompt-reviewer
• Migrating deprecated lib-commons observability shims to lib-observability → ring:migrating-to-lib-observability

Skip when

• General code review → use ring:reviewing-code with dev-team reviewer agents
• Debugging → trace from logs / metrics / telemetry

Related

Similar: ring:using-ring

Developer specialist agents. Dispatch via Task tool with subagent_type:.

Runtime Version Resolution

Always resolve lib-commons to latest v5.x at runtime:

gh api repos/LerianStudio/lib-commons/releases/latest --jq '.tag_name'

Do NOT hardcode specific patch versions.

Specialists

Dispatch Template

Task:
  subagent_type: "ring:{agent-name}"
  description: "{Brief task description}"
  prompt: |
    {Your specific request with full context}

Frontend Agent Selection Guide

Parallelization

When tasks are independent, dispatch multiple agents in ONE message:

# All in one Task call block
Task 1: ring:backend-go - implement X with TDD, coverage, and local runtime
Task 2: ring:backend-ts - implement Y with TDD, coverage, and local runtime
Task 3: ring:helm - update Helm chart

Sequential dispatch triples execution time for the same cost.

Example

Task:
  subagent_type: "ring:backend-go"
  description: "Implement multi-tenant repository for accounts"
  prompt: |
    Implement a multi-tenant PostgreSQL repository for the accounts domain.
    
    Standards: Load golang.md and multi-tenant.md via WebFetch.
    Project rules: docs/PROJECT_RULES.md
    
    Requirements:
    - Use tmcore.GetPGContext(ctx) for tenant context resolution
    - Table: accounts, tenant isolation via schema-per-tenant
    - TDD: write failing test first, then implement
    
    Output: files created, test results, acceptance criteria checklist