licongxu

Deep-read an academic paper and produce a durable, critical research note — not a loose summary. Use when given a paper title, DOI, arXiv ID, publisher/PDF/GitHub URL, or local PDF, or when asked to read closely, summarize, extract contributions, analyze experiments, critique, compare to related work, reproduce results, or maintain a paper-reading repository index. Works across fields (astro/physics, ML, bio, security, …); examples lean astro-ph but the workflow is general.

Remote, slice-level access to FLAMINGO HDF5 files on COSMA via the `hdfstream` Python module — no need to download whole snapshots. Covers install, server connection, navigation, dataset slicing, multi-slice batched reads, and integration with swiftsimio. Use when reading any FLAMINGO data product remotely.

FLAMINGO past-lightcone products: virtual observers, particle lightcones, HEALPix shell maps, integrated_maps, and halo lightcones. Use when building mock surveys, stacking Compton-y or lensing maps, or cross-correlating with observations.

Review code changes against requirements and quality standards before merge. Use when dispatching a review subagent, after major features, before merging, or when the user asks for a code review. Requires reading the actual diff.

Style and structure for research manuscript text: IMRaD, hourglass narrative, formal tone, topic sentences, reproducible Methods, captions that tell the story. Use when drafting or editing titles, abstracts, sections, captions, or reports.

Iterative VLM review of compiled LaTeX PDFs for layout clashes (text vs figures, tables, long equations). Use after the first compile or any float/equation edit; loop fix-recompile-recheck until no clashes remain.

End-to-end research paper workflow: plan the narrative, draft IMRaD sections, produce figure assets, compile LaTeX to PDF, and debug layout by visually inspecting output (VLM). Use when starting, editing, or submitting a manuscript.

Numerical correctness check on saved result arrays (npz, HDF5, torch, etc.). Use after plot-check or when validating metrics without a new figure. Domain laws, bounds, and thresholds live in the project's CLAUDE.md, not here.

Reviews proposed changes to hmfast for correctness, JAX compatibility, API layering, test coverage, and hardware-cost surprises. Use when the user asks for a review, a sanity check on a diff, or before merging a feature branch.

Guides changes to hmfast Cosmology, emulator loading, and cosmological parameter sets. Use when editing cosmology.py, emulator_load.py, download.py, or adding new emulator_set keys.

Diagnoses a failed or stuck SLURM/HPC job for hmfast (OOM, timeout, NaNs, CUDA errors, missing outputs). Use when the user asks "why did my job fail" or shows a SLURM log.

Guides edits to hmfast's differentiable JAX halo model (HaloModel, mass function, bias, concentration, profiles). Use when changing src/hmfast/halos/, power-spectrum methods, or halo-model consistency flags.

Plans and launches an hmfast experiment (training, inference, or scan) on the cluster with safe resource limits. Use when the user wants to run something that costs nontrivial compute, especially on GPU.

Guides adding or modifying hmfast tracers and halo profiles. Use when editing src/hmfast/tracers/ or src/hmfast/halos/profiles/, or integrating new observables with HaloModel.

Drafts or revises a section of an astrophysics or cosmology manuscript based on hmfast results. Use when the user asks for a draft, an edit pass, or a publishability review of a section, including its figures.