claude-wordpress-skills

왜 쓰나요

핵심 기능

WordPress Coding Standards (WPCS) baked in
Gutenberg block development with modern tooling
Security patterns: nonces, capabilities, sanitization, escaping
Performance: object cache, transients, query tuning
Theme/plugin packaging, i18n, accessibility checklists

라이브 데모

실제 사용 모습

claude-wordpress-skill.replay ▶ 준비됨

0/0

설치

작성자 저장소 · Claude Skills 공식 문서

사용 사례

실전 활용법: claude-wordpress-skills

How to build a Gutenberg block the modern way

👤 WordPress developers building custom blocks ⏱ ~45 min intermediate

언제 쓸까: You need a custom editor block and don't want to hand-roll outdated ESNext + webpack scaffolding.

흐름

Describe the block

Build a Testimonial block: quote text, author name, author photo — edit and save views.✓ 복사됨

→ block.json + edit.js + save.js scaffolded, @wordpress/scripts build setup
Add attributes and controls

Add an alignment control and a color picker.✓ 복사됨

→ BlockControls / InspectorControls added correctly
Bundle and register

Write the PHP that registers the block from block.json.✓ 복사됨

→ register_block_type( __DIR__ . '/build/block.json' )

결과: A working modern Gutenberg block with proper packaging.

함정

Missing i18n wrappers — Skill reminds Claude to wrap strings with __() and _x()

함께 쓰기: filesystem

Audit a plugin for common WordPress security issues

👤 Plugin maintainers, site owners ⏱ ~60 min advanced

언제 쓸까: Before shipping a plugin or inheriting one.

흐름

Scope the audit

Audit this plugin for: nonce usage on every form, capability checks on every action, output escaping, SQL prep.✓ 복사됨

→ Per-category findings with file:line
Fix the highest-risk ones

Apply the top 3 fixes — nonces on the admin form, esc_html on the dashboard widget, $wpdb->prepare on the custom query.✓ 복사됨

→ Diffs to the plugin files
Regression test

List what to manually test to confirm the fixes don't break anything.✓ 복사됨

→ Short manual test checklist

결과: A more secure plugin with documented fixes.

함정

False positives on nonces where a REST permission callback is already in place — Provide context: REST routes with permission callbacks don't need form nonces

함께 쓰기: github

Do a performance pass on a slow WordPress site

👤 Developers responsible for WordPress site perf ⏱ ~60 min advanced

언제 쓸까: TTFB is bad, dashboard is slow, or a specific template is dragging.

흐름

Identify the bottleneck

Walk me through common WordPress perf bottlenecks and which log/profiling tool to start with.✓ 복사됨

→ Query Monitor, debug.log, object cache check
Query tuning

Here are the top 5 slow queries. Suggest indexes or query rewrites.✓ 복사됨

→ Per-query recommendations
Cache strategy

Which caching layers should be active here? Object cache, page cache, fragment caching — suggest a stack.✓ 복사됨

→ Concrete cache plan with plugins/services

결과: Concrete perf wins you can measure on the next deploy.

함정

Adding a caching plugin without fixing the underlying slow query — Always measure before and after each change

조합

다른 MCP와 조합해 10배 효율

claude-wordpress-skill + filesystem

Operate across a plugin/theme directory for audits and refactors

Audit wp-content/plugins/my-plugin/ for security issues and apply the top 5 fixes.✓ 복사됨

claude-wordpress-skill + github

Open PRs for security fixes with proper descriptions

Open a PR titled 'Security: nonces on admin forms' with the patches.✓ 복사됨

도구

이 MCP가 노출하는 것

도구	입력	언제 호출
gutenberg-block-authoring	block intent + attributes	Any custom block work
wp-security-audit	plugin/theme path	Pre-ship or inheritance review
wp-performance-review	slow endpoints + config	When speed matters
wp-coding-standards	any PHP/JS code	Auto-applied during authoring

비용 및 제한

운영 비용

API 쿼터: none
호출당 토큰: 5–20k per audit or block
금액: free
팁: Scope by file or feature; don't feed Claude 100 plugins at once

보안

권한, 시크릿, 파급범위

자격 증명 저장: none at the skill level; WP admin creds if you also use a deploy/REST tool

데이터 외부 송신: none

Security audits are advisory — commission a proper audit for production e-commerce

문제 해결

자주 발생하는 오류와 해결

Block build fails with @wordpress/scripts

Verify Node version and that @wordpress/scripts is in devDependencies; rebuild.

확인: node -v && npx wp-scripts --version

Claude suggests outdated enqueue patterns

Specify the WordPress version you target and prefer register_block_type_from_metadata.

대안