add-servicelisted

# Add a service (or topic) to the Cosmos Use this skill when the user says "add X to the cosmos", "wire service X into the map", or "add a topic node for Y". This covers adding a standalone capsule — it does **not** add scenario steps (use the `add-scenario` skill for that). --- ## What you'll touch | File | Why | |---|---| | `src/scenarios/services.ts` | Add entries to `SERVICES` | | `src/scenarios/topics.ts` | Add entries to `TOPICS` (only for topics used in scenario steps) | | `src/scenarios/owners.ts` | Team ownership mapping | | `src/scenarios/types.ts` | Only if you need a new `Tech` variant | | `src/components/TechIcon.tsx` | Only if you added a new `Tech` variant | | `src/styles/tokens.css` | Only if you need a new `--svc-*` color hue | | `src/map/UICluster.tsx` | Only if the new service is a browser-facing UI surface | --- ## Step 1 — Research the service Before touching any file, **grep and read the service's source code** (use an Explore agent for repos not in the workspace). You need: - What does this service do? (one sentence role) - What stack does it run on? (framework, language) - What databases / infra does it use? (Kafka, Redis, Postgres, object storage…) - What Kafka topics does it produce / consume? - What HTTP endpoints does it expose or call? - What other services call it? What does it call? - What WebSocket connections does it open or accept? - What is its repository name in your GitHub org? Only proceed once you can answer all of these from so