dotfiles

Add beui-style loading animations (spinner, bouncing dots, bars, dot-matrix, dither, terminal/ascii spinners, shape morph, comet, scramble text, metaballs, newton's cradle, helix, percent counter) to any project as vanilla HTML/CSS/JS — no React, no build step, no dependency. Use this skill whenever the user wants a loader, spinner, loading indicator, progress animation, or "loading..." state in a non-React project — server-rendered templates (Go, Rails, Django, Flask/Jinja, PHP), HTMX, Web Components, static HTML, or plain JS apps — even if they don't mention beui by name. Also use it when the user asks to port or copy a beui motion component.

Audit a codebase for health issues — oversized files, duplicated logic, dead code, unused parameters, test coverage gaps, and documentation/config drift — and report findings ordered by severity. Use this skill whenever the user invokes "/check-code-health", asks about "code health", "tech debt", "code quality audit", "find dead code", "what needs cleanup", or wants a maintenance overview of the repo.

Update project dependencies safely — list outdated packages, upgrade minors/patches in bulk and majors individually with changelog review, verify with build and tests, and commit in clean chore(deps) commits. Use this skill whenever the user says "update dependencies", "upgrade deps", "bump packages", "are my dependencies outdated", "update to the latest version of X", or mentions dependabot/renovate-style maintenance. Not for adding a brand-new dependency.

Diagnose and fix a bug or GitHub issue with test-backed verification — reproduce, root-cause, fix, and guard with a red-green or regression test so it can't silently return. Use this skill whenever the user says "fix this bug", "there's a bug in", "this is broken", "fix issue

Get a failing build back to green — run the project's build, test, and lint commands, then fix every reported compile error, test failure, and lint violation until all pass. Use this skill whenever the user invokes "/fix-build", says "the build is broken", "fix the build", "it doesn't compile", "CI is red", "make the tests pass", or pastes build/compiler errors asking for them to be resolved.

Generate or update CLAUDE.md for a codebase the thorough way — discover architecture, workflows, and project-specific conventions, merge with existing AI-agent instruction files, and iterate with the user. Use this skill whenever the user invokes "/initialise", says "set up CLAUDE.md", "update the CLAUDE.md", "initialise this repo for Claude", or wants AI-agent onboarding docs written for a project. Prefer this over the built-in /init when the user asks for the fancy/thorough version.

Analyze a GitHub issue and write an implementation plan into the issue itself — without implementing anything. Use this skill whenever the user invokes "/plan-github-issue", says "plan issue

Cut a release from Conventional Commits history — generate or update the changelog, decide the semver bump, update version files, and create an annotated git tag. Use this skill whenever the user says "cut a release", "make a release", "prepare a release", "bump the version", "tag a version", "update the changelog", or asks "what should the next version be". Also use it when the user names a specific version to release ("release v1.4.0").

Write or extend automated tests for existing code — unit, integration, or regression — matching the project's test framework and conventions, then run them until green. Use this skill whenever the user says "write tests", "add tests", "test this", "add coverage", "this needs tests", names a file or function to test, or has just finished implementing something and wants it covered. Not for fixing bugs (use fix-bug) or running an app manually (use verify).

Create atomic git commits using Conventional Commits. Use this skill when the user invokes "/commit", says "commit this", "make a commit", "commit my changes", "split into commits", or otherwise asks to stage and commit pending git changes. Delegates the actual commit work to a Haiku or Sonnet subagent depending on diff complexity to keep the main loop fast and cheap.

This skill should be used when the user invokes "/whereami" or asks "where am I", "what's the state of this repo", "what was I working on", "remind me what this project is", or wants a quick project-state recap. Summarizes purpose, git state, recent commits, and likely next step.

Use this skill when creating Python scripts that use PEP 723 inline script metadata with uv, or when the user asks to "write a uv script", "create a standalone Python script with dependencies", "make a script that runs with uv run", or wants a self-contained Python script with automatic dependency management.

Create unique, visually appealing frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, or applications. Generates creative, polished code that avoids generic AI aesthetics.

Use uv and PEP 723 to write self-installing autocontained Python scripts