Ring banner
LerianStudio LerianStudio

Ring

AI community

Description

89 skills and 38 specialized agents that enforce proven engineering practices for AI-assisted development. TDD, systematic debugging, parallel code review, and 10-gate development cycles β€” as a Claude Code plugin marketplace.

Installation

This entry records only its repository, not the path inside it, so there is no exact command to give. Open the source below and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

README

Ring by Lerian

πŸ’ The Ring - Skills Library for AI Agents

**Proven engineering practices, enforced through skills.**

Ring is a comprehensive skills library and workflow system for AI agents that transforms how AI assistants approach software development. Currently implemented as a **Claude Code plugin marketplace** with **6 active plugins** and **96 skills** (see `.claude-plugin/marketplace.json` for current versions), the skills themselves are agent-agnostic and can be used with any AI agent system. Ring provides battle-tested patterns, mandatory workflows, and systematic approaches across the entire software delivery value chain.

✨ Why Ring?

Without Ring, AI assistants often:

  • Skip tests and jump straight to implementation
  • Make changes without understanding root causes
  • Claim tasks are complete without verification
  • Forget to check for existing solutions
  • Repeat known mistakes

Ring solves this by:

  • Enforcing proven workflows - Test-driven development, systematic debugging, proper planning
  • Providing 96 specialized skills (24 core + 34 dev-team + 16 product planning + 7 FinOps regulatory + 6 technical writing + 9 PMO)
  • 41 specialized agents - 10 review/planning + 15 developer + 4 product research + 3 FinOps regulatory + 3 technical writing + 6 PMO
  • Automating skill discovery - Skills load automatically at session start
  • Preventing common failures - Built-in anti-patterns and mandatory checklists

🧭 Project Identity

**Ring is Lerian-first, open-source-friendly.** Design decisions prioritize the Lerian engineering team's daily needs while keeping the architecture clean and reusable for external adoption. This means:

  • Lerian-specific skills stay active β€” Brazilian regulatory compliance (finops-team), internal integrations, and domain-specific workflows remain in the marketplace because the team uses them
  • **The architecture is unive