Agent skill
architecture
jhelm project architecture and module structure for a Java Helm implementation
Install this agent skill to your Project
npx add-skill https://github.com/majiayu000/claude-skill-registry/tree/main/skills/other/other/architecture-alexmond-jhelm
SKILL.md
jhelm Architecture
Java 21 | Spring Boot 4.0.2 | Kubernetes Client 25.0.0 | Picocli 4.7.6
Module Dependency Graph
jhelm (parent)
├── jhelm-gotemplate — Go template engine (standalone, no Spring)
├── jhelm-core — Helm logic, charts, actions (depends on: gotemplate)
├── jhelm-kube — Kubernetes client integration (depends on: core)
└── jhelm-app — CLI, Spring Boot + Picocli (depends on: core, kube)
Template Engine (jhelm-gotemplate)
- Pipeline: Lexer → Parser → AST → Executor
- Key classes:
GoTemplate,GoTemplateFactory,Functions - Functions by category: Sprig (strings, collections, logic, math, encoding, crypto, date, reflection, network, semver) and Helm (conversion, template, kubernetes, chart)
- No Spring dependency — pure Java library
Core Engine (jhelm-core)
Engine.java— Orchestrates template processingChart.java— Represents Helm charts with metadata and templatesRepoManager.java— Manages chart repositories- Creates new
GoTemplateFactoryper render to avoid template accumulation - Stack depth tracking prevents infinite template recursion
Kubernetes Integration (jhelm-kube)
HelmKubeService— Kubernetes resource deployment- Uses official Kubernetes Java Client 25.0.0
CLI Application (jhelm-app)
- Spring Boot 4.0.2 application
- Picocli-based command structure
- Entry point for user-facing commands
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
Didn't find tool you were looking for?