explainx.ainewsletter3.4k
Productivity

typst▌

lucifer1004/claude-skill-typst · updated Apr 8, 2026

MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.

$npx skills add https://github.com/lucifer1004/claude-skill-typst --skill typst
0 commentsdiscussion
summary

Modern typesetting system — simpler than LaTeX, faster compilation, programmable.

skill.md

Typst

Modern typesetting system — simpler than LaTeX, faster compilation, programmable.

Compilation

typst compile document.typ              # compile once
typst compile document.typ output.pdf   # explicit output path
typst compile src/main.typ --root .     # set project root for /path imports
typst watch document.typ                # recompile on change

Agents cannot preview PDFs. Verify via exit code and pdftotext:

typst compile document.typ && pdftotext document.pdf - | head -20

Minimal Document

#set page(paper: "a4", margin: 2cm)
#set text(size: 11pt)

= Title

Content goes here.

Writing Documents

When you need to... Read
Learn syntax, imports, functions, control flow basics.md
Learn data types, operators, string/array methods types.md
Style pages, headings, figures, layout styling.md
Tables, grids, cell spans, borders, data tables tables.md
Academic papers, bibliography, theorems, equations academic.md
Convert from Markdown or LaTeX conversion.md

Start with basics.md — it covers modes, imports, functions, control flow, and common pitfalls. For data types and operators, see types.md.

Developing Packages and Templates

When you need to... Read
Use state, context, query, or parse XML advanced.md
Create a reusable template function template.md
Create or publish a package package.md
Debug output (pdftotext, repr, measure) debug.md
Profile performance (--timings, hotspots) perf.md

basics.md and types.md are also the foundation for developers.

Finding Packages

Search the embedded index of Typst Universe packages (updated weekly):

python3 scripts/search-packages.py "what you need"
python3 scripts/search-packages.py "chart" --category visualization
python3 scripts/search-packages.py --category cv --top 5
python3 scripts/search-packages.py --list-categories

Import Pattern

#import "@preview/package-name:version": *
#import "@preview/package-name:version": specific-func

Common Errors

Error Cause Fix
"unknown variable" Undefined identifier Check spelling, ensure #let before use
"expected X, found Y" Type mismatch Check function signature in docs
"file not found" Bad import path Paths resolve relative to current file
"unknown font" Font not installed Use system fonts or web-safe alternatives
"maximum function call depth exceeded" Deep recursion Use iteration instead
"can only be used when context is known" Missing context wrapper Wrap in context { ... }
"unexpected argument" = instead of : for args Named args use : syntax: func(name: value)
"variables from outside are read-only" Mutating captured variable Use loop accumulation or state() — see advanced.md
"expected content, found string" (or vice versa) Content/string type mismatch Use [#str-var] to embed string in content
set/show rule has no effect Rule placed after content Place set/show rules before the content they target

Examples

Example Description
basic-document.typ Complete beginner document with all common elements
styled-document.typ Set/show rules, page layout, multi-region document
template-report.typ Reusable template with headers, counters, note boxes
tables-showcase.typ Table features: spans, stripes, grids, data gen
academic-paper.typ Paper with theorems, equations, bibliography layout
package-example/ Minimal publishable package with submodules

Dependencies

  • typst CLI: Install from https://typst.app or via package manager
    • macOS: brew install typst
    • Linux: cargo install typst-cli
    • Windows: winget install typst
  • pdftotext (optional): For text-level output verification
  • Python 3.10+ (optional): For package search and validation scripts
how to use typst

How to use typst on Cursor

AI-first code editor with Composer

1

Prerequisites

Before installing skills in Cursor, ensure your development environment meets these requirements:

  • ›Cursor installed and configured on your development machine
  • ›Node.js version 16.0+ with npm package manager (verify with node --version)
  • ›Active project directory or workspace where you want to add typst
2

Execute installation command

Execute the skills CLI command in your project's root directory to begin installation:

$npx skills add https://github.com/lucifer1004/claude-skill-typst --skill typst

The skills CLI fetches typst from GitHub repository lucifer1004/claude-skill-typst and configures it for Cursor.

3

Select Cursor when prompted

The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:

◆ Which agents do you want to install to?
│
│ ── Universal (.agents/skills) ── always included ────
│ • Amp
│ • Antigravity
│ • Cline
│ • Codex
│ ●Cursor(selected)
│ • Cursor
│ • Windsurf
4

Verify installation

Confirm successful installation by checking the skill directory location:

.cursor/skills/typst

Reload or restart Cursor to activate typst. Access the skill through slash commands (e.g., /typst) or your agent's skill management interface.

⚠

Security & Verification Notice

We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.

Skills execute code in your development environment. Always verify the publisher's identity, review recent commits, and test in isolated environments before production deployment.

Additional Resources

›View source code on GitHub›Skills CLI documentation›Learn more about Cursor›What are agent skills?

List & Monetize Your Skill

Submit your Claude Code skill and start earning

GET_STARTED →

Use Cases▌

User Story & Requirements Generation

Create detailed user stories, acceptance criteria, and feature specs

Example

Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios

✓

Reduce spec writing time by 50%, ensure comprehensive coverage

Competitive Analysis

Research competitors, compare features, identify gaps

Example

Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities

✓

Complete competitive research in 2 hours instead of 2 days

Roadmap Prioritization

Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs

Example

Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale

✓

Make data-driven prioritization decisions faster

Stakeholder Communication

Draft PRDs, status updates, and stakeholder presentations

Example

Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement

✓

Save 3-5 hours/week on communication overhead

Implementation Guide▌

Prerequisites

  • ›Claude Desktop or compatible AI client
  • ›Access to product documentation and roadmap tools (Jira, Notion, etc.)
  • ›Understanding of product management frameworks (RICE, Jobs-to-be-Done, etc.)
  • ›Stakeholder contact information and communication channels

Time Estimate

30-60 minutes to see productivity improvements

Installation Steps

  1. 1.Install product management skill
  2. 2.Start with user story generation for known feature
  3. 3.Progress to competitive analysis: research 2-3 competitors
  4. 4.Use for roadmap prioritization: apply RICE/ICE scoring
  5. 5.Draft stakeholder communications and refine based on feedback
  6. 6.Build template library for recurring PM tasks
  7. 7.Share effective prompts with product team

Common Pitfalls

  • ⚠Not validating competitive research—verify facts before sharing
  • ⚠Accepting user stories without involving engineering team
  • ⚠Over-relying on frameworks without qualitative judgment
  • ⚠Not customizing outputs to company culture and communication style
  • ⚠Skipping stakeholder validation of generated requirements

Best Practices▌

✓ Do

  • +Validate research and competitive analysis with real data
  • +Collaborate with engineering when generating technical requirements
  • +Customize frameworks and templates to your company context
  • +Use skill for first drafts, refine with stakeholder input
  • +Document successful prompt patterns for PM tasks
  • +Combine AI efficiency with human judgment and intuition

✗ Don't

  • −Don't publish competitive analysis without fact-checking
  • −Don't finalize user stories without engineering review
  • −Don't make prioritization decisions solely on AI scoring
  • −Don't skip customer validation of generated requirements
  • −Don't ignore company-specific context and culture

💡 Pro Tips

  • ★Provide context: company goals, constraints, customer feedback
  • ★Ask for alternatives: 'Show 3 ways to prioritize this roadmap'
  • ★Request stakeholder-specific formatting: 'Executive summary vs. engineering spec'
  • ★Use skill for 70% generation + 30% customization to company needs

When to Use This▌

✓ Use When

Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.

✗ Avoid When

Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.

Learning Path▌

  1. 1Basic: user stories, feature specs, status updates
  2. 2Intermediate: competitive analysis, prioritization frameworks, PRDs
  3. 3Advanced: product strategy, go-to-market planning, OKR setting
  4. 4Expert: product vision, market positioning, business model innovation

Discussion

Product Hunt–style comments (not star reviews)
  • No comments yet — start the thread.
general reviews

Ratings

4.8★★★★★43 reviews
  • ★★★★★Omar Choi· Dec 20, 2024

    typst is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.

  • ★★★★★Shikha Mishra· Dec 16, 2024

    We added typst from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.

  • ★★★★★Carlos Ndlovu· Dec 16, 2024

    typst has been reliable in day-to-day use. Documentation quality is above average for community skills.

  • ★★★★★Advait Harris· Dec 4, 2024

    typst fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.

  • ★★★★★Omar Perez· Nov 11, 2024

    Keeps context tight: typst is the kind of skill you can hand to a new teammate without a long onboarding doc.

  • ★★★★★Yash Thakker· Nov 7, 2024

    typst reduced setup friction for our internal harness; good balance of opinion and flexibility.

  • ★★★★★Dhruvi Jain· Oct 26, 2024

    typst is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.

  • ★★★★★Soo Haddad· Oct 2, 2024

    We added typst from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.

  • ★★★★★Isabella Lopez· Sep 25, 2024

    typst is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.

  • ★★★★★Advait Malhotra· Sep 13, 2024

    We added typst from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.

showing 1-10 of 43

1 / 5