quarto-dev

@quarto-dev source repo

18 skills
0 followers
8 hours ago last updated

▌
Brand Yml · quarto-dev bundle
Create and use brand.yml files for consistent branding across Shiny apps and Quarto documents. Covers: (1) Creating new _brand.yml files, (2) Applying to Shiny (R and Python), (3) Using in Quarto, (4) Modifying existing files, and (5) Troubleshooting. Includes complete specifications and integration guides.

0
installs
▌
Testing R Packages · quarto-dev bundle
Best practices for writing R package tests using testthat version 3+. Use when writing, organizing, or improving tests for R packages. Covers test structure, expectations, fixtures, snapshots, mocking, and modern testthat 3 patterns including self-sufficient tests, proper cleanup with withr, and snapshot testing.

0
installs
▌
R Package Development · quarto-dev
R package development with devtools, testthat, and roxygen2. Use when the user is working on an R package, running tests, writing documentation, or building package infrastructure.

0
installs
▌
Quarto Blog Post · quarto-dev bundle
Use when writing, drafting, or editing Quarto blog posts, creating Quarto feature or release announcements, or reviewing Quarto blog post drafts. Quarto posts publish on the Posit Open Source blog (posit-dev/open-source-website), not on quarto.org.

0
installs
▌
Capturing Screenshots · quarto-dev bundle
Capture or update documentation screenshots for the Quarto website using Playwright. Use when screenshots need refreshing, new screenshots are needed for docs pages, or the user mentions screenshots, screen captures, or visual documentation.

0
installs
▌
Release Merge · quarto-dev bundle
Use when merging the quarto-web prerelease branch into main for a Quarto release (publishing new stable docs), or when a release-time merge hits conflicts, backport-action noise, or _freeze hook failures. Not for ordinary PRs to main.

0
installs
▌
Review Extension Prs · quarto-dev bundle
Use when asked to review open pull requests that add Quarto extensions to the listing YAML files in docs/extensions/listings/. Triggers include "review extension PRs", "check extension submissions", "are there new listing PRs", or any request to triage or verify community extension submissions before merge.

0
installs
▌
Braid · quarto-dev
Reference for braid, this project's issue tracker (the "skein" of "strands"). Use whenever you need braid command syntax — finding ready work, creating/updating/closing strands, dependencies, ready/blocked queries — or when a user mentions braid, a strand, or a bd- issue id and you need the authoritative, version-matched usage. The body defers to `braid agents-info` for the full guide.

0
installs
▌
Triage · quarto-dev bundle
Set up an isolated worktree and triage a GitHub issue into a durable on-branch record. Use when the user says "triage issue

0
installs
▌
Snyk Pr · quarto-dev bundle
Remediate a Snyk bot PR ([Snyk] Upgrade ..., author posit-snyk-bot, branch snyk-upgrade-*) so it goes green on CI and becomes mergeable. Use when the user asks to fix, unblock, or "make mergeable" a Snyk PR, mentions a red Snyk upgrade PR, or pastes a snyk-upgrade-* branch name. Invoke as /snyk-pr <PR#>; with no argument, list open posit-snyk-bot PRs and stop. Fixes the branch only — never weakens or skips the CI guard tests.

0
installs
▌
Ejs Listing Port · quarto-dev bundle
ejs-listing-port Skill

0
installs
▌
Investigate Beads · quarto-dev bundle
Investigate a braid strand (bd-XXXX issue) in the current checkout, gather context from its dependency graph, and produce a plan-skeleton + triage verdict (ready / needs-info / blocked). Use when the user provides a strand ID (bd-XXXX) and asks to investigate, scope, or understand the work needed.

0
installs
▌
Upgrade Cargo Deps · quarto-dev bundle
Survey the workspace for available Rust dependency upgrades, apply patch/minor bumps in an isolated worktree, run full `cargo xtask verify`, and produce a plan doc + per-major braid strands so the user can review and merge. Also reconciles previously-filed `Cargo:` upgrade strands against the current tree, closing ones that unrelated work already resolved. Use when the user says "upgrade cargo deps", "check for dependency upgrades", "do the bi-weekly cargo upgrade", asks about outdated dependencies, or asks whether existing `Cargo:` chore strands are still real. Runs on demand only — there is no schedule.

0
installs
▌
Preview Render Parity · quarto-dev
Diagnose and fix DOM / style differences between `q2 preview` and `q2 render` so the two pipelines produce visually-equivalent output. Use when the user reports that the preview's appearance, spacing, classes, or DOM structure doesn't match the rendered site — phrases like "preview vs render differs", "preview shows X differently", "spacing/margin/padding off", "DOM doesn't match", "missing class in preview", or shows a specific computed-style mismatch (e.g. "17px in preview, 34px in render"). Also invoked explicitly via `/preview-parity`.

0
installs
▌
Reader Expectations Prose · quarto-dev
Improve prose clarity using the reader-expectations methodology of Gopen & Swan ("The Science of Scientific Writing", American Scientist, Nov-Dec 1990). Use when the user asks for writing improvement, prose review, revision suggestions, help making writing clearer or more readable, feedback on a draft, or mentions clarity, flow, emphasis, sentence structure, or "why this passage is hard to read". Works on any expository prose (papers, reports, memos, docs, essays), not only scientific writing.

0
installs
▌
Investigate Issue · quarto-dev
Use when investigating a suspected quarto-cli bug — a document that renders incorrectly, an unexpected error, or behavior that changed between versions. Not for "how does X work" or general architecture questions.

0
installs
▌
Quarto Preview Test · quarto-dev bundle
Use when testing `quarto preview` behavior — verifying live reload, validating a preview-related bug fix, or running the manual preview test matrix by ID or topic.

0
installs
▌
Make Release · quarto-dev
Drive a Quarto release end-to-end from the dev-docs release checklists. Handles three release types — a routine dev prerelease off main, the first stable release of a new major.minor cycle, or a patch release on an existing stable branch — by asking which one applies (or reading it from an unambiguous request), then follows the matching checklist, verifying real git/gh state at each step and pausing for explicit human confirmation before every irreversible or externally-visible action.

0
installs

18 published skills