How to correctly implement a Generic Helm Chart pattern in HelmRelease?

[NoSpooksAllowed]

I am using a Generic Helm Chart pattern to manage multiple services. However, I've encountered an issue where each HelmRelease seems to deploy the resources for all services defined in the chart, rather than isolating them.

Currently, I have a HelmRelease configured for each service. Below are the YAML snippets for my setup:
backend

├── charts
├── Chart.yaml
├── templates
│   ├── backend
│   │   ├── deployment.yaml
│   │   ├── job.yaml
│   │   └── service.yaml
│   ├── frontend
│   │   ├── deployment.yaml
│   │   └── service.yaml
│   └── _helpers.tpl
└── values.yaml

And I set HelmRelease for each service. Here are the yaml configs for both of them.
Backend:

apiVersion: helm.toolkit.fluxcd.io/v2
kind: HelmRelease
metadata:
  name: backend
  namespace: realworld-app
spec:
  interval: 10m
  chart:
    spec:
      chart: ./k8s/charts/realworld-app
      sourceRef:
        kind: GitRepository
        name: flux-system
        namespace: flux-system
      interval: 10m
  values:
    global:
      envSecretNames:
        - "backend-secrets"
    replicaCount: 2
    backend:
      image:
        tag: backend-bf4df8927f9a6404227949ab23a1b33c3c0239c9-93 # {"$imagepolicy": "flux-system:backend-policy:tag"}

And frontend:

apiVersion: helm.toolkit.fluxcd.io/v2
kind: HelmRelease
metadata:
  name: frontend
  namespace: realworld-app
spec:
  interval: 10m
  chart:
    spec:
      chart: ./k8s/charts/realworld-app
      sourceRef:
        kind: GitRepository
        name: flux-system
        namespace: flux-system
      interval: 10m
  values:
    replicaCount: 1
    frontend:
      image:
        tag: frontend-bf4df8927f9a6404227949ab23a1b33c3c0239c9-93 # {"$imagepolicy": "flux-system:frontend-policy:tag"}

NAMESPACE       NAME            REVISION        SUSPENDED       READY   MESSAGE                                                                                           
realworld-app   backend         0.1.0           False           True    Helm upgrade succeeded for release realworld-app/backend.v6 with chart [email protected] 
realworld-app   frontend        0.1.0           False           True    Helm upgrade succeeded for release realworld-app/frontend.v5 with chart [email protected]

NAME                            REVISION                SUSPENDED       READY   MESSAGE                                           
gitrepository/flux-system       main@sha1:fb67e31e      False           True    stored artifact for revision 'main@sha1:fb67e31e'

NAME                                    REVISION        SUSPENDED       READY   MESSAGE                                                   
helmchart/realworld-app-backend         0.1.0           False           True    packaged 'realworld-app-chart' chart with version '0.1.0'
helmchart/realworld-app-frontend        0.1.0           False           True    packaged 'realworld-app-chart' chart with version '0.1.0'

NAME                                    LAST SCAN                       SUSPENDED       READY   MESSAGE                                                
imagerepository/realworld-app-images    2025-12-27T22:31:17-03:00       False           True    successful scan: found 143 tags with checksum 10430668

NAME                            IMAGE                                           TAG                                                     READY   MESSAGE                                                                                                                               
imagepolicy/backend-policy      ghcr.io/nospooksallowed/realworld-fullstack-app backend-bf4df8927f9a6404227949ab23a1b33c3c0239c9-93     True    Latest image tag for ghcr.io/nospooksallowed/realworld-fullstack-app resolved to backend-bf4df8927f9a6404227949ab23a1b33c3c0239c9-93 
imagepolicy/frontend-policy     ghcr.io/nospooksallowed/realworld-fullstack-app frontend-bf4df8927f9a6404227949ab23a1b33c3c0239c9-93    True    Latest image tag for ghcr.io/nospooksallowed/realworld-fullstack-app resolved to frontend-bf4df8927f9a6404227949ab23a1b33c3c0239c9-93

NAME                                    LAST RUN                        SUSPENDED       READY   MESSAGE               
imageupdateautomation/flux-system       2025-12-27T22:29:21-03:00       False           True    repository up-to-date

NAME                            REVISION                SUSPENDED       READY   MESSAGE                              
kustomization/apps-common       main@sha1:fb67e31e      False           True    Applied revision: main@sha1:fb67e31e
kustomization/apps-services     main@sha1:fb67e31e      False           True    Applied revision: main@sha1:fb67e31e
kustomization/flux-system       main@sha1:fb67e31e      False           True    Applied revision: main@sha1:fb67e31e
kustomization/platform          main@sha1:fb67e31e      False           True    Applied revision: main@sha1:fb67e31e
kustomization/traefik-bootstrap main@sha1:fb67e31e      False           True    Applied revision: main@sha1:fb67e31e

Instead of deploying only the specific service defined in the values, both HelmRelease objects are applying the entire chart logic twice.

How can I ensure that each HelmRelease only manages its respective service while using a shared generic chart?