Adapter Studio

A prototype window that shows sample translations between Backstage, TypeSpec, Buf, Pact and Dev Container files and RobOS specs.

packages/adapter-studio

Adapter Studio is a demo of the idea behind the robos-adapters library: take a file in an existing standard (a Backstage catalog-info.yaml, a TypeSpec main.tsp, a Buf config, a Pact contract, a devcontainer.json) and show the matching RobOS spec next to it.

Everything on screen is hardcoded sample data in main.js (a “forms-api” service and a few fake branches). The status badges, entity counts, “100% Lossless” and “14/14 Pact” figures are not computed from your files.

What you can do in it

  • Pick one of the five adapters from the Open-Source Standards list. A search box filters the list by name or standard.
  • Read the two columns in the Bi-Directional Zero-Loss Translation Bridge panel: the raw input on the left, the translated RobOS specification on the right.
  • Change the branch in the header dropdown. It offers three fixed names (main, feature/TAX-1099-ein-verification, hotfix/calc-rate) and only changes the commit badge.
  • Click Export Backstage YAML or Run Adapter Suite (All 5 OSS Standards). Each one shows a confirmation banner. No file is written and no adapter runs.

Where the real code is

The conversion logic is in packages/robos-adapters: one module each for Backstage (importCatalog, exportCatalog), TypeSpec, Buf, Pact and Dev Containers. Adapter Studio does not import it. The library is exercised by the tests in packages/robos-test/tests/sdlc-graph/oss-adapters.test.js.

Running it 

electron packages/adapter-studio

The app needs no network access, Docker or tokens, and stores no data.

More in APIs, Contracts & Testing

Contract Studio A prototype console for browsing OpenAPI and AsyncAPI contracts and running Spectral, Pact and mock-server steps; the results are scripted samples. GraphQL Client & Explorer A GraphiQL-style window with a query editor, variables and response panes; it returns built-in sample data and never contacts the endpoint. gRPC Microservice Client A BloomRPC-style window that lists sample protobuf services and shows canned responses; no RPC is sent. KGraph Parse Portal Crawls a folder into knowledge-graph nodes, classifies files by type, parses documents through Apache Tika when available, and indexes the result for search. REST API Client & Runner Request editor and collection runner wired to a sample Acme Petshop collection on a local Kubernetes cluster. It is a demo built around that one scenario, not a general REST client yet.