21 Plugins aus öffentlichen Claude Code marketplaces. Jedes bündelt Skills, Slash-Commands, Agents, Hooks oder MCP servers, die zusammen installiert werden.
Zeige 21 Plugins, die diesen Filtern entsprechen.
cursor-rules-javajabrena/plinth3
healthclaw-marketplaceaks129/HealthClawGuardrails1
claude-code-plugins-plusjeremylongshore/tons-of-skills-marketplace1
agent-powerupsyeaight7/agent-powerups1Reiche das repo mit .claude-plugin/marketplace.json ein und wir listen jedes plugin auf.
Marketplace einreichenFHIR AI agent guardrails with 29 MCP tools including Compiled Truth (current state + evidence timeline) and Wearables (Garmin, Oura, Polar, Suunto, Whoop, Fitbit, Strava via Open Wearables). PHI redaction on every read, step-up auth for writes, immutable audit, tenant isolation, Curatr data quality, Fasten Connect EHR ingestion. FHIR R4 US Core v9 + R6 ballot3.
Manage test environments with Docker Compose, Testcontainers, and environment isolation
Test code review for test files only: conventions, isolation, object-model patterns, framework architecture audits, and test suite health checks. Includes a framework blueprint for new suites and a test design scorecard. Agents (test-code-critic, e2e-selector-quality-critic, framework-architecture-auditor, test-suite-health-auditor) review structure, assertions and mocking, selector fragility, framework architecture, and suite health. Production code is out of scope.
foundationsError diagnosis, fault isolation, log forensics, and incident investigation.
developer toolsWhite-box bug hunting, AI-agent and LLM red-teaming, cloud identity and CI/CD trust, client-app trust surfaces across browser and editor extensions and Electron, wire-protocol and token trust across gRPC, WebSocket, and JWT, enterprise identity lifecycle across SCIM and JIT provisioning, directory sync, MFA and key lifecycle, and Kerberos delegation, infrastructure-as-code and container hardening, mobile app security, smart-contract and DeFi review across EVM and Move, skill and MCP supply-chain vetting, API and object-authorization depth, host privilege escalation, network-service and transport trust, firmware and embedded-software trust, web trust boundaries, authentication and session depth, rate-limiting and multi-tenant isolation, injection and resource-exhaustion depth, file-upload and content handling, defensive detection and logging, supply-chain and dependency risk, business-logic and access-control depth, the classic web-attack classes across XSS, template and command injecti
securityFlaky test triage: find the condition a flake depends on, quarantine it with an expiry date, fix known flake patterns, and track flake rates. Agents (e2e-flake-bisector, regression-bisector) rerun a test under varied conditions with a shared-state isolation stage, and run git bisect to find the commit that introduced a regression, with a perf-measurement mode.
operations-resilienceConcurrency testing: deterministic race-condition tests, deadlock detection, async ordering checks, and database MVCC isolation-level tests. Includes ThreadSanitizer and the Go race detector with goleak, plus a critic agent (concurrency-critic) that flags unguarded shared state and lock-ordering risks. Code-level races, distinct from qa-resilience (infrastructure fault injection).
backend-distributedDesign and review end-to-end multi-tenant SaaS architectures: tenant and subscription semantics, control and application planes, pooled or isolated tenancy, onboarding, entitlements, metering, billing handoffs, lifecycle, partitioning, and tenant-aware operations. Use when a subscription product needs a coherent tenant model and architecture decision across these seams. Do not use for threat modeling or isolation controls, API contract semantics, data-platform design, backend implementation, migration execution, privacy compliance artifacts, capacity evidence, financial modeling, or infrastructure operations; route those to the named specialist owners.
Route a product through its full lifecycle — discovery, strategy, portfolio choice, roadmap, UX and requirements, experimentation, delivery handoff, adoption, success, and lifecycle review — by composing existing specialist product skills with phase-entry evidence, handoff artifacts, and escalation rules. Use when evaluating a new product idea, managing a product through its lifecycle, or connecting product phases that currently operate in isolation. Do not use for a single product task that is already owned by a specialist skill (load that skill directly); do not use for software delivery lifecycle work (route to neckbeard); do not use to duplicate product discovery, strategy, UX, experimentation, analytics, release, or delivery methods.
Design and review software architectures from business drivers through system boundaries, tradeoffs, runtime behavior, evolution, and architecture practice. Use when choosing a greenfield or target architecture, comparing modular-monolith and service shapes, designing distributed consistency, replication, partitioning, coordination, ordering, transaction isolation, or failure behavior, defining architecture fitness evidence, or facilitating a consequential architecture review. Do not use for reverse engineering, API contract semantics, data-platform design, implementation, infrastructure operations, security lifecycle, or migration execution; route those to the named specialist skills.
Design and build waiting-list portals for anticipated goods or services: classify whether the experience needs interest capture, verified early access, referral growth, a virtual waiting room, appointment backfill, or scarce-item allocation; choose a reversible architecture; and define the state machine, abuse controls, consent and email lifecycle, fairness, observability, and release gates. Optionally validate supplied email and phone contacts with expiring magic links or provider-managed verification, then feed eligible, consented records to a runtime-configured CRM adapter. Use for prelaunch signups, beta access, launches, bookings, reservations, traffic-spike queues, and premium or cinematic campaign experiences. Do not use for generic landing-page copy, ordinary CRM or email operations, or checkout and inventory systems in isolation; route those parts to the appropriate specialist skill.
Tenant isolation testing for B2B SaaS: cross-tenant leak tests with a CI gate, row-level security, and tenant onboarding and offboarding tests. Includes silo / pool / bridge isolation models and a Postgres-first RLS reference. A review agent (tenant-leak-critic) traces tenant-id propagation through a diff to find leak risks.
security-complianceSwift Concurrency (iOS 13+). Use when writing async/await, diagnosing data races, fixing actor isolation, migrating to Swift 6, or handling Sendable conformance.
Coordinate staged or parallel jobs across live-verified coding-agent runtimes, coding-agent sessions, and in-session subagents through one runtime-adapter contract and a normalized event protocol, routed by deterministic capability- and risk-based policy with an optional provider-neutral System-1 decision plane for trace watching, failure triage, and pre-arbiter gating. Worktree isolation, resumable state, capture, safety gates, and independent arbiter review included.
productivityOpt-in, outside every domain bundle: orchestrate opencode workers from Claude Code to cut token costs, with single workers or parallel scout/coder/tester swarms on free or open-source models and worktree isolation. Requires the third-party opencode CLI and an opencode account; by default worker prompts and code go to opencode's hosted service (point --model at a local model to keep code on your machine), so install it only if you accept that data flow.
Use when you need to write or improve integration tests — including Testcontainers with @ServiceConnection, @DataJdbcTest persistence slices, TestRestTemplate or MockMvcTester for HTTP, data isolation, and container lifecycle management for Spring Boot 4.0.x.
Use when you need data access with Quarkus Hibernate ORM Panache — including PanacheEntity / PanacheEntityBase, PanacheRepository, named queries, JPQL, native SQL, DTO projections (project(Class)), pagination (Page.of()), N+1 avoidance (JOIN FETCH), optimistic locking (@Version / OptimisticLockException), @NamedQuery for validated reusable queries, transactions, @TestTransaction for test isolation, and immutable-friendly patterns. This is the Quarkus analogue to Spring Data for relational persistence.
Use when you need to write or improve integration tests for Quarkus — including @QuarkusTest, Dev Services for automatic container provisioning, Testcontainers via QuarkusTestResourceLifecycleManager, WireMock for external HTTP stubs, @QuarkusIntegrationTest for black-box testing against packaged artifacts, REST Assured, data isolation strategies (@TestTransaction vs @BeforeEach cleanup), and Maven Surefire/Failsafe three-tier split (*Test, *IT, *AT).
Docker image development patterns for Dockerfile, docker-compose, docker-bake.hcl, and .dockerignore. Multi-stage builds, layer optimization, CI testing patterns (entrypoint bypass, DNS mocking, compose validation), Docker Bake multi-platform, Trivy scanning, network isolation. By Netresearch.
Application-security & compliance QA role bundle: one-command install of unified security scanning (SAST, DAST, SCA, secrets, SBOM), fuzzing, compliance, multi-tenancy isolation, test-data privacy, and IaC policy testing.
role-bundles
