Create, edit, and troubleshoot Typst documents, a system for producing formatted documents from text files. Uses bundled documentation to check syntax and styling, with formatting checks and compilation when the required tools are available.
Generate idiomatic Typst (.typ) code, edit and troubleshoot Typst documents and projects, and answer Typst syntax/reference questions. Use when working with .typ files or when the user explicitly asks for Typst document creation, editing, debugging, compilation, formatting, template work, or package usage.
Review the instructions the agent will receive before you install.
This skill helps agents generate, edit, and reason about Typst documents. It provides quick‑start examples, detailed workflows, and links to the full Typst documentation (guides, tutorials, reference).
#set document(title: "My Document", author: "Author Name")
#set page(numbering: "1")
#set text(lang: "en")
// Enable paragraph justification and character-level justification
#set par(
justify: true,
justification-limits: (
tracking: (min: -0.012em, max: 0.012em),
spacing: (min: 75%, max: 120%),
)
)
#title[My Document]
= Heading 1
This is a paragraph in Typst.
== Heading 2
#lorem(50)
.typ file(s). After each .typ edit, follow the post-edit formatting checks below when typstyle is available..typ file, follow the post-edit formatting checks below.set rule, show rule, and custom themes.docs/reference/syntax.mddocs/reference/styling.mddocs/reference/scripting.mddocs/guides/page-setup.md and docs/guides/tables.mddocs/tutorial/writing-in-typst.md, docs/guides/*.md, and docs/reference/**/*.mddocs/ folder before generating code..typ source according to the user's request..typ file you created or edited in that pass.typst compile after the formatting decision is complete when you created or edited .typ files, or when the user explicitly asks for verification (if tool access is allowed)..typ content only when the user requests it or when direct editing is not possible, and optionally include a rendered preview (PDF/HTML)..typ files. Expose the value with metadata(...) <probe> and read it with typst query - "<probe>" --field value --one. See docs/reference/introspection/query.md and docs/reference/introspection/metadata.md.printf '#metadata(1 + 2) <probe>\n' | typst query - "<probe>" --field value --onetypstyle is available with command -v typstyle. If it is unavailable, skip the remaining formatting checks..typ file modification, run typstyle --check <file> for the file you just created or edited.typstyle --check fails, inspect the formatter changes with typstyle --diff <file> before deciding what to do.typstyle -i <file> only when the formatter changes are limited to a newly created file or to code you created or edited in the current task.(item1, item2) (parentheses). See docs/reference/foundations/array.md.(key: value, key2: value2) (parentheses with colons). See docs/reference/foundations/dictionary.md.[markup content] (square brackets). See docs/reference/foundations/content.md.# to start a code expression inside markup or content blocks; it disambiguates code from text. This is required for content-producing function calls and field access in markup: #figure[...], #image("file.png"), text(...)[#numbering(...)].# inside code contexts (argument lists, code blocks, show-rule bodies). Example: #figure(image("file.png")) (no # before image).// Incorrect (missing # inside content block)
text(...)[(numbering(...))]
// Correct
text(...)[(#numbering(...))]
set: Set rule to configure optional parameters on element functions (style defaults scoped to the current block or file).show: Show rule to target selected elements and apply a set rule or transform/replace the element output.set for common styling; use show for selective or structural changes (e.g., heading.where(level: 1), labels, text, regex).// Set rule: configure optional parameters for an element type
#set heading(numbering: "I.")
#set text(font: "New Computer Modern")
// Show-set rule: apply a set rule only to selected elements
#show heading: set text(navy)
// Show transform rule: replace/reshape element output
#show heading: it => block[#emph(it.body)]
[] for arrays (use () instead).arr[0] (use arr.at(0)).# in markup/content blocks (e.g., text(...)[numbering(...)] should be text(...)[#numbering(...)]).# inside code contexts (e.g., figure(#image("x.png")) in an argument list).[] with code blocks {}.color.hsl instead of just hsl).\begin{...}, \section, or other LaTeX commands).tabular does not exist; use table).When working on large projects, consider organizing the project across multiple files.
#include "file.typ" to split into multiple filesIf you see "unknown font family" warnings, remove the font specification to use system defaults. Note: Font warnings don't prevent compilation; the document will use fallback fonts.
If import fails with "package not found":
@preview/package:version syntax.Common fixes:
#{ } or use proper syntax.# (or #(...)) in markup/content blocks.() for both, dictionaries need key: value, singleton arrays are (elem,).No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Provides shared reference material for mathematical modeling competitions, covering writing conventions, problem-specific pitfalls, and chart guidelines. Other skills consult relevant sections during their work; this resource does not run independently.
Coordinates a mathematical modeling competition project from planning to final checks. It records formatting and language preferences, creates a plan and task checklist, and calls dedicated skills for modeling, coding, diagrams, paper writing, and verification.
Turns mathematical modeling competition problems and attachments into an implementation-ready report. It breaks down questions, examines ambiguous assumptions and data quality, and defines variables, equations, constraints, solution methods, and validation steps.
Implements mathematical models from a design report as reproducible code, runs calculations, and checks results. It records methods and validation findings in a results report and produces data-based PDF charts for papers.
Turn mathematical modeling reports into DrawIO diagrams showing solution steps, model structures, and data processing flows. Produce editable source files, export PDFs for papers when DrawIO is available, and record diagram choices and export results.
Write mathematical modeling competition papers from existing analysis reports, results, and figure PDFs. Use competition templates in Typst or LaTeX, tools for document layout, to organize sections, place figures, and prepare references and summaries.