typst-author
Author idiomatic, compilable Typst documents. Use when creating or editing Typst (.typ) files, when a task involves Typst syntax, packages, templates, or bibliographies, or when a Typst build fails and the error needs a fix.
- License 许可
- MIT
- 所属仓库
- hadronomy/skills
- 最近更新
- 2026-10-08
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- typst-author
- description
- Author idiomatic, compilable Typst documents. Use when creating or editing Typst (.typ) files, when a task involves Typst syntax, packages, templates, or bibliographies, or when a Typst build fails and the error needs a fix.
- compatibility
- Requires typst 0.15.x, typstyle, and tinymist on PATH. Needs network on the first fetch of a new package.
02 资源文件 3
- 参考文档references/bibliography.md788 B
- 参考文档references/packages.md1.3 KB
- 参考文档references/syntax-traps.md1.5 KB
03 SKILL.md 正文
Typst author
Contract: every .typ file left behind compiles with a clean format check. The loop is compile-verify: compile on every edit, read the diagnostics, fix, recompile. Never finish on "the code looks right".
Preflight
Run once per task, before any edit:
command -v typst && typst --version
Expect typst 0.15.x. If the shim fails, stop and fix the toolchain first. Nothing below works without a compiler.
Workflow
- Write or edit the
.typfile, following the reference that matches the task (table below). - Run
typst compile main.typ --diagnostic-format short. The flag prints one diagnostic per line for easy parsing. - If diagnostics appear, fix them and recompile. Repeat until the exit code is 0.
- Run
typstyle --check main.typ. If it reports drift, runtypstyle -i main.typand recompile. - Verify content, not just exit codes: export
typst compile main.typ out.pdfand confirm the pages hold what the task asked for. For text checks, export HTML (-f html) and read it.
Done means: exit code 0, typstyle clean, and the output holds the requested content.
Task map
| Task | Reach |
|---|---|
Syntax traps (arrays, content blocks, context, set vs show) |
references/syntax-traps.md |
Packages (find, pin, init, local overrides) |
references/packages.md |
| Bibliography and citations | references/bibliography.md |
Material every run needs stays above. Material only some runs reach lives behind those links.
04 同仓库更多 Skills
windows-mcp
Driving the Windows desktop on `workstation` through the windows MCP server. Use before any `mcp__windows__` tool, when a desktop call blocks or returns "Desktop busy", when Snapshot or Screenshot come back empty, or when this agent has no desktop tools and the task needs them.
setup-hadronomy
暂无简介
rust-craft
Craft production Rust the way the top toolchain teams do. Use when writing, reviewing, or restructuring Rust — workspace layout, Cargo manifests, lints, and profiles; type, trait, and error API design; performance, allocation, and profiling work; async and concurrency; CLI construction; test, snapshot, and benchmark suites; crate selection; release, semver, MSRV, and feature flags.
pr-craft
Write pull requests a reviewer can act on. Use when opening, rewriting, or reviewing the body of a pull request — title and description, the problem and approach, call-stack diffs, before-and-after screenshots, verification steps, risks, a review guide, and the tools that produce each part.
effect-craft
Craft Effect TypeScript APIs with the discipline of the Effect and opencode codebases. Use when modeling data with Schema, building services with Context and Layer, naming operations with Effect.fn, exposing modules through barrels, designing hooks or HTTP surfaces, or writing JSDoc with runnable examples — new code, refactors, and API reviews.
docs-craft
Documentation discipline for code comments, API docs, and docs pages. Use when writing or reviewing doc comments, JSDoc or rustdoc, README sections, or framework docs pages — or when comments and docs read as filler and need cutting.