公開されている Claude Code marketplace からの 12 件のプラグインです。それぞれにスキル、スラッシュコマンド、エージェント、フック、MCP サーバーがまとめてインストールされます。
これらのフィルターに一致するプラグインを 12 件表示しています。
ef-harnessmicaelcf/ef-harness1
cc-arsenal-marketplacemgiovani/cc-arsenal1.claude-plugin/marketplace.json を含むリポジトリを提出すると、すべての plugin を掲載します。
marketplace を提出するEngineering & tech skills: Code Review Checklist, Incident Postmortem, API Docs Writer, Architecture Decision Record, Debugging Log Analyser, PR Description Writer, System Design Interview, Changelog Generator, Test Strategy Doc, Runbook Writer, CI/CD Playbook, SLO & Error Budget, Developer Onboarding Doc, On-Call Runbook, Security Threat Model, Performance Budget, Database Schema Design, Database Migration Plan, Technical Debt Register, RFC Writer, Capacity Planning, Load Testing Plan, Disaster Recovery Plan, Feature Flag Guide, Dependency Audit, Service Catalog Entry, Monitoring Setup Guide, Local Dev Setup, API Versioning Strategy, Infra-as-Code Review, Engineering Weekly Report, Tech Radar, Sprint Velocity Analysis, Microservices Decomposition, Engineering Hiring Rubric, Context Mode, Claude Superpowers, Skill Security Auditor, Error Decoder, Regex Builder, Git Troubleshooter, Dependency Conflict Resolver, Code Explainer, Writing Great Skills. 44 structured skills for engineering t
Eleven commands that take a project — new or existing — to a verified PRD, prioritized features, project rules, and sequenced RFCs — then guide implementation, review, and testing.
Five-stage, repo-agnostic feature pipeline: grill the decisions, author RFC/PRD, discover per repo, build against named proofs, then one adversarial audit gate. Plus /ef:ready: a deterministic gate that keeps the agent rulebook small and true.
developmentDocumentation skills: ADR, RFC, diagrams, init, check, and update
Authentication flow testing: OAuth 2.0 with PKCE, multi-factor authentication, and session management, plus Keycloak, Auth0 and Okta integration tests. Anchored on RFC 7636, RFC 9700 and OWASP ASVS V3. A critic agent (token-storage-security-critic) flags tokens in localStorage, auth cookies missing httpOnly / Secure / SameSite, and tokens leaking into logs or URLs.
integrations-protocolsProject progress ledger written automatically. A Stop hook logs the working-tree delta each turn that touched files (ship, rfc, or plain conversation), so what moved is recorded without remembering to log; next reads it.
memoryQuery unfinished prd/rfc/ship work and the exact command to resume it. Derives an open-work board from artifact frontmatter; a SessionStart hook auto-surfaces it so context survives /clear.
orientationCache testing across browser, CDN, proxy, application and data-store layers: Redis, CDN purges, Varnish VTC tests, and cache-key collision audits. Covers RFC 9111 HTTP caching, Cloudflare / Fastly / CloudFront purge APIs, browser Cache-Control tests, and cache-coherence patterns with stampede and stale-while-revalidate references. A detector agent (cache-key-collision-detector) finds keys missing a tenant, user or locale discriminator.
backend-distributedDesign workflow in the RFC tradition: problem -> alternatives -> tradeoffs -> design -> risks -> recommendation -> impl plan. Two sizes with hard ceilings.
planningThis plugin is for network operations engineers who wish to tune and publish IP geolocation feeds in RFC 8805 format. It consists of an AI Skill and an associated MCP server that geocodes geolocation place names to real cities for accuracy.
Use when you need to design, review, or improve REST APIs with Quarkus REST (Jakarta REST) — including resource classes, HTTP methods, status codes, request/response DTOs, Bean Validation, exception mappers, optional runtime OpenAPI exposure (SmallRye), contract-first generation from OpenAPI, content negotiation, pagination, sorting and filtering, API versioning, idempotency (Idempotency-Key), optimistic concurrency (ETag / If-Match), HTTP caching (Cache-Control), API deprecation (Sunset / Deprecation headers), RFC 7807 Problem Details, ISO-8601 for time in contracts, and security-aware boundaries.
Explores a codebase for architectural friction through the lens of Ousterhout's deep-module principle (small interface, large implementation). Seven-step interactive workflow: an Explore sub-agent navigates the codebase organically — the friction it experiences IS the signal. Surfaces candidate clusters with coupling reasons, call patterns, shared types, dependency categories, and existing tests that a boundary test would replace. User picks what to explore, frames the problem, then 3–4 parallel sub-agents design competing deep-module interfaces. Chosen design becomes a structured RFC action file readable by GitHub MCP or ROVO (Jira) MCP. Use when the user says "arch review", "find shallow modules", "module depth", "deep module", "Ousterhout", "testability audit", "surface coupling", "design interfaces", "RFC issues", or "architectural friction".
