Spec-driven development for existing WordPress sites
On client sites, agents write plausible code against a stack that is not there. Specs help when they record what your WordPress install actually runs. These are the facts I pin down first.
Category: AI in WordPress
WordPress Guidelines stores agent memory as plain content
WordPress Guidelines keeps agent memory, skills and instructions in an ordinary custom post type, and it’s headed for Core. Here’s what that means for plugins with their own memory stores, which permissions to test first, and when a separate table still makes sense.
AI agent cost optimization is a modeling problem
Agent features drift from one helper to a sprawl nobody can put a price on. This post maps four operations research models onto real decisions, like which agents to build and how to route requests, then covers where the solver should live on a WordPress site.
What to check before you run WooCommerce AI Product Advisor
WooCommerce’s beta AI Product Advisor ranks your catalog and suggests copy fixes. The ranked queue and revert log are the useful parts. The WordPress.com connection and the lift math are where it bites, so stage it, clear stray output first, and apply in small batches.
WooCommerce AI analytics should ask, not count
An AI chat over your WooCommerce orders will hand you confident numbers that don’t match Analytics. Let the model pick the question and let your code answer it. Here’s how I’d wire that with one REST endpoint and a strict args schema.
Why your enterprise RAG architecture fails, and the four-brick fix
Naive RAG wrappers that just chunk PDFs into a vector store break on real contracts and reports. Here is the four-brick approach I use instead: structured parsing, question parsing with an expert dictionary, filtered retrieval, and typed generation.
Prompt engineering isn’t enough: you need an LLM control layer
Tightening the prompt won’t make an LLM integration reliable in production. Here’s the control layer I put between WordPress and the model: input guards, a circuit breaker, response validation and retries.
Practical AI transparency patterns for WordPress interfaces
A spinner tells users nothing when an AI agent takes 20 seconds to think. These are the patterns I use instead: specific status updates, a thinking toggle, checklists that handle partial success, and a saved audit trail.
WordPress Core AI leadership changes on the road to 7.0
Felix Arntz and James are stepping back as Core AI Team Reps, and Jason Adams takes over. The handover lands as the Abilities API matures and the WP AI Client heads into core for WordPress 7.0.
3 Claude skills worth learning as a data scientist in 2026
Using Claude for data science now goes well past chat prompts. Three skills I’d pick up: throwaway interactive dashboards for EDA, Claude Cowork for Jira and reporting chores, and Claude Code for tracing broken dbt pipelines.