From e2ad333908accae637cf03cd1c20669ab41c114f Mon Sep 17 00:00:00 2001 From: Kiran Date: Tue, 28 Apr 2026 11:44:14 +0200 Subject: [PATCH 1/3] Add CLAUDE.md with project context for AI agents --- CLAUDE.md | 44 ++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 44 insertions(+) create mode 100644 CLAUDE.md diff --git a/CLAUDE.md b/CLAUDE.md new file mode 100644 index 0000000..4ee410e --- /dev/null +++ b/CLAUDE.md @@ -0,0 +1,44 @@ +# charts + +Helm charts for deploying GlassFlow components on Kubernetes. + +## Repo layout + +``` +charts/ + glassflow-etl/ # Main GlassFlow ETL chart (operator + pipeline components) + pgbouncer/ # PgBouncer connection pooler chart + postgresql/ # PostgreSQL chart +ct.yaml # Chart testing config +``` + +## Commands + +```bash +make lint # helm lint all charts +helm lint charts/ # Lint a single chart +helm template charts/ # Render templates locally (useful for debugging) +``` + +## Key conventions + +- `Chart.yaml` — chart name, version, appVersion. Both `version` (chart) and `appVersion` (deployed image tag) must be updated on release. +- `values.yaml` — default values; keep all configurable fields here with comments. +- Template files go in `templates/`; helpers in `templates/_helpers.tpl`. +- Don't commit `Chart.lock` or `values.yaml.new` — these are generated artifacts. + +## Boundaries with other repos + +- Packages `clickhouse-etl` pipeline components +- Packages `glassflow-etl-k8s-operator` +- Deployed by `cli/` via embedded Helm operations + +## Release process + +Chart versions are bumped on each release. The `cli` embeds or references chart versions — coordinate chart version bumps with CLI releases. + +## Git & PR conventions + +- Branch naming follows Linear ticket ID: `ETL-XYZ` or `username/ETL-XYZ-description` +- Reviewed by: Petr, Pablo, Kiran +- No `Co-Authored-By: Claude` or AI attribution in commits/PRs From 1647a451ebea4b96cbd43e8774e755e2ed6319cb Mon Sep 17 00:00:00 2001 From: Kiran Date: Tue, 28 Apr 2026 12:23:53 +0200 Subject: [PATCH 2/3] Add domain context pointer to glassflow-agent-context --- CLAUDE.md | 14 ++++++++++++++ 1 file changed, 14 insertions(+) diff --git a/CLAUDE.md b/CLAUDE.md index 4ee410e..38a3670 100644 --- a/CLAUDE.md +++ b/CLAUDE.md @@ -42,3 +42,17 @@ Chart versions are bumped on each release. The `cli` embeds or references chart - Branch naming follows Linear ticket ID: `ETL-XYZ` or `username/ETL-XYZ-description` - Reviewed by: Petr, Pablo, Kiran - No `Co-Authored-By: Claude` or AI attribution in commits/PRs + +## Domain context + +For glossary, architecture diagrams, customer personas, and cross-repo workflows see the shared context repo (sibling directory): + +``` +../glassflow-agent-context/ + domain/glossary.md # Key terms and definitions + domain/deployment-topology.md # How components fit together in prod + workflows/release-process.md # Release and versioning process + workflows/linear-tickets.md # Ticket → branch → PR flow +``` + +Load these on demand when doing design work, writing PR descriptions, or when domain terminology is ambiguous. Don't load them for routine code tasks. From ea083c14d575dcc0d316d90b0f879f563ec9152b Mon Sep 17 00:00:00 2001 From: Kiran Date: Tue, 28 Apr 2026 12:27:22 +0200 Subject: [PATCH 3/3] Update domain context to use active trigger instructions --- CLAUDE.md | 15 ++++++--------- 1 file changed, 6 insertions(+), 9 deletions(-) diff --git a/CLAUDE.md b/CLAUDE.md index 38a3670..296f489 100644 --- a/CLAUDE.md +++ b/CLAUDE.md @@ -45,14 +45,11 @@ Chart versions are bumped on each release. The `cli` embeds or references chart ## Domain context -For glossary, architecture diagrams, customer personas, and cross-repo workflows see the shared context repo (sibling directory): +The shared context repo lives at `../glassflow-agent-context/` (sibling directory). Read files from it when: -``` -../glassflow-agent-context/ - domain/glossary.md # Key terms and definitions - domain/deployment-topology.md # How components fit together in prod - workflows/release-process.md # Release and versioning process - workflows/linear-tickets.md # Ticket → branch → PR flow -``` +- **Implementing a feature or ticket** → read `../glassflow-agent-context/workflows/linear-tickets.md` before branching +- **Writing a PR description** → read `../glassflow-agent-context/prompts/pr-description.md` +- **Bumping chart versions for a release** → read `../glassflow-agent-context/workflows/release-process.md` +- **Domain terminology is ambiguous** → read `../glassflow-agent-context/domain/glossary.md` -Load these on demand when doing design work, writing PR descriptions, or when domain terminology is ambiguous. Don't load them for routine code tasks. +Don't load these for routine bug fixes or code tasks — read the code directly instead.