Update to ArchLang

{
  "description": "Use when the user gives a written brief for a new floor plan (rooms, areas, how rooms connect, a plot size) and wants the drawing, e.g. \"design a two-bedroom flat of about 75 m²\" or \"lay out a small office with four rooms\". Writes an ArchLang .arch file from the brief, checks it against the brief with the archlang CLI, and finishes it as a sheet. Not for changing an existing plan (archlang-edit-plan) or for exporting one (archlang-export).",
  "included_files": [],
  "name": "archlang-brief-to-plan",
  "skill_md_contents": "---\nname: archlang-brief-to-plan\ndescription: Use when the user gives a written brief for a new floor plan (rooms, areas, how rooms connect, a plot size) and wants the drawing, e.g. \"design a two-bedroom flat of about 75 m²\" or \"lay out a small office with four rooms\". Writes an ArchLang .arch file from the brief, checks it against the brief with the archlang CLI, and finishes it as a sheet. Not for changing an existing plan (archlang-edit-plan) or for exporting one (archlang-export).\nlicense: MIT\ncompatibility: Needs a shell with Node 18+ and the archlang CLI (npx -y @chanmeng666/archlang@1.50.0, or npm i -g @chanmeng666/archlang@1.50.0 for a global archlang).\n---\n\n# Brief to plan\n\nTurn a written brief into a checked `.arch` floor plan. Every step is a CLI call; never judge the\nplan from the SVG markup.\nIf `archlang` is not on the path, write `npx -y @chanmeng666/archlang@1.50.0` in its place.\nNever run a bare `arch`: on Linux, macOS and Git Bash that name is the coreutils command.\n\nThis skill is a workflow, not a language reference. The language is whatever `archlang spec` prints.\n\n## Scope\n\n- Run the `archlang` CLI commands below and no other program.\n- Write one new plan file, `plan.arch` here or the name the user gives, in the user's working\n  directory, plus the drawings the CLI renders beside it. If a file of that name already exists,\n  ask the user before replacing it.\n- The user's explicit instructions take priority over these steps.\n\n## Steps\n\n1. **Read the language.** Run `archlang spec` and read all of it before writing a line. For one\n   command's flags and examples run `archlang <cmd> --help`, for example `archlang finish --help`.\n2. **List what the brief asks for.** Write down each room, each stated area, each stated\n   connection (\"opens off the hall\"), each stated window, and any outer size. Keep numbers exactly\n   as the brief states them. If two requirements cannot both hold, stop and tell the user which\n   ones; do not quietly change a number.\n3. **Write `plan.arch`.** Give every room an `id`, a `label` and a `uses`. Attach doors and windows\n   to walls and place furniture by anchor, as `archlang spec` shows, instead of computing coordinates.\n   Give every room a door or an opening.\n4. **Compile.** `archlang compile plan.arch -o plan.svg --json`. If `ok` is false, read each\n   `diagnostics[].fix`. Preview the mechanical fixes with `archlang fix plan.arch --dry-run --json`,\n   then apply them with `archlang fix plan.arch`. Fix the rest by hand and compile again.\n5. **Check the plan against your list.** `archlang describe plan.arch --select rooms,doors,windows,totals --json`.\n   Compare room count, labels, each area, what each door connects and which rooms have windows\n   with the list from step 2. Edit and repeat from step 4 until they match. `area_m2` is measured on\n   wall centrelines; `net_area_m2` is the floor no wall stands on.\n6. **Check soundness.** `archlang lint plan.arch --json`. Fix each warning, or keep it on purpose and\n   say why. If a room cannot be reached or a bedroom has no window, `archlang suggest plan.arch --json`\n   returns door and window statements you can paste.\n7. **Finish the drawing.** `archlang finish plan.arch --dry-run --json` shows the furniture and sheet\n   statements it would add; `archlang finish plan.arch` applies them. Read `unresolved`: it names each\n   room left empty and each statement left out, with the reason.\n8. **Gate and show.** `archlang validate plan.arch --strict --json` must exit `0`, or you must be able\n   to name each remaining warning as deliberate. Then `archlang preview plan.arch -o plan.png` to show\n   the user.\n\n## Report to the user\n\n- The file you wrote and the drawing you rendered.\n- Every requirement of the brief the plan does not meet, or \"none\".\n- Which area you quote: `net_area_m2` is the floor no wall stands on, `area_m2` the larger\n  centreline figure. If a room has no `net_area_m2`, say its net area could not be computed.\n- Every lint warning still present, with the reason it stays.\n\n## When something goes wrong\n\n- Exit code `2` is a fault in the source. Read the diagnostic and fix it; do not run the same\n  command again unchanged. `3` is a wrong flag: run `archlang <cmd> --help`.\n- For an unfamiliar code, run `archlang explain <CODE> --json`.\n- To gate on the brief as data instead of by eye, write it as an intent file and run\n  `archlang validate plan.arch --intent intent.json --feedback --json`. The archlang-review-plan\n  skill covers this.\n"
}