lhm-wordpress-hub

Build an Astro website from the approved HTML prototype. Use this when the user says 'build the Astro site', 'convert the prototype to Astro', 'astro build', 'scaffold the Astro project', 'convert to Astro', 'build out the Astro pages', or 'start Phase 5 for an Astro build'. This is the Phase 5 equivalent for projects where platform is Astro. Requires an approved HTML prototype (html-prototype skill) and a design system. Converts prototype sections to .astro components, extracts copy to content collections, wires up SEO, sitemap, and robots.txt, and configures for deployment.

Evaluate Gutenberg native blocks vs custom blocks for the project. Output block specifications and pattern requirements. Use this when the user says 'block architecture', 'which blocks do I need', 'custom blocks', 'block specs', 'gutenberg blocks', 'block evaluation', or 'native vs custom'. Phase 4 of the website build. Requires content files and design system.

Extract or define brand guidelines — colors, typography, tone of voice, imagery direction. Use this when the user says 'brand guidelines', 'define the brand', 'brand discovery', 'color palette', 'brand identity', 'typography choices', 'visual identity', or 'brand direction'. Phase 4 of the website build. Can also be run standalone.

Extract structured facts from client call notes, Fathom transcripts, meeting recordings, or uploaded documents. Use this when the user says 'process call notes', 'extract client info', 'intake from transcript', 'add client context', 'process Fathom notes', 'client discovery', or 'client onboarding'. Outputs facts only — no marketing copy. Phase 1 of the website build.

Sets up the Data Collection step of new web client onboarding — creates the client's Drive folder and credentials tracking sheet, files the BasicOps Data Gathering task with the standard access checklist (including Cloudflare), drafts the data-gathering email, and sets up a weekly automated follow-up so nothing gets missed. Use this when the user says 'start client onboarding', 'new client data gathering', 'set up new client folder', 'collect client access', 'chase client for credentials', 'data gathering for [client]', or is starting a new web client right after Michael's welcome email has gone out. Phase 0 of the web project onboarding flow — runs before client-context-intake.

This skill should be used when the user wants to "set up contact form submissions", "wire up a contact form", "add form handling to Cloudflare Pages", "save form submissions to D1", "upload images or files from a form", "store form uploads in Cloudflare R2", "add Turnstile spam protection", "set up email notifications for forms", "create a thank-you page for a form", "add an admin submissions page", or "integrate a form with Cloudflare Pages Functions". Provides the complete implementation workflow for reliable, spam-protected, tracked contact forms and private file uploads on Astro/Cloudflare Pages sites.

Validate that the WordPress theme CSS matches the approved HTML prototype CSS. Run this after theme installation and before page building. Use this when the user says 'check the CSS', 'CSS sync', 'does the theme match', 'validate theme CSS', 'CSS audit', 'compare CSS', or 'theme CSS check'. Catches styling divergence before pages are built.

Add and configure Decap CMS (also called Decap CRM by users) for an Astro website hosted on Cloudflare Pages. Use when asked to add a CMS, client content editing, Git-backed editorial approval, draft or scheduled blog publishing, or full-page deploy previews to an Astro build.

Generate design tokens, spacing scale, and component specs for theme.json. Use this when the user says 'design system', 'design tokens', 'spacing scale', 'generate theme.json settings', 'component specs', or 'design variables'. Phase 4 of the website build. Requires brand guidelines from Brand Discovery.

Runs the GA4-checkable portion of the client's Digital Audit — confirms GA4 is receiving data, lists conversion/key events, checks the Google Ads link, writes a report to the client's Drive folder, and files a BasicOps checklist task (including manual GTM/GSC items). Use this when the user says 'digital audit', 'audit analytics', 'check GA4 setup', 'check tracking', 'verify conversions', or 'digital audit for [client]'. Step 4 of the web project onboarding flow — GA4 checks are automated, GTM and Search Console stay manual (no connector exists for either).

Generate static HTML prototypes of key pages using the design system. Use this when the user says 'HTML prototype', 'static prototype', 'mockup', 'preview the design', 'HTML preview', or 'prototype the homepage'. Phase 4 of the website build. Optional step — requires brand guidelines and design system.

Write landing page copy for each ad group in a PPC campaign. Use this when the user says 'write landing page copy', 'write copy for the campaign', 'lp-copy', 'write the landing pages', 'create copy for the ad groups', or provides a list of ad groups and keywords. Requires client_profile.md. Produces one copy file per ad group in /lp/copy/.

Push the first landing page HTML prototype into WordPress as Gutenberg HTML blocks. Use this when the user says 'deploy the landing page', 'push to WordPress', 'lp-deploy-1', 'drop in the prototype', 'set up the subsite and get the page live', or 'deploy deploy-1'. Requires lp-subsite-setup to have run and a prototype at /lp/prototype/. Wraps prototype sections in wp:html blocks and creates the WordPress page.

Convert a landing page from raw Gutenberg HTML blocks to native WordPress blocks for full editor editability. Use this when the user says 'convert to blocks', 'convert to Gutenberg', 'lp-deploy-2', 'make the landing page editable', 'convert the HTML blocks', or 'Gutenberg conversion'. Requires lp-deploy-1 to have run successfully. Produces a native block version of the page that works in the Gutenberg editor.

Deploy all remaining landing pages (ad groups 2, 3, etc.) to WordPress after the primary page has been set up. Use this when the user says 'deploy the rest', 'deploy remaining pages', 'lp-deploy-3', 'add the other landing pages', 'build the remaining ad group pages', or 'deploy all pages'. Requires lp-deploy-1 (and ideally lp-deploy-2) to have run on the primary page.

Read, create, or update the landing-page-project-management.md file for a landing page campaign. Use this when the user mentions 'LP project status', 'landing page status', 'where are we at with the landing page', 'update LP project', 'create LP project', 'LP progress', 'what's left on the landing page', or 'landing page project management'. Also run this at the start of any LP workflow to ensure the project file exists.

Build HTML/CSS landing page prototypes for a PPC campaign. Use this when the user says 'build the prototype', 'create the landing page prototype', 'build the HTML for the landing page', 'lp-prototype', or 'create the landing pages'. Reads from /lp/copy/ and the health theme template to produce a pixel-perfect HTML/CSS file per ad group.

Deploy a LeadScalePro multisite subsite from local Docker to the live server. Use this when the user says 'deploy the subsite', 'push subsite to live', 'deploy to LeadScalePro', 'push to production', 'deploy client site', 'lp-subsite-deploy', 'sync subsite to server', or 'push [client] live'. Exports everything from the local Docker subsite (theme, pages, locations, images, customizer, options) and creates/updates the matching subsite on the remote multisite. Reads SSH credentials from the multisite project's SSH access file.

Configure a WordPress multisite subsite for a landing page campaign. Use this when the user says 'set up landing page site', 'configure subsite', 'set up the health theme', 'set up branding on the landing page site', 'configure the multisite for [client]', or 'lp-subsite-setup'. Handles theme activation, site identity, brand colours, typography, social proof, social media URLs, and location CPT entries. Always run this before lp-deploy-1.

Generate per-page content briefs with target keywords, search intent, page sections, and CTAs. Use this when the user says 'create page briefs', 'write a brief', 'page brief', 'content brief', 'brief for homepage', 'brief for service page', or 'section outline'. Phase 2 of the website build. Requires sitemap and keyword map from the Sitemap Architect.

Write page content from a page brief. Produces complete page copy with YAML frontmatter, SEO metadata, section-by-section content, and component declarations. Use this when the user says 'write page content', 'write the copy', 'write homepage', 'content from brief', 'fill in the content', or 'write [page name] page'. Phase 3 of the website build. Requires page briefs from Phase 2.

Create, import, clean up, and verify Rank Math 301 redirects on WordPress sites during migrations, sitemap replacements, launch QA, or Squarespace-to-WordPress URL changes. Use when the user asks to set up redirects in Rank Math, import a redirect map, redirect old URLs, verify 301s, or troubleshoot Rank Math redirect matching.

Set up Git repositories for a new client project. Use this when the user says 'set up the repo', 'init the client repo', 'create the client repos', 'initialise the project repo', 'set up GitHub for this client', 'create repos for a client', 'new client repo', 'repo-init', or is starting a new client project and needs Git set up. Creates both client-site and client-prototype repos on GitHub, scaffolds the code repo's docs/ folder with context documents pulled from existing client files, and commits the initial scaffold.

Clone a client project repository onto a new machine or for a new team member. Use this when the user says 'install the repo', 'clone the client project', 'set up my machine for [client]', 'pull down the client repo', 'clone the repos', 'install the client site locally', 'get the client repo', 'repo-install', or needs to access a client project that already has repos set up. Sets up the correct local folder structure and clones the code and/or prototype repos. Also use when someone already has the repo and just needs to pull the latest.

Pre-launch QA checklist for WordPress and Astro websites. Runs automated checks (links, SSL, robots.txt, sitemap, console errors, PageSpeed, meta tags, favicon) then walks the user through manual checks that AI cannot verify. Updates the project management doc with QA results at the end. Use this when the user says 'run the QA checklist', 'pre-launch QA', 'site QA', 'launch checklist', 'quality assurance check', 'ready to go live checklist', or 'QA the site before launch'.

Build the site information architecture — keyword map, sitemap, page hierarchy, and 301 redirect map. Use this when the user says 'plan the sitemap', 'site structure', 'information architecture', 'IA planning', 'page hierarchy', 'keyword mapping', 'site map', or 'audit the live site before the rebuild'. Phase 2 of the website build. Requires client profile from Phase 1.

Canonical worker entry for Astro website builds and revisions, verification and approved deployment.

Canonical worker entry for creating or revising client sitemaps and homepage prototypes, with explicitly approved publishing.

Canonical worker entry for WordPress builds and revisions, verification and explicitly approved staging or live delivery.

Scaffold a custom WordPress block theme with theme.json, templates, template parts, patterns, and styles. Use this when the user says 'scaffold theme', 'create theme', 'build theme', 'theme.json', 'block theme', 'custom theme', or 'WordPress theme'. Phase 5 of the website build. Requires design system and block specs.

Pixel-perfect visual regression testing using Playwright MCP. Compares the approved HTML prototype against the live WordPress build at multiple viewport sizes. Use this when the user says 'visual QA', 'check the build', 'compare to prototype', 'pixel perfect check', 'screenshot comparison', 'does it match', 'visual regression', 'test the pages', 'QA the site', or 'check responsive'. Also triggered automatically after every page build, blog post, or site extension.

Verify Prototype, Astro or WordPress delivery against its dispatch envelope, artefact, approval boundary and completion test.

Publish blog posts to a WordPress site from markdown files via WP-CLI over SSH. Use this when the user says 'publish blog posts', 'upload blog posts', 'schedule blog posts', 'push posts to WordPress', 'publish articles', or 'post to the blog'. Handles markdown-to-HTML conversion, category creation, author assignment, scheduling, and Yoast SEO meta. Requires SSH access and WP-CLI on the server.

Build individual pages in WordPress from content and design artefacts. Use this when the user says 'build pages', 'create pages in WordPress', 'page builder', 'add pages to WordPress', 'build the homepage', or 'WP build'. Phase 5 of the website build. Requires content files, design system, and theme installed.

Performance audit and optimization for WordPress sites. Core Web Vitals, caching, image optimization, and speed improvements. Use this when the user says 'performance audit', 'speed optimization', 'Core Web Vitals', 'page speed', 'site speed', 'LCP', 'CLS', 'FID', 'caching', or 'optimize WordPress'. Phase 6 of the website build. Can also be run standalone on any WordPress site.

Read, create, or update the website-project-management.md file for a full WordPress or Astro website build. Use this when the user mentions 'WP project status', 'Astro project status', 'where are we at with the website', 'update website project', 'create the website PM doc', 'website progress', 'what's left on the build', or 'website project management'. Also called by phase agents after task completion to mark off checkboxes, and by wp-start at session start to detect current state.

Initialize the canonical folder structure for a new WordPress website project. Use this when the user says 'new project', 'set up project folders', 'initialize website project', 'create project structure', or 'start fresh'. Detects whether shared client-root scaffolding exists; creates only the wordpress/ subtree if it does, otherwise creates both layers.

Security hardening checklist for WordPress sites. Headers, permissions, plugin audit, backups, and pre-launch checks. Use this when the user says 'security hardening', 'secure WordPress', 'security audit', 'pre-launch checklist', 'security headers', 'harden WordPress', or 'launch checklist'. Phase 6 of the website build. Can also be run standalone.

Push a local WordPress site to a remote server via SSH and WP-CLI. Use this when the user says 'deploy to server', 'push to production', 'sync to live', 'upload site via SSH', 'deploy via SSH', 'push WordPress to server', or 'wp-ssh-deploy'. Handles theme files, pages, custom post types with meta, media, customizer settings, menus, and options. Requires SSH access to a server with WP-CLI installed.

Start a session in the WordPress hub. Use this when the user wants to begin a website project, asks 'build a website', 'start a WordPress site', 'start an Astro site', mentions 'website build', 'new site', 'landing page', 'LP campaign', or invokes /lhm-wordpress-hub:wp-start. Also use when the user mentions 'contact form', 'form submissions', 'wire up forms', 'set up form handling', 'Cloudflare forms', 'D1 form submissions', or 'Turnstile'. Also use when the user mentions 'QA checklist', 'run the QA', 'pre-launch checklist', 'site QA', 'launch checklist', or 'ready to go live'. This skill is a router — it detects which workflow (full WP build, LP campaign, or standalone utility skill) and hands off to the right orchestrator or skill.