[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7ESMSGCQHT67DTG0C1KQ06D":3,"skill-same:01M7ESMSGCQHT67DTG0C1KQ06D":47},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":25,"commitSha":26,"skillDirectory":27,"forksCount":28,"repositoryHtmlUrl":29,"repositoryHomepageUrl":6,"ownerHtmlUrl":30,"ownerBlogUrl":31,"ownerDescription":6,"updatedAt":32,"install":33,"resources":46},"01M7ESMSGCQHT67DTG0C1KQ06D","latex-pro",null,"LaTeX authoring and automation — documents, templates, and programmatic generation — use for academic papers, reports, and math-heavy docs.","TanNhatCMS\u002Fjarvis","TanNhatCMS","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F113796420?v=4","01M753MV17KG5CD3152G3WQEQY","KietNT","01M7EKEDYVYQ6PWVJJMZ911VMX",0,"MIT","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fams-latex-pro\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: latex-pro\ndescription: LaTeX authoring and automation — documents, templates, and programmatic generation — use for academic papers, reports, and math-heavy docs.\ncategory: document-processing\n---\n\n## Overview\n\nLaTeX remains the gold standard for math-heavy documents, theses, and\npublication-quality typesetting. Beyond authoring, LaTeX is automatable:\ngenerate reports from data, manage bibliographies programmatically, and build\nreproducible document pipelines. This skill covers both craft and automation.\n\n## When to use\n\n- Writing papers, theses, or technical reports with mathematics\n- Creating reusable templates (letterheads, invoices, certificates, CVs)\n- Managing bibliographies (BibTeX\u002FBibLaTeX) at scale\n- Generating LaTeX documents programmatically from data\n- Debugging compilation errors and package conflicts\n\n## Core concepts\n\n**Structure with semantics.** `\\section`, `\\label`\u002F`\\ref`, `\\cite`, and\nenvironments (`theorem`, `figure`, `table`) — not manual numbering or\nhardcoded \"see page 12\". Semantic markup is what makes cross-references,\nTOCs, and bibliographies maintain themselves.\n\n**Preamble discipline.** Load packages once, in a sensible order, with a\ncommented preamble or a shared `.sty` file for projects. Package conflicts\n(fontenc\u002Finputenc ordering, hyperref loaded last-ish) cause the most\nmysterious errors; a curated preamble prevents them.\n\n**BibLaTeX + Biber for bibliographies.** The modern stack handles Unicode,\ncomplex entry types, and per-chapter bibliographies far better than legacy\nBibTeX. Keep one curated `.bib` file; use a reference manager or consistent\ncitation keys (`author:year:keyword`).\n\n**Compilation is a pipeline.** `pdflatex → biber → pdflatex → pdflatex` (or\n`latexmk`, which automates the dance). Build with `latexmk -pdf` and let it\nresolve the multi-pass requirements; in CI, pin the TeX distribution version\nfor reproducible builds.\n\n**Programmatic generation.** Templates with placeholders filled from data\n(CSV, JSON, databases) produce invoices, certificates, and reports with\ntypeset quality. Escape LaTeX special characters (`& % $ # _ { } ~ ^ \\`) in\ndata — unescaped input is the #1 generation bug.\n\n## Practical workflow\n\n1. **Start from a template** (article, report, beamer, or your org's class) —\n   don't build a preamble from scratch for each document.\n2. **Write with labels from day one:** `\\label{sec:method}` on everything\n   you'll reference; `\\cite{}` as you write, not at the end.\n3. **Manage figures properly:** vector formats (PDF) for plots and diagrams,\n   sensible DPI for raster images, `\\includegraphics` with relative widths,\n   captions that actually explain the figure.\n4. **For math:** `amsmath` environments (`align`, `gather`), numbered only\n   equations you'll reference; define macros for repeated notation\n   (`\\newcommand{\\R}{\\mathbb{R}}`).\n5. **Automate builds:** `latexmk` locally, CI job for the final artifact;\n   check in the `.tex`, `.bib`, and figures — never the generated PDF as\n   source of truth.\n6. **For generated documents:** template + data + escaping + a compile check\n   in the pipeline; render a sample and visually inspect before bulk runs.\n\n## Common pitfalls\n\n- **Ignoring compilation warnings** — undefined references and multiply\n  defined labels compound; fix them as they appear.\n- **Manual bibliography formatting** — hand-typed reference lists drift and\n  misformat; use BibLaTeX always.\n- **Special characters in generated content** — `%` in data comments out the\n  rest of the line; escape everything from untrusted data.\n- **Huge monolithic .tex files** — split chapters into `\\input` files; giant\n  files are unmergeable and slow to navigate.\n- **Package soup** — loading dozens of packages \"just in case\" invites\n  conflicts; load what you use, in documented order.\n- **Committing build artifacts** (`.aux`, `.log`, `.pdf`) — `.gitignore` them;\n  only sources and the build recipe belong in version control.\n","## Overview\n\nLaTeX remains the gold standard for math-heavy documents, theses, and\npublication-quality typesetting. Beyond authoring, LaTeX is automatable:\ngenerate reports from data, manage bibliographies programmatically, and build\nreproducible document pipelines. This skill covers both craft and automation.\n\n## When to use\n\n- Writing papers, theses, or technical reports with mathematics\n- Creating reusable templates (letterheads, invoices, certificates, CVs)\n- Managing bibliographies (BibTeX\u002FBibLaTeX) at scale\n- Generating LaTeX documents programmatically from data\n- Debugging compilation errors and package conflicts\n\n## Core concepts\n\n**Structure with semantics.** `\\section`, `\\label`\u002F`\\ref`, `\\cite`, and\nenvironments (`theorem`, `figure`, `table`) — not manual numbering or\nhardcoded \"see page 12\". Semantic markup is what makes cross-references,\nTOCs, and bibliographies maintain themselves.\n\n**Preamble discipline.** Load packages once, in a sensible order, with a\ncommented preamble or a shared `.sty` file for projects. Package conflicts\n(fontenc\u002Finputenc ordering, hyperref loaded last-ish) cause the most\nmysterious errors; a curated preamble prevents them.\n\n**BibLaTeX + Biber for bibliographies.** The modern stack handles Unicode,\ncomplex entry types, and per-chapter bibliographies far better than legacy\nBibTeX. Keep one curated `.bib` file; use a reference manager or consistent\ncitation keys (`author:year:keyword`).\n\n**Compilation is a pipeline.** `pdflatex → biber → pdflatex → pdflatex` (or\n`latexmk`, which automates the dance). Build with `latexmk -pdf` and let it\nresolve the multi-pass requirements; in CI, pin the TeX distribution version\nfor reproducible builds.\n\n**Programmatic generation.** Templates with placeholders filled from data\n(CSV, JSON, databases) produce invoices, certificates, and reports with\ntypeset quality. Escape LaTeX special characters (`& % $ # _ { } ~ ^ \\`) in\ndata — unescaped input is the #1 generation bug.\n\n## Practical workflow\n\n1. **Start from a template** (article, report, beamer, or your org's class) —\n   don't build a preamble from scratch for each document.\n2. **Write with labels from day one:** `\\label{sec:method}` on everything\n   you'll reference; `\\cite{}` as you write, not at the end.\n3. **Manage figures properly:** vector formats (PDF) for plots and diagrams,\n   sensible DPI for raster images, `\\includegraphics` with relative widths,\n   captions that actually explain the figure.\n4. **For math:** `amsmath` environments (`align`, `gather`), numbered only\n   equations you'll reference; define macros for repeated notation\n   (`\\newcommand{\\R}{\\mathbb{R}}`).\n5. **Automate builds:** `latexmk` locally, CI job for the final artifact;\n   check in the `.tex`, `.bib`, and figures — never the generated PDF as\n   source of truth.\n6. **For generated documents:** template + data + escaping + a compile check\n   in the pipeline; render a sample and visually inspect before bulk runs.\n\n## Common pitfalls\n\n- **Ignoring compilation warnings** — undefined references and multiply\n  defined labels compound; fix them as they appear.\n- **Manual bibliography formatting** — hand-typed reference lists drift and\n  misformat; use BibLaTeX always.\n- **Special characters in generated content** — `%` in data comments out the\n  rest of the line; escape everything from untrusted data.\n- **Huge monolithic .tex files** — split chapters into `\\input` files; giant\n  files are unmergeable and slow to navigate.\n- **Package soup** — loading dozens of packages \"just in case\" invites\n  conflicts; load what you use, in documented order.\n- **Committing build artifacts** (`.aux`, `.log`, `.pdf`) — `.gitignore` them;\n  only sources and the build recipe belong in version control.\n",{"name":5,"category":24,"description":7},"document-processing","main","af388a77c2fe5e0b4fd879cca4300a0ffa9a6579","skills\u002Fams-latex-pro",1,"https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis","https:\u002F\u002Fgithub.com\u002FTanNhatCMS","https:\u002F\u002Fmrkiet.name.vn","2026-11-07 14:23:08",{"source":8,"skillName":5,"commands":34,"prompt":44,"zipAvailable":45},[35,38,41],{"tool":36,"command":37},"npx","npx skills add TanNhatCMS\u002Fjarvis --skill latex-pro",{"tool":39,"command":40},"bunx","bunx skills add TanNhatCMS\u002Fjarvis --skill latex-pro",{"tool":42,"command":43},"pnpm","pnpm dlx skills add TanNhatCMS\u002Fjarvis --skill latex-pro","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fams-latex-pro\u002FSKILL.md",true,[],[48,55,63,70,77,84],{"skillNo":49,"name":50,"nameZh":6,"description":51,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":52,"categories":53,"keywords":54,"publishedAt":19},"01M7EWYJR0J8DARY7E59Z6Y9MV","web-scrape","Turn web pages into LLM-ready markdown via the Firecrawl API (renders JS, anti-bot handling). Use when browser_open\u002Ffetch fails on JS-heavy pages, or when you need clean markdown\u002Fstructured extraction from a site. Requires FIRECRAWL_API_KEY.","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fweb-scrape\u002FSKILL.md",[],[],{"skillNo":56,"name":57,"nameZh":6,"description":58,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":59,"sourceHtmlUrl":60,"categories":61,"keywords":62,"publishedAt":19},"01M7EWYBN5P6F2AJG3FR24T9BP","design-taste-frontend","tasteskill v2, the anti-slop frontend skill. Art direction for websites, distilled from a study of 247 curated gallery sites (One Page Love, Awwwards Sites of the Day). Deals researched directions (idea, composition, type, palette, photographs, section blueprints) from a library, enforces a strict no-slop house style with a real-browser inspector, and runs a look-and-fix loop on screenshots. Use this whenever you build, design, redesign, restyle, polish or review a landing page, marketing site, portfolio, product page, one-pager, hero or any public-facing web page, in any stack (HTML\u002FCSS, React, Next.js, Vue, Svelte, Astro, Tailwind) — also when the user says a page looks generic, templated, \"AI-made\", sloppy, or asks to make it look designed, premium, award-level or less like every other site. Not for dashboards or app screens.","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Ftaste-design\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Ftaste-design\u002FSKILL.md",[],[],{"skillNo":64,"name":65,"nameZh":6,"description":66,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":67,"categories":68,"keywords":69,"publishedAt":19},"01M7EWY8FQFNQ2GB7NZZWGSSDX","test-driven-development","Use when implementing any feature or bugfix, before writing implementation code","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fsuperpowers-tdd\u002FSKILL.md",[],[],{"skillNo":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":19},"01M7EWY5SHBFRH1HDHVWM9K7TV","systematic-debugging","Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fsuperpowers-debugging\u002FSKILL.md",[],[],{"skillNo":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":19},"01M7EWY3NM0Z0JAKS7HDZ24K66","requesting-code-review","Use when completing tasks, implementing major features, or before merging to verify work meets requirements","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fsuperpowers-code-review\u002FSKILL.md",[],[],{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":19},"01M7EWY0WRMWX4M9ZFY0WKC593","brainstorming","You MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or planning anything new, in software or out of it (a talk, a business, a renovation).","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fsuperpowers-brainstorming\u002FSKILL.md",[],[]]