Claude Code plugins
28 plugins from public Claude Code marketplaces. Each one bundles skills, slash commands, agents, hooks or MCP servers that install together.
Showing 28 plugins that match these filters.
28 plugins from public Claude Code marketplaces. Each one bundles skills, slash commands, agents, hooks or MCP servers that install together.
Showing 28 plugins that match these filters.
Submit 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.
Twelve-skill bundle covering the Agricultural Systems manuscript lifecycle, centered on systems analysis and modelling — whole-farm and food-system interactions, trade-offs, model description and evaluation, and decision support.
academicTwelve CHI-specific skills for human-computer interaction conference strategy, grounded in the CHI 2027 Papers call, review-process pages, SIGCHI accessibility and video guides, and ACM open-access policy.
academicTwelve HRI-specific skills for the ACM/IEEE International Conference on Human-Robot Interaction and its interdisciplinary, human-subjects-centered evidence culture, grounded in the HRI 2026/2027 calls, humanrobotinteraction.org, the ACM Digital Library, IEEE Xplore, and dblp.
academicTwelve-skill bundle covering the Social Psychology Quarterly (SPQ) manuscript lifecycle across sociological social psychology — self and identity, social structure and personality, group processes, symbolic interaction, status, and affect.
academic21 design-method skills for people and agents: evidence, prototypes, tokens, typography, semantic interactions, scroll stories, optional sound, reviews, and framework adaptation.
designAutomates browser interactions for web testing, form filling, screenshots, and data extraction
developmentApple's Xcode 27 bundled agent skills: SwiftUI, App Intents, Siri integration and evaluations, app resizability, macOS touch gestures, Swift Testing, C bounds safety, security build settings, accessibility audits, String Catalog translation, device interaction, xctrace profiling.
Analyzes how multiple regulations interact for a specific product, service, or business model. Identifies where obligations overlap, reinforce, complement, duplicate, or conflict; builds a priority matrix; produces an integrated compliance timeline; and estimates the total compliance burden. Use when (1) scoping a new product or service against the full regulatory landscape before launch, (2) conducting M&A due diligence on a target's multi-regulation exposure, (3) building a strategic compliance roadmap where single-regulation analyses miss the interactions, (4) advising on complex situations where regulations touch the same conduct from different angles, or (5) estimating budget and resourcing for multi-regulation compliance. Primary coverage of EU digital regulation (GDPR, Data Act, AI Act, CRA, NIS2, DORA, DMA, DSA, ePrivacy) and national implementations; the framework extends to any jurisdiction where overlapping regulatory regimes apply to the same activity.
Framework for demonstrating AI capabilities in legal contexts. Provides detailed personas across tenant law, business contracts, startup disputes, employment claims, and consumer protection with progressive complexity scenarios. Use when: (1) Demonstrating AI-powered legal triage or intake systems, (2) Showcasing responsible AI-assisted client interactions, (3) Training staff on appropriate AI use in legal contexts, (4) Creating realistic scenarios for legal tech presentations, (5) Developing educational materials about AI in legal services, or (6) Testing AI-powered legal information systems in controlled environments.
Load and performance testing with k6 and JMeter, Lighthouse CI for Web Vitals, SLO-driven load plans, and performance budget gates. Covers tool choice and load profiles (with Gatling and Locust references), per-interaction INP budgets, flame-graph analysis, and database query-plan analysis.
operations-resilience10 working methods for ui ux: empty-and-error-states, information-architecture, interaction-design, onboarding-ux, and more
Assess whether a Fundamental Rights Impact Assessment (FRIA) is required under Article 27 EU AI Act, and structure or draft that assessment for a specific high-risk AI deployment. Covers deployer scope gating (public bodies and private entities providing public services), affected group mapping, Charter rights analysis, proportionality, safeguards evaluation, residual risk, DPIA/FRIA interaction, notification under Article 27(3), and DACH-specific considerations. Use when asked about FRIA obligations, Article 27 scope, fundamental rights and AI, or deployer assessment duties.
Briefs statutes and legislative Acts using the MAPS + RULES framework: a system-level map of the whole Act (citation and text status, purpose, structure, scope, definitions) plus operational rule-modules for each operative provision (elements, legal effect, exceptions, procedure, consequences, forum, interaction rules). Works from statutory text supplied by the user and never invents statutory language. Use when briefing a statute, analyzing legislative text, mapping statutory architecture, extracting the elements of a provision, or applying a statute to facts. Triggers on "brief this statute", "analyze this Act", "map the statute", "apply [statute] to [scenario]", "what are the elements of [provision]", "statutory analysis", and on references to codified sections such as 42 U.S.C. or the Texas Health and Safety Code. Two modes: (A) text-only briefing for structural analysis, and (B) scenario-driven briefing that applies provisions to specific facts with verbatim quotation and pinpoint
CLI design for AI agents — evaluate, design, and refactor CLIs so they reliably serve humans, AI agents, and orchestration systems simultaneously. Structured output, self-description, delegated auth, safety tiers, and a complete 8-phase interaction loop.
Affordance, feedback, errors, and user control. Covers Fitts's Law, Affordance, Forgiveness, Feedback Loop, Errors, Constraint, Mapping, Expectation Effect, and Control.
designMaestro mobile E2E testing - YAML flows, selectors, flow control, environment variables, JavaScript expressions, device interactions, Maestro Studio, Maestro Cloud CI, tags, test suites
Storybook patterns - CSF 3.0, args, controls, autodocs, play functions, interaction testing, visual testing, addons configuration
Create comprehensive brand identity documentation for any brand. Guides you through documenting strategy, visual identity (logo, color, typography, imagery), voice and tone, customer-centered messaging handoffs, application guidelines, governance, and asset inventory. Produces markdown specs, compiled brand books, and brand-compliant images via reference-image-aware generation. Use when you need to capture a brand's identity in structured, durable form — for vault storage, agency handoff, or press kit distribution. Do not use for market positioning decisions or conversion experiments; use go-to-market. Route interaction behavior to product-design-and-ux.
Define user-facing product behavior from validated evidence and approved scope. Use for information architecture, task flows, state and recovery models, interface contracts, usability-study plans, interaction-pattern tradeoffs, AI recommendations and generated outputs, uncertainty, human control, feedback, or engineering UX handoffs. Use after product discovery and product decisions; route WCAG/ARIA conformance work to web-accessibility and formal software specifications to spec-driven-development. Do not use this skill for unrelated requests; route to the nearest named specialist.