brycewang-stanford/Auto-Empirical-Research-Skills / skills/35-bahayonghang-academic-writing-skills/skills/latex-paper-en
latex-paper-en
VerifiedEnglish LaTeX academic paper assistant for existing `.tex` projects. Use this skill whenever the user wants to compile, lint, audit, or improve an English LaTeX conference or journal paper such as IEEE, ACM, Springer, NeurIPS, or ICML submissions. Trigger even when the user only mentions one paper issue, such as bibliography errors, grammar cleanup, sentence splitting, logic review, expression polishing, translation, title optimization, figure checks, pseudocode review, algorithm block cleanup, de-AI editing, experiment-section review, table structure validation, three-line table generation, abstract structure diagnosis, or journal adaptation. Also trigger for "proofread my paper", "fix my LaTeX", "prepare for submission", "check my manuscript", "improve my writing", "three-line table", "booktabs", "check abstract", "reformat for another journal", "换投", `algorithm2e`, `algorithmicx`, `algpseudocodex`, `Require/Ensure`, or "Algorithm 1" when the user has a .tex file.
references/TABLE_GUIDE.md
View on GitHub# Three-Line Table Guide
This guide defines the standard for professional academic tables using the "three-line" (booktabs) convention. All table-related checks and generation follow these rules.
## Three-Line Table Standard
A three-line table has exactly three horizontal rules and **no vertical lines**:
1. **Top rule** (`\toprule`): above column headers
2. **Mid rule** (`\midrule`): below column headers, above data rows
3. **Bottom rule** (`\bottomrule`): below the last data row
### Anti-Patterns (must flag)
- Vertical lines (`|` in column spec, `\vline`, `\hline` with `|`)
- Internal horizontal lines (`\hline` or `\cline` between data rows, except for grouping sub-headers)
- Using `\hline` instead of booktabs commands
- Missing `\usepackage{booktabs}` in preamble
### Minimal Correct Example
```latex
\begin{table}[t]
\caption{Comparison of model accuracy (\%).}
\label{tab:accuracy}
\centering
\begin{tabular}{lSSS}
\toprule
Model & {Precision} & {Recall} & {F1} \\
\midrule
Baseline & 85.3 & 82.1 & 83.7 \\
Ours & \textbf{91.2} & \textbf{89.5} & \textbf{90.3} \\
\bottomrule
\end{tabular}
\end{table}
```
## Decimal Alignment
Use the `siunitx` package `S` column type to align numbers by decimal point:
```latex
\usepackage{siunitx}
\sisetup{detect-weight, mode=text}
% Column spec: {l S[table-format=2.1] S[table-format=2.1]}
% Wrap non-numeric headers in braces: {Precision}
```
When `siunitx` is unavailable, right-align numeric columns with `r` and ensure consistent decimal places manually.
## Statistical Significance Markers
Use superscript symbols with footnote definitions in the table note:
| Symbol | Meaning |
|--------|---------|
| `*` | p < 0.05 |
| `**` | p < 0.01 |
| `***` | p < 0.001 |
| `n.s.` | not significant |
Place significance markers immediately after the value: `91.2***`.
## Number Precision Rules
| Data type | Precision | Example |
|-----------|-----------|---------|
| Percentage | 1 decimal place | 85.3% |
| Mean ± SD | 2 decimal places | 3.14 ± 0.05 |
| p-value | 3 significant figures | 0.0032 |
| Correlation coefficient | 2-3 decimal places | 0.87 |
| Large counts | No decimals | 1,024 |
Precision must be consistent within each column. Mixed precision in the same column is a warning.
## Caption and Note Placement
- **Caption**: above the table (`\caption{...}` before `\begin{tabular}`)
- **Label**: immediately after caption (`\label{tab:...}`)
- **Table note**: below the table, starting with "Note." (English) or "注:" (Chinese)
Table note format:
```latex
\begin{tablenotes}
\small
\item Note. Bold values indicate best performance.
\item * $p < 0.05$; ** $p < 0.01$; *** $p < 0.001$.
\end{tablenotes}
```
Or use `\par\vspace{2pt}{\footnotesize Note. ...}` after `\end{tabular}` if `threeparttable` is not loaded.
## Bold Best Values
In comparison tables, bold the best value in each column using `\textbf{}`. When using `siunitx` S columns, use `\bfseries` or wrap in `{\textbf{91.2}}`.
Add direction indicators when the "best" direction is ambiguous:
- `↑` (higher is better): accuracy, recall, F1
- `↓` (lower is better): error rate, latency, loss
## Booktabs Package Requirements
The `booktabs` package must be loaded for `\toprule`, `\midrule`, `\bottomrule`. These commands produce variable-weight rules (top/bottom are heavier than mid) for a professional appearance.
Never mix `\hline` with booktabs commands in the same table.
## Word Compatibility Note
When submitting to venues that require .docx, convert the three-line table by:
1. Create a standard table in Word
2. Select the entire table → Borders → No Border
3. Add top border to first row, bottom border to header row, bottom border to last row
4. Result: a three-line table matching the booktabs aesthetic
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| rea-analysis-optimizationmorluto/reaOptimize REA providers and shared analysis workflows for agent context, latency, CPU, and memory while preserving correctness and Evidence. Use for analysis bottlenecks and cache or query design; CI/test-suite optimization belongs to rea-ci-tests-audit. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| rea-ci-tests-auditmorluto/reaAudit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for suite or workflow investigations and efficiency changes, rather than ordinary feature testing or a single test failure. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first. | Stars: 196k | Updated | Claude CodeCodex | Verified | Install |