versa/skills/versatiles-frontend/SKILL.md
VersaTiles Frontend — pre-built TypeScript SPA from versatiles-org/versatiles-frontend GitHub releases. Third static-SPA-via-python-http.server in the versa image (after maputnik + pmtiles-viewer). Served on port 8002 (host-mapped 28002). Also re-exports the versatiles-style layer's bundle at /style/ so the notebook's mo.iframe can reach it via an absolute URL. MUST be invoked before building, deploying, or troubleshooting the versatiles-frontend layer.
npx skillsauth add overthinkos/overthink-plugins versatiles-frontendInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
| Property | Value |
|----------|-------|
| Dependencies | supervisord, versatiles-style (re-exported under /style/) |
| Distros | arch + fedora |
| Build deps | curl, jq |
| Ports | 8002 (host-mapped to 28002) |
| Service | versatiles-frontend (supervisord, restart: always, priority 38) |
| Static dist | /opt/versatiles-frontend/ |
versatiles-org/versatiles-frontend ships pre-built static SPAs on
every release (four variants: frontend, frontend-dev,
frontend-min, frontend-tiny). We pick frontend (full feature
set) since the versa image targets interactive exploration, not
minimal embedding. Build deps (nodejs, npm, vite) are NOT
needed inside the versa image — saves ~250 MB image size.
This contrasts with /charly-versa:maputnik-layer which DOES build
from source (npm ci + npm run build -- --base=/) because
maputnik ships no pre-built tarball.
service:
- name: versatiles-frontend
exec: /usr/bin/python3 -m http.server 8002 --directory /opt/versatiles-frontend
restart: always
working_directory: /opt/versatiles-frontend
priority: 38
enable: true
scope: system
Mirrors maputnik (priority 34) and pmtiles-viewer (priority 35). All three are stdlib python3 http.server processes — no shared infrastructure, easy to debug independently.
After the install task completes, /opt/versatiles-frontend/
contains:
| Path | Source |
|---|---|
| index.html | unpacked from frontend.tar.gz |
| assets/, tile-data/, ... | unpacked from frontend.tar.gz |
| style/versatiles-style.js, style/... | copied from /opt/versatiles-style/ so the notebook's iframe can import the bundle via the same http.server |
The cross-layer dependency on versatiles-style is declared via
require: [supervisord, versatiles-style] — image-build ordering
ensures versatiles-style runs first and populates
/opt/versatiles-style/ before this layer's cp -r copies it
under /opt/versatiles-frontend/style/.
Build-scope:
versatiles-frontend-index-html — /opt/versatiles-frontend/index.html existsversatiles-frontend-style-bundle — find /opt/versatiles-frontend/style -name 'versatiles-style*.js' -size +1c matches (verifies the cross-layer cp ran)Deploy-scope:
versatiles-frontend-running — supervisord service RUNNINGversatiles-frontend-port-reachable — TCP 8002 reachableversatiles-frontend-http-up — GET / returns 200versatiles-frontend-style-fetchable — curl http://localhost:8002/style/ returns success (the directory listing or index file)Operator opens http://127.0.0.1:28002/ in a browser to:
The frontend ALSO serves the versatiles-style bundle at /style/,
which is the load path the notebook's iframe uses. This is a
secondary role of the same http.server — operators don't need to
visit /style/ directly.
/charly-versa:versa — image composing this layer/charly-versa:versatiles — the tile-server backend the frontend
connects to by default/charly-versa:versatiles-style — the bundle re-exported under /style//charly-versa:pmtiles-viewer — sibling static-SPA layer (port 28001)/charly-versa:maputnik-layer — sibling static-SPA layer (port 28000)/charly-versa:notebook-osm — the shortbread MapLibre cell that loads
the re-exported versatiles-style bundle via this layer's http.servertools
Use when authoring or modifying a charly PLUGIN — a candy with a `plugin:` block that contributes Providers (verbs/kinds/deploy-targets/steps/builders/commands), its own CUE schema, builtin (compiled-in) or external (out-of-tree git repo). Covers the unified Provider model, the per-plugin CUE-schema contract (single source → Go params for dev + schema-over-Describe RPC for runtime), the SDK, and the loader.
tools
The CUE data-validation / configuration CLI (cue), pinned to v0.16.1. Use when working with the cue candy, installing the cue binary into a box or onto a target:local dev host, or running the offline schema-vendoring pipeline that feeds charly's egress validation.
tools
CUE EGRESS validation — validating (and, where it adds value, generating) the config files charly WRITES to a system BEFORE the bytes hit disk. MUST be invoked before working on charly/egress.go, the vendored schemas under candy/plugin-egress/egress-schemas/vendor/, the ValidateEgress / registerVendoredEgressKind path, the offline `task cue:vendor` pipeline, or adding an egress schema for any written artifact (cloud-init, k8s manifests, traefik routes, runtime config, install ledger, systemd/quadlet units, ssh_config, libvirt XML).
tools
Kubernetes cluster-probe declarative check verb — the `kube:` check verb (nodes, pods, ingress, storage class, addon health, apply/delete, and arbitrary resource GETs) served out-of-process by the candy/plugin-kube plugin (vendored client-go; no external kubectl required).