tableslisted

# Table Designer ## Heritage and scope This is an original Open Science Skills workflow for table production in social-science manuscripts. It is general — apply to descriptive tables, regression tables, balance tables, and summary tables across any method. For tables whose interpretation depends on method-specific standards, also consult the relevant sibling skill (`conjoint-design`, `conjoint-diagnostics`, `list-experiment`, `topic-modeling`, `text-classification`, `vlm-ocr-pipeline`). For end-stage QA on a finished table set, hand off to `figure-table-audit`. Tables are for precise reading. A good table is one where the relevant comparison can be made without arithmetic, and where every number that appears in the manuscript text can be traced back to a specific cell. If readers have to do mental subtraction to recover the substantive quantity, the table is the wrong shape. ## Instructions ### 1. Decide whether the result belongs in a table at all Tables are for reading values; figures are for seeing patterns. Use a table when: - Readers need exact values (descriptive statistics for a sample, balance check, key effect sizes for citation). - The comparison spans many models or specifications and a coefficient plot would be too dense. - Regulatory or replication norms require it (CONSORT flow numbers, baseline balance). Use a figure when the substantive claim is a *pattern* — a slope, a non-monotonicity, a difference of differences. Many regression tables in social sc