Sponsored by

Find leads on Reddit on auto pilot

Topic: tdd

465 skills in this topic.

ring:dev-validation Development cycle validation gate (Gate 5) - validates all acceptance criteria are met and requires explicit user approval before completion.
LerianStudio/ring 169
ring:systemplane-migration Gate-based systemplane migration orchestrator. Migrates Lerian Go services from .env/YAML-based configuration to the systemplane — a database-backed, hot-reloadable runtime configuration and settings management plane with full audit history, optimistic concurrency, change feeds, component-granular bundle rebuilds, and atomic infrastructure replacement. Requires lib-commons v4.3.0+.
LerianStudio/ring 169
ring:using-dev-team 12 specialist developer agents for backend (Go/TypeScript), DevOps, frontend, design, Helm charts, UI implementation, QA (backend + frontend), SRE, and prompt quality review. Dispatch when you need deep technology expertise.
LerianStudio/ring 169
ring:using-lib-commons Comprehensive reference for lib-commons v4.6.0 — Lerian's shared Go library providing 35+ packages across database connections, messaging, multi-tenancy, runtime configuration, observability, security, resilience, HTTP tooling, and event-driven tenant discovery. Load this skill to discover available APIs, find the right package, and learn correct initialization patterns.
LerianStudio/ring 169
ring:infrastructure-cost-estimation Orchestrates infrastructure cost estimation with tier-based or custom TPS sizing. Offers pre-configured tiers (Starter/Growth/Business/Enterprise) or custom TPS input. Skill discovers components, asks shared/dedicated for EACH, selects environment(s), reads actual Helm chart configs, then dispatches agent for accurate calculations.
LerianStudio/ring 169
ring:regulatory-templates 5-stage regulatory template orchestrator - manages setup, Gate 1 (analysis + auto-save), Gate 2 (validation), Gate 3 (generation), optional Test Gate, optional Contribution Gate. Supports any regulatory template (BACEN, RFB, CVM, SUSEP, COAF, or other).
LerianStudio/ring 169
ring:regulatory-templates-gate1 Gate 1 sub-skill - performs regulatory compliance analysis, field mapping, batch approval by confidence level, and auto-saves dictionary after approval. Supports both pre-defined templates (dictionary exists) and new templates (any spec).
LerianStudio/ring 169
ring:regulatory-templates-gate2 Gate 2 sub-skill - validates uncertain mappings from Gate 1 and confirms all field specifications through testing.
LerianStudio/ring 169
ring:regulatory-templates-gate3 Gate 3 sub-skill - generates complete .tpl template file with all validated mappings from Gates 1-2.
LerianStudio/ring 169
ring:regulatory-templates-setup Initial setup sub-skill - handles template selection and context initialization for the 5-stage regulatory workflow. Supports any regulatory template (pre-defined or new) via official spec intake (URL/XSD/PDF).
LerianStudio/ring 169
ring:using-finops-team 3 FinOps agents: 2 for Brazilian financial regulatory compliance (BACEN, RFB, Open Banking), 1 for infrastructure cost estimation when onboarding customers. Supports any regulatory template via open intake system.
LerianStudio/ring 169
sample-skill
LerianStudio/ring 169
ring:delivery-status-tracking Delivery status tracking and progress reporting. Analyzes repository against delivery roadmap to calculate actual vs planned progress, identify delays, and provide insights on velocity and risk trends.
LerianStudio/ring 169
ring:lerian-map-management Manage the Lerian Map platform — maintain products, features, iterations, and delivery roadmaps via REST API. Enforces Lerian naming/tagging standards, keeps map data in sync with repository activity, and supports TPMs/PMs in keeping the map 100% accurate.
LerianStudio/ring 169
ring:pre-dev-api-design Gate 4: API contracts document - defines component interfaces and data contracts before protocol/technology selection. Large Track only.
LerianStudio/ring 169
ring:pre-dev-data-model Gate 5: Data structures document - defines entities, relationships, and ownership before database technology selection. Large Track only.
LerianStudio/ring 169
ring:pre-dev-delivery-planning Gate 9 (Full Track) / Gate 4 (Small Track): Delivery roadmap and timeline planning. Transforms tasks into realistic delivery schedule with critical path analysis, resource allocation, and delivery breakdown. MANDATORY gate for both workflows.
LerianStudio/ring 169
ring:pre-dev-dependency-map Gate 6: Technology choices document - explicit, versioned, validated technology selections with justifications. Large Track only. HARD BLOCK: Must load Ring Standards and PROJECT_RULES.md before proceeding.
LerianStudio/ring 169
ring:pre-dev-design-validation Gate 1.5/2.5: Design Validation - verifies UX specifications are complete before proceeding to technical architecture. Checklist-based validation that prevents incomplete designs from reaching implementation.
LerianStudio/ring 169
ring:pre-dev-feature Lightweight 5-gate pre-dev workflow for small features (<2 days). Orchestrates topology discovery, research, PRD with UX validation, design validation, TRD, task breakdown, and delivery planning in a sequential gated process with human approval at each gate.
LerianStudio/ring 169
ring:pre-dev-feature-map Gate 2: Feature relationship map - visualizes feature landscape, groupings, and interactions at business level before technical architecture.
LerianStudio/ring 169
ring:pre-dev-full Complete 10-gate pre-dev workflow for large features (>=2 days). Orchestrates topology discovery, research, PRD, feature map, design validation, TRD, API design, data model, dependency map, task breakdown, subtask creation, and delivery planning in a sequential gated process with human approval at each gate.
LerianStudio/ring 169
ring:pre-dev-prd-creation Gate 1: Business requirements document - defines WHAT/WHY before HOW. Creates PRD with problem definition, user stories, success metrics.
LerianStudio/ring 169
ring:pre-dev-research Gate 0 research phase for pre-dev workflow. Dispatches 4 parallel research agents to gather codebase patterns, external best practices, framework documentation, and UX/product research BEFORE creating PRD/TRD. Outputs research.md with file:line references and user research findings.
LerianStudio/ring 169