dsh-office-kit 0.4.2 → 0.4.3

package/assets/skills/office-spreadsheets/recipes/charts.md

@@ -1,8 +1,6 @@
 # Native charts
 
-A native chart is an object bound to cell ranges: the numbers stay in cells, the
-chart reads them, and editing a cell moves the bar. That is the whole reason to
-add one instead of pasting an image.
+A native chart is an object bound to cell ranges: the numbers stay in cells, the chart reads them, and editing a cell moves the bar. That is the whole reason to add one instead of pasting an image.
 
 ```python
 import sys
@@ -30,37 +28,21 @@ wb.save(sys.argv[2])
 
 ## Orientation is the bug people hit
 
-A one-row source is **one series of many points**, not many series of one point.
-`Reference` cannot express that; `add_data(..., from_rows=True)` can. Without it
-a monthly row becomes twelve invisible one-point series and the chart renders
-blank. The mirror case is a one-column source added with `from_rows=True`: you
-get one series per cell row, so only pass it when the data really is row-wise.
+A one-row source is **one series of many points**, not many series of one point. `Reference` cannot express that; `add_data(..., from_rows=True)` can. Without it a monthly row becomes twelve invisible one-point series and the chart renders blank. The mirror case is a one-column source added with `from_rows=True`: you get one series per cell row, so pass it only when the data really is row-wise.
 
 ## What the helper CLI gives you
 
-`xlsx create` accepts `charts[]` with `type`, `title`, `anchor`,
-`height`/`width`, `data {min_col,min_row,max_col,max_row,titles_from_data}` and
-`categories`. `container_tools/add_chart.py` adds the same chart to an existing
-file and handles the row-oriented case. Neither sets axis number formats, series
-colours, legend position, data labels, or gap width — if the chart needs those,
-use a snippet like the one above.
+`xlsx create` accepts `charts[]` with `type`, `title`, `anchor`, `height`/`width`, `data {min_col,min_row,max_col,max_row,titles_from_data}` and `categories`. `container_tools/add_chart.py` adds the same chart to an existing file and handles the row-oriented case. Neither sets axis number formats, series colours, legend position, data labels, or gap width — if the chart needs those, use a snippet like the one above.
 
 ## Checks before you present
 
 - Series count matches the intent (one line per series, not one per point).
 - Categories are labels, not values and not an empty axis with `1, 2, 3, …`.
-- Bar, column, and area axes start at zero; line and scatter may narrow the
-  range, but the scale must be visible and stated.
-- No default legend on a single series; name each series in `titles_from_data`
-  or the legend reads `Series 1`.
-- Axis number formats are set on the chart, not inherited from cells — a source
-  column formatted as `0.0%` does not format the axis.
-- The chart sits near its data, over empty cells, and is not clipped by the
-  print area when the sheet is printed.
+- Bar, column, and area axes start at zero; line and scatter may narrow the range, but the scale must be visible and stated.
+- No default legend on a single series; name each series in `titles_from_data` or the legend reads `Series 1`.
+- Axis number formats are set on the chart, not inherited from cells — a source column formatted as `0.0%` does not format the axis.
+- The chart sits near its data, over empty cells, and is not clipped by the print area when the sheet is printed.
 
 ## Editing a chart in an existing file
 
-Read the object first (`inspect_workbook.py` lists type, anchor, and series
-refs), change the smallest property, and re-render. Moving a chart a few cells is
-fine; rebuilding it with different styling when the user asked for one number to
-be added is not.
+Read the object first (`inspect_workbook.py` lists type, anchor, and series refs), change the smallest property, and re-render. Moving a chart a few cells is fine; rebuilding it with different styling when the user asked for one number to be added is not.

package/assets/skills/office-spreadsheets/recipes/conditional-formats.md

@@ -1,9 +1,6 @@
 # Conditional formats
 
-Conditional formatting paints a cell from a rule, not from a value. The rule is
-stored separately from the cell format, so a cell can look red while its stored
-fill stays default — and a reader who copies the value out gets the number, not
-the colour.
+Conditional formatting paints a cell from a rule, not from a value. The rule is stored separately from the cell format, so a cell can look red while its stored fill stays default — and a reader who copies the value out gets the number, not the colour.
 
 ```python
 import sys
@@ -39,31 +36,17 @@ ws.conditional_formatting.add(
 wb.save(sys.argv[2])
 ```
 
-- `ColorScaleRule`/`DataBarRule` take a range, not a cell; one rule covers the
-  rectangle and scales against the values inside it.
-- `CellIsRule` compares one cell: `operator` in `lessThan`, `greaterThan`,
-  `between`, `equal`, `notEqual`, …
-- `FormulaRule` evaluates a formula with the range's **top-left** cell, so write
-  the reference for that cell (`$F2` with row relative) and Excel fills the rest.
-- A whole-column range (`D:D`) is cheap to write and slow to render; bound the
-  range to the current data (`D2:D13`) and extend it when rows are added.
-- Rules stack in priority order; later rules win only when the earlier ones do
-  not match. `stopIfTrue=True` ends the chain — use it when a second rule must
-  not repaint an already-flagged cell.
-- Do not also set a static fill on the same cells: the static fill shows through
-  where no rule matches and the sheet looks half-formatted.
+- `ColorScaleRule`/`DataBarRule` take a range, not a cell; one rule covers the rectangle and scales against the values inside it.
+- `CellIsRule` compares one cell: `operator` in `lessThan`, `greaterThan`, `between`, `equal`, `notEqual`, …
+- `FormulaRule` evaluates a formula with the range's **top-left** cell, so write the reference for that cell (`$F2` with row relative) and Excel fills the rest.
+- A whole-column range (`D:D`) is cheap to write and slow to render; bound the range to the current data (`D2:D13`) and extend it when rows are added.
+- Rules stack in priority order; later rules win only when the earlier ones do not match. `stopIfTrue=True` ends the chain — use it when a second rule must not repaint an already-flagged cell.
+- Do not also set a static fill on the same cells: the static fill shows through where no rule matches and the sheet looks half-formatted.
 
 ## Editing an existing file
 
-Replace a rule, do not add a near-duplicate: iterate
-`ws.conditional_formatting` and rebuild the collection for that range. Two rules
-covering `D2:D13` with slightly different thresholds give a result nobody can
-explain. Keep the rule count per sheet small — a dashboard with forty rules is a
-compatibility minefield in other engines.
+Replace a rule; do not add a near-duplicate. Iterate `ws.conditional_formatting` and rebuild the collection for that range — two rules covering `D2:D13` with slightly different thresholds give a result nobody can explain. Keep the rule count per sheet small: a dashboard with forty rules is a compatibility minefield in other engines.
 
 ## Verify
 
-Read the file back with `container_tools/inspect_workbook.py`; it lists each
-range and rule type. Then render and look: a data bar that never appears is
-usually a range that does not overlap the data, and a rule that fires on the
-wrong cells is almost always an absolute/relative mistake in `FormulaRule`.
+Read the file back with `container_tools/inspect_workbook.py`; it lists each range and rule type. Then render and look: a data bar that never appears is usually a range that does not overlap the data, and a rule that fires on the wrong cells is almost always an absolute/relative mistake in `FormulaRule`.

package/assets/skills/office-spreadsheets/recipes/data-tables.md

@@ -1,10 +1,6 @@
 # Data tables (Excel Tables)
 
-An Excel Table (`ListObject`) is the object behind `Insert > Table`: a name, a
-structured reference, banded rows, an optional totals row, and header filters.
-It is not a pivot table and not a formatted range. Use it when the user asks for
-a table, when a filter row helps, or when formulas should read
-`Sales[Amount]` instead of `$D$2:$D$900`.
+An Excel Table (`ListObject`) is the object behind `Insert > Table`: a name, a structured reference, banded rows, an optional totals row, and header filters. It is not a pivot table and not a formatted range. Use it when the user asks for a table, when a filter row helps, or when formulas should read `Sales[Amount]` instead of `$D$2:$D$900`.
 
 ```python
 import sys
@@ -23,19 +19,14 @@ wb.save(sys.argv[2])
 
 Rules that survive contact with the user:
 
-- `displayName` has no spaces, no hyphens, and must be unique in the workbook — it
-  becomes the structured reference name (`PipelineTable[Amount]`).
-- `ref` must start at the header row and match the real data rectangle. A table
-  whose `ref` is off by one row shows a phantom header and breaks the filter.
+- `displayName` has no spaces, no hyphens, and must be unique in the workbook — it becomes the structured reference name (`PipelineTable[Amount]`).
+- `ref` must start at the header row and match the real data rectangle. A table whose `ref` is off by one row shows a phantom header and breaks the filter.
 - One table per rectangle, one header row, no merged cells inside it.
-- Give it a style from `TableStyleLight*`/`Medium*`/`Dark*`; a bare table with no
-  style looks like an unstyled range and the user asks why the stripes went away.
+- Give it a style from `TableStyleLight*`/`Medium*`/`Dark*`; a bare table with no style looks like an unstyled range and the user asks why the stripes went away.
 
 ## Appending rows to a table
 
-Rows written below the last table row are outside the table until you widen
-`ref`. Widen it in the same pass, or the new records will not filter, will not
-band, and structured references will not see them.
+Rows written below the last table row are outside the table until you widen `ref`. Widen it in the same pass, or the new records will not filter, will not band, and structured references will not see them.
 
 ```python
 table = ws.tables["PipelineTable"]
@@ -44,15 +35,8 @@ new_last = first_row + added
 table.ref = f"A1:G{new_last}"          # same columns, one row longer
 ```
 
-Copy the format and any formula from the previous row (`ws.cell(r, c)._style =
-ws.cell(r - 1, c)._style`) before widening, so the new row does not appear as a
-plain block inside a banded table.
+Copy the format and any formula from the previous row (`ws.cell(r, c)._style = ws.cell(r - 1, c)._style`) before widening, so the new row does not appear as a plain block inside a banded table.
 
 ## Totals row
 
-`table.totalsRowCount = 1` declares a totals row, and `totalsRowFunction` on a
-column sets `sum`, `count`, `average`, `min`, `max`, `stdDev`, or `var`. The row
-below the last data row must exist and hold the header labels Excel expects; a
-totals row declared without that row renders oddly in some engines. If the user
-only wants a bold total line under a table, a formula row outside the table is
-simpler and less fragile.
+`table.totalsRowCount = 1` declares a totals row, and `totalsRowFunction` on a column sets `sum`, `count`, `average`, `min`, `max`, `stdDev`, or `var`. The row below the last data row must exist and hold the header labels Excel expects; a totals row declared without that row renders oddly in some engines. If the user only wants a bold total line under a table, a formula row outside the table is simpler and less fragile.

package/assets/skills/office-spreadsheets/recipes/named-ranges.md

@@ -1,8 +1,6 @@
 # Named ranges
 
-A defined name is a saved reference with a readable name: `Q4Growth` instead of
-`Model!$B$6`. Formulas that use names survive row and column insertion, and the
-user can select the name box instead of hunting for a cell.
+A defined name is a saved reference with a readable name: `Q4Growth` instead of `Model!$B$6`. Formulas that use names survive row and column insertion, and the user can select the name box instead of hunting for a cell.
 
 ```python
 import sys
@@ -15,27 +13,16 @@ wb.defined_names["PlanRevenue"] = DefinedName("PlanRevenue", attr_text="Model!$B
 wb.save(sys.argv[2])
 ```
 
-- The name must be a legal identifier: letters, digits, underscore, not a cell
-  address (`Q4` alone is a column, so it is refused).
-- `attr_text` is a full sheet reference; quote sheet names with spaces:
-  `'Case A'!$B$4`.
-- Workbook-level names live in `wb.defined_names`. To scope a name to one sheet,
-  put it on the worksheet: `wb["Model"].defined_names["Rate"] = ...` — the same
-  name can then mean different cells on different sheets, which confuses readers
-  unless the workbook already works that way.
-- Read the existing names with `container_tools/inspect_workbook.py` before
-  adding one; a duplicate name is a repair prompt in Excel.
-- Never point a name at a range whose size changes (`A2:A900`) unless the sheet
-  really ends there; prefer the exact used range, or a table reference.
+- The name must be a legal identifier: letters, digits, underscore, not a cell address (`Q4` alone is a column, so it is refused).
+- `attr_text` is a full sheet reference; quote sheet names with spaces: `'Case A'!$B$4`.
+- Workbook-level names live in `wb.defined_names`. To scope a name to one sheet, put it on the worksheet: `wb["Model"].defined_names["Rate"] = ...` — the same name can then mean different cells on different sheets, which confuses readers unless the workbook already works that way.
+- Read the existing names with `container_tools/inspect_workbook.py` before adding one; a duplicate name is a repair prompt in Excel.
+- Never point a name at a range whose size changes (`A2:A900`) unless the sheet really ends there; prefer the exact used range, or a table reference.
 
 ## Using names in formulas
 
-`=PlanRevenue*Q4Growth` is more readable than `=Model!$B$11*Model!$B$6`, and it
-does not break when a row is inserted. Paste the formula text exactly as the user
-would type it; openpyxl never resolves the name.
+`=PlanRevenue*Q4Growth` is more readable than `=Model!$B$11*Model!$B$6`, and it does not break when a row is inserted. Paste the formula text exactly as the user would type it; openpyxl never resolves the name.
 
 ## Removing a name
 
-Deleting a name leaves every formula that used it as `#NAME?`. Find the users
-first (formula text is visible in `inspect_workbook.py` output and
-`xlsx read`), then delete, then recalculate and check the gate.
+Deleting a name leaves every formula that used it as `#NAME?`. Find the users first (formula text is visible in `inspect_workbook.py` output and `xlsx read`), then delete, then recalculate and check the gate.

package/assets/skills/office-spreadsheets/recipes/number-formats.md

@@ -1,9 +1,6 @@
 # Number formats
 
-A number format changes how a stored value is displayed, never the value. The
-cell keeps full precision; `0.0%` shows `6.4%` for `0.06398`. Never store a
-rounded number to make a column look tidy, and never store `"6.4%"` as text —
-it stops summing.
+A number format changes how a stored value is displayed, never the value. The cell keeps full precision; `0.0%` shows `6.4%` for `0.06398`. Never store a rounded number to make a column look tidy, and never store `"6.4%"` as text — it stops summing.
 
 ```python
 import sys
@@ -42,31 +39,18 @@ wb.save(sys.argv[2])
 | Date | `yyyy-mm-dd` | Sortable, unambiguous; store a real date, not text |
 | Text passthrough | `@` | For codes and account numbers with leading zeros |
 
-Do not use `0,0%` or `#.##0`. They are not locale-independent and render
-differently on an engine that reads `,` as a decimal separator.
+Do not use `0,0%` or `#.##0`. They are not locale-independent and render differently on an engine that reads `,` as a decimal separator.
 
 ## Signs, units, and scale
 
-- State the unit once, in the header or title (`Revenue (USD)`), and keep the
-  stored value in that unit. A column that stores thousands but is headed
-  "USD" is a defect waiting to be discovered.
-- If the presentation needs thousands (`$K`) while the data is in units,
-  format does not divide — either store thousands and say so, or divide with a
-  formula in a helper column. Never scale twice.
-- Percentages: store `0.064`, never `6.4`. A stored `6.4` formatted `0.0%`
-  reads `640.0%`.
+- State the unit once, in the header or title (`Revenue (USD)`), and keep the stored value in that unit. A column that stores thousands but is headed "USD" is a defect waiting to be discovered.
+- If the presentation needs thousands (`$K`) while the data is in units, format does not divide — either store thousands and say so, or divide with a formula in a helper column. Never scale twice.
+- Percentages: store `0.064`, never `6.4`. A stored `6.4` formatted `0.0%` reads `640.0%`.
 
 ## Widths and `###`
 
-`###` means the column is narrower than the formatted number. Widen that
-column (`ws.column_dimensions["B"].width = 14`) or shrink the font for the block.
-Never shorten the number, switch to text, or reduce decimals just to fit — and do
-not autofit every column in the sheet to fix one.
+`###` means the column is narrower than the formatted number. Widen that column (`ws.column_dimensions["B"].width = 14`) or shrink the font for the block. Never shorten the number, switch to text, or reduce decimals just to fit — and do not autofit every column in the sheet to fix one.
 
 ## Dates
 
-Write a real date (`datetime.date(2026, 1, 31)`) and set `yyyy-mm-dd`. Storing
-an ISO string sorts alphabetically and calculates as text: `EDATE`, `SUMIFS` on
-dates, and `YEAR()` all fail silently or with `#VALUE!`. A date typed as a number
-of days since 1899-12-30 is a serial — fine for formulas, unreadable for people,
-so format it.
+Write a real date (`datetime.date(2026, 1, 31)`) and set `yyyy-mm-dd`. An ISO string sorts alphabetically and calculates as text: `EDATE`, `SUMIFS` on dates, and `YEAR()` all fail silently or with `#VALUE!`. A date typed as a number of days since 1899-12-30 is a serial — fine for formulas, unreadable for people, so format it.

package/assets/skills/office-spreadsheets/recipes/sparklines.md

@@ -1,8 +1,6 @@
 # Sparklines and in-cell bars
 
-openpyxl writes no sparkline object (and neither does the helper CLI), so a
-"sparkline" here is one of two things: a formula that draws a bar inside the
-cell, or a tiny native chart. Pick by what the user needs to read.
+openpyxl writes no sparkline object (and neither does the helper CLI), so a "sparkline" here is one of two things: a formula that draws a bar inside the cell, or a tiny native chart. Pick by what the user needs to read.
 
 ```python
 import sys
@@ -21,23 +19,12 @@ ws.row_dimensions[4].height = 14
 wb.save(sys.argv[2])
 ```
 
-- `REPT` needs a repeat count that fits the column. A 9-character column shows
-  about 7 blocks at 9pt; anything longer spills into the neighbouring cell and
-  the bars look like one continuous smear. Scale to the column width, not to 22.
-- Keep the count formula-driven (`value / MAX(values) * width`), so a changed
-  number moves the bar.
-- The block character is text. Sorting the column sorts blocks, and a reader who
-  copies the cell gets `████`, not a number — never put these in the column the
-  numbers should be read from.
-- Guard blanks with `IF(cell="","",…)`, otherwise a blank reads as zero and every
-  missing month draws a minimum bar.
-- A native in-cell chart is not the same as a chart object: if the user needs a
-  hover tooltip, axis, or legend, build a real chart with `recipes/charts.md`
-  instead of stretching a formula.
+- `REPT` needs a repeat count that fits the column. A 9-character column shows about 7 blocks at 9pt; anything longer spills into the neighbouring cell and the bars look like one continuous smear. Scale to the column width, not to 22.
+- Keep the count formula-driven (`value / MAX(values) * width`), so a changed number moves the bar.
+- The block character is text. Sorting the column sorts blocks, and a reader who copies the cell gets `████`, not a number — never put these in the column the numbers should be read from.
+- Guard blanks with `IF(cell="","",…)`, otherwise a blank reads as zero and every missing month draws a minimum bar.
+- An in-cell native chart is not the same as a chart object: if the user needs a hover tooltip, axis, or legend, build a real chart with `recipes/charts.md` instead of stretching a formula.
 
 ## When a real chart is the right answer
 
-A sparkline is context for one number, in a dense table. If the sheet has space
-and the point is the trend itself, a small `LineChart` (height 4, width 9, no
-legend, no gridlines) reads better and stays editable. Two or three word-sized
-charts beat a wall of block characters.
+A sparkline is context for one number, in a dense table. If the sheet has space and the point is the trend itself, a small `LineChart` (height 4, width 9, no legend, no gridlines) reads better and stays editable. Two or three word-sized charts beat a wall of block characters.

package/assets/skills/office-spreadsheets/references/charts.md

@@ -1,8 +1,6 @@
 # Chart choice and audit
 
-A chart earns its place when it makes a comparison, a trend, a distribution, or a
-relationship easier to see than a table would. If the reader only needs the
-figures, a compact table or a KPI tile is better — and cheaper to check.
+A chart earns its place when it makes a comparison, a trend, a distribution, or a relationship easier to see than a table would. If the reader only needs the figures, a compact table or a KPI tile is better — and cheaper to check.
 
 | Question | Default | Notes |
 | --- | --- | --- |
@@ -16,48 +14,31 @@ figures, a compact table or a KPI tile is better — and cheaper to check.
 
 ## Honesty
 
-- Series must read from cells, not from typed arrays, and derived values must be
-  formulas. A chart of pasted numbers drifts the moment the table updates.
-- Include zero on bar, column, and area axes. Narrowing a line or scatter axis is
-  acceptable when the limits are stated; a truncated bar axis turns a 5% change
-  into a dramatic cliff.
+- Series must read from cells, not typed arrays, and derived values must be formulas. A chart of pasted numbers drifts the moment the table updates.
+- Include zero on bar, column, and area axes. Narrowing a line or scatter axis is acceptable when the limits are stated; a truncated bar axis turns a 5% change into a dramatic cliff.
 - No 3-D, no shadows, no gradients. They occlude data and date the workbook.
-- One period, one baseline, one unit across comparable charts. Disclose omitted
-  periods and missing values; do not let a blank read as zero.
-- Sort categories deliberately (by value, or by the natural order of time), and
-  keep the same order across charts that will be compared.
+- One period, one baseline, one unit across comparable charts. Disclose omitted periods and missing values; do not let a blank read as zero.
+- Sort categories deliberately (by value, or by the natural order of time), and keep the same order across charts that will be compared.
 
 ## Formatting rules that catch reviewers' eyes
 
-- Title states subject and unit: `Profit by category ($m)`, `Monthly revenue
-  (USD)`. No placeholder titles, no legend standing in for a title.
-- Units in the title or on the axis: `($K)`, `($M)`, `(USD thousands)`. Never
-  `($000)`.
-- Axis number formats are set on the chart. Source cell formats do not carry over,
-  and a `0.0%` column can still produce `0.06, 0.08` ticks.
-- Few series: direct labels. More series: legend above the plot area, consistent
-  colours per series across the workbook.
-- Single series: no legend, one colour. A reference or target line is neutral or
-  dashed so it does not read as another data series.
-- Selective data labels only — the last point, the maximum, the one the user asked
-  about. Ten labels on a twelve-point line is a table with extra steps.
+- Title states subject and unit: `Profit by category ($m)`, `Monthly revenue (USD)`. No placeholder titles, no legend standing in for a title.
+- Units in the title or on the axis: `($K)`, `($M)`, `(USD thousands)`. Never `($000)`.
+- Axis number formats are set on the chart. Source cell formats do not carry over, and a `0.0%` column can still produce `0.06, 0.08` ticks.
+- Few series: direct labels. More series: legend above the plot area, consistent colours per series across the workbook.
+- Single series: no legend, one colour. A reference or target line is neutral or dashed so it does not read as another data series.
+- Selective data labels only — the last point, the maximum, the one the user asked about. Ten labels on a twelve-point line is a table with extra steps.
 - Line strokes are set explicitly; a fill alone may not colour an exported line.
 
 ## Placement
 
-Charts sit next to the data they describe, aligned to a column edge, over empty
-cells, and never over the data, the controls, or a note. Size them to their
-content; a chart stretched across the page with two bars in it looks unfinished.
+Charts sit next to the data they describe, aligned to a column edge, over empty cells, and never over the data, the controls, or a note. Size them to their content; a chart stretched across the page with two bars looks unfinished.
 
 ## Verifying a chart
 
 1. Read the object back: type, anchor, series count, category source.
-2. Render and look at the image: are there categories, is anything clipped, is the
-   legend empty, do the bars reach the values in the table?
+2. Render and look at the image: are there categories, is anything clipped, is the legend empty, do the bars reach the values in the table?
 3. Compare the visual against the sheet's numbers at one or two points.
-4. Re-open in the app the user will use if the colours matter — an authoring
-   preview is not proof that a filled series exports as a visible line.
+4. Re-open in the app the user will use if the colours matter — an authoring preview is not proof that a filled series exports as a visible line.
 
-If the chart cannot be delivered as asked (the engine has no box plot, the data
-cannot be rearranged), say so and use the closest clear alternative. Never claim a
-requirement was met by a chart that does not show it.
+If the chart cannot be delivered as asked (the engine has no box plot, the data cannot be rearranged), say so and use the closest clear alternative. Never claim a requirement was met by a chart that does not show it.

package/assets/skills/office-spreadsheets/references/domain/financial-models.md

@@ -1,29 +1,15 @@
 # Financial models
 
-Applies to forecasts, budgets, cash-flow plans, and valuation work in any
-industry.
+Forecasts, budgets, cash-flow plans, and valuation work in any industry.
 
-- Periods run left to right with the scale in the header (Actual, Forecast,
-  Budget). Do not mix a monthly column with a quarterly total in the same row
-  without a labelled total column at the edge.
-- Drivers first, results second: volume × price, headcount × cost, days × rate.
-  A revenue row that jumps straight to a number cannot be reviewed.
-- Units are stated once and kept: thousands vs millions in the same block is the
-  classic reconciliation failure. Put the unit in the title, not in a footnote.
-- Three statements or none: if the workbook includes a balance sheet and a cash
-  flow, the balance sheet must balance and closing cash must equal the cash-flow
-  ending balance. Add those as checks, not as comments.
-- Working capital moves: receivables from revenue × DSO, payables from cost × DPO,
-  inventory from COGS × days. Hard-coded changes in working capital break when the
-  drivers move.
-- Scenarios: one selector, one set of case inputs per driver, and an explicit
-  `Case Selected:` on each output. A workbook with two switch cells reports two
-  answers.
-- Never hard-code a total that already exists as a sum, and never sum a column that
-  already contains a total (double counting is silent).
-- Sensitivity: one or two variables, closed-form or a small grid with the base case
-  marked. A native What-If Data Table is a different object with its own limits —
-  only build one when the user asks for it and the engine supports it.
+- Periods run left to right with the scale in the header (Actual, Forecast, Budget). Do not mix a monthly column with a quarterly total in the same row unless a labelled total column sits at the edge.
+- Drivers first, results second: volume × price, headcount × cost, days × rate. A revenue row that jumps straight to a number cannot be reviewed.
+- State units once and keep them: thousands and millions in the same block is the classic reconciliation failure. Put the unit in the title, not a footnote.
+- Three statements or none: if the workbook has a balance sheet and a cash flow, the balance sheet must balance and closing cash must equal the cash-flow ending balance. Make these checks, not comments.
+- Working capital moves: receivables from revenue × DSO, payables from cost × DPO, inventory from COGS × days. Hard-coded working-capital changes break when drivers move.
+- Scenarios: one selector, one set of case inputs per driver, and an explicit `Case Selected:` on each output. Two switch cells report two answers.
+- Never hard-code a total that exists as a sum, and never sum a column that already holds a total — double counting is silent.
+- Sensitivity: one or two variables, closed-form or a small grid with the base case marked. A native What-If Data Table is a different object with its own limits; build one only when the user asks and the engine supports it.
 
 ## Checks a finance reader looks for first
 
@@ -36,5 +22,4 @@ industry.
 | Case consistency | Every tab shows the same selected case |
 | No hard-coded totals | Total cells are formulas |
 
-Put them on a check tab, terminal and read-only, and make a failing check visually
-obvious without painting passing checks green.
+Put them on a check tab, terminal and read-only. Make a failing check visually obvious without painting passing checks green.

package/assets/skills/office-spreadsheets/references/domain/healthcare.md

@@ -1,22 +1,11 @@
 # Healthcare operations
 
-Workbooks here usually track volume, capacity, cost, and quality — not patients.
-Treat patient-level data as sensitive: do not paste identifiers into a workbook
-unless the user asks for it, do not copy rows from files you were shown into new
-sheets, and prefer aggregates.
+Workbooks here usually track volume, capacity, cost, and quality — not patients. Treat patient-level data as sensitive: do not paste identifiers into a workbook unless the user asks, do not copy rows from files you were shown into new sheets, and prefer aggregates.
 
-- Name the denominator in every rate: per patient day, per discharge, per 1,000
-  members, per available bed. A percentage without its base is not a metric.
-- Volume and capacity are different columns. Utilization is
-  `used ÷ available`, and both sides need the same period and unit (bed-days, not
-  beds).
-- Payer mix, service line, and site of care are separate dimensions. One table with
-  a column per dimension beats four tables that must be read together.
-- Quality and safety metrics keep their own definitions; do not average a rate
-  across sites without stating whether it is volume-weighted.
-- Claims and remittance data arrive with gaps. Show missing as blank or `n.a.`,
-  never as zero, and state the coverage period.
-- Do not invent clinical thresholds, targets, or compliance claims. Use the
-  targets the source file provides, and cite the sheet and cell.
-- Money and counts follow the finance conventions: units stated once, totals as
-  formulas, checks that detail rows reconcile to the summary.
+- Name the denominator in every rate: per patient day, per discharge, per 1,000 members, per available bed. A percentage without its base is not a metric.
+- Volume and capacity are different columns. Utilization is `used ÷ available`, and both sides need the same period and unit (bed-days, not beds).
+- Payer mix, service line, and site of care are separate dimensions. One table with a column per dimension beats four tables that must be read together.
+- Quality and safety metrics keep their own definitions; do not average a rate across sites without stating whether it is volume-weighted.
+- Claims and remittance data arrive with gaps. Show missing as blank or `n.a.`, never as zero, and state the coverage period.
+- Do not invent clinical thresholds, targets, or compliance claims. Use the targets the source file provides, and cite the sheet and cell.
+- Money and counts follow the finance conventions: units stated once, totals as formulas, checks that detail rows reconcile to the summary.

package/assets/skills/office-spreadsheets/references/domain/marketing.md

@@ -1,28 +1,14 @@
 # Marketing and advertising
 
-Campaign work is a funnel plus a spend table, and both are easy to make look
-better than they are.
+Campaign work is a funnel plus a spend table, and both are easy to make look better than they are.
 
-- One row per campaign, channel, or creative — with that grain named in the header.
-  Mixing a channel total into a campaign table double counts.
-- The funnel reads spend → impressions → clicks → conversions → revenue, in that
-  order, with rates derived by formula: `CTR = clicks / impressions`,
-  `CVR = conversions / clicks`, `CPA = spend / conversions`,
-  `ROAS = revenue / spend`.
-- Never compute a ratio from cells that are not the same period and the same
-  population. A monthly CTR built from a quarterly spend and a weekly click count
-  is a number nobody can defend.
-- Attribution is a claim: say which model the numbers use (last click, platform
-  reported, blended) and keep it constant across the table. Do not add platform
-  conversions together and call it incremental revenue.
-- Missing spend or reach for a period is blank, not zero — a zero-spend month
-  shows an infinite CPA and a fake collapse in the trend.
-- Benchmarks and targets belong in a labelled row or column with their source, not
-  in a note the reader has to find.
+- One row per campaign, channel, or creative, with that grain named in the header. Mixing a channel total into a campaign table double counts.
+- The funnel reads spend → impressions → clicks → conversions → revenue in that order, with rates derived by formula: `CTR = clicks / impressions`, `CVR = conversions / clicks`, `CPA = spend / conversions`, `ROAS = revenue / spend`.
+- Never compute a ratio from cells that are not the same period and the same population. A monthly CTR built from a quarterly spend and a weekly click count is a number nobody can defend.
+- Attribution is a claim: say which model the numbers use (last click, platform reported, blended) and keep it constant across the table. Do not add platform conversions together and call it incremental revenue.
+- Missing spend or reach for a period is blank, not zero — a zero-spend month shows an infinite CPA and a fake collapse in the trend.
+- Benchmarks and targets belong in a labelled row or column with their source, not in a note the reader has to find.
 
 ## Charts for marketing
 
-Spend and return on the same chart only when both are in the same unit; otherwise
-two aligned charts. Sort channel bars by spend or by return — not alphabetically —
-and keep the same order across charts. A conversion trend belongs on a line chart
-with the campaign launch dates marked, not on a pie.
+Put spend and return on one chart only when both use the same unit; otherwise two aligned charts. Sort channel bars by spend or by return, not alphabetically, and keep the same order across charts. A conversion trend belongs on a line chart with the campaign launch dates marked, not on a pie.

package/assets/skills/office-spreadsheets/references/domain/research.md

@@ -1,22 +1,11 @@
 # Scientific and research data
 
-The spreadsheet is usually a working copy of measurements, not the record of
-truth. Keep it that way: never edit raw measurements in place, and never let a
-formatted view replace the values behind it.
+The spreadsheet is usually a working copy of measurements, not the record of truth. Keep it that way: never edit raw measurements in place, and never let a formatted view replace the values behind it.
 
-- Raw data on its own sheet, untouched, in columns whose headers carry the unit
-  (`time (s)`, `temp (C)`, `conc (mg/L)`). Derived columns live on a build sheet
-  and reference the raw cells.
-- One row per observation, one column per variable. Do not encode a variable in a
-  colour, a note, or a header font.
-- Replicates are separate rows with a replicate id and a group id; the mean and
-  standard deviation are formulas over those rows, never typed.
-- Keep the precision the instrument gives you and let the format hide extra
-  decimals. Rounding stored values destroys the ability to recompute a mean.
-- Uncertainty, detection limits, and excluded points are stated in labelled cells.
-  An excluded point stays in the data with a reason column — deleting it hides the
-  decision.
-- Smoothing, binning, and unit conversion are formulas with visible inputs, or they
-  do not exist. A trend line drawn over noisy points is not an analysis.
-- Distribution, trend, and relationship: choose the chart by the question, and
-  check that the axis ranges and bins are stated (`references/charts.md`).
+- Raw data on its own sheet, untouched, in columns whose headers carry the unit (`time (s)`, `temp (C)`, `conc (mg/L)`). Derived columns live on a build sheet and reference the raw cells.
+- One row per observation, one column per variable. Do not encode a variable in a colour, a note, or a header font.
+- Replicates are separate rows with a replicate id and a group id; mean and standard deviation are formulas over those rows, never typed.
+- Keep the precision the instrument gives you and let the format hide extra decimals. Rounding stored values destroys the ability to recompute a mean.
+- State uncertainty, detection limits, and excluded points in labelled cells. An excluded point stays in the data with a reason column — deleting it hides the decision.
+- Smoothing, binning, and unit conversion are formulas with visible inputs, or they do not exist. A trend line drawn over noisy points is not an analysis.
+- Distribution, trend, and relationship: choose the chart by the question, and check that axis ranges and bins are stated (`references/charts.md`).