Claude Code plugins
12 Plugins aus öffentlichen Claude Code marketplaces. Jedes bündelt Skills, Slash-Commands, Agents, Hooks oder MCP servers, die zusammen installiert werden.
Zeige 12 Plugins, die diesen Filtern entsprechen.
12 Plugins aus öffentlichen Claude Code marketplaces. Jedes bündelt Skills, Slash-Commands, Agents, Hooks oder MCP servers, die zusammen installiert werden.
Zeige 12 Plugins, die diesen Filtern entsprechen.
Reiche das repo mit .claude-plugin/marketplace.json ein und wir listen jedes plugin auf.
Marketplace einreichenRuns a substantial task through a mandatory built-in intake grill, then 10 gated stages (docs, brainstorm+decompose, spec, plan, subagent build, tests, lint/deploy, post-deploy, docs/wiki, acceptance). Every stage's doctrine is built into the skill — no companion plugin required — with typed auto/judgment/manual gates, a frozen requirement spine that closes with evidence, a work board and a verification ledger that outlive a run, an exposure line naming what shipped unconfirmed, a progress rail computed from the project's own config, a proportional short path for small changes, a loop guard whose ceilings stop and record a blocker, and stage-3 tracks for what a product does, how it sounds and how it looks. Two modes need no task: `checkup` (what is unverified) and `setup` (audit existing docs); a third, `waves`, takes the whole board and closes it in waves that each finish in one pass. Retro insights can publish upstream as issues, opt-in and redacted.
developmentScenario-driven UI development: a versioned design chain in docs/ux/ that runs product vision -> personas, JTBD, journeys and stories -> user flows -> a screens+states UI map with Figma frames -> traced use-case scenarios -> evidence-backed audits -> concrete fix plans. Skills: vision, ux-foundation, ux-flows, ux-scenarios, ux-audit, brand-voice, copywriting. /ux is the single plain-language entry point and reaches every skill; a stdlib linter fails on doc drift; a tag-indexed best-practices catalog, PRN heuristics and component guidelines guide design; one style pack (via the sheleg-design companion) locks the visual identity.
developmentGo, BubbleTea TUI, Wish SSH, and Prometheus code review
Coordination layer for multi-agent repositories. Gives task-pipeline runs leases with a TTL, race-free ID reservation, a cross-repo signal feed, an append-only run journal and a machine-generated read-only board. A lease is decided by a primitive that genuinely has compare-and-swap — an atomic file create on one machine, a pushed git ref across machines — never by the knowledge base, which loses concurrent writes; the store carries the record and the ID allocation, which is positional over the merged log. The knowledge backend is a pluggable adapter (Outline, filesystem) declaring its own capabilities and degrading out loud. Ships Claude Code hooks that deny edits to guarded registry files without a live lease.
developmentOperational skills for flowctl setup, task health monitoring, log analysis, connector management, and SSH tunnel troubleshooting
Ubuntu Server provisioning suite — the three configuration layers of an unattended on-premise / air-gapped Ubuntu Server LTS 24.04 / 26.04 bring-up: ubuntu-autoinstall (the Subiquity `autoinstall:` v1 schema — identity, storage LVM/ZFS/RAID/encryption, apt mirror + proxy + offline fallback, early/late-commands, NoCloud zero-touch delivery), ubuntu-cloud-init (NoCloud-datasource `#cloud-config` user-data — users, ssh, write_files, runcmd, local apt mirrors, internal-CA ca_certs, seed ISO / SMBIOS serial / `ds=nocloud` cmdline, boot stages, `datasource_list` pinning), and ubuntu-netplan (the `/etc/netplan/*.yaml` v2 network substrate both share — static addressing, bonds, bridges, VLANs, VRFs, policy routing, predictable interface naming, systemd-networkd renderer). The installer's `network:` block is netplan and its `user-data:` block is cloud-config, so the three are designed to be used together.
infrastructureAdminister and troubleshoot remote Linux, FreeBSD, NetBSD, OpenBSD, and macOS systems safely, one host or a fleet at a time. Use when a task requires SSH, Ansible, Paramiko, POSIX diagnostics, service management, software updates, system configuration, firewall changes, or evidence-led remote operations. Do not use for local-only desktop administration, container or cluster orchestration (route to kubernetes), or cloud consoles that expose no remote shell.
Bitnami-exit suite — migrate off dead-ended Bitnami charts/images. First member: redis-to-valkey (Sentinel HA migration to Valkey: the RDB-version wall, RedisShake/rdb-cli logical replay, chart selection and values translation, consumer-app reconnection, air-gap mirroring, Argo CD source rewiring away from charts.bitnami.com).
kubernetesOfficial-doc-first Yocto Project and BitBake skills: route to current documentation, debug BitBake build failures, and review recipes, layers, images, BSP/kernel metadata, and security/SBOM workflows.
developmentRead-only discovery for a fleet harness repository: a POSIX probe sent over ssh collects OS, kernel, CPU, RAM, disks, Docker, NVIDIA and Intel Arc GPUs, addresses, ports, tunnels and DNAT rules; discover.py turns it into the host card after comparing it with the card, render_index.py validates every card and regenerates the host index and an optional self-contained network map.
opsOnboard a server into a fleet harness repository: reach it over ssh with a confirmed host key, discover it read-only with server-discovery, place it in a namespace, write the host card and README, mirror its compose stacks and system configs, add it to the namespace Topology, regenerate the index, and hand a box with an incomplete GPU stack to gpu-server-setup once the user agrees.
opsLinux system administration, systemd service management, journald logs, disk/RAM troubleshooting, and SSH hardening