name	bas-graphics
description	Use when building operator graphics, equipment synoptic pages, SVG/HMI-style layouts, live value bindings, or navigation from graphic to point detail. Triggers on: graphic, synoptic, dashboard, AHU, VAV, DOAS, VRF, CRAH, chiller, plant, room, dark theme, graphic.html.

BAS graphics (building-program aware)

bas_build_spec/frontend_example/graphic.html — :root tokens, card chrome, status colors (see spec § DESIGN STYLE).

Graphics must be data-driven, not locked to a single archetype:

Support multiple templates seeded or configured per building program (office VAV + AHU, VRF + DOAS, HP DOAS, data-center CRAH / chilled water, lab pressurization / ACH, hospital isolation OR, etc.).
Each template binds to points and equipment from the domain model (BACnet or simulator). If a site has no chiller, the plant graphic omits or collapses that region—no hardcoded empty placeholders required in acceptance testing beyond “template renders without error.”

name	bas-graphics
description	Use when building operator graphics, equipment synoptic pages, SVG/HMI-style layouts, live value bindings, or navigation from graphic to point detail. Triggers on: graphic, synoptic, dashboard, AHU, VAV, DOAS, VRF, CRAH, chiller, plant, room, dark theme, graphic.html.

bas_build_spec/frontend_example/graphic.html — :root tokens, card chrome, status colors (see spec § DESIGN STYLE).

Graphics must be data-driven, not locked to a single archetype:

Support multiple templates seeded or configured per building program (office VAV + AHU, VRF + DOAS, HP DOAS, data-center CRAH / chilled water, lab pressurization / ACH, hospital isolation OR, etc.).
Each template binds to points and equipment from the domain model (BACnet or simulator). If a site has no chiller, the plant graphic omits or collapses that region—no hardcoded empty placeholders required in acceptance testing beyond “template renders without error.”

bas-graphics