The bundles. Take what you want.
Each one is a slice of the .claude/ directory I run on my own projects: skills, rules, hooks, settings, and the CLAUDE.md lines that make them make sense together.
AI Models
Lets Claude call the models you run yourself or reach through a gateway, for speech, vision, embeddings, reranking, decisions, images, video and music, from one CSV of endpoints.
Browser Testing
Prove UI changes in a real browser with playwright-cli. Install-if-missing, the snapshot→ref→act workflow, the test-account convention and evidence discipline.
Doc Fetcher
A generator for per-library documentation skills. Configure a template and Claude Code fetches a library's real docs from GitHub instead of recalling them.
Docs Discipline
The three-tier docs model (handovers, living wiki, frozen specs) with a handover skill and a mechanical wiki-parity test.
Iterative Spec Design
Design a system section by section with an approval checkpoint after each one, so a wrong assumption is caught in section two instead of in the finished spec.
Nuxt
Nuxt 4 framework docs fetcher and the rule that makes Claude Code check it before guessing a composable.
Nuxt UI
Nuxt UI v4 component docs and template fetchers plus the rule that makes Claude Code check them before touching a .vue file.
Quality Hooks
Fail-closed Claude Code hooks: protect .env and credential files, lint after every edit, and flag an unwritten convention before context is compacted.
Read-only DB Access
A dedicated read-only role, a one-statement runner wrapped in BEGIN READ ONLY, and the rule that keeps destructive SQL out of Claude's hands.
Remote Ops Quoting
The ssh argument-flattening trap that silently runs your command on the wrong machine, the two forms that work, and the base64 hop for anything with nested quotes or SQL.