ring-creating-helm-charts

Creating 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.

Jump to install

Repository: LerianStudio/ring
Last source activity: June 6, 2026 at 22:57
Detected SKILL.md language: English
Stars: 205
Forks: 26

Install options

The review-first prompt is selected by default. You can switch to a direct command or download a local copy.

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

A direct command skips the review prompt. Inspect the source before running it.

npx skills add https://github.com/LerianStudio/ring --skill ring-creating-helm-charts

The command stays on one line. Scroll horizontally to inspect it before copying.

Prefer a local copy? Download the files currently available to SkillsMP.

Review the source files

Read SKILL.md and any companion files shown by SkillsMP before deciding whether to install.

SKILL.md

Source instructions · Read-only preview

Back to search Back to installation

ring-declaring-plugin-permissions

Interactively 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 (WireFromEnv) instead of the access-manager seed owning them, or when writing/fixing a permissions.yaml. It also bumps the repo's github-actions-shared-workflows CI pin to the release carrying the permission-manifest nudge. Skip when the plugin has no auth guards, or you only need the wiring (see WireFromEnv) and the manifest already exists.

2026-08-11

ring-writing-plans

Writing a rolling-wave phased implementation plan from a spec before coding: a phase-epic-task hierarchy where Phase 1 is detailed into dispatch-ready tasks and later phases stay epic-level for elaboration during execution. Use when a multi-file feature needs decomposition; runs after ring:exploring-codebases or pre-dev gates, hands off to ring:executing-plans or ring:running-dev-cycle. Skip for single-file changes or spikes.

2026-07-02

ring-applying-licenses

Applying 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.

2026-07-02

View all from this repository

name

ring:creating-helm-charts

description

Helm Chart Creation & Maintenance

When to use

Creating a new Helm chart for any Lerian service
Modifying an existing Helm chart (adding components, dependencies, templates)
Reviewing a Helm chart PR for convention compliance
Migrating a docker-compose setup to Helm

Skip when

Modifying only application code (no chart changes)
Working on non-Helm deployment (docker-compose only) → use backend engineer via ring:implementing-tasks

Sequence

Standalone/on-demand. Not part of the lean backend dev-cycle.

Complementary: ring:implementing-tasks

Standards reference: dev-team/docs/standards/helm/ Executor agent: ring:helm

You orchestrate. ring:helm creates chart files.

Step 1: Validate Input

Required: service_name, chart_type (single|multi-component|umbrella), components (non-empty). Optional: dependencies (postgresql, mongodb, rabbitmq, valkey, keda), has_worker, namespace.

Step 2: Naming Convention

Default: {service_name}-helm  (e.g., reporter-helm, tracer-helm)
Exceptions (no -helm suffix):
  - plugin-access-manager
  - otel-collector-lerian

Task: subagent_type: "ring:helm" description: "Create Helm chart for {service_name}" prompt: | ## Helm Chart Creation service_name: {service_name} components: {components} dependencies: {dependencies} chart_type: {chart_type} namespace: {namespace} Standards: Load dev-team/docs/standards/helm/ files. ## Required Steps 1. Read application .env.example and bootstrap/config.go — extract ALL env vars (missing vars = CrashLoopBackOff) 2. Verify health check endpoint in application source 3. Create chart structure: charts/{service_name}-helm/ ├── Chart.yaml ├── values.yaml ├── templates/ │ ├── _helpers.tpl │ ├── deployment.yaml │ ├── service.yaml │ ├── configmap.yaml │ ├── secret.yaml (if secrets exist) │ ├── hpa.yaml (optional) │ └── serviceaccount.yaml └── charts/ (dependencies) 4. Chart.yaml: name, version, appVersion, description, type: application 5. _helpers.tpl: name, fullname, chart, labels, selectorLabels, versionLabelValue 6. values.yaml structure: - global: replicaCount, image.repository/tag/pullPolicy - Per-component config sections - configmap: all non-secret env vars - secrets: all sensitive env vars (no real values) - service: type: ClusterIP, port, targetPort - resources: requests/limits - probes: livenessProbe, readinessProbe (match /health and /readyz) - dependencies config sections 7. Security defaults: - securityContext: runAsNonRoot: true, runAsUser: 1000 - readOnlyRootFilesystem: true - allowPrivilegeEscalation: false 8. Service type: ALWAYS ClusterIP (never NodePort or LoadBalancer) ## Required Output - Env Var Coverage table (100% of .env.example covered) - helm lint result: MUST PASS - helm template render: MUST produce valid YAML - Files created list

ring-creating-helm-charts

Install options

Review the source files

Helm Chart Creation & Maintenance

When to use

Skip when

Sequence

Related

Step 1: Validate Input

Step 2: Naming Convention

Helm Chart Creation & Maintenance

When to use

Skip when

Sequence

Related

Step 1: Validate Input

Step 2: Naming Convention

Step 3: Dispatch Agent

Step 4: Validate Output

Worker Chart (if has_worker = true)

Validation Checklist

ring-creating-helm-charts

Source facts

Install options

Review the source files

More from this repository

Helm Chart Creation & Maintenance

When to use

Skip when

Sequence

Related

Step 1: Validate Input

Step 2: Naming Convention

Helm Chart Creation & Maintenance

When to use

Skip when

Sequence

Related

Step 1: Validate Input

Step 2: Naming Convention

Step 3: Dispatch Agent

Step 4: Validate Output

Worker Chart (if has_worker = true)

Validation Checklist

More from this repository