← ClaudeAtlas

paper-webpage-builderlisted

Build a polished single-page academic project webpage from a paper directory or paper source, including content extraction, figure selection/conversion, module planning, visual design, tables, assets, and validation. Use when asked to create or update webpages for papers, benchmarks, arXiv-style projects, OpenRaiser project pages, or paths containing paper.tex/PDF/images/assets.
OpenRaiser/paper-webpage-builder · ★ 2 · Web & Frontend · score 65
Install: claude install-skill OpenRaiser/paper-webpage-builder
# Paper Webpage Builder Use this skill to turn a paper project folder into a web-ready project page. It is optimized for repos with `paper.tex`, `*.pdf`, `images/`, and `assets/`, but also works from a PDF plus image assets. ## Core Rule Do not mechanically clone an existing webpage. Use prior pages only as references for interaction patterns and content completeness. The final design must follow the target paper's topic, figures, color palette, density, and audience. Two failure modes to actively avoid: - Do not reuse a background system from another paper page by default. Grids, coordinate paper, dark sections, gradients, or canvas textures are allowed only when they are supported by the target paper's own figures, domain, or visual language. - Do not summarize away central evidence. If the paper's main claim depends on a main experiment table, benchmark comparison table, dataset statistics table, or ablation table, the webpage must include that table in full or provide a clearly equivalent full presentation. - Do not show partial or horizontally scrolling tables. Table rows, headers, and cell text must be statically visible; they must not be clipped by smaller white/card containers, fixed-height panels, masks, fades, `overflow:hidden`, or `overflow-x:auto/scroll`. Wide tables should use grouped columns, multiple full sub-tables, readable density reduction, or a larger responsive container while preserving values. ## Workflow 1. Inspect inputs before editing. - Lo