Dan Vega’s Skills

My agent skills for everyday development, Spring, and the workflows behind danvega.dev, my YouTube channel, and Spring Office Hours.

These capture choices, conventions, and lessons I want an agent to carry into the next task. Start with dev for everyday work or shipit for building a demo or product. The content workflows are tailored to my setup and can serve as examples to adapt.

Use a skill

Clone the repo and enter it:

git clone https://github.com/danvega/skills.git
cd skills

For Claude Code, link the skill folders you want into your personal skills directory:

mkdir -p "$HOME/.claude/skills"
ln -s "$PWD/skills/dev/readme" "$HOME/.claude/skills/readme"

The link points to this checkout, so edits and pulled updates are available through it. Keep the checkout at the same path. If readme is already installed, check its location before replacing it.

To copy instead of linking, use this command in place of ln -s:

cp -R skills/dev/readme "$HOME/.claude/skills/"

Replace skills/dev/readme with another skill folder to install it. Copy the entire folder so its scripts, references, and assets come with it. For a project-only skill, use that project’s .claude/skills/ directory instead.

Once installed, invoke it by name, such as /readme, or describe a task that matches its description. See the Claude Code skills documentation for discovery and configuration. Other agents may use a different skill directory.

What’s here

dev

General development skills with plain language and short instructions.

• readme: write a README for a demo, library, CLI, or product, checked against the code

shipit

A process for new demos, small tools, and products: decide enough to start, build something you can verify, then review and update. PRODUCT.md holds current scope and decisions. Supporting files hold work and history, and are created only when useful.

The skills are not seven required stages. See the shipit guide for the flow and examples of where to start.

• shipit-shape: clarify an idea and find the smallest useful version
• shipit-mvp: create a short initial PRODUCT.md and refine it as the project takes shape
• shipit-stack: resolve material technical choices and record their reasons
• shipit-prototype: explore an uncertain screen or interaction when a prototype would help
• shipit-verify: reuse or add checks, separating verified behavior from evidence awaiting review
• shipit-feature: build within scope, check the result, and batch review
• shipit-retro: use evidence from a run to propose a focused process improvement

spring

Focused guidance for Spring Boot 4 migrations, under skills/spring/spring-boot-4/.

• jackson-3: Jackson 3 migration, JSON configuration, and changed defaults
• modular-auto-config: modular auto-configuration and missing starter dependencies

blog

The workflow behind danvega.dev, from choosing a topic to preparing a post and cover.

• blog-seo-opportunities: rank topics and improvements using Search Console evidence
• blog-new-post: scaffold and draft a post with the site’s frontmatter and writing style
• blog-seo-optimize: research keywords and improve an existing post
• blog-cover: render the site’s terminal-style cover image

newsletter

• newsletter-publish: republish a Beehiiv edition on the site with its links, images, and formatting

podcast

The Spring Office Hours episode workflow.

• spring-office-hours-prep: run the audio edit and show-notes steps for one episode
• spring-office-hours-edit: edit a recording into a podcast MP3 and transcript
• spring-office-hours-show-notes: assemble the episode title, description, and resource links
• spring-office-hours-spring-io-pr: prepare the spring.io post and PR after the episode is published on Transistor

video

The YouTube edit pipeline, from raw recordings to a Premiere timeline. These skills call the vedit tool in my video-editor project, so they need that project installed.

• video-edit: run the whole edit pipeline from raw recordings to the Premiere XML
• video-project: create a new video project folder from the template
• video-transcribe: transcribe recordings locally with parakeet-mlx, or transcribe a finished export for publishing
• video-rough-cut: remove dead air, fillers, and retakes, with a review page before rendering
• video-zoom: add punch-ins and slow pushes centered on my face
• video-motion-graphics: add lower thirds, list reveals, link popups, and icon pops
• video-broll-research: find cited sources and show them with a highlighter sweep
• video-sfx: add sound effects timed to the graphics
• video-music: add a ducked background music bed from Epidemic Sound
• video-x-clips: cut 1 to 3 clips for X with ready-to-paste post copy

Adapt these to your setup

The dev and shipit skills can work with the conventions and tools in your project. The Spring skills provide guidance for their stated framework versions.

The blog, newsletter, podcast, and video workflows include my paths, branding, and publishing conventions. Some rely on Search Console, Figma, local site repos, or media tools such as Node.js, ffmpeg, and transcription software. Read the selected skill’s prerequisites and replace personal paths and account details before using it. Copying a skill does not install its tools or connect its accounts.

Maintain the collection

Keep name and description valid in each skill’s YAML frontmatter, and keep this catalog aligned with the folders in skills/. See CLAUDE.md for authoring conventions.

License

Original material is licensed under MIT.