Examples

Built by describing it

Four real workflows, each one conversation. What was asked, what got built, and the tools that did it.

Terrain survey

Fire-base site survey, drawn on the map

> For each candidate fire base, check the ground is flat enough for artillery, then draw the usable pads and the overlooking ridgelines on the F10 map.

Terrain statistics over each candidate zone scored slope and elevation spread; clear-spot search found the buildable pads; the ridgelines that overlook each site came from profile sampling. Everything was drawn back onto the F10 map as circles, polylines, and labels — a survey the whole squadron can read at a glance.

terrain_statsfind_clear_spotterrain_profileadd_drawing_circleadd_drawing_line_segments

Air defense

A full SAM site in one sentence

> Stand up an SA-11 battery on the high ground east of the river, oriented west, and put its threat ring on the Blue layer.

One call placed the whole battery — search radar, TELARs, and command post in correct formation, aligned to face the threat axis. A second drew the engagement ring where Blue pilots plan around it. What used to be twenty minutes of unit-by-unit placement is one exchange, and the AI fights it properly because the composition is right.

create_sa11_sitefind_clear_spotadd_drawing_circle

Multiplayer

A multiplayer mission, built while the server waited

> Tonight's flight is eight people: two 4-ship client flights off Batumi, a tanker track, AWACS, and something for them to fight over the border. Radios and kneeboards set up to match.

Client slots, a tanker on station, AWACS coverage, opposing ground forces, radio presets per flight, and kneeboard pages with frequencies and the game plan — assembled conversationally in minutes, saved, and loaded onto the server the same evening.

add_plane_groupcreate_refuel_flightcreate_awacs_flightset_radio_presetsadd_aircraft_kneeboard

Campaign scale

One change, twelve missions

> Across every mission in the campaign folder: move the start time an hour earlier, roll the weather to the next day of the front, and make sure each airfield warehouse actually stocks the loadouts the client flights carry.

The kind of maintenance that kills campaign projects — a dozen missions, three changes each, all of it consistency-critical — becomes a loop: open, edit, validate, save, next. A mission report at the end confirms every file got the same treatment.

open_mizset_start_timeset_weatherset_warehouse_inventoryvalidatemission_report

Got a build of your own? The showcase grows from the community — share what you made on the Discord and it may end up here.