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