plugin▌

Secure WordPress plugin development with hooks, database interactions, Settings API, custom post types, and REST API. \n \n Covers three architecture patterns (Simple, OOP, PSR-4) plus the Security Trinity (sanitize input, validate logic, escape output) with 29 documented vulnerability prevention patterns \n Includes critical security foundations: unique prefixes, ABSPATH checks, nonce verification, prepared statements, and capability checks with real 2025-2026 CVE examples \n Addresses WordPres

Store per-project plugin configuration and state in .claude/plugin-name.local.md files with YAML frontmatter. \n \n Settings files use YAML frontmatter for structured configuration and markdown body for additional context or prompts \n Hooks, commands, and agents can read settings to customize behavior without requiring code changes \n Includes bash parsing patterns for extracting individual fields (strings, booleans, numerics) and markdown body content \n Common patterns include toggling hook a

Standardized directory structure and manifest configuration for Claude Code plugins with automatic component discovery. \n \n Conventional layout with auto-discovery: commands, agents, skills, and hooks load automatically from standard directories without explicit registration \n Manifest-driven configuration in .claude-plugin/plugin.json supporting metadata, custom component paths, and optional MCP server definitions \n Portable path references using ${CLAUDE_PLUGIN_ROOT} environment variable f

Complete WordPress plugin development workflow from architecture through security and release packaging. \n \n Covers plugin structure, hooks/actions/filters, activation/deactivation/uninstall lifecycle, and Settings API for admin UI and options management \n Includes mandatory security baseline: input validation/sanitization, nonces, capability checks, and parameterized SQL queries via $wpdb->prepare() \n Supports data storage patterns, cron task setup with idempotency, and schema migrations wi

Per-project plugin configuration stored in YAML frontmatter and markdown files within the .claude/ directory. \n \n Settings files use .claude/plugin-name.local.md format with YAML frontmatter for structured config and markdown body for additional context or prompts \n Hooks, commands, and agents can read settings to customize behavior; quick-exit pattern checks file existence and enabled flag to skip when not configured \n Parsing techniques provided for extracting individual fields (strings, b

Generate TypeSpec API plugins for Microsoft 365 Copilot with REST operations, authentication, and Adaptive Cards. \n \n Scaffolds complete TypeSpec projects with agent definitions (main.tsp) and API operations (actions.tsp) following Microsoft 365 Copilot conventions \n Supports four authentication modes: public APIs, API key headers, OAuth2 with authorization code flow, and registered auth references \n Includes optional confirmation dialogs for destructive operations and Adaptive Card template

Claude Code plugins follow a standardized directory structure with automatic component discovery. Understanding this structure enables creating well-organized, maintainable plugins that integrate seamlessly with Claude Code.

Creates dashboard plugin extensions for Wix CLI applications. Dashboard plugins are interactive widgets that embed into predefined slots on dashboard pages managed by Wix first-party business apps (Wix Stores, Wix Bookings, Wix Blog, Wix eCommerce, etc.).

Scaffold, structure, and manage Claude Code plugins with automated manifest generation and version control. \n \n Includes Python scripts for creating plugins and bumping semantic versions across both plugin.json and marketplace.json manifests \n Supports four component types: commands (with namespace-based naming), skills, agents, and hooks, each with defined directory structures \n Provides three plugin patterns (framework, utility, domain) with reference documentation covering structure, mark

$22