Claude Skills by lfurze

Claude Code Skills

A collection of reusable Claude Code skills for common workflows.

What are skills?

Skills are markdown files that teach Claude Code how to perform specific tasks. When you invoke a skill (via /skill-name or by describing what you want), Claude follows the instructions in the skill file — including architecture decisions, code patterns, and step-by-step workflows.

Think of them as reusable prompts with deep context: not just "build me a website" but "build me a website this way, with these patterns, following these conventions."

Available Skills

Skill	Description
astro-website	Build multi-page static websites from content (markdown, PDFs, eBooks) using Astro 5, deployed to Cloudflare Pages
book-editor	Professional book and manuscript editing with Word track changes — multi-pass editing (structural, line, copy, polish) for .docx files
claude-code-video-transcription	Analyse video files by extracting timestamped frames and Whisper transcripts, then producing structured analysis documents

How to Install a Skill

Copy the skill folder into your Claude Code skills directory:

# Copy a skill into your global skills directory
cp -r astro-website ~/.claude/skills/

# Or clone the whole repo and symlink what you want
git clone https://github.com/lfurze/claude-skills.git
ln -s "$(pwd)/claude-skills/astro-website" ~/.claude/skills/astro-website

Some skills require a specific folder name — check the skill's own README for details. For example, claude-code-video-transcription must be installed as ~/.claude/skills/video-analyse/.

Each skill folder contains:

• SKILL.md — the main skill definition (instructions, workflow, architecture)
• references/ — (optional) supporting files the skill reads during execution (design tokens, component patterns, templates)

Some skills also include scripts and dependencies (e.g. Python scripts, requirements.txt).

Customisation

These skills are designed to be forked and adapted. Look for [square brackets] in the files — these mark values you should replace with your own (domain names, author info, form IDs, etc.).

The design system and component patterns reflect one particular aesthetic ("barely-there UI" with glass borders, fluid typography, dark mode). Feel free to rip these out and substitute your own.

License

MIT