Claude Code plugins
17 Plugins aus öffentlichen Claude Code marketplaces. Jedes bündelt Skills, Slash-Commands, Agents, Hooks oder MCP servers, die zusammen installiert werden.
Zeige 17 Plugins, die diesen Filtern entsprechen.
17 Plugins aus öffentlichen Claude Code marketplaces. Jedes bündelt Skills, Slash-Commands, Agents, Hooks oder MCP servers, die zusammen installiert werden.
Zeige 17 Plugins, die diesen Filtern entsprechen.
Reiche das repo mit .claude-plugin/marketplace.json ein und wir listen jedes plugin auf.
Marketplace einreichenGate a UI before it is called done: check the build, not the design file. Three deterministic stdlib scripts: a finish linter that blocks on controls that do nothing, dead links, placeholder copy and removed focus rings, and warns on template defaults; an interaction-state checker that derives loading, empty, error, busy and focus states from each surface's kind and blocks when they are missing or unevidenced; and a rendered audit that reads a browser snapshot and blocks on WCAG 2.2 AA failures in contrast, focus visibility, focus obscured, reflow at 320 px, accessible names and target size. Ships a read-only snapshot collector, an optional Playwright keyboard pass, cs-design-qa agent, /cs-design-qa and /cs-ui-finish-lint commands, 3 cited references and a finish sign-off.
A four-tier memory ladder for Claude Code where promotion is earned by recurrence, not asserted by confidence. L0 raw transcripts are never injected; L1 candidate atoms are gitignored and recalled on lexical relevance per prompt; L2 project context loads each session start; L3 stable persona is always loaded. L1 to L2 needs three distinct sessions spanning two distinct calendar days (a stated claim needs two; a verified claim is the only single-observation path); L2 to L3 needs two projects and thirty days. Two gates refuse rather than guess: a claim altered by the redaction pass never promotes on evidence alone, and a contradicted claim freezes until a human resolves it. Three hooks run the loop unattended and every one fails open. Nothing reaches a committed CLAUDE.md without an explicit human adopt. Ships 5 stdlib scripts, 3 hooks, a cs-memory-curator agent, /cs-memory, a JSON schema, and a 69-check validator. Concept from TencentCloud/TencentDB-Agent-Memory (MIT); no upstream code
Free open-source OSINT and investigation toolkit for Claude Code: case workflow, 54 OSINT adapters, structured analysis, chain-of-custody evidence capture, threat-intel MCP servers.
Audit a public website with crawl, SEO, accessibility, conversion and evidence-backed reports.
Model supplied software economics and costs with explicit scenarios and evidence.
Runs 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.
developmentModernize COBOL, DB2, VSAM, and JCL systems with evidence-first archaeology, REQ-NNN lineage, bounded correction loops, an extracted engineering graph, behavior and data equivalence proof, and human-gated delivery.
Modernize COBOL, DB2, VSAM, and JCL systems with the four-stage classic workshop: evidence-first archaeology, REQ-NNN lineage, bounded implementation, and hardened evolution, without the correction-loop and engineering-graph layer.
Modernize Software AG Natural and Adabas systems with evidence-first archaeology, REQ-NNN lineage, bounded correction loops, an extracted engineering graph, behavior and data equivalence proof, and a preview-first workspace publisher.
Modernize Software AG Natural and Adabas systems with the four-stage SIFAP workshop: evidence-first archaeology, REQ-NNN lineage, bounded implementation, and hardened evolution, without the correction-loop and engineering-graph layer.
Turn Littlebird memory into evidence-backed operating work.
Turn screen recordings into ready-to-file bug drafts, specs, backlogs and meeting actions — local Whisper transcript + keyframes + OCR + wall-clock evidence via the talkthrough MCP server.
Domain-agnostic data-product skills, operating loops and analyst evidence graphs, with healthcare, marketing, logistics/ops and ecommerce applications.
Evidence-driven JavaScript reverse-engineering skill: signature recovery, runtime instrumentation, deobfuscation, verbatim sandbox harnesses, misdiagnosis triage, and replay delivery.
Ten skills forming a documentation chain: AGENTS.md entry point, PRD, technical specs, ADRs, implementation plans, status tracking with crash recovery, a git workflow with evidence-carrying PRs, an independent verification gate, gated documentation maintenance, and a brownfield onboarding on-ramp — plus a bundled verifier agent and router + run-loop drivers shipped as both commands and skills (works in Claude Code, GitHub Copilot CLI, and Codex). The harness layer for long-running, loop-driven development.
workflowsStructured persuasion for tech leads, PMs, founders—five scenarios on Hook→Context→Proposal→Evidence→Ask with AI intake and checklist
workflow