LerianStudio/ring

9 specialist developer agents for backend (Go/TypeScript), DevOps, frontend, design, UI implementation, QA (backend + frontend), and SRE. Dispatch when you need deep technology expertise.

Analyzes frontend codebase against Ring standards and generates refactoring tasks for ring:dev-cycle-frontend. Dispatches frontend-specific agents in ANALYSIS mode.

Multi-tenant development cycle orchestrator following Ring Standards. Auto-detects the service stack (PostgreSQL, MongoDB, Redis, RabbitMQ, S3) and service type (plugin vs product), then executes a gate-based implementation using tenantId from JWT for database-per-tenant isolation via lib-commons v3 tenant-manager sub-packages (postgres.Manager, mongo.Manager). For plugins: includes mandatory M2M credential retrieval from AWS Secrets Manager via lib-commons v3 secretsmanager package (per-tenant authentication with product APIs). MUST update lib-commons v3 first; lib-auth v2 depends on it. Both are required dependencies. Each gate dispatches ring:backend-engineer-golang with context and section references. The agent loads multi-tenant.md via WebFetch and has all code examples.

Frontend development cycle orchestrator with 9 gates. Loads tasks from PM team output or backend handoff and executes through implementation → devops → accessibility → unit testing → visual testing → E2E testing → performance testing → review → validation.

Delivery Verification Gate — verifies that what was requested is actually delivered as reachable, integrated code. Not quality review (Gate 8), not test verification (Gate 9) — this gate answers: "Is every requirement from the original task actually functioning in the running application?" Applies to ANY task type: features, refactors, fixes, infrastructure, API endpoints, middleware, business logic, integrations.

Generate beautiful, self-contained HTML pages that visually explain systems, code changes, plans, and data. Use when the user asks for a diagram, architecture overview, diff review, plan review, project recap, comparison table, or any visual explanation of technical concepts. Also use proactively when you are about to render a complex ASCII table (4+ rows or 3+ columns) — present it as a styled HTML page instead.

Structured workflow for disaster recovery planning, implementation, and testing including RTO/RPO definition, DR strategy selection, and failover procedures.

3-gate regulatory template orchestrator - manages setup, Gate 1 (analysis), Gate 2 (validation), Gate 3 (generation) for BACEN/RFB compliance.

Autonomous two-phase codebase exploration - first discovers natural perspectives (layers, components, boundaries), then dispatches adaptive deep-dive explorers based on what was discovered. Synthesizes findings into actionable insights.

Mandatory orchestrator protocol - establishes ORCHESTRATOR principle (dispatch agents, don't operate directly) and skill discovery workflow for every conversation.

Gate 3 of development cycle - ensures unit test coverage meets threshold (85%+) for all acceptance criteria using TDD methodology.

Comprehensive 23-dimension production readiness audit. Runs in batches of 3 explorers, appending incrementally to a single report file. Categories - Structure (pagination, errors, routes, bootstrap, runtime), Security (auth, IDOR, SQL, validation, rate limiting), Operations (telemetry, health, config, connections, logging), Quality (idempotency, docs, debt, testing, dependencies, performance, concurrency, migrations). Produces scored report (0-230) with severity ratings.

Gate 1 of the development cycle. Creates/updates Docker configuration, docker-compose setup, and environment variables for local development and deployment readiness.

Gate 4 of development cycle - dispatches 5 specialized reviewers (code, business-logic, security, test, nil-safety) in parallel for comprehensive code review feedback.

Gate 3: Technical architecture document - defines HOW/WHERE with technology-agnostic patterns before concrete implementation choices.

Development cycle validation gate (Gate 5) - validates all acceptance criteria are met and requires explicit user approval before completion.