mcpField
V
visual-audit

visual-audit

github.com/pedrohcgsDesign & UI1.7k53 installsUpdated 4w ago
Repository

About visual-audit

visual-audit is a skill for reviewing slide decks for visual and layout issues. It renders Quarto or Beamer files, checks for overflow and consistency, and produces slide-by-slide recommendations.

Key features

  1. 01Render Quarto slide decks
  2. 02Compile Beamer presentations
  3. 03Check overflow and broken assets
  4. 04Review layout, fonts, and spacing
  5. 05Produce severity-ranked recommendations

Use cases

  1. 01Checking slides before publication
  2. 02Finding overflow in rendered slides
  3. 03Reviewing dense slides and figures
  4. 04Preparing prioritized layout fixes

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/pedrohcgs/claude-code-my-workflow --skill visual-audit

After installing, type/visual-auditin Claude Code to confirm it loaded.

Details

From the project README

Visual Audit of Slide Deck

Perform a thorough visual layout audit of a slide deck.

Steps

  1. Read the slide file specified in $ARGUMENTS

  2. For Quarto (.qmd) files:

    • Render with quarto render Quarto/$ARGUMENTS
    • Measure the render: "${SLIDE_QA_PYTHON:-python3}" scripts/slide-qa.py Quarto/<deck>.html. It loads the deck in headless Chrome with every fragment shown and writes quality_reports/audits/slide-qa/<deck>/report.md — per-slide pixels past each edge, the offending element, content hidden inside scrolling elements — plus one screenshot per slide, and broken images or local files whose path is missing or in the wrong letter case (these break on GitHub Pages). OVERFLOW findings come from this report, and a broken or wrong-case asset is a finding too; Read the screenshots of flagged and dense slides for the other checks.
    • If it exits 2 (usually Playwright is missing — the script prints the one-time venv install and the SLIDE_QA_PYTHON line to set), say so, fall back to reading the rendered HTML of the dense slides and any screenshot the user supplies, and name the slides the user should eyeball
  3. For Beamer (.tex) files:

    • Compile (see /compile-latex), check the log for overfull hbox warnings, and Read the PDF pages that carry figures or dense content
  4. Audit every slide for:

    OVERFLOW: Content exceeding slide boundaries FONT CONSISTENCY: Inline font-size overrides, inconsistent sizes BOX FATIGUE: 3+ colored boxes on one slide (INV-7 allows two), wrong box types SPACING: Missing negative margins, missing fig-align LAYOUT: Missing transitions, missing framing sentences, semantic colors

  5. Produce a report organized by slide with severity and recommendations

  6. Follow the spacing-first principle:

    1. Reduce vertical spacing with negative margins
    2. Consolidate lists
    3. Move displayed equations inline
    4. Reduce image/SVG size
    5. Last resort: font size reduction (never below 0.85em)

Comments

Markdown supported