Facade Module

Take an elevation, a module, and the grid behind it, and get back the division arithmetic: how many panels, what is left over, and the ways the leftover can be taken, each with what it costs the layout. The choice between them is design; the arithmetic before the choice is this skill.

Workflow

Step 1. Collect the dimensions

Ask, in one message:

1. The elevations to panelize: each length, and the floor-to-floor heights if the horizontal joints matter too.
2. The module, or modules, to test, and where each came from.
3. Any hard limits: maximum or minimum panel dimension, from the named manufacturer document. If there are none yet, the run says so and the options carry a note that limits may strike some later.
4. The column grid: bay dimensions and where the grid sits relative to the facade line.
5. Anything fixed that panels must meet: entries, party walls, expansion joints, corners that must match.

Step 2. Divide, and show it

Per elevation, per module:

<elevation>  <length> / <module> = <count> panels + <remainder>

If the division is exact, say so; that elevation needs no options and the run moves on.

Step 3. Lay out the remainder options

For each elevation with a remainder, the standard set, each with its arithmetic:

Option 1  resize all equal      <length> / <count+1> = <new module>
Option 2  end panels            <count> x <module> + 2 end panels @ <dim>
Option 3  one feature bay       <count> x <module> + one panel @ <dim>

Under each option, one line on what it gives up: the module moves off the grid, the corners go special, the odd panel lands where it lands. If the user named fixed points in Step 1, check each option against them. If a manufacturer limit was supplied, strike the options that break it, quoting the limit and its document.

Step 4. Check the grid and the floors

bay / module = <value>   mullion on column line: <yes / no / every nth>
floor-to-floor vs horizontal module: <arithmetic, joint at slab: yes / no>

A module that divides the bay keeps mullions off the columns' faces or on them, whichever the user said they wanted; report the fact, not a preference.

Step 5. Report, and save if asked

One table, elevations by options, counts and odd dimensions in the cells, the give-up line under each. Close with what is undecidable from here: the options that survive arithmetic and limits are design-equal until you choose. Then ask whether to write it to a file and where. Write it directly; there is no template and no script.

Rules

• Never supply a module, a limit, or a panel size. There are none in this file. The manufacturer's literature, named, is the only source of limits.
• Show the division on every line. A panel count without its remainder hides exactly the thing the run is for.
• Options that break a supplied limit are struck with the limit quoted, not silently dropped.
• Report grid alignment as a fact per option. Whether mullions should land on column lines is the user's call.
• Never convert units, and never round an odd panel to a neater figure without labeling it as a changed dimension.
• Do not recommend an option.

Anti-patterns

• Supplying a maximum glass size because the module looks big. Fabrication and shipping limits are the supplier's numbers and change by product and by year.
• Rounding the leftover into the last panel without saying so. The odd panel is the whole finding.
• Averaging the remainder across panels and presenting the result as the original module.
• Judging an option "cleaner". The report carries arithmetic and named trade-offs; taste stays with the designer.
• Extending the run into mullion sizing, anchor layout, or thermal checks because the dimensions are already on the table.

Resources

None. This skill is one file. Output is written directly at the path you choose.