yousiki's Claude Plugins
A personal marketplace of Claude Code plugins.
Language servers, MCP servers, formatter hooks, and room for future plugin kinds such as slash commands and agents. Most tool-backed plugins are wrapped in launchers that probe a runtime fallback chain (bunx / uvx and friends), so nothing has to be installed globally on the host; a smaller set of language servers with no npm/PyPI distribution invoke their native-toolchain binary directly instead — see Design.

Install · Plugins · Design · Layout · Contributing
Highlights
- No global installs, where the ecosystem allows it. Most plugins launch through a runtime fallback chain — JS/TS via
bunx → pnpm dlx → npx, Python via uvx → pipx run. You only need one runtime from each chain on PATH.
- On-demand resolution. Packages resolve from the registry at launch time, so there are no pinned global binaries to keep up to date.
- Native-toolchain servers, honestly labeled. A handful of language servers (C/C++, C#, Go, Java, Kotlin, Lua, Ruby, Rust, Swift) have no npm/PyPI package to run on demand — their plugin invokes the bare binary and expects it already on
PATH, same as the official Anthropic plugin directory does for these languages.
- Broad plugin coverage. Current plugins span language servers, MCP servers,
PostToolUse formatter hooks, and an all-in-one bundle (languages-pack); the marketplace is structured to add future Claude Code plugin kinds such as slash commands and agents.
- Metadata-only folders. One folder per plugin — no vendored binaries, no submodules.
- Personal scope. These are the tools I reach for; expect the roster to drift as my own workflow changes.
Plugins
Grouped by current plugin kind. The roster is 26 plugins across language servers, MCP servers, formatter hooks, and one all-in-one bundle; future categories can be added when they become useful. All plugins live under plugins/ and are registered in .claude-plugin/marketplace.json.
Language Servers — zero-install (11)
Resolve on demand through a runtime fallback chain; nothing to install beyond the runtime.
| Plugin | Language | Runtime chain | Notes |
|---|
typescript-lsp | TypeScript, JavaScript | JS/TS | typescript-language-server, pulls the typescript peer dep fresh |
basedpyright-lsp | Python | Python | Stricter community fork of Pyright |
biome-lsp | JS, TS, JSON | JS/TS | Biome language server (lint + format diagnostics) |
bash-lsp | Bash, shell | JS/TS | bash-language-server; integrates with shellcheck when on PATH |
yaml-lsp | YAML | JS/TS | Red Hat yaml-language-server |
tombi-lsp | TOML | Python | tombi LSP; schema-aware for pyproject.toml, Cargo.toml, and similar files |
vscode-html-lsp | HTML | JS/TS | vscode-langservers-extracted (HTML binary) |
vscode-css-lsp | CSS, SCSS, LESS | JS/TS | vscode-langservers-extracted (CSS binary) |
vscode-json-lsp | JSON, JSONC | JS/TS | vscode-langservers-extracted (JSON binary) |
php-lsp | PHP | JS/TS | Intelephense, published on npm |
liquid-lsp | Shopify Liquid | JS/TS | Shopify CLI's theme language-server subcommand |
Language Servers — native toolchain (9)
No npm/PyPI package exists for these, so there's no fallback chain to wrap — the plugin invokes the bare binary directly, and it must already be on PATH (same approach the official Anthropic plugin directory takes for these languages). See each plugin's README for install instructions.