wp-plugin-options-storage

What problem does it solve?

WordPress plugin developers often choose storage primitives poorly, worsening performance, complicating migrations, and polluting autoload footprints. This skill provides a structured approach to selecting the correct persistence mechanism (options, meta, transients, site options, or a custom table) and guides how to architect durable, scalable storage for plugin-owned data.

Core Features & Use Cases

• Guidance on when to use each storage primitive (options vs meta vs transient vs site option vs custom table) across single-site and multisite scenarios.
• Best practices for grouping plugin settings into one option, managing autoload, and applying consistent naming conventions.
• Multisite caveats, audits, and migration patterns to avoid performance pitfalls and data skew.

Quick Start

Identify the plugin data you need to persist and select the most appropriate storage primitive, then document the choice with justification.