FAQ

Frequently Asked Questions

What do I need to start?

A computer with Node.js 18+ installed, a WordPress.com account, and a Claude.ai account (Pro or Team plan recommended for MCP access). Everything else is covered in Day 0. Total setup time: about 20 minutes.

Do I need to be a developer?

No. The program is designed for anyone who works with a WordPress site — creators, marketers, product folks, and developers. You’ll copy-paste commands into a terminal and write prompts in natural language. Days 1-25 require zero coding. Day 26 (custom abilities) is more technical but can be completed as a design exercise — you write specs, your engineering team builds them.

How much time does it take per day?

10-20 minutes per exercise. Some days (like the demo prep on Day 27) take 25-30 minutes. You can do it during your morning coffee.

Do I need a WordPress account?

No. Most exercises work with any WordPress site. WordPress AI plugin features (Days 5, 13, 20) are platform-specific, but the program provides alternative approaches for non-WordPress sites. MCP, Telex, Studio CLI, Playground, and the Abilities API work with any WordPress setup.

What if I can’t install tools or don’t have an API key?

You can still do most of the course. There are three paths, and the first needs nothing but a browser:

  • 🌐 Browser-only (no install, no key): Playground, Telex, and copy-paste with the free Claude.ai cover the large majority of exercises. For any “AI reads/drafts/optimizes my content” step, paste your content into Claude.ai and paste the result back — you lose automatic writing to WordPress, but keep the whole lesson.
  • 🔗 WordPress.com (account, no API key): Studio Code generates AI responses using WordPress.com infrastructure with no key required, and the built-in MCP server (paid plans) handles the connect-to-your-site flow — no terminal, no key management.
  • 💻 Full local (install + key): Studio CLI plus your own provider API key unlocks the fully automated path. This is the default the exercises assume, but it’s never the only way.

Each day that needs a key or an install has a 🔓 “No key or can’t install? Do this instead” note with the exact substitution. Nobody gets fully blocked.

What is MCP and why does it matter?

MCP (Model Context Protocol) is an open standard that connects AI agents to external tools and data. For WordPress, it means Claude can directly read your posts, create drafts, manage categories, and execute workflows — without you copy-pasting content between the AI and your CMS. It’s the difference between “AI as a writing tool” and “AI as a workflow partner.” Setup guide →

What’s the Abilities API?

A framework in WordPress core (since 6.9) that lets plugins and themes declare what they can do in a way AI agents can discover. It’s like a menu for AI — agents read it to know what actions are available on your site. Detailed explanation on Day 6. Developer docs →

What’s Telex?

Telex is Automattic AI Labs’ natural language builder. Describe a block or theme in plain English, and Telex generates a working WordPress plugin or theme as a downloadable .zip. It’s covered in Day 3 (blocks), Day 12 (content blocks), and Day 19 (themes).

What’s Studio Code vs Studio CLI?

Start with the Studio desktop app — it creates local sites with a click, and Studio Code lives right inside it (no terminal needed). For automation fans, Studio CLI (wp-studio) is the command-line equivalent. Studio Code is an AI coding agent built on Claude Code — available in Studio Desktop and the Studio CLI, free in beta — tuned for WordPress development — it can build themes, run audits, and manage your site through natural language. Studio is covered on Day 2; Studio Code features throughout Weeks 3-4.

Can I use this with my team?

Absolutely — that’s the goal. The program is designed as a self-paced curriculum you can share with your entire team. Week 4 focuses specifically on scaling: writing an AI policy (Day 22), building a team playbook (Day 23), pairing with teammates (Day 24), and measuring impact (Day 25).

What about content quality and accuracy?

AI-generated content should always be reviewed by a human before publication. The program emphasizes this repeatedly: AI drafts, humans refine and publish. Day 22 covers building an AI content policy with clear Green/Yellow/Red guidelines for your team.

What plugins should I install?

The course works without any third-party plugins — all exercises use WordPress core features, MCP, and the tools in the stack. But several popular plugins now support the Abilities API, which means AI agents can discover and use their features automatically. Installing these will make your exercises richer:

🔧 Plugins with Abilities API support — These plugins expose their capabilities to AI agents, making them discoverable via MCP. Full list →

PluginWhat It DoesWhy It Helps
Yoast SEOSEO analysis, meta descriptions, sitemapsDays 9, 16, 20 — AI agents can read and optimize your SEO settings
JetpackPublishing, analytics, security, formsDays 0, 1 — Widely used by publishers, AI-discoverable features
ACF (6.8+)Custom fields, post types, taxonomiesDay 26 — AI agents can discover and create custom content models
WPFormsForms, surveys, lead generationPractical for editorial feedback loops and audience research
WordPress AI pluginTitle gen, excerpts, alt text, content optimizationDay 5 — Core AI features in the editor, works with any AI provider

You don’t need all of these — pick the ones relevant to your workflow. The WordPress AI plugin is the only one used directly in the exercises. The others enhance what AI agents can do when connected via MCP.

Where can I learn more about each tool?

← Back to Home