跳至正文
OpenAgentSkill
浏览已开放 · 目录记录日期 2026-11-21 · 自动更新和账户服务暂时关闭。
设计与 UI

wp-acf-and-content-modeling

WordPress ACF and content modeling review for Codex. Use when reviewing ACF field groups, CPT and taxonomy design, options pages, repeaters, flexible content, relationship fields, ACF JSON sync, and meta-heavy content architecture.

jorgerosal · 已有 AI 审核记录

安装与使用

运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。

npx skills add jorgerosal/wordpress-skills --skill wp-acf-and-content-modeling

技能说明


name: wp-acf-and-content-modeling description: WordPress ACF and content modeling review. Use when reviewing Advanced Custom Fields usage, field group architecture, CPT and taxonomy design, options pages, repeaters, flexible content, block-bound field groups, meta storage patterns, or when user mentions "ACF", "field groups", "flexible content", "repeater", "custom post type design", "taxonomy design", "content model", "relationship fields", "ACF JSON", "options page", or "meta query performance". Detects schema drift, weak content modeling, brittle field naming, and performance issues in meta-heavy WordPress builds.

WordPress ACF and Content Modeling Skill

Overview

Systematic review skill for WordPress projects that rely on Advanced Custom Fields and custom content architecture. Core principle: a healthy WordPress content model is durable, query-aware, editor-friendly, and predictable to migrate. Review focuses on CPT and taxonomy design, field-group boundaries, naming consistency, storage strategy, ACF JSON synchronization, and the long-term cost of meta-heavy patterns. Report findings grouped by file or subsystem with severity labels (CRITICAL, WARNING, INFO), line references where possible, and concrete remediation guidance.

When to Use

Use when:

  • Auditing a plugin or theme that registers custom post types, taxonomies, or ACF field groups
  • Reviewing acf_add_local_field_group() or field group JSON exports
  • Checking whether repeaters / flexible content are the right fit for the content problem
  • Evaluating options pages, relationship fields, clone fields, or block field groups
  • Investigating slow admin screens or expensive meta_query usage in content-heavy builds
  • Planning a new content model for an editorial site, directory, landing-page builder, or headless setup
  • Reviewing ACF JSON sync, field key drift, or environment-to-environment portability

Don't use for:

  • Generic plugin architecture without meaningful ACF/content-model work (use wp-plugin-development)
  • Pure REST route design (use wp-rest-api-development)
  • Gutenberg block implementation details unrelated to field modeling (use wp-block-development)
  • Performance audits not tied to content schema or metadata access (use wp-performance-review)
  • WooCommerce domain modeling (use wp-woocommerce-dev unless the issue is truly generic ACF modeling)

Review Workflow

Follow this seven-step workflow.

  1. Identify the model boundary

    • What is the real domain: articles, locations, staff, products, events, landing pages, settings, or reusable content fragments?
    • Determine whether the model is single-site, multisite, or headless-facing.
    • Inventory CPTs, taxonomies, options pages, and field groups before evaluating implementation quality.
  2. Check core content entities first

    • Validate each CPT has a clear purpose and does not merely duplicate posts/pages without a reason.
    • Check whether taxonomies model classification and relationships better than extra text/meta fields.
    • Flag overloaded post types used as catch-alls for unrelated content.
  3. Review field-group architecture

    • Inspect location rules, naming conventions, instructions, conditional logic, defaults, and required flags.
    • Check whether field groups are split by editorial task instead of becoming giant monoliths.
    • Verify repeaters and flexible content are used intentionally, not as a substitute for missing entity design.
  4. Scan for CRITICAL patterns

    • Field names or data shapes changed without a migration path.
    • Environment-specific field keys relied on directly in code.
    • Content that should be relational or taxonomic stored as plain text blobs.
    • Massive meta_query dependence for core archive/search behavior with no mitigation.
    • Flexible-content or repeater structures used where separate entities are clearly required.
    • Options-page values treated as request-specific content without cache or invalidation awareness.
  5. Check WARNING patterns

    • Ambiguous field names (title, image, link) with no domain prefix or context.
    • Duplicate field groups or cloned definitions drifting across environments.
    • Relationship/post object fields with no return-format consistency.
    • Fields exposed to editors with weak instructions, no defaults, or unclear conditional logic.
    • ACF JSON enabled inconsistently or committed unreliably.
    • Repeater-heavy landing pages likely to become impossible to query, reuse, or migrate.
  6. Note INFO improvements

    • Taxonomies could improve filtering, SEO, or editorial consistency.
    • An options page could replace duplicated per-page settings.
    • A custom table may be justified for high-volume structured data.
    • Shared components may benefit from clone fields or a reusable block strategy.
    • Field instructions, tabs, and groups could reduce editor error rates.
  7. Report with context-aware severity

    • Enterprise/editorial site: prioritize governance, migration safety, query behavior, and authoring ergonomics.
    • Marketing/landing-page builder: prioritize maintainability and editorial constraints over abstract purity.
    • Headless site: prioritize schema stability, API exposure shape, and relationship modeling.
    • Add cross-skill notes when findings should be followed by wp-rest-api-development, wp-performance-review, or wp-block-development.

Model-Level Checks

Content Type Design (ACF-01)

CRITICAL

  • Multiple unrelated business concepts forced into one CPT with flags like type, layout, or kind doing all the work
  • A CPT exists only to simulate grouped fields that belong on an existing content type
  • Important relational content stored in serialized arrays or long text fields instead of structured entities

WARNING

  • CPT labels, supports, or archive behavior do not match editorial intent
  • Post types rely on custom fields for primary titles or slug
阅读完整来源 ↗