Skip to content

1solomonwakhungu/typst-dev-container / skills/typst-devcontainer-pandoc-setup

typst-devcontainer-pandoc-setup

Verified

Sets up and verifies containerized Typst and Pandoc document environments using the published multi-architecture Docker image ghcr.io/1solomonwakhungu/typst-dev-container/typst. Use when setting up a Typst dev container or devcontainer, configuring VS Code Dev Containers or GitHub Codespaces, converting Markdown or LaTeX with Pandoc, compiling Typst to PDF, pinning reproducible document builds, or troubleshooting container image pulls and compiles.

Typst Dev Container

Use the published multi-architecture image from ghcr.io/1solomonwakhungu/typst-dev-container/typst. Keep changes scoped to the user's document project; do not replace an existing container setup without first inspecting it and accounting for its features, mounts, users, and editor settings.

Configure the workspace

  1. Inspect .devcontainer/devcontainer.json, any Compose files, and the project's existing build commands.
  2. If the project has no container configuration, add a minimal .devcontainer/devcontainer.json using the published image. Use latest when the user wants automatic toolchain updates. For a reproducible build, inspect the currently published tags and pin an explicit Typst version.
  3. Preserve unrelated customizations. For VS Code, recommend Tinymist for Typst language support; add other extensions only when the project needs them.
  4. Keep generated PDFs and intermediate files wherever the project already expects them. Do not invent a new output layout for an established project.

A minimal new configuration is:

{
  "name": "Typst + Pandoc",
  "image": "ghcr.io/1solomonwakhungu/typst-dev-container/typst:latest",
  "customizations": {
    "vscode": {
      "extensions": ["myriad-dreamin.tinymist"]
    }
  }
}

The image supports Linux amd64 and arm64. Do not add host-specific Typst, Pandoc, or Rust installations when the container already supplies them.

Work with documents

  • Compile once with typst compile input.typ output.pdf.
  • Watch during editing with typst watch input.typ output.pdf.
  • Convert Markdown to editable Typst with pandoc input.md --to typst --output output.typ, then compile the generated .typ file separately. Review the conversion rather than assuming Pandoc preserves every layout detail.
  • Preserve the document's existing fonts, package imports, bibliography paths, and output naming unless the user asks to change them.

Verify the result

Run these checks inside the container:

typst --version
pandoc --version
rustc --version
typst compile path/to/input.typ path/to/output.pdf
test -s path/to/output.pdf

For a new workspace, compile a tiny smoke-test document if no real .typ file exists. Report separately whether the container opened, the tool binaries ran, and the PDF compiled; one result does not prove the others.

Diagnose failures

  • An image-pull failure is a registry, authentication, tag, or platform issue. Check those before changing document source.
  • A missing binary after a successful pull usually means the wrong image or tag is running. Confirm the container image from inside the active workspace.
  • A Typst compile error is a document or resource-path issue unless the same minimal document also fails.
  • When latest changes behavior, reproduce with an explicit version tag before editing the project.

The source, supported version matrix, and architecture mapping live at https://github.com/1solomonwakhungu/typst-dev-container.

writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deploymentStars: 319kUpdated Claude CodeCodexVerifiedInstall
xlsxanthropics/skillsUse this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .xltx, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved.Stars: 197kUpdated Claude CodeCodexVerifiedInstall
shipping-and-launchaddyosmani/agent-skillsPrepares production launches. Use when preparing to deploy to production, or when asking what needs to be in place before shipping. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy.Stars: 118kUpdated Claude CodeCodexVerifiedInstall
childhoodthedotmack/claude-memBabysit a shipped release after merge, publication, or deployment. Verify published packages, production behavior, installed plugins, and late CI or user reports until the observation window is clean; use babysit for PR readiness before release.Stars: 118kUpdated Claude CodeCodexVerifiedInstall