11 plugins from public Claude Code marketplaces. Each one bundles skills, slash commands, agents, hooks or MCP servers that install together.
Showing 11 plugins that match these filters.
air-gapped-marketplaceair-gapped/skills1
smartclidwgx/SmartCLI1Submit the repo with .claude-plugin/marketplace.json and we list every plugin.
Submit marketplaceGate 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.
UX writing & content design skills: Microcopy Writer, Error Message Writer, Empty State Writer, Product Naming, Content Style Guide, and Onboarding Copy. The small words that make a product clear, usable, and on-voice.
10 working methods for ui ux: empty-and-error-states, information-architecture, interaction-design, onboarding-ux, and more
Frontend specification planning frameworks. Use when a spec touches UI components, forms, client state, or user-facing flows. Covers UI-state completeness (loading, error, empty, success), component boundaries, form validation contracts, state ownership, and measurable UI success criteria.
LiteLLM proxy operator suite — multi-pod Redis/Valkey coordination (the silent per-pod-fallback failure mode, the 4-way coordination-Redis resolution order incl. the undocumented general_settings.coordination_redis block since v1.93.0, Sentinel/Cluster support matrix with fix versions, per-pod-vs-shared truth table with real staleness bounds, no-op documented knobs, open-issue catalog) and the management REST API (447-path control plane, ~63% undocumented; the four 'empty means unlimited' footguns, budget semantics traps, presence-sensitive updates that trigger spurious enterprise 403s, config-vs-DB precedence, recon-first protocol via GET /routes).
inferenceThree terminal Agent Skills over one pluggable PTY+pyte core: drive-tui (drive interactive TUIs via perceive-decide-act-wait-confirm), cmd-art (design terminal visual effects and ASCII art with the fx engine), and tui-ui (web-like cell-accurate terminal layout engine + widgets emitting tmux-safe ANSI frames).
developer-toolsThe de-slop skill: removes AI-slop (empty hedging, listicle stems, filler) and rewrites toward a real point of view; self-scores against an embedded rubric and flags hollow spans rather than fabricating.
All 24 protein design skills
Diagnose and recover a scrape that is blocked, throttled, or served empty or partial content, in cost order, before paying for a heavier Actor. Use when a run returns 0 items, when a site answers 403, 429 or a challenge page, when the HTML comes back empty or truncated, when a request fails with no response at all, when the page shows data in a browser that the Actor does not see, or when a scraper that worked yesterday suddenly returns nothing. Triggers - "I'm getting blocked", "403 from the site", "429 rate limited", "Cloudflare challenge", "scraper returns empty results", "connection reset", "page loads in my browser but not in the Actor", "do I need residential proxies", "should I switch to a browser", "my scraper broke overnight". Escalates in cost order - a cheaper published source first, then reachability, request rate and IP spread, request fidelity, session tokens, the site's own internal API, browser last.
Start from what the customer is trying to do and end at a screen someone could build. Journey, copy, flows, visual craft — and a reviewer that asks about the empty state and the focus ring you forgot.
design
When the user wants to optimize post-signup onboarding, user activation, first-run experience, or time-to-value. Also use when the user mentions "onboarding flow," "activation rate," "user activation," "first-run experience," "empty states," "onboarding checklist," "aha moment," or "new user experience." For signup/registration optimization, see signup-flow-cro. For ongoing email sequences, see email-sequence.
