pinit-workflow
Place, debug, and fix pinit annotations in Typst documents. ALWAYS use this skill when: writing any #pin(), #pinit-highlight, #pinit-point-from, #pinit-point-to, #pinit-place, or #pinit-line-to call; when an arrow, label, or annotation box is in the wrong place, overlapping text, outside the page, or pointing at nothing; when the user asks 'how do I annotate', 'how does pinit work', 'my arrow is wrong', 'my box is off-page', or 'how do I debug pinit'. Also use when the user asks about the debug module (dbg-pin, dbg-grid), Recipe A vs Recipe B vs Recipe C, coordinate reading, the AI correction loop, margin/sidebar annotations, absolute-place patterns, the pinit offset coordinate-system bug, or why offset-dx keeps drifting despite correct math. This skill supersedes general Typst layout advice whenever a @preview/pinit call is involved.
Works with
This skill's source license couldn't be confirmed as safe to mirror here, so it isn't inlined. View the full skill directly on its source repository.
View on GitHubMore Debugging skills
diagnosing-bugs
mattpocock/skills
Diagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose"/"debug this", or reports something broken/throwing/failing/slow.
explore-code
lllllllama/rigorpilot-skills
Rigor Improve implementation leaf skill for auditable candidate implementation in deep learning research repositories. Use when the researcher explicitly authorizes exploratory work on an isolated branch or worktree to transplant modules, adapt a backbone, add LoRA or adapter layers, replace a head, or stitch together meaningful low-risk migration ideas with rollback-aware records in `explore_outputs/`. Do not use for end-to-end exploration orchestration on top of `current_research`, trusted baseline reproduction, conservative debugging, environment setup, verified contribution claims, or default repository analysis.
safe-debug
lllllllama/rigorpilot-skills
Rigor Debug / Rigor Audit skill for deep learning research work. Use when the user pastes a traceback, terminal error, CUDA OOM, checkpoint load failure, shape mismatch, NaN loss symptom, or training failure and wants conservative diagnosis before any patching, with debug fixes clearly separated from research contributions. Do not use for broad refactoring, speculative adaptation, automatic exploratory patching, or general repository familiarization.
