All authors
Claude Skills by LerianStudio
github.com/LerianStudio77 skills0 installs57 views
- Test Driven DevelopmentRED-GREEN-REFACTOR implementation methodology - write failing test first, minimal implementation to pass, then refactor. Ensures tests verify behavior.Votes: 0GitHub stars: 215
- Testing Skills With SubagentsSkill testing methodology - run scenarios without skill (RED), observe failures, write skill (GREEN), close loopholes (REFACTOR).Votes: 0GitHub stars: 215
- Using RingMandatory orchestrator protocol - establishes ORCHESTRATOR principle (dispatch agents, don't operate directly) and skill discovery workflow for every conversation.Votes: 0GitHub stars: 215
- Writing SkillsTDD for process documentation - write test cases (pressure scenarios), watch baseline fail, write skill, iterate until bulletproof against rationalization.Votes: 0GitHub stars: 215
- Using AssertDual-mode skill for lib-observability/assert — Lerian's production-grade runtime assertion package. Sweep Mode dispatches 6 parallel explorers to find DIY invariant checks, zero-panic violations, hand-rolled domain predicates, and missing metric initialization. Reference Mode catalogs the full API (asserter lifecycle, domain predicates, observability trident, AssertionError unwrapping) and the panic-vs-assert-vs-error decision tree. Skip for non-Go or frontend code.Votes: 0GitHub stars: 215
- Using Dev TeamSpecialist developer agents for backend (Go/TypeScript), frontend, design, Helm charts, UI implementation, frontend QA, and prompt quality review. Dispatch when you need deep technology expertise.Votes: 0GitHub stars: 215
- Using Lib CommonsDual-mode skill for github.com/LerianStudio/lib-commons v5, Lerian's shared Go library — the non-observability surface. Sweep Mode dispatches parallel explorers to detect DIY implementations that should use lib-commons, with file:line replacement precision. Reference Mode catalogs lib-commons packages for lifecycle (Launcher), outbox repository, circuit breakers, tenant management, idempotency, security/TLS, database, messaging, HTTP toolkit. Observability (log, metrics, tracing, assertions, ...Votes: 0GitHub stars: 215
- Using Lib ObservabilityDual-mode skill for github.com/LerianStudio/lib-observability v1.0.0, Lerian's OpenTelemetry foundation. Sweep Mode dispatches 5 parallel explorers to detect DIY logging/metrics/redaction/OTel-attribute usage that should route through lib-observability. Reference Mode catalogs the log, metrics, zap, redaction, and constants packages with verified API signatures. This library is the foundation: lib-commons v5, lib-systemplane, and lib-streaming all depend on it. Skip for non-Go services, front...Votes: 0GitHub stars: 215
- Using Lib StreamingDual-mode skill for github.com/LerianStudio/lib-streaming, Lerian's producer-only event publication library (Kafka, SQS, RabbitMQ, EventBridge). Sweep Mode dispatches parallel explorers to find DIY publishers (franz-go, sarama, amqp091-go, watermill, raw AWS SDK calls) and re-implemented manifests / circuit breakers that should be replaced with lib-streaming. Reference Mode catalogs the public facade — Config, Catalog, Builder, Emitter, NoopEmitter, manifest, CloudEvents codec, errors, stream...Votes: 0GitHub stars: 215
- Using Lib SystemplaneDual-mode skill for github.com/LerianStudio/lib-systemplane, Lerian's dual-backend (Postgres LISTEN/NOTIFY or MongoDB change streams) hot-reload runtime configuration plane. Sweep Mode dispatches 7 parallel explorers to detect DIY runtime-config wiring (env reload via SIGHUP, fsnotify/viper.WatchConfig, raw pgx LISTEN, hand-rolled change-stream watchers, manual tenant-scoping, hand-built admin CRUD UIs, v4 systemplane residue). Reference Mode catalogs the API by lifecycle (construct → registe...Votes: 0GitHub stars: 215
- Using OutboxDual-mode skill for the transactional outbox pattern across lib-streaming (writer side) and lib-commons/v5/commons/outbox (repository + relay side). Sweep Mode dispatches 6 parallel explorers to find DIY outbox tables, hand-rolled relay loops, send-and-pray emits, missing WithOutboxTx wrapping, synchronous broker calls inside DB transactions, and hand-rolled idempotency keys. Reference Mode catalogs OutboxWriter / TransactionalOutboxWriter / WithOutboxTx / OutboxRepository / OutboxEnvelope pl...Votes: 0GitHub stars: 215
- Using RuntimeDual-mode skill for lib-observability/runtime — the panic observability trident that turns silent goroutine deaths into production signal. Sweep Mode dispatches 6 parallel explorers to find naked goroutines, unobservable defer recover(), and missing panic-metric init. Reference Mode catalogs the API (SafeGo, RecoverWithPolicy, InitPanicMetrics) and framework integrations (Fiber, gRPC, RabbitMQ). Skip for non-Go or frontend code.Votes: 0GitHub stars: 215
- Using TracingDual-mode skill for github.com/LerianStudio/lib-observability/tracing — OpenTelemetry SDK lifecycle, trace context propagation across HTTP/gRPC/queues, span error and event recording, and struct-to-attribute conversion with PII redaction. Sweep Mode dispatches parallel explorers to find raw OTEL setup, hand-rolled header propagation, manual span attribute assembly, DIY redaction, and untraced boundaries. Reference Mode catalogs the API (Telemetry, TelemetryConfig, Redactor, propagation helper...Votes: 0GitHub stars: 215
- Creating Grafana DashboardsAuthor Grafana dashboards for Lerian Go services rooted in real lib-observability telemetry (tracing, metrics, log, constants). Three phases — Sweep (telemetry inventory), Iterate (PM deliberation on SLIs/SLOs and alerts), Author (Grafonnet libsonnet → JSON in CI) — and installs a blocking CI drift gate. Use when scaffolding dashboards, building a telemetry dictionary, or auditing observability. Skip if service is non-Go, emits no telemetry, or task is just folder organization.Votes: 0GitHub stars: 215
- Using Pm Team12 pre-dev workflow skills + 2 standalone discovery skills + 1 standalone dashboard skill + 4 research agents organized into Small Track (5 gates, <2 days) and Large Track (10 gates, 2+ days) for systematic feature planning with research-first approach.Votes: 0GitHub stars: 215
- Using Tw TeamTechnical writing specialists for functional and API documentation. Dispatch when you need to create guides, conceptual docs, or API references following established documentation standards.Votes: 0GitHub stars: 215
- Executing PlansInline execution of an implementation plan task-by-task with review checkpoints. Loads a written plan, reviews it critically, executes tasks in order with verification, and hands off to finishing skills when done.Votes: 0GitHub stars: 215
- Writing PlansAuthoring comprehensive implementation plans from a spec or requirements before touching code. Produces bite-sized, TDD-shaped tasks with exact file paths, complete code, and verifiable commands — executable by an engineer with zero context for the codebase.Votes: 0GitHub stars: 215
- Analyzing OptionsAnalyzing different approaches for a task or problem with structured comparisons, effort estimates, and recommendations. Use when facing strategic decisions, architecture choices, or multiple viable approaches. Skip when there's an obvious single approach or the decision is already made.Votes: 0GitHub stars: 215
- Auditing Production ReadinessAuditing a service's production readiness against Ring engineering standards across base dimensions plus a conditional multi-tenant dimension, then emitting a scored report and an HTML dashboard. Use before production deploy, periodic review, onboarding, or a major release. Skip for prototypes, libraries, or single-dimension checks.Votes: 0GitHub stars: 215
- Cleaning CommentsCleaning redundant and obvious comments following clean code principles while preserving meaningful documentation. Supports git scope filtering (staged, unstaged, branch, commit-range). Use when code has excessive comments, during code review, or post-refactor cleanup. Skip when reviewing documentation files or comments are already minimal.Votes: 0GitHub stars: 215
- Committing ChangesCommit changes with scope allowlist enforcement, atomic grouping, GPG-signed conventional commits, and trailer management. Detects the repo's PR-validation scope policy before proposing any message. Use when the user asks to commit or has changes ready to record. Skip when the working tree is clean or the user wants raw git commands without grouping.Votes: 0GitHub stars: 215
- Creating HandoffsCreating a handoff document that captures session state (completed work, decisions, open items, next steps) and delivering it via Plan Mode so the user gets the native 'clear context and continue implementing' resume option. Use when ending a session, when context grows large, or the user says 'handoff', 'save session', or 'context transfer'. Skip when context is minimal or work is fully complete with no resume planned.Votes: 0GitHub stars: 215
- Creating WorktreesCreating an isolated git worktree for parallel branch work: selects the directory by priority order, verifies/adds .gitignore safety, auto-installs the detected toolchain's dependencies, runs a baseline test, and reports readiness. Use before a feature that needs isolation from the main workspace or before executing an implementation plan. Skip for a quick fix on the current branch or when already in the feature's worktree.Votes: 0GitHub stars: 215
- Dispatching WorkflowsExecuting a phased plan in rolling waves where each phase runs as one multi-agent workflow harness: the supervisor elaborates the phase into tasks against the real landed code, launches a workflow that implements with TDD and runs mandatory in-harness review plus an adversarial contrarian pass (and researchers when the phase hits an unknown) before returning verified work, then reviews it, checkpoints with the user, and rolls to the next phase. Use when each wave should be a reviewed multi-ag...Votes: 0GitHub stars: 215
- Engineering PromptsExpert prompt engineering and optimization for LLMs and AI systems. Covers core patterns (zero-shot, few-shot, CoT, role-playing, constitutional, tree-of-thoughts), common use cases, and a three-phase process. Use when crafting or optimizing prompts for AI systems. Skip when the prompt is trivial or already performing well.Votes: 0GitHub stars: 215
- Exploring CodebasesExploring a codebase across phases: scopes the target, detects architecture, components, and layers, deep-dives each discovered perspective, then synthesizes findings into actionable guidance with file:line evidence. Use to understand how a feature or system works before planning changes, or to orient on an unfamiliar codebase. Skip for a single signature lookup, a file-exists check, or reading an error from a known file.Votes: 0GitHub stars: 215
- Fixing LintFixing lint to a clean state: runs the linter, groups reported issues into independent streams, and dispatches one parallel fixer agent per stream (ring:backend-go for Go, ring:general-purpose otherwise), iterating until clean. Use when a codebase has lint errors across multiple files. Skip for a single error (fix directly), already-passing lint, or view-only requests; security lints are reported, not auto-fixed.Votes: 0GitHub stars: 215
- Generating Pr DescriptionsGenerating pull request descriptions from git branch changes with automatic title generation, change-type detection, and smart analysis. Uses branch-only scope to avoid full history analysis. Use when preparing a PR for review. Skip when the PR is a single trivial commit or description already exists.Votes: 0GitHub stars: 215
- Generating Release GuidesGenerating an internal Operations-facing update/migration guide from the git diff between two refs, documenting per-change client impact, deploy ordering, monitoring, and rollback notes in English, pt-br, or both. Use when preparing a version release or recording what changed for the Ops team. Runs read-only by default and previews before writing. Skip with no git repo or a trivial single-file change.Votes: 0GitHub stars: 215
- Opening Pull RequestsOpen a GitHub Pull Request with automatic base branch detection, scope allowlist enforcement, PR template filling, and post-create base verification. Replaces ring:generating-pr-descriptions. Use after pushing a branch when ready to open a PR. Skip if the branch is not yet pushed or there are uncommitted changes — commit first with ring:committing-changes.Votes: 0GitHub stars: 215
- Reviewing CodeReviewing code by dispatching the default reviewer subagents in parallel (plus conditional specialists for lib-observability, lib-systemplane, or lib-streaming when the diff triggers them), then aggregating findings by severity into a report. Use as Gate 8 of ring:running-dev-cycle at epic cadence over the cumulative diff, or before merging. Report-only. Skip for a single-command Go pre-merge verdict (use ring:verifying-code).Votes: 0GitHub stars: 215
- Searching CodeForensic code search and analysis with optional Chain of Draft (CoD) ultra-concise mode. Five-phase methodology (clarification, planning, execution, analysis, synthesis) with severity assessment. Use for targeted investigation of specific patterns, bugs, or vulnerabilities. Skip for broad architecture mapping (use ring:exploring-codebases instead).Votes: 0GitHub stars: 215
- Shipping ChangesEnd-to-end git orchestrator: branch → commit → push → PR, with a full plan presented before any execution. Detects base branch and scope allowlist once and propagates to all phases. Use when ready to ship a complete unit of work. Skip if only one phase is needed: commit-only → ring:committing-changes, PR-only → ring:opening-pull-requests.Votes: 0GitHub stars: 215
- VisualizingGenerating self-contained, Lerian-branded HTML artifacts — D2 diagrams, comparison tables/matrices, code diffs, dashboards, slide decks, and plan/diff/recap reviews — from mandatory templates, then opening them in the browser. Use for architecture overviews, any table with 4+ rows or 3+ columns, slide presentations, or visual diff/plan/review output. Skip for simple tables that fit the terminal or text-only answers.Votes: 0GitHub stars: 215
- Adding Multi TenancyAdding database-per-tenant isolation into a Go service end-to-end via an 11-gate cycle: detects the stack, audits compliance, then dispatches backend agents to implement tenantId-from-JWT routing through the lib-commons v5 dispatch layer (config, middleware, repositories, metrics, tests) and runs reviewers. Use when adding tenant isolation to a Go service. Skip for non-Go services or organization_id-style soft tenancy.Votes: 0GitHub stars: 215
- Adopting Lib Commons Huma WrapperAdopting the lib-commons/v5 shared Huma (OAS 3.1) OpenAPI wrapper + RFC 9457 problem model (commons/net/http/{openapi,problem}) in a Lerian Go service: wire openapi.New/ServeSpec + problem.Install (central >=500 scrub) on BOTH runtime and spec-gen paths, the per-rail problem.MapError flex seam, and rename-only spec regen. Orchestrates a gated cycle dispatching ring:backend-go. Use for greenfield Huma or migrating a service off a local openapi/humaerr wrapper. Skip for non-Go or non-HTTP work.Votes: 0GitHub stars: 215
- Applying Composition PatternsReact composition patterns that scale. Avoid boolean prop proliferation by using compound components, lifting state, and composing internals. Use when refactoring components with boolean prop proliferation, building flexible component libraries, or during architecture review. Skip for simple components with 1-2 props or non-React code.Votes: 0GitHub stars: 215
- Applying LicensesApplying or switching a repository's license (Apache 2.0, Elastic License v2, or Proprietary): rewrites the LICENSE file, updates Go/TS source headers, sets SPDX identifiers, and validates consistency after user confirmation. Use when asked to set, apply, or switch a license, or when scaffolding a service with no LICENSE. Skip when license, headers, and SPDX already match, or for non-code repos.Votes: 0GitHub stars: 215
- Auditing Dependency SecurityAuditing a dependency for supply-chain risk before install (pip/npm/go/cargo): checks typosquatting, maintainer/age risk, vulnerability DBs (OSV, GHSA, Socket), and lockfile hash pinning, then emits a risk score and approve/conditional/escalate/block decision. Use when adding or updating a dependency, reviewing a dependency PR, or investigating a compromise. Skip when no new dependency is involved or it is already vetted.Votes: 0GitHub stars: 215
- Checking Frontend QualityChecking frontend quality against changed UI via ring:qa-frontend in accessibility, visual, e2e, or performance mode and aggregating pass/fail verdicts. Use when a frontend change needs standalone a11y, visual-snapshot, Playwright e2e, or Lighthouse/Core-Web-Vitals validation outside the dev cycle. Skip for backend-only or non-UI work, or inside ring:running-dev-cycle-frontend, which already runs these in Gate 0.Votes: 0GitHub stars: 215
- Creating Helm ChartsCreating Helm charts to Lerian conventions via ring:helm: standardized chart structure, full env-var coverage from .env.example, security defaults (runAsNonRoot, readOnlyRootFilesystem), ClusterIP-only services, and health probes; validates helm lint and template render. Use when creating, modifying, or reviewing a chart, or migrating docker-compose to Helm. Skip for app-code-only changes or docker-compose-only deployments.Votes: 0GitHub stars: 215
- Declaring Plugin PermissionsInteractively authoring an access-manager permission-declaration manifest (permissions.yaml) for the access-manager "inversão de responsabilidade": drives a plugin team through discovering its real Authorize() surface, normalizing every action to the SEMANTIC standard (never HTTP verbs), declaring roles/group grants and the M2M contract, then emits and validates a manifest that matches the lib-auth/v3 auth/declaration schema. Use when a plugin must publish its own permissions at boot (WireFro...Votes: 0GitHub stars: 215
- Detecting Goroutine LeaksDetecting goroutine leaks in Go: greps for goroutine patterns, audits goleak coverage (VerifyTestMain/VerifyNone), runs goleak, and dispatches ring:backend-go to fix leaks and add regression tests. Use after implementation or during review when code spawns goroutines or a leak is suspected. Runs before ring:reviewing-code. Skip for non-Go or code with no goroutines. Skip for panic/silent-death observability (use ring:using-runtime).Votes: 0GitHub stars: 215
- Generating Llms TxtGenerating or auditing a repository's llms.txt per the llmstxt.org spec, and creating CLAUDE.md / AGENTS.md when missing, by analyzing README, build files, docs, and API surface. Use when creating an llms.txt, auditing an existing one for spec compliance and live links, or improving a repo's AI readability. Skip when the llms.txt is current, the task is code-only with no doc scope, or the repo needs no LLM discoverability.Votes: 0GitHub stars: 215
- Hardening DockerfilesHardening Dockerfiles to reach Docker Hub Health Score grade A: enforcing a non-root USER, minimal/distroless multi-stage base images, no fixable critical/high CVEs, no AGPL-3.0 deps, and SBOM+provenance attestations. Use when creating a new Dockerfile, auditing one for security, or preparing images for Docker Hub publication. Skip when the project has no Dockerfile, changes are app-code-only, or you consume pre-built images.Votes: 0GitHub stars: 215
- Implementing ReadyzImplementing the canonical /readyz readiness-probe contract across Go, TypeScript, and Next.js via a 12-gate cycle: detects stack, audits compliance, then dispatches agents to build the dependency probe, url.Parse TLS detection, ValidateSaaSTLS enforcement, metrics, startup self-probe, and graceful drain, then runs reviewers. Use when a service lacks or has incomplete /readyz. Skip for libraries, CLI tools, or batch jobs.Votes: 0GitHub stars: 215
- Implementing TasksImplementing a single planned task (Task N.M.T) end-to-end: selects the right backend agent by language and service type, drives one TDD RED->GREEN turn, then verifies coverage, lint, license headers, runtime, and delivery before handoff. Runs as Gate 0 before ring:reviewing-code. Use to drive ONE task inside an already-running cycle. Skip when asked to implement a whole plan.md or multiple tasks (use ring:running-dev-cycle).Votes: 0GitHub stars: 215
- Instrumenting Streaming EventsInstrumenting streaming events: wires lib-streaming event emission end-to-end into a Lerian Go service via a 13-gate cycle (catalog, Builder bootstrap, Emit sites, outbox, HTTP manifest, NoopEmitter fallback, integration and chaos tests), dispatching ring:backend-go under TDD. Consumes the validated instrumentation-map.json from ring:mapping-streaming-events. Use after that map exists. Skip for non-Go or when no map is present.Votes: 0GitHub stars: 215
- Managing Dev CycleManaging an in-progress development cycle without driving it: status reports phase, epic/gate progress, assertiveness, and elapsed time from current-cycle.json; cancel confirms, marks the cycle cancelled, and writes a partial feedback report. Use when checking the status of, or cancelling, a running dev cycle. Skip when no cycle is active or the question is general project status, not cycle-specific.Votes: 0GitHub stars: 215