54 Plugins aus öffentlichen Claude Code marketplaces. Jedes bündelt Skills, Slash-Commands, Agents, Hooks oder MCP servers, die zusammen installiert werden.
Zeige 54 Plugins, die diesen Filtern entsprechen.
magnus-agent-skillsmagnus919/agent-skills3
agent-plugins-for-awsawslabs/agent-plugins2
onewave-skillsOneWave-AI/claude-skills1
keep-the-whyoliver-zehentleitner/keep-the-why1Reiche das repo mit .claude-plugin/marketplace.json ein und wir listen jedes plugin auf.
Marketplace einreichenEnterprise React 18 migration toolkit with specialized agents and skills for upgrading React 16/17 class-component codebases to React 18.3.1. Includes auditor, dependency surgeon, class component migration specialist, automatic batching fixer, and test guardian.
Migrate, modernize, and upgrade codebases to AWS. Transforms .NET Framework to .NET 8/10, mainframe COBOL to Java, VMware VMs to EC2, SQL Server to Aurora, and upgrades Java/Python/Node.js versions and AWS SDKs. AWS Transform - continuous modernization analyzes codebases for tech debt, security issues, and upgrade opportunities, then remediates them.
Analyze codebases to generate structured technical documentation with source-of-truth citations. Optimized for AWS workloads using CDK, CloudFormation, and Terraform.
Safe refactoring, dead-code removal, legacy modernization, and dependency hygiene.
developer toolsEnterprise React 19 migration toolkit with specialized agents and skills for upgrading React 18 codebases to React 19. Includes auditor, dependency surgeon, source code migrator, and test guardian. Handles removal of deprecated APIs including ReactDOM.render, forwardRef, defaultProps, legacy context, string refs, and more.
Search-first codebase understanding, context retrieval, mapping, pattern detection, and living project intelligence.
developer toolsDeploy a 2-layer parallel agent hierarchy for large, parallelizable work: big refactors, multi-file migrations, codebase-wide audits, and bulk generation. Pick an army size and power level; includes git checkpoints, a pre-deploy gate, phantom-completion checks, and multi-wave follow-up.
The why layer of repo-native project memory: the reasoning behind a codebase, kept as Markdown in the repository.
Investigation flow (Glob -> Grep -> Read), evidence-based research with file:line references, structured output format for AI consumption. Use for pattern discovery, implementation research, and codebase investigation.
Review a code change for correctness, security, maintainability, and test adequacy, and reach a defensible verdict. Use when reviewing a pull request, diff, patch, or AI-generated change; when scoping an oversized review into reviewable units; when writing or triaging review comments; when assigning reviewers or setting review policy; or when investigating why a defect escaped review. Covers change sizing and attention budgets, risk-tiered checklists, severity-labeled comments, verdict and residual-risk records, review metrics that resist gaming, and the measured limits of checklists and AI reviewers. Do not use for implementing the requested change, root-cause debugging of a failing test or incident (use systematic-debugging), security assessment of a whole system (use security-audit-methodology), designing new code securely (use secure-software-engineering), architecture review across systems (use software-architecture), or reverse-engineering an unfamiliar codebase (use software-arc
Use when designing or implementing software securely: define security requirements, threat-model a feature, choose secure defaults, design authentication and authorization, handle untrusted data and secrets, evaluate dependencies, design multi-tenant trust boundaries, or review security-sensitive changes. Use for prevention during requirements, design, implementation, and review; not for post-build security assessments or scanning an existing codebase.
Use this skill to reverse-engineer an existing software system, map its architecture, data flow, privacy posture, coupling, quality characteristics, and feature surface, then produce an evidence-grounded clean-room design document, PRD, or migration plan under new constraints. Use for codebase archaeology, implicit contract extraction, architecture health assessment, or decomposition-readiness analysis. Do not use for greenfield architecture design, direct code review, bug hunting, security auditing, or implementation of API, data, platform, or migration changes; route those to the relevant neighboring skill.
Time and timezone testing: fake clocks across runtimes, DST transitions, leap seconds, and timezone test matrices built from a codebase's date handling. Fake clocks cover freezegun, Jest and Sinon fake timers, timecop, java.time.Clock, .NET TimeProvider and libfaketime. A critic agent (time-handling-critic) flags naive now() calls and DST-unsafe arithmetic.
backend-distributedCreate distill-style interactive explainers from documents, web research, or a codebase, with a fact-checking gate that supports, corrects, or cuts every claim.
Run Claude (or any capable LLM) as an autonomous senior engineer on any codebase — config-driven hooks enforcing discover-then-reuse, plus coordinator/succession/doc-sync skills and planner/builder/auditor agents. Frontend or backend, any language.
productivityWrite and audit Tailwind CSS with practices that keep a fast-to-write codebase maintainable — design tokens, grouped tokens, consistent class ordering, and fixed variants for design-system components
frontendMulti-agent PR, CI, and downstream fork-sync review desk for Claude Code.
Task Researcher and Task Planner for intermediate to expert users and large codebases - Brought to you by microsoft/edge-ai
Context-efficient routing: dispatch tables for workflow, review, and codebase-intelligence commands.
developer toolsWork in a Codebase Wiki project: an agent-authored, source-grounded wiki of the surrounding codebase.
