QCLang Output Targets
=====================


       
      

**Output Targets**

 

 
        QCLang currently produces one primary output format: validated JSON. This JSON is structured
        to be directly usable with Qiskit Metal and the Qubit-Pro frontend. Future targets are
        planned as the project expands. 

json_ir (primary output)
------------------------

The default output of ```` parse_prompt() ```` . A structured JSON string containing
            chip metadata, qubits (TransmonCross), resonators (RouteMeander), and couplers
            (RoutePath). This is the JSON intermediate representation used by the Qubit-Pro frontend
            and backend APIs.

qiskit_metal
------------

The component types in the JSON ( ```` TransmonCross ```` , ```` RouteMeander ```` , 
             ```` RoutePath ```` ) map directly to Qiskit Metal component classes. The geometry
            parameters (cross_width, trace_width, fillet, etc.) are Qiskit Metal parameters. The
            JSON can be consumed to programmatically instantiate Qiskit Metal designs.

Qubit-Pro API
-------------

The parser is exposed through backend API endpoints ( ```` /api/qclang/parse ```` , 
             ```` /api/qclang/compile ```` ). The frontend editor submits prompts to these
            endpoints and receives JSON to display in the visual designer.

Future targets
--------------

HFSS geometry export, Q3D netlist, SPICE-style circuit representation, and GDS layout
            are planned for future releases as the synthesis pipeline matures.