wordpress-legacy

Enforce WordPress coding standards and security practices for themes and plugins.

2|1|Updated Jan 20, 2026
One-click install
npx skills add https://github.com/sraloff/gravityboots --skill wordpress-legacy
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: wordpress-legacy
Source: https://github.com/sraloff/gravityboots/tree/main/.agent/skills/wordpress-legacy
Command: npx skills add https://github.com/sraloff/gravityboots --skill wordpress-legacy

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

WordPress developers often struggle to maintain consistent coding standards, secure practices, and maintainable plugin/theme code across projects.

Core Features & Use Cases

  • Enforce WordPress coding standards (snake_case naming, slug-prefixed functions/classes) and mandatory escaping and sanitization.
  • Provide security guidance for common tasks: nonce verification, capability checks, and safe data handling.
  • Guide for plugin and theme development, debugging, and secure deployment to reduce common WordPress vulnerabilities.

Quick Start

Begin by reviewing the WordPress legacy guidelines to start a secure theme or plugin project.

Frequently Asked Questions about wordpress-legacy

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I enforce WordPress coding standards for custom plugins and themes?

WordPress coding standards are enforced by applying snake_case naming conventions, slug-prefixed functions, and mandatory escaping. This ensures consistent, maintainable code across custom plugin and theme development projects of any size.

What security best practices should I follow when developing WordPress themes?

WordPress theme security best practices require mandatory escaping, sanitization, nonce verification, and capability checks. Applying these guidelines reduces common vulnerabilities and ensures safe data handling during custom theme development.

How do I add nonce checks and capability checks to a custom WordPress plugin?

Add nonce checks and capability checks by following WordPress security guidance for common tasks. This process specifies requirements for safe data handling, ensuring consistent, maintainable, and safer code for plugin deployments.

Can I use WordPress coding standards for debugging and secure deployments?

Yes, WordPress coding standards apply to plugin and theme development, debugging, and secure deployments. They guide consistent and maintainable code practices for custom features across projects of any size.

What is the best way to prevent common WordPress vulnerabilities in custom code?

The best way to prevent common WordPress vulnerabilities is enforcing mandatory escaping, sanitization, and secure data handling. Following specific coding requirements ensures safer, consistent plugin and theme code.