9 plugins de marketplaces públicos do Claude Code. Cada um agrupa skills, slash commands, agents, hooks ou MCP servers que são instalados juntos.
specpowers-marketplaceSAXEM1997/specpowers1
muto-atlasB7Kompirine/muto-atlas1Envie o repo com .claude-plugin/marketplace.json e nós listaremos cada plugin.
Enviar marketplaceBuild, debug, profile, test, refactor, and release Swift apps across iOS, macOS, Xcode, SwiftUI, SwiftPM, Tuist, and App Store Connect.
developmentRuns 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.
developmentFive-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.
developmentFuses OpenSpec (SDD) and Superpowers (TDD) into a complete Phase 0→4 workflow with multi-model progressive review, UltraReview gates, and convergence tracking. Use when starting any non-trivial development task.
developmentGround truth for FiveM/GTA V development. 24 offline data layers built from your own GTA V install and FiveM server: natives with apiset resolution and a Lua linter, archetypes, world placements, vanilla animation names, skeleton bone tags, vehicles, weapon components, peds, MLO interiors, embedded lights, weather timecycles, and your server's framework API. It checks your own files before the game sees them, decodes and edits prop lights against a measured vanilla reference, and covers parallax shaders and vanilla interior measurements. Nothing is guessed; a file that could not be inspected is never reported as clean.
developmentCoordination layer for multi-agent repositories. Gives task-pipeline runs leases with a TTL, race-free ID reservation, a cross-repo signal feed, an append-only run journal and a machine-generated read-only board. A lease is decided by a primitive that genuinely has compare-and-swap — an atomic file create on one machine, a pushed git ref across machines — never by the knowledge base, which loses concurrent writes; the store carries the record and the ID allocation, which is positional over the merged log. The knowledge backend is a pluggable adapter (Outline, filesystem) declaring its own capabilities and degrading out loud. Ships Claude Code hooks that deny edits to guarded registry files without a live lease.
developmentDesign, generate, and run multi-agent AI pipelines — scope-aware, multi-pipeline, spec-driven, write/review-isolated, with step-level create/update/delete and integrated audit
developmentUse when navigating or refactoring code with a language server - choosing between semantic (LSP), exact-text (rg), and fuzzy/semantic search; anchoring LSP calls by position; gating degraded results; and disclosing tool substitutions, in any language.
development
