Ring:Using Dev Team logo

Ring:Using Dev Team

Organization
LerianStudio
ring:using-dev-team

Selecting and dispatching the right Ring developer specialist agent (backend Go/TS, frontend, UI designer/engineer, Helm, frontend QA, prompt reviewer) for a technology task. Use when you need deep stack expertise and must decide which agent to invoke via the Task tool, including parallel dispatch of independent work. Skip for general code review (use ring:reviewing-code).

Overview

PublisherLerianStudio
Repositoryring
Skill namering:using-dev-team
Stars
215
Forks
28
Bundled files
Instructions only
LicenseApache-2.0
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • Self-contained

    Everything the model needs lives in the instructions — no extra files to sync.

  • Open source

    Published by LerianStudio on GitHub. Read the source before you install it.

Installation

Install the Ring:Using Dev Team AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/LerianStudio/ring.git /tmp/ring
mkdir -p .claude/skills
cp -r /tmp/ring/dev-team/skills/using-dev-team .claude/skills/lerianstudio-ring-using-dev-team
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Ring:Using Dev Team in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Ring:Using Dev Team on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Ring:Using Dev Team is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

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:

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

Do NOT hardcode specific patch versions.

Specialists

AgentSpecializationsUse When
ring:backend-goGo microservices, PostgreSQL/MongoDB, RabbitMQ, OAuth2/JWT, gRPC, concurrencyGo services, DB optimization, auth/authz, concurrency
ring:backend-tsTypeScript/Node.js, Express/Fastify/NestJS, Prisma/TypeORM, Jest/VitestTS backends, NestJS design, JS→TS migration
ring:bff-tsNext.js BFF, Clean/Hexagonal Architecture, DDD patterns, Inversify DIBFF layer, Clean Architecture, DDD domains, API orchestration
ring:ui-designerBold typography, color systems, animations, unexpected layoutsLanding pages, portfolios, design systems
ring:frontendReact/Next.js, App Router, Server Components, accessibility, performanceFinancial dashboards, enterprise apps, modern React
ring:helmHelm charts, Lerian conventions, chart structure, security, operational patternsCreating/maintaining Helm charts, platform deployments
ring:ui-engineerWireframe-to-code, Design System compliance, UI states implementationImplementing from product-designer specs
ring:prompt-reviewerAgent quality analysis, prompt deficiency detection, quality scoringEvaluating agent executions, identifying prompt gaps
ring:qa-frontendVitest, Testing Library, axe-core, Playwright, Lighthouse, snapshot testingFrontend test planning, accessibility, E2E, performance

Dispatch Template

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

Frontend Agent Selection Guide

NeedAgent
Visual aesthetics, design specs (no code)ring:ui-designer
React/Next.js UI developmentring:frontend
Business logic, BFF, Clean Architecturering:bff-ts
Implementing from wireframes/ux-criteriaring:ui-engineer

Parallelization

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

yaml
# 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

yaml
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

Frequently asked questions

What does the Ring:Using Dev Team AI skill do?

Selecting and dispatching the right Ring developer specialist agent (backend Go/TS, frontend, UI designer/engineer, Helm, frontend QA, prompt reviewer) for a technology task. Use when you need deep stack expertise and must decide which agent to invoke via the Task tool, including parallel dispatch of independent work. Skip for general code review (use ring:reviewing-code).

Why use Ring:Using Dev Team on TypingMind?

Because you install it once and use it with any model. Ring:Using Dev Team is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Ring:Using Dev Team in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/LerianStudio/ring/tree/main/dev-team/skills/using-dev-team. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Ring:Using Dev Team?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Ring:Using Dev Team?

As many as you like. As long as a model supports skills, you can use Ring:Using Dev Team with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Ring:Using Dev Team AI skill free?

Yes. It is published on GitHub by LerianStudio under the Apache-2.0 license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇