Skip to content

pedrohcgs/claude-code-my-workflow / .claude/skills/deploy

deploy

Verified

Render Quarto `.qmd` slides to HTML and sync to `docs/` for GitHub Pages. Use when user says "deploy", "publish the slides", "ship to pages", "push the lecture live", "render and publish", or after Quarto edits that need to go public. NOT for local Quarto render only — use `quarto render` directly for that.

Deploy Slides to GitHub Pages

Render Quarto slides and sync all files to docs/ for GitHub Pages deployment.

Steps

  1. Run the sync script:

    • If $ARGUMENTS is provided (e.g., "Lecture4"): ./scripts/sync_to_docs.sh "$ARGUMENTS"
    • If no argument: ./scripts/sync_to_docs.sh (syncs all lectures)
  2. Verify deployment:

    • Check that HTML files exist in docs/slides/
    • Check that _files/ directories were copied (RevealJS assets)
    • Check that docs/Figures/ was synced from Figures/
    • Check that docs/files/code/ contains the R scripts (if scripts/R/ has any)
  3. Verify interactive charts (if applicable):

    • Grep rendered HTML for interactive widget count
    • Confirm count matches expected
  4. Verify TikZ SVGs (if applicable):

    • Check that all referenced SVG files exist in docs/Figures/LectureN/
  5. Open in browser for visual verification:

    • open docs/slides/LectureX_Name.html # macOS
    • # xdg-open docs/slides/LectureX_Name.html # Linux
    • Confirm slides render, images display, navigation works
  6. Report results to the user

What the sync script does:

  • Renders all .qmd files in Quarto/ (skips *_backup* files)
  • Copies HTML and _files/ directories to docs/slides/
  • Copies Beamer PDFs from Slides/ to docs/slides/
  • Syncs Figures/ to docs/Figures/ using rsync
  • Copies every scripts/R/*.R into docs/files/code/ (published beside the slides)
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: 196kUpdated 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