Loading...
Loading...
Found 95 Skills
Use when starting a new WooCommerce extension, setting up plugin headers, checking WooCommerce availability, declaring HPOS and block checkout compatibility with FeaturesUtil, or understanding WooCommerce extension architecture. Covers Requires Plugins header, WC requires at least, WC tested up to, before_woocommerce_init, declare_compatibility for custom_order_tables and cart_checkout_blocks, plugins_loaded initialization, class_exists WooCommerce check, and Interactivity API store privacy (lock true).
Use when developing custom Checkstyle checks, filters, and plugin integrations for project-specific Java code standards.
Use when working with WordPress core APIs in plugins or themes. Covers add_menu_page, add_submenu_page, add_options_page, add_shortcode, add_meta_box, register_post_type, register_taxonomy, HTTP API (wp_remote_request, wp_remote_get, wp_remote_post), wp_schedule_event (WP-Cron), wp_add_dashboard_widget, users and roles (add_role, current_user_can), privacy tools (wp_register_personal_data_exporter), theme mods, site health API, global variables ($wpdb, $post, $wp_query), add_image_size, responsive images, and advanced hooks (do_action, apply_filters, remove_action).
Develop custom WebF native plugins based on Flutter packages. Create reusable plugins that wrap Flutter/platform capabilities as JavaScript APIs. Use when building plugins for native features like camera, payments, sensors, file access, or wrapping existing Flutter packages.
Guide for creating and validating Claude Code plugin.json files. Use when creating plugins, validating plugin schemas, or troubleshooting plugin configuration.
Use when creating, adding, or modifying plugins in this Glean Claude Plugins marketplace repository. Triggers on "create plugin", "add plugin", "new plugin", "plugin checklist", "marketplace", or when working with plugin.json, marketplace.json, or the plugins/ directory. Ensures all required files are updated correctly.
Develops custom FiftyOne plugins (operators and panels) from scratch. Use when creating plugins, extending FiftyOne with custom operators, building interactive panels, or integrating external APIs.
Use when creating, modifying, or debugging Claude Code plugins. Triggers on .claude-plugin/, plugin.json, marketplace.json, commands/, agents/, skills/, hooks/ directories. Provides schemas, templates, validation workflows, and troubleshooting.
Write, refactor, and debug Joplin plugins for desktop/mobile using the official Joplin plugin architecture, API, and manifest rules. Use when a user asks to create a new Joplin plugin, add features to an existing plugin, build CodeMirror/editor extensions, fix plugin loading/runtime errors, prepare manifest/package output, or align implementation with official docs from laurent22/joplin and joplin/plugins.
Generate Orderly SDK plugin scaffolding with unique ID, registration boilerplate, and typed interceptors. Use when the user mentions creating, developing, registering, implementing, or generating a plugin (e.g. 'create a plugin', 'generate a plugin', 'develop a plugin', 'register a plugin', 'implement a plugin', 'build a plugin', 'add a plugin', 'scaffold a plugin', 'new plugin').
Create a new plugin for Claude Code marketplace with validation, ADR, and release automation. TRIGGERS - create plugin, new plugin, scaffold plugin, add plugin, plugin-dev create.