Skills
Agent skills I maintain — reusable instruction sets that encode my development workflows, conventions, and best practices. Pulled from urmzd/dotfiles.
AI & Agents
AI Workflows
AI tools, Claude Code configuration, sr commits, AGENTS.md standard, skills-as-docs philosophy, and llms.txt. Use when setting up AI tooling, configuring projects for AI, or working with agent skills.
configure-aiCreate llms.txt
Generate a spec-compliant llms.txt file for any project by analyzing its codebase, docs, and public URLs. Use when creating an llms.txt, making a project LLM-discoverable, or when the user mentions "llms.txt" in the context of generating or scaffolding one.
create-llms-txtCreate OSS Skill
Create well-formed Agent Skills following the agentskills.io specification — scaffold directories, write SKILL.md files, bundle scripts, and structure instructions for progressive disclosure. Use when creating a new skill, reviewing skill structure, optimizing a skill description, or setting up evals for skill quality.
create-oss-skillExtend OSS Skills to Claude
Extend standard agentskills.io skills with Claude Code-specific features — invocation control, subagent execution, dynamic context injection, string substitutions, model/effort overrides, and deployment scoping. Use when adapting a portable skill for Claude Code, adding Claude-specific frontmatter, setting up subagent delegation, or configuring skill permissions.
extend-oss-skills-to-claudeCLI & DevEnv
Development
CI/CD Standards
CI/CD conventions — ci.yml + release.yml naming, concurrency, bot skip, embed-src/teasr steps, and workflow structure. Language-specific pipelines live in scaffold-rust, scaffold-go, scaffold-python, scaffold-node, scaffold-terraform. Use when setting up GitHub Actions or understanding CI conventions.
setup-ciCLI Patterns
CLI conventions — output modes, TTY detection, JSON piping, stdout/stderr separation, interactivity, signal handling, visual style, and CI integration. Use when building or reviewing any CLI tool.
build-cliCode Quality
Code quality assessment — readability, onboarding ease, scalability without bloat, brand coherence across projects, and intentional design for developers and AI agents. The foundational "why" behind all conventions. Use when reviewing code quality, assessing project health, onboarding to a new project, or making architectural decisions about structure and consistency.
assess-qualityDevelopment Practices
Tech stack, coding patterns, commit conventions, interface design, error handling, testing, and junior-friendly philosophy. Use when writing code, making commits, or choosing tools/patterns.
write-codePragmatic Programming
Pragmatic Programmer principles — DRY, orthogonality, tracer bullets, prototyping, estimation, design by contract, and pragmatic paranoia. Use when writing, reviewing, or refactoring code.
review-designProject Scaffolding
Project structure — standard files, documentation conventions, and dispatch to language-specific scaffolds. Use when creating or standardizing projects. Delegates to scaffold-rust, scaffold-go, scaffold-python, scaffold-node, or scaffold-terraform for CI/CD, release pipelines, and language-specific config.
scaffold-projectRelease Workflow
Release pipeline conventions — sr.yaml config, sr action usage, git hooks, monorepo support, post-release patterns, and version file mapping. Language-specific build targets and publishing live in scaffold-rust, scaffold-go, scaffold-python, scaffold-node. Use when setting up or modifying release pipelines.
setup-releaseScaffold Go Project
Scaffold a complete Go project with CI/CD, release pipeline, Makefile, sr.yaml, .envrc, and standard files. Uses go toolchain and make as the native build system. Use when creating a new Go CLI, service, or module, or when the user mentions "new Go project", "go mod init", or "Go scaffold".
scaffold-goScaffold Node/TypeScript Project
Scaffold a complete Node/TypeScript project with CI/CD, release pipeline, sr.yaml, .envrc, and standard files. Uses npm scripts and biome. Use when creating a new Node.js app, TypeScript library, or website, or when the user mentions "new Node project", "npm init", "TypeScript scaffold", or "Astro site".
scaffold-nodeScaffold Python Project
Scaffold a complete Python project with CI/CD, release pipeline, justfile, sr.yaml, pyproject.toml, .envrc, and standard files. Uses uv, ruff, and justfile (Python lacks a native task runner like npm scripts, so just fills that gap). Use when creating a new Python CLI, library, or application, or when the user mentions "new Python project", "uv init", or "Python scaffold".
scaffold-pythonScaffold Rust Project
Scaffold a complete Rust project with CI/CD, release pipeline, sr.yaml, .envrc, and standard files. Uses cargo as the native build system. Use when creating a new Rust CLI, library, or workspace, or when the user mentions "new Rust project", "cargo init", or "Rust scaffold".
scaffold-rustScaffold Terraform Project
Scaffold a Terraform infrastructure project with CI/CD (plan on PR, apply on push), AWS OIDC auth, .envrc, and standard files. Uses terraform CLI as the native tool. Use when creating infrastructure repos, or when the user mentions "new Terraform project", "terraform init", "AWS infra", or "infrastructure scaffold".
scaffold-terraformTesting Practices
Testing philosophy, test types, per-language conventions, file organization, fixtures/mocks, CI strategy, and what NOT to test. Use when writing tests, reviewing test coverage, setting up test infrastructure, or deciding what to test.
test-codeTools
Canonical tech stack reference organized by purpose — release, docs/demos, codegen, and per-language tools. Use when choosing libraries, setting up projects, or selecting the right tool.
choose-stackGeneral
diagnose-ci
Find failing CI pipelines, pull logs, identify root cause, and suggest or apply fixes. Use when CI is red or the user asks why a pipeline failed.
diagnose-cifix-and-retry
Diagnose a CI failure, apply the fix, commit, push, and watch the re-run. Use after a pipeline fails and you want to fix and retry in one shot.
fix-and-retryget-work
Scan a folder for git repos and report GitHub status, branch divergence, and what's needed to get each repo up to date. Use when checking on multiple repos at once.
get-workpersona-architect
Adopt the Architect persona — interface-first systems design with verbose, principle-driven reasoning. Use for module decomposition, phased delivery plans, and systematic design work.
persona-architectpersona-curator
Adopt the Curator persona — prescriptive perfectionist focused on consistency, polish, and visual hierarchy. Use when refining documentation, formatting, naming, and cross-project standards.
persona-curatorpersona-debugger
Adopt the Debugger persona — terse, empirical root-cause analysis. Use when something is broken and you need fast, evidence-based diagnosis.
persona-debuggerpersona-ideator
Adopt the Ideator persona — expansive, generative creative exploration. Use when brainstorming features, exploring UX possibilities, and pushing boundaries before constraining.
persona-ideatorpersona-strategist
Adopt the Strategist persona — imperative, structured orchestration across multiple systems and repos. Use for multi-repo sweeps, batch operations, and systematic coordination.
persona-strategistpersona-writer
Adopt the Writer persona — concise, outcome-focused technical documentation. Use for READMEs, skill files, API docs, and any documentation that must serve both humans and AI agents.
persona-writerpr
Create a pull request with auto-generated summary from commits, following conventional commit conventions. Use when creating PRs.
prrelease-audit
Audit releases, tags, and assets for a repo or all repos in a directory. Finds orphaned tags, missing assets, and sr config issues. Use when checking release health.
release-auditrepo-init
Full repo bootstrap — create GitHub repo, add license, scaffold CI/release, write README, set metadata, and push. Use when starting a new project from scratch.
repo-initship
Commit with conventional message, push, and watch CI pipeline until it passes or fails. Use when shipping code changes.
shipupdate-repo-meta
Update GitHub repo metadata — topics, description, homepage, and visibility via gh CLI. Use when updating repo settings.
update-repo-metaMaintenance
Security
Visual & Branding
README Standards
README structure — centered header, badges, demos, section order, install.sh pattern, quickstart, embed-src usage, and llms.txt. Use when creating or updating any project README.
write-readmeVisual Identity
Terminal theme, font, VHS demos, teasr integration, asset conventions, and branding across README/demos. Use when configuring appearance, recording demos, or maintaining visual consistency.
style-brand