ku5ic
UsermacOS development environment with Neovim, tmux, zsh, Claude and automation
Categories
Indexed Skills (38)
backup-patterns
Backup patterns for Linux servers and applications covering the 3-2-1 rule, rsync file backups, PostgreSQL dumps with pg_dump, encrypted backups with restic, retention policies, and restore testing. Use whenever the project contains shell scripts using pg_dump, rsync, or restic, a Brewfile or requirements file with restic or pgbackup tooling, cron job definitions for backups, or backup-related systemd units, OR the user asks about backups, disaster recovery, data retention, pg_dump, rsync, or restic, even if "backup" is not mentioned by name.
bash-patterns
Bash and shell script patterns covering safety flags, quoting, conditionals, traps, functions, ShellCheck discipline, and review-worthy anti-patterns. Use whenever the project contains `.sh`, `.bash`, `.zsh` files (or files with bash/sh shebangs), scripts in `bin/`, dotfiles like `.zshrc`/`.bashrc`/`.zprofile`, Makefile recipes, OR the user asks about bash, shell, scripts, or any shell-pipeline work, even if "bash" is not mentioned by name.
context-gathering
Confirms project conventions, existing patterns, and relevant rules were actually checked before a change lands, not just available to check. Use whenever you are about to read or edit any file in a repo for the first time this session, OR the user asks why a change does not match existing conventions, style, or established patterns, even if "context" is not mentioned by name.
django-patterns
Django patterns, anti-patterns, ORM gotchas, view design, migrations, settings, and review checklist for Django backend work. Use whenever the project contains `manage.py`, `settings.py`, `apps.py`, OR `pyproject.toml`/`requirements.txt`/`Pipfile` with `django` (or `Django`) listed as a dependency, OR the user asks about Django, Python web backend, ORM queries, models, views, forms, templates, migrations, admin, signals, middleware, or any work touching `.py` files in a Django app structure, even if Django is not mentioned by name.
docker-patterns
Docker patterns covering Dockerfile best practices, multi-stage builds, Compose service configuration, networking, volumes, and security. Use whenever the project contains a Dockerfile, docker-compose.yml, .dockerignore, or compose.yaml, OR the user asks about Docker, containers, docker-compose, multi-stage builds, base images, volumes, healthcheck, depends_on, even if Docker is not mentioned by name.
drf-patterns
Django REST Framework patterns, serializers, viewsets, permissions, throttling, filtering, pagination, and review checklist. Use whenever the project contains `djangorestframework` in dependencies, `rest_framework` in INSTALLED_APPS, files following DRF naming patterns (`serializers.py`, `viewsets.py`, `permissions.py`), OR the user asks about DRF, Django REST, serializers, viewsets, ModelViewSet, permission_classes, throttle_classes, even if DRF is not mentioned by name.
engineering-fundamentals
Engineering fundamentals reference covering requirements clarity, design integrity, code-level quality, test design, verification and validation, and metric thresholds. Use whenever the project contains source files in any compiled or scripted language (`.js`, `.ts`, `.py`, `.rb`, `.go`, `.rs`, `.java`, `.sh`, etc.), OR the user asks about code quality, design principles, SOLID, DRY, KISS, requirements clarity, test design, metrics, or any engineering review, audit, plan, or refactor task, even if "principles" or "fundamentals" are not mentioned by name.
fastapi-patterns
FastAPI patterns, Pydantic schemas, dependency injection, async correctness, response models, error handling, OpenAPI, and auth. Use whenever the project contains `fastapi` in dependencies, files importing from `fastapi`, `@app.get`/`@router.get` decorators, Pydantic BaseModel subclasses used as request/response types, OR the user asks about FastAPI, Pydantic v2, Depends(), HTTPException, OAuth2PasswordBearer, APIKeyHeader, response_model, even if FastAPI is not mentioned by name.
fix-sizing
Right-sizes a bug fix to its actual defect before any edit lands, catching oversized blast radius and overengineered solutions early. Use whenever you are about to read or edit any file in the course of diagnosing, fixing, or patching reported behavior, OR the user asks about scope creep, overengineering, blast radius, or why a change touched more than expected, even if "fix-sizing" is not mentioned by name.
flow-debug
Investigate unexpected behavior without a clear failing signal
flow-explore
Survey requirements and implementation approaches for an obscure or under-specified task using parallel agents
flow-plan
Ground a task in the codebase, then turn it into an ordered implementation plan with explicit tradeoffs
flow-preflight
Establish shared understanding of the codebase before any work begins
flow-quick
Implement a small net-new feature end to end without a plan artifact, with full per-file integrity gates
git-patterns
Git workflow patterns covering Conventional Commits, interactive rebase, branch strategy, recovery with reflog, bisect, worktrees, and stash. Use whenever a project uses git, or the user asks about commit messages, rebase, branch strategy, merge conflicts, git history, or recovering lost commits, even if "git" is not mentioned by name.
javascript-patterns
JavaScript language patterns, modern syntax, async handling, module systems (ESM/CJS), error handling, and review checklist for JavaScript code without TypeScript. Use whenever the project contains `.js`, `.mjs`, `.cjs`, or `.jsx` files (and no `tsconfig.json`), `package.json` without TypeScript dependencies, OR the user asks about JavaScript, JS, ECMAScript, async/await, promises, modules, ESM, CommonJS, package.json, npm, pnpm, yarn, bun, or any work in JavaScript code without explicit TypeScript usage, even if "JavaScript" is not mentioned by name.
logging-patterns
Python logging patterns covering stdlib logging configuration, structured logging with structlog, log levels, handlers, formatters, and context binding. Use whenever a project uses Python logging, structlog, or the user asks about log levels, log formatting, structured logs, or JSON logging, even if "logging" is not mentioned by name.
markdown-report
Consistent format for audit reports, review output, and workflow artifacts including required sections, severity rubric (failure/warning/info), file naming convention, and summary line rubric. Use whenever a command writes a report to `~/.claude/scratch/` or `docs/`, OR the user asks for a structured audit, review, finding report, or any output requiring the failure/warning/info severity rubric, regardless of domain.
meta-feature
Shape a fuzzy feature request into a structured brief before planning
meta-prompt
Turn a fuzzy ask into a sharp Claude Code prompt with context and acceptance criteria
monitoring-patterns
Application monitoring patterns covering Prometheus metrics (Counter, Gauge, Histogram, Summary), the prometheus-client Python library, metric naming conventions, labels, and health check endpoints. Use whenever a Python project instruments metrics, uses prometheus-client, or the user asks about Prometheus, metrics, monitoring, health checks, or observability, even if "Prometheus" is not mentioned by name.
next-app-router-patterns
Next.js App Router patterns covering server/client boundary, data fetching and caching, server actions, streaming, parallel and intercepting routes, edge vs node runtime, and review checklist. Use whenever the project contains `next.config.js`, `next.config.mjs`, `next.config.ts`, an `app/` directory with `page.tsx`/`page.jsx`/`layout.tsx`/`layout.jsx`/`route.ts`, OR `next` in `package.json` dependencies, OR the user asks about Next.js, App Router, server components, client components, server actions, route handlers, parallel routes, intercepting routes, streaming, generateMetadata, generateStaticParams, even if Next.js is not mentioned by name.
nuxt-patterns
Nuxt 3+ patterns covering rendering modes, data fetching (useFetch, useAsyncData, $fetch), server routes, SSR-safe state, file-based routing, Nitro runtime, and review checklist. Use whenever the project contains `nuxt.config.ts`, `nuxt.config.js`, `nuxt` in `package.json` dependencies, or `pages/`/`server/`/`composables/` directories at project root, OR the user asks about Nuxt, useFetch, useAsyncData, $fetch, server routes, Nitro, Nuxt SSR, even if Nuxt is not mentioned by name.
python-patterns
Python language-level patterns covering type hints, strictness, project layout, async, error handling, packaging, and review-worthy anti-patterns. Use whenever the project contains `.py` files, `pyproject.toml`, `requirements.txt`, `Pipfile`, `uv.lock`, `poetry.lock`, OR the user asks about Python, type hints, mypy, pyright, async, packaging, project structure, or any work in a `.py` file, even if "Python" is not mentioned by name.
question-hard
Answers a hard question requiring deep reasoning, cross-layer analysis, or architectural judgment. Use whenever the question involves novel architectural tradeoffs, multi-layer debugging, subtle correctness or concurrency reasoning, or security or performance analysis with non-obvious interactions, OR the user asks for a rigorous, deep-dive, or high-stakes answer, even if "hard" is not mentioned by name.
question-medium
Answers a medium-difficulty question requiring real reasoning, verification, or stack-specific knowledge, but not deep architecture or long correctness chains. Use whenever the question is substantive but routine - not a lookup, not a novel architectural or multi-layer tradeoff - OR the user asks for a considered, verified answer without a full deep-dive, even if "medium" is not mentioned by name.
react-patterns
React patterns, anti-patterns, hooks rules, performance, component design, and review checklist for React core (independent of any specific meta-framework). Use whenever the project contains `.jsx` or `.tsx` files, `react` in `package.json` dependencies, OR the user asks about React, hooks, components, JSX, TSX, useState, useEffect, useMemo, useCallback, rendering, hydration, React performance, or any React component work, even if React is not mentioned by name.
root-cause-diagnosis
Determines whether a failure is a defect in a dependency (a third-party library, an internal shared module, or any package the current code does not own) or a misuse of it, before proposing a fix, so the fix lands at the right layer. Use whenever a bug involves a library, framework, or internal shared module behaving unexpectedly, OR the user asks whether something is "a bug in the library" versus "how we're using it," even if "root cause" is not mentioned by name.
security-patterns
Security checklist covering XSS, injection, authentication, authorization, sessions, CSRF, CSP, secrets, dependency CVEs, input validation, and severity calls. Use whenever the project includes auth code, session handling, environment variable reads, user input handling, route handlers, server actions, middleware, or external API calls, OR the user asks about security, hardening, vulnerabilities, auth, authentication, authorization, sessions, cookies, XSS, CSRF, SQL injection, secrets, environment variables, CSP, headers, or reviews changes that touch user input, auth, or external data, even if "security" is not mentioned by name.
skill-authoring
Rules and conventions for authoring or editing Claude Code skills in `~/.dotfiles/claude/skills/`. Use whenever editing a SKILL.md file or any file under `claude/skills/`, OR the user asks about authoring a skill, editing a skill, skill descriptions, skill conventions, or skill structure, even if the word "skill" is not used.
tailwind-patterns
Tailwind CSS v4 patterns, CSS-first config via @theme directive, v3-vs-v4 deltas, variant rules, and anti-patterns. Use whenever the project contains `tailwind.config.js`, `tailwind.config.ts`, `@import "tailwindcss"` in CSS, `@tailwindcss/postcss` or `@tailwindcss/vite` in `package.json` dependencies, OR the user asks about Tailwind, utility classes, CSS, styling in a Tailwind project, @theme, @apply, design tokens, dark mode strategy, or any work touching CSS class names or theme configuration, even if Tailwind is not mentioned by name.
test-patterns
Testing conventions covering test design, fixtures, mocking, query priority, async handling, behavior-vs-implementation tests, boundary coverage, and what to skip. Use whenever the project contains test config files (e.g. `vitest.config.*`, `jest.config.*`, `playwright.config.*`, `pytest.ini`, `conftest.py`) or test directories (`tests/`, `__tests__/`, `spec/`), OR the user asks about tests, testing, unit tests, integration tests, e2e tests, mocking, fixtures, coverage, test failures, or extending test coverage in any stack, even if a specific framework is not mentioned by name.
typescript-patterns
TypeScript patterns, strictness flags, type-safety anti-patterns, and review checklist covering any vs unknown, satisfies operator, branded types, discriminated unions, generic constraints, and module boundaries. Use whenever the project contains `.ts` or `.tsx` files, `tsconfig.json`, `tsconfig.base.json`, or `typescript` in `package.json` dependencies, OR the user asks about TypeScript, types, type errors, type narrowing, generics, tsconfig, or any work in a `.ts` or `.tsx` file, even if "TypeScript" is not mentioned by name.
vps-provisioning
VPS provisioning patterns for Linux servers covering initial setup, firewall, nginx reverse proxy, SSL/TLS with Let's Encrypt, systemd service management, and server hardening. Use whenever the project contains Ansible playbooks, shell provisioning scripts, nginx configs, systemd unit files, or certbot references, OR the user asks about VPS setup, server hardening, ufw, fail2ban, nginx reverse proxy, certbot, Let's Encrypt, systemd services, unattended-upgrades, even if VPS is not mentioned by name.
vue-patterns
Vue 3 Composition API patterns, reactivity, single-file components, anti-patterns, and review checklist. Use whenever the project contains `.vue` files, `vue` in `package.json` dependencies, `vite.config.*` with the Vue plugin, OR the user asks about Vue, Vue 3, Composition API, ref, reactive, computed, watch, watchEffect, defineProps, defineEmits, defineSlots, script setup, single-file components, Pinia, even if Vue is not mentioned by name.
question-easy
Answers an easy question - a lookup, recall, or short factual answer with a direct path to the answer. Use whenever the question needs no cross-file verification, reasoning chain, or tradeoff call, OR the user explicitly asks for a quick, low-effort, or shallow answer, even if "easy" is not mentioned by name.
flow-checks
Run the project's verification checklist via run-checks.sh
flow-fix
Surgical fix from a failing signal (test, type error, runtime error, lint)
Bio shown is the top-scored skill's repo description as a fallback — real GitHub bios land in a future update.