192건 · 관련도순
Expert guide for headless WordPress architecture — WPGraphQL, ACF Pro, Faust.js, Next.js/Astro frontend, webhooks, and caching / Panduan ahli arsitektur WordPress headless.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Uses the WordPress wp-rest-api skill to help an agent design, register, validate, and troubleshoot custom REST routes without skipping schema, auth, or permission_callback details. This is for agent-led endpoint work in plugins, themes, or core-adjacent codebases, not for browsing the WordPress REST API as a product catalog.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Bedrock is a WordPress boilerplate with Composer-based dependency management, environment-specific configuration via .env files, and an improved folder structure. It separates WordPress core from application code for cleaner version control and deployment.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
PHP coding standards and WordPress patterns for ATmosphere plugin. Use when writing PHP code, creating classes, implementing WordPress hooks, or structuring plugin files.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Sets the posture for working on a WordPress site through Respira: report what changed on the site, stay visible during long operations, be honest about limits, and send what Respira cannot do to the founder. Use whenever Respira is mentioned, the user references their WordPress site, or the user wants to edit a site.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when the user says 'analyze my wordpress site', 'what is running on my site', 'site dna', or 'what plugins are on my site'. Detects every page builder, audits active versus dead-weight plugins, maps content structure, finds orphaned shortcodes, and checks performance and security posture.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when the user says 'clean up my wordpress', 'what is bloating my wordpress', 'find orphaned shortcodes', or 'scan for unused plugins'. Audits orphaned shortcodes from deleted plugins, unused plugins, database bloat, unused media, and leftover data from inactive builders.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when the user says 'optimize my wordpress images with ai', 'compress and optimize all images', 'audit my media library', or 'improve image performance'. Downloads images, compresses, converts to WebP, resizes and renames locally, re-uploads, and updates every content reference.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when exposing a WordPress site to AI agents via MCP, or when WordPress MCP setup fails.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Analyze GTmetrix (and PageSpeed) reports for WordPress sites and produce a prioritized optimization plan, a custom WPCode-ready PHP optimization snippet, and a self-contained HTML summary report. Covers PDF report extraction with pypdf, live-page cross-referencing, WordPress-specific fix mapping (Elementor, WooCommerce, Breeze, reCAPTCHA, Google-tag duplication, WebP conversion), and staging-test discipline. Use when asked to review GTmetrix reports, optimize page speed or Core Web Vitals, create a custom performance optimization snippet, or produce an optimization report for a WordPress site.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Audit page descriptions used for search results, identify text reused across URLs, and write descriptions specific to each page. Review CMS settings and shared templates so each route outputs its own description in the final HTML.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Connect a CMS to notfair SEO tools. Guides users through configuring WordPress, Strapi, Contentful, or Ghost — tests the connection, and writes credentials to .env.local. Once set up, seo-analysis automatically cross- references CMS content against Google Search Console data. Use whenever the user says "connect my CMS", "set up WordPress", "configure Strapi", "add Contentful", "connect Ghost", or "CMS setup". Also trigger if the user asks why no CMS data appears in a seo-analysis report.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Extract, suggest, and sync tags and categories for blog posts across all major CMS platforms. Supports WordPress REST API, Shopify GraphQL, Ghost Content API, Strapi REST/GraphQL, and Sanity GROQ. Generates tag suggestions from content analysis (keyword frequency, heading extraction, semantic grouping), enforces minimum post-count thresholds to prevent thin tag archives, and syncs taxonomy via authenticated API calls. Use when user says "tags", "categories", "taxonomy", "tag suggestions", "sync tags", "WordPress tags", "Shopify tags".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Suggest tags and categories for a blog post from its content, audit a site's tag and category health, and, only after the user approves a shown plan, sync tags and categories to WordPress, Shopify, Ghost, Strapi, or Sanity. suggest and audit are read-only; sync is dry-run by default and never deletes, merges, or edits post content. Use when the user says "tag suggestions", "taxonomy audit", "sync tags", "WordPress tags", "Shopify tags". Not for keyword research (blog-brief) or schema markup (blog-schema).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Verify a WordPress plugin's Abilities API registrations: enumerate abilities, check that callback behavior matches each annotation's claim (the adversarial readonly-but-writes detection), validate permissions and schemas, and validate audit documents produced by wp-abilities-audit.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when developing WordPress plugins: architecture and hooks, activation/deactivation/uninstall, admin UI and Settings API, data storage, cron/tasks, security (nonces/capabilities/sanitization/escaping), and release packaging.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when building UIs leveraging the WordPress Design System (WPDS) and its components, tokens, patterns, etc.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when developing WordPress block themes: theme.json (global settings/styles), templates and template parts, patterns, style variations, and Site Editor troubleshooting (style hierarchy, overrides, caching).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Audit a WordPress plugin's REST surface and produce a standardized audit document proposing Abilities API registrations. Produces a markdown doc with a YAML schema and prose sections that humans and agents can both consume when planning a registration rollout. Works on any WP plugin.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when working with WP-CLI (wp) for WordPress operations: safe search-replace, db export/import, plugin/theme/user/content management, cron, cache flushing, multisite, and scripting/automation with wp-cli.yml.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Pattern: create or update WordPress block patterns (starter pages, templates, template parts, Query Loop layouts), review pattern registration, block markup, categories, accessibility, or i18n/escaping, or improve pattern design quality. Route custom blocks to wp-block-development; route frontend interactivity to wp-interactivity-api.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when investigating or improving WordPress performance (backend-only agent): profiling and measurement (WP-CLI profile/doctor, Server-Timing, Query Monitor via REST headers), database/query optimization, autoloaded options, object caching, cron, HTTP API calls, and safe verification.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when the deliverable is WordPress Playground Blueprint JSON or a Blueprint bundle, including creating, editing, reviewing, validating schema keys, choosing steps/resources, and debugging Blueprint files. For only running or sharing a Playground environment, use wp-playground.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when building, extending, or debugging WordPress REST API endpoints/routes: register_rest_route, WP_REST_Controller/controller classes, schema/argument validation, permission_callback/authentication, response shaping, register_rest_field/register_meta, or exposing CPTs/taxonomies via show_in_rest.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.