brycewang-stanford/Auto-Empirical-Research-Skills / skills/35-bahayonghang-academic-writing-skills/skills/typst-paper
typst-paper
VerifiedTypst academic paper assistant for existing `.typ` paper projects in English or Chinese. Use this skill whenever the user wants to compile, audit, or improve a Typst paper, including format checks, bibliography validation for BibTeX or Hayagriva, grammar/sentence/logic review, expression polishing, translation, title optimization, pseudocode review, algorithm block cleanup, de-AI editing, experiment-section review, table structure validation, three-line table generation, abstract structure diagnosis, or journal adaptation. Trigger even when the user only mentions one Typst file, one bibliography issue, one pseudocode block, one section rewrite, "three-line table", "check abstract", or "reformat for another journal". Also trigger when the user mentions ".typ files", "typst compile error", "typst export", "typst bibliography", `algorithm-figure`, `lovelace`, or `algorithmic` even without saying the word "Typst" explicitly.
references/NUMBER_UNIT_GUIDE.md
View on GitHub# Number and Unit Formatting Guide
This reference defines conventions for numbers, units, and statistical reporting in academic papers.
## SI Unit Formatting
- Always insert a space between the number and the unit: `5 kg`, `100 mL`, `25 °C`
- Exceptions: percentage (`5%`), degree symbol alone (`45°`), currency (`$100`)
- Use SI base/derived units; spell out non-standard units on first use
- In LaTeX: use `\SI{5}{kg}` (siunitx) or `5\,kg` for thin space
- In Typst: use `5 #unit("kg")` or manual thin space `5#h(0.15em)kg`
## Number-Word Thresholds
| Context | Rule |
|---------|------|
| Sentence start | Always spell out: "Twenty participants..." |
| Values 1-9 in prose | Spell out: "three experiments", "five categories" |
| Values 10+ in prose | Use digits: "12 features", "256 samples" |
| Precise measurements | Always digits: "3 mL", "7 days" |
| Large round numbers | Mixed: "1.2 million", "3 billion" |
| Adjacent numbers | Alternate forms: "two 3-layer networks" |
## Statistical Reporting
| Measure | Format | Example |
|---------|--------|---------|
| Percentage | 1 decimal place | 85.3% |
| Mean +/- SD | 2 decimal places | 3.14 +/- 0.05 |
| p-value | Exact (3 sig figs) or threshold | p = 0.003, p < 0.001 |
| Correlation | 2-3 decimal places | r = 0.87 |
| Confidence interval | Same precision as estimate | [2.10, 4.18] |
| Effect size (Cohen's d) | 2 decimal places | d = 0.75 |
| F-statistic | 2 decimal places with df | F(2, 47) = 3.85 |
| t-statistic | 2 decimal places with df | t(49) = 2.10 |
| Chi-square | 2 decimal places with df | chi-sq(3) = 7.81 |
## Consistency Rules
- Precision must be consistent within each column of a table
- Precision must be consistent for the same measure across the paper
- Report exact p-values when p >= 0.001; use "p < 0.001" otherwise
- Never report "p = 0.000" — use "p < 0.001"
## Range Formatting
- Use en dash for number ranges: "10--20", "pp. 1--15"
- In LaTeX: `10--20` renders as `10–20`
- In Typst: `10--20` or `10#sym.dash.en 20`
- Do not use "from X-Y"; use "from X to Y" or "X--Y"
## Large Number Formatting
- Use comma separators for numbers >= 1,000: `1,024`, `10,000`
- In some European venues, use period: `1.024`, `10.000` — check venue guide
- Scientific notation for very large/small: `3.2 x 10^5`, `1.5 x 10^{-3}`
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: 194k | Updated | Claude CodeCodex | Verified | Install |