Genel Claude Code pazaryerlerinden 10 eklenti. Her biri birlikte yüklenen beceriler, eğik çizgi komutları, ajanlar, kancalar veya MCP sunucuları içerir.
coaltippleTheColliery/CoalTipple1
wayfinder-mapsrengwu/wayfinder-maps1.claude-plugin/marketplace.json içeren depoyu gönderin, biz de her plugini listeleyelim.
Marketplace gönderTest process and strategy: risk-based testing, test strategies, Definition of Done, smoke gates, test pyramid balance, effort estimates and post-mortems. Also covers E2E suite budgets, test ideas from stories and live features, framework choice, and attack-surface checklists. Agents (release-readiness-checker, quality-coach, release-engineer) run multi-gate go / no-go checks, audit work against the Definition of Done, and walk a release runbook with human gates.
foundations88 curated skills (incl. workspace-mode for cross-repo flows), 30 composite slash commands, 14 specialist subagents with per-agent model + reasoning-effort tuning, and 10 hook scripts that quietly enforce discipline (confirm-to-commit on protected branches, destructive-git gating, no AI-attribution trailers in commits/PRs, dependency pre-flight, iron rules injected at session start). Covers the whole SDLC — including post-PR: CI diagnosis, releases, dependency audits, live incident response. Drives the senior-IC loop end-to-end via /orc:flow — workspace-aware: from a parent dir with multiple sibling repos, one flow spans them all with N linked PRs.
Reviews outside counsel invoices against billing guidelines, flags non-compliant entries by category, and produces the documents needed to approve, reduce, reject, and communicate those decisions. Covers the full invoice compliance workflow: line-item review through to formal firm escalation. Works with or without an e-billing platform. Where an e-billing system is in place, LEDES format and UTBMS coding are hard gates. Where there is no e-billing system, invoice submission by email is the channel and UTBMS coding is a best-efforts flag.
161 agent skills, 63 slash commands, 6 subagents for Claude Code, effort-routed for Opus 5.5. Install: /plugin install kenji@kenji
Model/effort router: delegate a task you CAN do but is large+cheap DOWN to a lower tier to save tokens; escalate a task beyond the current tier UP for quality — up to the fable rung, the top of the ladder (a consent-gated, real-money spawn). Two-knob routing (tier × effort, effort-before-tier), an alias-floor tier ranking (haiku<sonnet<opus<fable + modelTiers pins) the platform resolves at spawn-time, a validity-gated ranking Lock that never routes on broken state, and git-optional damage control. Advise-only Phoenix-pure hook; the model performs the routing. Claude Code only.
Plan huge, foggy efforts as a shared map of investigation tickets (.plan/), plus the skills the method leans on. Original skills by Matt Pocock (github.com/mattpocock/skills). The repo also ships the read-only map viewer binary.
Use when you need to analyze Java profiling data collected during the detection phase — including interpreting flamegraphs, memory allocation patterns, CPU hotspots, threading issues, systematic problem categorization, evidence documentation with profiling-problem-analysis and profiling-solutions markdown files, or prioritizing fixes using Impact/Effort scoring.
Research, spy on, and analyze ads across Meta (Facebook & Instagram), Google (Ads Transparency Center + paid search results), TikTok (Ads Library + Creative Center), LinkedIn Ad Library, and X (Twitter — promoted tweets, best-effort) using Apify Actors. Use when user asks about competitor ads, ad library research, winning creatives, ad copy analysis, landing page audits from ads, cross-platform ad audits, brand transparency checks, or any task involving paid ad creatives, advertiser data, or ad targeting from public ad libraries.
Generic effort model for TYPO3 LTS upgrades: per-version risk multipliers (v14 Fluid 5 strict VHs, HashService removal, TSFE removal, asset-pipeline removal), breaking-change baselines, compatibility matrix, Rector coverage adjustments, 7-phase assessment workflow. Pair with team history.
Use for prioritization, or when there are more tasks than capacity: "what should we do first?", "rank this backlog", "cut scope for the MVP", "RICE score these". Picks a method (RICE, ICE, MoSCoW, impact-effort), scores items and sets a cut line. Skip for choosing between two designs.
