agentleFS
Sign inStart free
podopodo/design-agent-skills/skills/cc-slidev/SKILL.md

cc-slidev

Skill32 starsChanged 6 months agoMITView on GitHub

Claude Code plugin and skills for creating developer-focused technical presentations (tech talks, conference content) with Slidev, with evidence-based design guardrails for slide quality. Adds opinionated constraints on top of raw Slidev for presentation polish.

  • Installs packages

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    When raw Slidev flexibility is preferred over guardrails — use slidev-skill instead

    line 78

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

cc-slidev

Catalogue stub — full package: rhuss/cc-slidev

<!-- das:install:start — generated from stub.yaml by `npm run generate`; edit stub.yaml, not this block -->

Decision tree

  1. Is the full skill already installed? This package installs 6 skills (slidev-mastery, presentation-design, slide-quality-assessment, visual-design, excalidraw-generation, latex-handouts); checking the first.
    • Global: f=~/.agents/skills/slidev-mastery/SKILL.md; [ -f "$f" ] && ! grep -q "^das:" "$f" && echo "installed" || echo "pointer"
    • Project: f=.agents/skills/slidev-mastery/SKILL.md; [ -f "$f" ] && ! grep -q "^das:" "$f" && echo "installed" || echo "pointer"
    • installed → the skill is installed as slidev-mastery, invoke it and proceed
    • pointer → go to step 2

  2. Detect scope, then install:

    [ -e ~/.agents/skills/cc-slidev ] && echo "global" || echo "project"

    Global:

    npx skills add rhuss/cc-slidev --skill "Slidev Mastery" "Presentation Design" "Slide Quality Assessment" "Visual Design" "Excalidraw Generation" "LaTeX Handouts" -g -y

    Project:

    npx skills add rhuss/cc-slidev --skill "Slidev Mastery" "Presentation Design" "Slide Quality Assessment" "Visual Design" "Excalidraw Generation" "LaTeX Handouts" -y

    Claude Code: send a command as a chat message starting with ! to run it without leaving the conversation.

Claude Code plugin route:

/plugin marketplace add rhuss/cc-slidev
/plugin install slidev@slidev-dev-marketplace

Heads-up

  • Requires: Slidev CLI (npm install -g @slidev/cli) and Node.js 18+; Optional: LaTeX (pdflatex) for handouts, mermaid-cli for offline diagram rendering
  • License: MIT
<!-- das:install:end -->

Invoke after install

  • Skills (every install route): Slidev Mastery (installed as slidev-mastery), Presentation Design, Slide Quality Assessment, Visual Design, Excalidraw Generation, LaTeX Handouts
  • Slash commands (Claude Code plugin route only): /slidev:init <topic> runs the guided end-to-end workflow; or use the phases one by one: /slidev:frame, /slidev:brainstorm, /slidev:outline, /slidev:generate, /slidev:visuals, /slidev:notes, /slidev:handout, /slidev:export <format>
  • Trigger phrases: "cc-slidev", "conference slides", "tech talk slides", "rhuss slidev"

What it does

A Claude Code plugin that wraps Slidev for technical conference and developer talk slide creation. Adds evidence-based design guardrails (limits on elements and body text per slide, assertion titles, minimum font size and contrast, colorblind-safe palettes) on top of Slidev's flexible Markdown format, and covers the workflow from framing and outline to modular slide generation, diagrams, presenter notes, LaTeX handouts and export.

The npx skills add route installs the six skills that the CLI can read, without the slash commands. Two further upstream skills (diagram-design and slide-management) have frontmatter the CLI cannot parse, so it skips them.

When NOT to use

  • Non-technical presentations where the constraints would be limiting
  • When raw Slidev flexibility is preferred over guardrails — use slidev-skill instead
  • Marp output — use marp-slides instead
  • Reveal.js output — use revealjs-skill instead

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free