wordpress

WordPress CMS development with themes, plugins, and Gutenberg. Use for content sites.

7 stars

byG1Joshi

View on GitHub Installation ↓

Best use case

wordpress is best used when you need a repeatable AI agent workflow instead of a one-off prompt.

WordPress CMS development with themes, plugins, and Gutenberg. Use for content sites.

Teams using wordpress should expect a more consistent output, faster repeated execution, less prompt rewriting.

When to use this skill

You want a reusable workflow that can be run more than once with consistent structure.

When not to use this skill

You only need a quick one-off answer and do not need a reusable workflow.
You cannot install or maintain the underlying files, dependencies, or repository context.

Installation

Claude Code / Cursor / Codex

$curl -o ~/.claude/skills/wordpress/SKILL.md --create-dirs "https://raw.githubusercontent.com/G1Joshi/Agent-Skills/main/skills/frameworks/wordpress/SKILL.md"

Manual Installation

Download SKILL.md from GitHub
Place it in .claude/skills/wordpress/SKILL.md inside your project
Restart your AI agent — it will auto-discover the skill

How wordpress Compares

Feature / Agent	wordpress	Standard Approach
Platform Support	Not specified	Limited / Varies
Context Awareness	High	Baseline
Installation Complexity	Unknown	N/A

Frequently Asked Questions

What does this skill do?

WordPress CMS development with themes, plugins, and Gutenberg. Use for content sites.

Where can I find the source code?

You can find the source code on GitHub using the link provided at the top of the page.

SKILL.md Source

# WordPress

WordPress 6.6 (2025) continues the **Full Site Editing (FSE)** revolution. Everything is a block.

## When to Use

- **Content Sites**: Blogs, News, Marketing sites.
- **Client Handoff**: Clients know the WP Admin interface.
- **E-commerce**: WooCommerce is standard.

## Core Concepts

### Gutenberg (Block Editor)

React-based editor. `blocks` are the unit of content.

### Themes (Block Themes)

composed of `html` parts and `theme.json`, reducing PHP usage.

### Plugins

The ecosystem hook system (actions/filters).

## Best Practices (2025)

**Do**:

- **Use `theme.json`**: For defining global styles.
- **Use Bedrock**: For 12-factor (Git-controlled) WordPress.
- **Use Headless**: WP as an API (GraphQL) + Next.js frontend if needed.

**Don't**:

- **Don't edit core**: Never touch `wp-includes`.

## References

- [WordPress Developer](https://developer.wordpress.org/)