Profession 35 · Free AI prompt handbook

120 WordPress Developer & AI Website Optimization Prompts

A practical, searchable English tutorial for WordPress developers: plan, build, debug, optimize and deliver client websites. Each custom reference shortcode identifies a copy-ready prompt; it is not an executable WordPress shortcode.

120 templates12 modulesResponsive & copy-ready

How to use this library

Search by task, tool or reference ID, or choose a module.
Copy the prompt and replace every [BRACKETED INPUT] with your verified client information.
Provide sanitized screenshots or logs where relevant; request a tailored response.
Review generated code on staging, make a backup, test mobile/accessibility/security, then deploy with client approval.

No prompt can replace environment-specific testing. Do not paste credentials or private user data into AI services.

120 of 120 prompts

01. Discovery & Architecture

WP-001

Client discovery questionnaire

Use this when handling client discovery questionnaire for a WordPress client. Replace the bracketed project inputs, attach sanitized evidence, and verify all outputs before deployment.

Act as a senior WordPress developer and AI-assisted website optimization specialist. TASK: Client discovery questionnaire.

PROJECT INPUTS (replace every bracket):
- Website or staging URL: [URL or sanitized description]
- Business type and target audience: [DETAILS]
- WordPress version, theme, builder and relevant plugins: [VERIFIED STACK]
- Current behavior and desired outcome: [CURRENT / TARGET]
- Constraints (budget, hosting, deadlines, permissions): [CONSTRAINTS]
- Evidence supplied (screenshots, logs, analytics or brief): [EVIDENCE OR NONE]

DELIVERABLE: Produce a tailored client discovery questionnaire for this project. Begin with a concise diagnosis or goal, then provide a prioritized step-by-step plan, implementation examples (code/configuration only where appropriate), validation tests, rollback options, and a client-facing summary. Explain assumptions and mark missing inputs as questions instead of inventing evidence. For any WordPress change, consider staging, backups, compatibility, mobile accessibility, privacy, security, and SEO impact. Distinguish verified observations from hypotheses. Never claim to have accessed a site, run a test, installed a plugin or measured performance unless evidence is supplied. For security-sensitive tasks, focus on authorized defensive work. End with clear acceptance criteria and the next safe action.

WP-002

Business goals to website requirements

Use this when handling business goals to website requirements for a WordPress client. Replace the bracketed project inputs, attach sanitized evidence, and verify all outputs before deployment.

Act as a senior WordPress developer and AI-assisted website optimization specialist. TASK: Business goals to website requirements.

PROJECT INPUTS (replace every bracket):
- Website or staging URL: [URL or sanitized description]
- Business type and target audience: [DETAILS]
- WordPress version, theme, builder and relevant plugins: [VERIFIED STACK]
- Current behavior and desired outcome: [CURRENT / TARGET]
- Constraints (budget, hosting, deadlines, permissions): [CONSTRAINTS]
- Evidence supplied (screenshots, logs, analytics or brief): [EVIDENCE OR NONE]

DELIVERABLE: Produce a tailored business goals to website requirements for this project. Begin with a concise diagnosis or goal, then provide a prioritized step-by-step plan, implementation examples (code/configuration only where appropriate), validation tests, rollback options, and a client-facing summary. Explain assumptions and mark missing inputs as questions instead of inventing evidence. For any WordPress change, consider staging, backups, compatibility, mobile accessibility, privacy, security, and SEO impact. Distinguish verified observations from hypotheses. Never claim to have accessed a site, run a test, installed a plugin or measured performance unless evidence is supplied. For security-sensitive tasks, focus on authorized defensive work. End with clear acceptance criteria and the next safe action.

WP-003

Site architecture plan

Use this when handling site architecture plan for a WordPress client. Replace the bracketed project inputs, attach sanitized evidence, and verify all outputs before deployment.

Act as a senior WordPress developer and AI-assisted website optimization specialist. TASK: Site architecture plan.

PROJECT INPUTS (replace every bracket):
- Website or staging URL: [URL or sanitized description]
- Business type and target audience: [DETAILS]
- WordPress version, theme, builder and relevant plugins: [VERIFIED STACK]
- Current behavior and desired outcome: [CURRENT / TARGET]
- Constraints (budget, hosting, deadlines, permissions): [CONSTRAINTS]
- Evidence supplied (screenshots, logs, analytics or brief): [EVIDENCE OR NONE]

DELIVERABLE: Produce a tailored site architecture plan for this project. Begin with a concise diagnosis or goal, then provide a prioritized step-by-step plan, implementation examples (code/configuration only where appropriate), validation tests, rollback options, and a client-facing summary. Explain assumptions and mark missing inputs as questions instead of inventing evidence. For any WordPress change, consider staging, backups, compatibility, mobile accessibility, privacy, security, and SEO impact. Distinguish verified observations from hypotheses. Never claim to have accessed a site, run a test, installed a plugin or measured performance unless evidence is supplied. For security-sensitive tasks, focus on authorized defensive work. End with clear acceptance criteria and the next safe action.

WP-004

Content inventory and migration map

Use this when handling content inventory and migration map for a WordPress client. Replace the bracketed project inputs, attach sanitized evidence, and verify all outputs before deployment.

Act as a senior WordPress developer and AI-assisted website optimization specialist. TASK: Content inventory and migration map.

PROJECT INPUTS (replace every bracket):
- Website or staging URL: [URL or sanitized description]
- Business type and target audience: [DETAILS]
- WordPress version, theme, builder and relevant plugins: [VERIFIED STACK]
- Current behavior and desired outcome: [CURRENT / TARGET]
- Constraints (budget, hosting, deadlines, permissions): [CONSTRAINTS]
- Evidence supplied (screenshots, logs, analytics or brief): [EVIDENCE OR NONE]

DELIVERABLE: Produce a tailored content inventory and migration map for this project. Begin with a concise diagnosis or goal, then provide a prioritized step-by-step plan, implementation examples (code/configuration only where appropriate), validation tests, rollback options, and a client-facing summary. Explain assumptions and mark missing inputs as questions instead of inventing evidence. For any WordPress change, consider staging, backups, compatibility, mobile accessibility, privacy, security, and SEO impact. Distinguish verified observations from hypotheses. Never claim to have accessed a site, run a test, installed a plugin or measured performance unless evidence is supplied. For security-sensitive tasks, focus on authorized defensive work. End with clear acceptance criteria and the next safe action.

WP-005

Hosting environment assessment

Use this when handling hosting environment assessment for a WordPress client. Replace the bracketed project inputs, attach sanitized evidence, and verify all outputs before deployment.

Act as a senior WordPress developer and AI-assisted website optimization specialist. TASK: Hosting environment assessment.

PROJECT INPUTS (replace every bracket):
- Website or staging URL: [URL or sanitized description]
- Business type and target audience: [DETAILS]
- WordPress version, theme, builder and relevant plugins: [VERIFIED STACK]
- Current behavior and desired outcome: [CURRENT / TARGET]
- Constraints (budget, hosting, deadlines, permissions): [CONSTRAINTS]
- Evidence supplied (screenshots, logs, analytics or brief): [EVIDENCE OR NONE]

DELIVERABLE: Produce a tailored hosting environment assessment for this project. Begin with a concise diagnosis or goal, then provide a prioritized step-by-step plan, implementation examples (code/configuration only where appropriate), validation tests, rollback options, and a client-facing summary. Explain assumptions and mark missing inputs as questions instead of inventing evidence. For any WordPress change, consider staging, backups, compatibility, mobile accessibility, privacy, security, and SEO impact. Distinguish verified observations from hypotheses. Never claim to have accessed a site, run a test, installed a plugin or measured performance unless evidence is supplied. For security-sensitive tasks, focus on authorized defensive work. End with clear acceptance criteria and the next safe action.

WP-006

Plugin selection matrix

Use this when handling plugin selection matrix for a WordPress client. Replace the bracketed project inputs, attach sanitized evidence, and verify all outputs before deployment.

Act as a senior WordPress developer and AI-assisted website optimization specialist. TASK: Plugin selection matrix.

PROJECT INPUTS (replace every bracket):
- Website or staging URL: [URL or sanitized description]
- Business type and target audience: [DETAILS]
- WordPress version, theme, builder and relevant plugins: [VERIFIED STACK]
- Current behavior and desired outcome: [CURRENT / TARGET]
- Constraints (budget, hosting, deadlines, permissions): [CONSTRAINTS]
- Evidence supplied (screenshots, logs, analytics or brief): [EVIDENCE OR NONE]

DELIVERABLE: Produce a tailored plugin selection matrix for this project. Begin with a concise diagnosis or goal, then provide a prioritized step-by-step plan, implementation examples (code/configuration only where appropriate), validation tests, rollback options, and a client-facing summary. Explain assumptions and mark missing inputs as questions instead of inventing evidence. For any WordPress change, consider staging, backups, compatibility, mobile accessibility, privacy, security, and SEO impact. Distinguish verified observations from hypotheses. Never claim to have accessed a site, run a test, installed a plugin or measured performance unless evidence is supplied. For security-sensitive tasks, focus on authorized defensive work. End with clear acceptance criteria and the next safe action.

WP-007

Theme strategy comparison

Use this when handling theme strategy comparison for a WordPress client. Replace the bracketed project inputs, attach sanitized evidence, and verify all outputs before deployment.

Act as a senior WordPress developer and AI-assisted website optimization specialist. TASK: Theme strategy comparison.

PROJECT INPUTS (replace every bracket):
- Website or staging URL: [URL or sanitized description]
- Business type and target audience: [DETAILS]
- WordPress version, theme, builder and relevant plugins: [VERIFIED STACK]
- Current behavior and desired outcome: [CURRENT / TARGET]
- Constraints (budget, hosting, deadlines, permissions): [CONSTRAINTS]
- Evidence supplied (screenshots, logs, analytics or brief): [EVIDENCE OR NONE]

DELIVERABLE: Produce a tailored theme strategy comparison for this project. Begin with a concise diagnosis or goal, then provide a prioritized step-by-step plan, implementation examples (code/configuration only where appropriate), validation tests, rollback options, and a client-facing summary. Explain assumptions and mark missing inputs as questions instead of inventing evidence. For any WordPress change, consider staging, backups, compatibility, mobile accessibility, privacy, security, and SEO impact. Distinguish verified observations from hypotheses. Never claim to have accessed a site, run a test, installed a plugin or measured performance unless evidence is supplied. For security-sensitive tasks, focus on authorized defensive work. End with clear acceptance criteria and the next safe action.

WP-008

Accessibility requirements brief

Use this when handling accessibility requirements brief for a WordPress client. Replace the bracketed project inputs, attach sanitized evidence, and verify all outputs before deployment.

Act as a senior WordPress developer and AI-assisted website optimization specialist. TASK: Accessibility requirements brief.

PROJECT INPUTS (replace every bracket):
- Website or staging URL: [URL or sanitized description]
- Business type and target audience: [DETAILS]
- WordPress version, theme, builder and relevant plugins: [VERIFIED STACK]
- Current behavior and desired outcome: [CURRENT / TARGET]
- Constraints (budget, hosting, deadlines, permissions): [CONSTRAINTS]
- Evidence supplied (screenshots, logs, analytics or brief): [EVIDENCE OR NONE]

DELIVERABLE: Produce a tailored accessibility requirements brief for this project. Begin with a concise diagnosis or goal, then provide a prioritized step-by-step plan, implementation examples (code/configuration only where appropriate), validation tests, rollback options, and a client-facing summary. Explain assumptions and mark missing inputs as questions instead of inventing evidence. For any WordPress change, consider staging, backups, compatibility, mobile accessibility, privacy, security, and SEO impact. Distinguish verified observations from hypotheses. Never claim to have accessed a site, run a test, installed a plugin or measured performance unless evidence is supplied. For security-sensitive tasks, focus on authorized defensive work. End with clear acceptance criteria and the next safe action.

WP-009

Staging and release plan

Use this when handling staging and release plan for a WordPress client. Replace the bracketed project inputs, attach sanitized evidence, and verify all outputs before deployment.

Act as a senior WordPress developer and AI-assisted website optimization specialist. TASK: Staging and release plan.

PROJECT INPUTS (replace every bracket):
- Website or staging URL: [URL or sanitized description]
- Business type and target audience: [DETAILS]
- WordPress version, theme, builder and relevant plugins: [VERIFIED STACK]
- Current behavior and desired outcome: [CURRENT / TARGET]
- Constraints (budget, hosting, deadlines, permissions): [CONSTRAINTS]
- Evidence supplied (screenshots, logs, analytics or brief): [EVIDENCE OR NONE]

DELIVERABLE: Produce a tailored staging and release plan for this project. Begin with a concise diagnosis or goal, then provide a prioritized step-by-step plan, implementation examples (code/configuration only where appropriate), validation tests, rollback options, and a client-facing summary. Explain assumptions and mark missing inputs as questions instead of inventing evidence. For any WordPress change, consider staging, backups, compatibility, mobile accessibility, privacy, security, and SEO impact. Distinguish verified observations from hypotheses. Never claim to have accessed a site, run a test, installed a plugin or measured performance unless evidence is supplied. For security-sensitive tasks, focus on authorized defensive work. End with clear acceptance criteria and the next safe action.

WP-010

Project scope and acceptance criteria

Use this when handling project scope and acceptance criteria for a WordPress client. Replace the bracketed project inputs, attach sanitized evidence, and verify all outputs before deployment.

Act as a senior WordPress developer and AI-assisted website optimization specialist. TASK: Project scope and acceptance criteria.

PROJECT INPUTS (replace every bracket):
- Website or staging URL: [URL or sanitized description]
- Business type and target audience: [DETAILS]
- WordPress version, theme, builder and relevant plugins: [VERIFIED STACK]
- Current behavior and desired outcome: [CURRENT / TARGET]
- Constraints (budget, hosting, deadlines, permissions): [CONSTRAINTS]
- Evidence supplied (screenshots, logs, analytics or brief): [EVIDENCE OR NONE]

DELIVERABLE: Produce a tailored project scope and acceptance criteria for this project. Begin with a concise diagnosis or goal, then provide a prioritized step-by-step plan, implementation examples (code/configuration only where appropriate), validation tests, rollback options, and a client-facing summary. Explain assumptions and mark missing inputs as questions instead of inventing evidence. For any WordPress change, consider staging, backups, compatibility, mobile accessibility, privacy, security, and SEO impact. Distinguish verified observations from hypotheses. Never claim to have accessed a site, run a test, installed a plugin or measured performance unless evidence is supplied. For security-sensitive tasks, focus on authorized defensive work. End with clear acceptance criteria and the next safe action.

02. WordPress Core & Gutenberg

WP-011

WordPress installation checklist

Use this when handling wordpress installation checklist for a WordPress client. Replace the bracketed project inputs, attach sanitized evidence, and verify all outputs before deployment.

Act as a senior WordPress developer and AI-assisted website optimization specialist. TASK: WordPress installation checklist.

PROJECT INPUTS (replace every bracket):
- Website or staging URL: [URL or sanitized description]
- Business type and target audience: [DETAILS]
- WordPress version, theme, builder and relevant plugins: [VERIFIED STACK]
- Current behavior and desired outcome: [CURRENT / TARGET]
- Constraints (budget, hosting, deadlines, permissions): [CONSTRAINTS]
- Evidence supplied (screenshots, logs, analytics or brief): [EVIDENCE OR NONE]

DELIVERABLE: Produce a tailored wordpress installation checklist for this project. Begin with a concise diagnosis or goal, then provide a prioritized step-by-step plan, implementation examples (code/configuration only where appropriate), validation tests, rollback options, and a client-facing summary. Explain assumptions and mark missing inputs as questions instead of inventing evidence. For any WordPress change, consider staging, backups, compatibility, mobile accessibility, privacy, security, and SEO impact. Distinguish verified observations from hypotheses. Never claim to have accessed a site, run a test, installed a plugin or measured performance unless evidence is supplied. For security-sensitive tasks, focus on authorized defensive work. End with clear acceptance criteria and the next safe action.

WP-012

Roles and permissions plan

Use this when handling roles and permissions plan for a WordPress client. Replace the bracketed project inputs, attach sanitized evidence, and verify all outputs before deployment.

Act as a senior WordPress developer and AI-assisted website optimization specialist. TASK: Roles and permissions plan.

PROJECT INPUTS (replace every bracket):
- Website or staging URL: [URL or sanitized description]
- Business type and target audience: [DETAILS]
- WordPress version, theme, builder and relevant plugins: [VERIFIED STACK]
- Current behavior and desired outcome: [CURRENT / TARGET]
- Constraints (budget, hosting, deadlines, permissions): [CONSTRAINTS]
- Evidence supplied (screenshots, logs, analytics or brief): [EVIDENCE OR NONE]

DELIVERABLE: Produce a tailored roles and permissions plan for this project. Begin with a concise diagnosis or goal, then provide a prioritized step-by-step plan, implementation examples (code/configuration only where appropriate), validation tests, rollback options, and a client-facing summary. Explain assumptions and mark missing inputs as questions instead of inventing evidence. For any WordPress change, consider staging, backups, compatibility, mobile accessibility, privacy, security, and SEO impact. Distinguish verified observations from hypotheses. Never claim to have accessed a site, run a test, installed a plugin or measured performance unless evidence is supplied. For security-sensitive tasks, focus on authorized defensive work. End with clear acceptance criteria and the next safe action.

WP-013

Gutenberg page layout specification

Use this when handling gutenberg page layout specification for a WordPress client. Replace the bracketed project inputs, attach sanitized evidence, and verify all outputs before deployment.

Act as a senior WordPress developer and AI-assisted website optimization specialist. TASK: Gutenberg page layout specification.

PROJECT INPUTS (replace every bracket):
- Website or staging URL: [URL or sanitized description]
- Business type and target audience: [DETAILS]
- WordPress version, theme, builder and relevant plugins: [VERIFIED STACK]
- Current behavior and desired outcome: [CURRENT / TARGET]
- Constraints (budget, hosting, deadlines, permissions): [CONSTRAINTS]
- Evidence supplied (screenshots, logs, analytics or brief): [EVIDENCE OR NONE]

DELIVERABLE: Produce a tailored gutenberg page layout specification for this project. Begin with a concise diagnosis or goal, then provide a prioritized step-by-step plan, implementation examples (code/configuration only where appropriate), validation tests, rollback options, and a client-facing summary. Explain assumptions and mark missing inputs as questions instead of inventing evidence. For any WordPress change, consider staging, backups, compatibility, mobile accessibility, privacy, security, and SEO impact. Distinguish verified observations from hypotheses. Never claim to have accessed a site, run a test, installed a plugin or measured performance unless evidence is supplied. For security-sensitive tasks, focus on authorized defensive work. End with clear acceptance criteria and the next safe action.

WP-014

Reusable block pattern design

Use this when handling reusable block pattern design for a WordPress client. Replace the bracketed project inputs, attach sanitized evidence, and verify all outputs before deployment.

Act as a senior WordPress developer and AI-assisted website optimization specialist. TASK: Reusable block pattern design.

PROJECT INPUTS (replace every bracket):
- Website or staging URL: [URL or sanitized description]
- Business type and target audience: [DETAILS]
- WordPress version, theme, builder and relevant plugins: [VERIFIED STACK]
- Current behavior and desired outcome: [CURRENT / TARGET]
- Constraints (budget, hosting, deadlines, permissions): [CONSTRAINTS]
- Evidence supplied (screenshots, logs, analytics or brief): [EVIDENCE OR NONE]

DELIVERABLE: Produce a tailored reusable block pattern design for this project. Begin with a concise diagnosis or goal, then provide a prioritized step-by-step plan, implementation examples (code/configuration only where appropriate), validation tests, rollback options, and a client-facing summary. Explain assumptions and mark missing inputs as questions instead of inventing evidence. For any WordPress change, consider staging, backups, compatibility, mobile accessibility, privacy, security, and SEO impact. Distinguish verified observations from hypotheses. Never claim to have accessed a site, run a test, installed a plugin or measured performance unless evidence is supplied. For security-sensitive tasks, focus on authorized defensive work. End with clear acceptance criteria and the next safe action.

WP-015

Navigation structure and menus

Use this when handling navigation structure and menus for a WordPress client. Replace the bracketed project inputs, attach sanitized evidence, and verify all outputs before deployment.

Act as a senior WordPress developer and AI-assisted website optimization specialist. TASK: Navigation structure and menus.

PROJECT INPUTS (replace every bracket):
- Website or staging URL: [URL or sanitized description]
- Business type and target audience: [DETAILS]
- WordPress version, theme, builder and relevant plugins: [VERIFIED STACK]
- Current behavior and desired outcome: [CURRENT / TARGET]
- Constraints (budget, hosting, deadlines, permissions): [CONSTRAINTS]
- Evidence supplied (screenshots, logs, analytics or brief): [EVIDENCE OR NONE]

DELIVERABLE: Produce a tailored navigation structure and menus for this project. Begin with a concise diagnosis or goal, then provide a prioritized step-by-step plan, implementation examples (code/configuration only where appropriate), validation tests, rollback options, and a client-facing summary. Explain assumptions and mark missing inputs as questions instead of inventing evidence. For any WordPress change, consider staging, backups, compatibility, mobile accessibility, privacy, security, and SEO impact. Distinguish verified observations from hypotheses. Never claim to have accessed a site, run a test, installed a plugin or measured performance unless evidence is supplied. For security-sensitive tasks, focus on authorized defensive work. End with clear acceptance criteria and the next safe action.

WP-016

Custom post type requirements

Use this when handling custom post type requirements for a WordPress client. Replace the bracketed project inputs, attach sanitized evidence, and verify all outputs before deployment.

Act as a senior WordPress developer and AI-assisted website optimization specialist. TASK: Custom post type requirements.

PROJECT INPUTS (replace every bracket):
- Website or staging URL: [URL or sanitized description]
- Business type and target audience: [DETAILS]
- WordPress version, theme, builder and relevant plugins: [VERIFIED STACK]
- Current behavior and desired outcome: [CURRENT / TARGET]
- Constraints (budget, hosting, deadlines, permissions): [CONSTRAINTS]
- Evidence supplied (screenshots, logs, analytics or brief): [EVIDENCE OR NONE]

DELIVERABLE: Produce a tailored custom post type requirements for this project. Begin with a concise diagnosis or goal, then provide a prioritized step-by-step plan, implementation examples (code/configuration only where appropriate), validation tests, rollback options, and a client-facing summary. Explain assumptions and mark missing inputs as questions instead of inventing evidence. For any WordPress change, consider staging, backups, compatibility, mobile accessibility, privacy, security, and SEO impact. Distinguish verified observations from hypotheses. Never claim to have accessed a site, run a test, installed a plugin or measured performance unless evidence is supplied. For security-sensitive tasks, focus on authorized defensive work. End with clear acceptance criteria and the next safe action.

WP-017

Taxonomy planning

Use this when handling taxonomy planning for a WordPress client. Replace the bracketed project inputs, attach sanitized evidence, and verify all outputs before deployment.

Act as a senior WordPress developer and AI-assisted website optimization specialist. TASK: Taxonomy planning.

PROJECT INPUTS (replace every bracket):
- Website or staging URL: [URL or sanitized description]
- Business type and target audience: [DETAILS]
- WordPress version, theme, builder and relevant plugins: [VERIFIED STACK]
- Current behavior and desired outcome: [CURRENT / TARGET]
- Constraints (budget, hosting, deadlines, permissions): [CONSTRAINTS]
- Evidence supplied (screenshots, logs, analytics or brief): [EVIDENCE OR NONE]

DELIVERABLE: Produce a tailored taxonomy planning for this project. Begin with a concise diagnosis or goal, then provide a prioritized step-by-step plan, implementation examples (code/configuration only where appropriate), validation tests, rollback options, and a client-facing summary. Explain assumptions and mark missing inputs as questions instead of inventing evidence. For any WordPress change, consider staging, backups, compatibility, mobile accessibility, privacy, security, and SEO impact. Distinguish verified observations from hypotheses. Never claim to have accessed a site, run a test, installed a plugin or measured performance unless evidence is supplied. For security-sensitive tasks, focus on authorized defensive work. End with clear acceptance criteria and the next safe action.

WP-018

Media library governance

Use this when handling media library governance for a WordPress client. Replace the bracketed project inputs, attach sanitized evidence, and verify all outputs before deployment.

Act as a senior WordPress developer and AI-assisted website optimization specialist. TASK: Media library governance.

PROJECT INPUTS (replace every bracket):
- Website or staging URL: [URL or sanitized description]
- Business type and target audience: [DETAILS]
- WordPress version, theme, builder and relevant plugins: [VERIFIED STACK]
- Current behavior and desired outcome: [CURRENT / TARGET]
- Constraints (budget, hosting, deadlines, permissions): [CONSTRAINTS]
- Evidence supplied (screenshots, logs, analytics or brief): [EVIDENCE OR NONE]

DELIVERABLE: Produce a tailored media library governance for this project. Begin with a concise diagnosis or goal, then provide a prioritized step-by-step plan, implementation examples (code/configuration only where appropriate), validation tests, rollback options, and a client-facing summary. Explain assumptions and mark missing inputs as questions instead of inventing evidence. For any WordPress change, consider staging, backups, compatibility, mobile accessibility, privacy, security, and SEO impact. Distinguish verified observations from hypotheses. Never claim to have accessed a site, run a test, installed a plugin or measured performance unless evidence is supplied. For security-sensitive tasks, focus on authorized defensive work. End with clear acceptance criteria and the next safe action.

WP-019

WordPress settings audit

Use this when handling wordpress settings audit for a WordPress client. Replace the bracketed project inputs, attach sanitized evidence, and verify all outputs before deployment.

Act as a senior WordPress developer and AI-assisted website optimization specialist. TASK: WordPress settings audit.

PROJECT INPUTS (replace every bracket):
- Website or staging URL: [URL or sanitized description]
- Business type and target audience: [DETAILS]
- WordPress version, theme, builder and relevant plugins: [VERIFIED STACK]
- Current behavior and desired outcome: [CURRENT / TARGET]
- Constraints (budget, hosting, deadlines, permissions): [CONSTRAINTS]
- Evidence supplied (screenshots, logs, analytics or brief): [EVIDENCE OR NONE]

DELIVERABLE: Produce a tailored wordpress settings audit for this project. Begin with a concise diagnosis or goal, then provide a prioritized step-by-step plan, implementation examples (code/configuration only where appropriate), validation tests, rollback options, and a client-facing summary. Explain assumptions and mark missing inputs as questions instead of inventing evidence. For any WordPress change, consider staging, backups, compatibility, mobile accessibility, privacy, security, and SEO impact. Distinguish verified observations from hypotheses. Never claim to have accessed a site, run a test, installed a plugin or measured performance unless evidence is supplied. For security-sensitive tasks, focus on authorized defensive work. End with clear acceptance criteria and the next safe action.

WP-020

Editorial publishing workflow

Use this when handling editorial publishing workflow for a WordPress client. Replace the bracketed project inputs, attach sanitized evidence, and verify all outputs before deployment.

Act as a senior WordPress developer and AI-assisted website optimization specialist. TASK: Editorial publishing workflow.

PROJECT INPUTS (replace every bracket):
- Website or staging URL: [URL or sanitized description]
- Business type and target audience: [DETAILS]
- WordPress version, theme, builder and relevant plugins: [VERIFIED STACK]
- Current behavior and desired outcome: [CURRENT / TARGET]
- Constraints (budget, hosting, deadlines, permissions): [CONSTRAINTS]
- Evidence supplied (screenshots, logs, analytics or brief): [EVIDENCE OR NONE]

DELIVERABLE: Produce a tailored editorial publishing workflow for this project. Begin with a concise diagnosis or goal, then provide a prioritized step-by-step plan, implementation examples (code/configuration only where appropriate), validation tests, rollback options, and a client-facing summary. Explain assumptions and mark missing inputs as questions instead of inventing evidence. For any WordPress change, consider staging, backups, compatibility, mobile accessibility, privacy, security, and SEO impact. Distinguish verified observations from hypotheses. Never claim to have accessed a site, run a test, installed a plugin or measured performance unless evidence is supplied. For security-sensitive tasks, focus on authorized defensive work. End with clear acceptance criteria and the next safe action.

03. Kadence & Elementor

WP-021

Kadence page structure

Use this when handling kadence page structure for a WordPress client. Replace the bracketed project inputs, attach sanitized evidence, and verify all outputs before deployment.

Act as a senior WordPress developer and AI-assisted website optimization specialist. TASK: Kadence page structure.

PROJECT INPUTS (replace every bracket):
- Website or staging URL: [URL or sanitized description]
- Business type and target audience: [DETAILS]
- WordPress version, theme, builder and relevant plugins: [VERIFIED STACK]
- Current behavior and desired outcome: [CURRENT / TARGET]
- Constraints (budget, hosting, deadlines, permissions): [CONSTRAINTS]
- Evidence supplied (screenshots, logs, analytics or brief): [EVIDENCE OR NONE]

DELIVERABLE: Produce a tailored kadence page structure for this project. Begin with a concise diagnosis or goal, then provide a prioritized step-by-step plan, implementation examples (code/configuration only where appropriate), validation tests, rollback options, and a client-facing summary. Explain assumptions and mark missing inputs as questions instead of inventing evidence. For any WordPress change, consider staging, backups, compatibility, mobile accessibility, privacy, security, and SEO impact. Distinguish verified observations from hypotheses. Never claim to have accessed a site, run a test, installed a plugin or measured performance unless evidence is supplied. For security-sensitive tasks, focus on authorized defensive work. End with clear acceptance criteria and the next safe action.

WP-022

Kadence responsive spacing system

Use this when handling kadence responsive spacing system for a WordPress client. Replace the bracketed project inputs, attach sanitized evidence, and verify all outputs before deployment.

Act as a senior WordPress developer and AI-assisted website optimization specialist. TASK: Kadence responsive spacing system.

PROJECT INPUTS (replace every bracket):
- Website or staging URL: [URL or sanitized description]
- Business type and target audience: [DETAILS]
- WordPress version, theme, builder and relevant plugins: [VERIFIED STACK]
- Current behavior and desired outcome: [CURRENT / TARGET]
- Constraints (budget, hosting, deadlines, permissions): [CONSTRAINTS]
- Evidence supplied (screenshots, logs, analytics or brief): [EVIDENCE OR NONE]

DELIVERABLE: Produce a tailored kadence responsive spacing system for this project. Begin with a concise diagnosis or goal, then provide a prioritized step-by-step plan, implementation examples (code/configuration only where appropriate), validation tests, rollback options, and a client-facing summary. Explain assumptions and mark missing inputs as questions instead of inventing evidence. For any WordPress change, consider staging, backups, compatibility, mobile accessibility, privacy, security, and SEO impact. Distinguish verified observations from hypotheses. Never claim to have accessed a site, run a test, installed a plugin or measured performance unless evidence is supplied. For security-sensitive tasks, focus on authorized defensive work. End with clear acceptance criteria and the next safe action.

WP-023

Kadence custom HTML integration

Use this when handling kadence custom html integration for a WordPress client. Replace the bracketed project inputs, attach sanitized evidence, and verify all outputs before deployment.

Act as a senior WordPress developer and AI-assisted website optimization specialist. TASK: Kadence custom HTML integration.

PROJECT INPUTS (replace every bracket):
- Website or staging URL: [URL or sanitized description]
- Business type and target audience: [DETAILS]
- WordPress version, theme, builder and relevant plugins: [VERIFIED STACK]
- Current behavior and desired outcome: [CURRENT / TARGET]
- Constraints (budget, hosting, deadlines, permissions): [CONSTRAINTS]
- Evidence supplied (screenshots, logs, analytics or brief): [EVIDENCE OR NONE]

DELIVERABLE: Produce a tailored kadence custom html integration for this project. Begin with a concise diagnosis or goal, then provide a prioritized step-by-step plan, implementation examples (code/configuration only where appropriate), validation tests, rollback options, and a client-facing summary. Explain assumptions and mark missing inputs as questions instead of inventing evidence. For any WordPress change, consider staging, backups, compatibility, mobile accessibility, privacy, security, and SEO impact. Distinguish verified observations from hypotheses. Never claim to have accessed a site, run a test, installed a plugin or measured performance unless evidence is supplied. For security-sensitive tasks, focus on authorized defensive work. End with clear acceptance criteria and the next safe action.

WP-024

Kadence global typography plan

Use this when handling kadence global typography plan for a WordPress client. Replace the bracketed project inputs, attach sanitized evidence, and verify all outputs before deployment.

Act as a senior WordPress developer and AI-assisted website optimization specialist. TASK: Kadence global typography plan.

PROJECT INPUTS (replace every bracket):
- Website or staging URL: [URL or sanitized description]
- Business type and target audience: [DETAILS]
- WordPress version, theme, builder and relevant plugins: [VERIFIED STACK]
- Current behavior and desired outcome: [CURRENT / TARGET]
- Constraints (budget, hosting, deadlines, permissions): [CONSTRAINTS]
- Evidence supplied (screenshots, logs, analytics or brief): [EVIDENCE OR NONE]

DELIVERABLE: Produce a tailored kadence global typography plan for this project. Begin with a concise diagnosis or goal, then provide a prioritized step-by-step plan, implementation examples (code/configuration only where appropriate), validation tests, rollback options, and a client-facing summary. Explain assumptions and mark missing inputs as questions instead of inventing evidence. For any WordPress change, consider staging, backups, compatibility, mobile accessibility, privacy, security, and SEO impact. Distinguish verified observations from hypotheses. Never claim to have accessed a site, run a test, installed a plugin or measured performance unless evidence is supplied. For security-sensitive tasks, focus on authorized defensive work. End with clear acceptance criteria and the next safe action.

WP-025

Elementor section reconstruction

Use this when handling elementor section reconstruction for a WordPress client. Replace the bracketed project inputs, attach sanitized evidence, and verify all outputs before deployment.

Act as a senior WordPress developer and AI-assisted website optimization specialist. TASK: Elementor section reconstruction.

PROJECT INPUTS (replace every bracket):
- Website or staging URL: [URL or sanitized description]
- Business type and target audience: [DETAILS]
- WordPress version, theme, builder and relevant plugins: [VERIFIED STACK]
- Current behavior and desired outcome: [CURRENT / TARGET]
- Constraints (budget, hosting, deadlines, permissions): [CONSTRAINTS]
- Evidence supplied (screenshots, logs, analytics or brief): [EVIDENCE OR NONE]

DELIVERABLE: Produce a tailored elementor section reconstruction for this project. Begin with a concise diagnosis or goal, then provide a prioritized step-by-step plan, implementation examples (code/configuration only where appropriate), validation tests, rollback options, and a client-facing summary. Explain assumptions and mark missing inputs as questions instead of inventing evidence. For any WordPress change, consider staging, backups, compatibility, mobile accessibility, privacy, security, and SEO impact. Distinguish verified observations from hypotheses. Never claim to have accessed a site, run a test, installed a plugin or measured performance unless evidence is supplied. For security-sensitive tasks, focus on authorized defensive work. End with clear acceptance criteria and the next safe action.

WP-026

Elementor mobile breakpoint review

Use this when handling elementor mobile breakpoint review for a WordPress client. Replace the bracketed project inputs, attach sanitized evidence, and verify all outputs before deployment.

Act as a senior WordPress developer and AI-assisted website optimization specialist. TASK: Elementor mobile breakpoint review.

PROJECT INPUTS (replace every bracket):
- Website or staging URL: [URL or sanitized description]
- Business type and target audience: [DETAILS]
- WordPress version, theme, builder and relevant plugins: [VERIFIED STACK]
- Current behavior and desired outcome: [CURRENT / TARGET]
- Constraints (budget, hosting, deadlines, permissions): [CONSTRAINTS]
- Evidence supplied (screenshots, logs, analytics or brief): [EVIDENCE OR NONE]

DELIVERABLE: Produce a tailored elementor mobile breakpoint review for this project. Begin with a concise diagnosis or goal, then provide a prioritized step-by-step plan, implementation examples (code/configuration only where appropriate), validation tests, rollback options, and a client-facing summary. Explain assumptions and mark missing inputs as questions instead of inventing evidence. For any WordPress change, consider staging, backups, compatibility, mobile accessibility, privacy, security, and SEO impact. Distinguish verified observations from hypotheses. Never claim to have accessed a site, run a test, installed a plugin or measured performance unless evidence is supplied. For security-sensitive tasks, focus on authorized defensive work. End with clear acceptance criteria and the next safe action.

WP-027

Builder CSS conflict diagnosis

Use this when handling builder css conflict diagnosis for a WordPress client. Replace the bracketed project inputs, attach sanitized evidence, and verify all outputs before deployment.

Act as a senior WordPress developer and AI-assisted website optimization specialist. TASK: Builder CSS conflict diagnosis.

PROJECT INPUTS (replace every bracket):
- Website or staging URL: [URL or sanitized description]
- Business type and target audience: [DETAILS]
- WordPress version, theme, builder and relevant plugins: [VERIFIED STACK]
- Current behavior and desired outcome: [CURRENT / TARGET]
- Constraints (budget, hosting, deadlines, permissions): [CONSTRAINTS]
- Evidence supplied (screenshots, logs, analytics or brief): [EVIDENCE OR NONE]

DELIVERABLE: Produce a tailored builder css conflict diagnosis for this project. Begin with a concise diagnosis or goal, then provide a prioritized step-by-step plan, implementation examples (code/configuration only where appropriate), validation tests, rollback options, and a client-facing summary. Explain assumptions and mark missing inputs as questions instead of inventing evidence. For any WordPress change, consider staging, backups, compatibility, mobile accessibility, privacy, security, and SEO impact. Distinguish verified observations from hypotheses. Never claim to have accessed a site, run a test, installed a plugin or measured performance unless evidence is supplied. For security-sensitive tasks, focus on authorized defensive work. End with clear acceptance criteria and the next safe action.

WP-028

Header and footer specification

Use this when handling header and footer specification for a WordPress client. Replace the bracketed project inputs, attach sanitized evidence, and verify all outputs before deployment.

Act as a senior WordPress developer and AI-assisted website optimization specialist. TASK: Header and footer specification.

PROJECT INPUTS (replace every bracket):
- Website or staging URL: [URL or sanitized description]
- Business type and target audience: [DETAILS]
- WordPress version, theme, builder and relevant plugins: [VERIFIED STACK]
- Current behavior and desired outcome: [CURRENT / TARGET]
- Constraints (budget, hosting, deadlines, permissions): [CONSTRAINTS]
- Evidence supplied (screenshots, logs, analytics or brief): [EVIDENCE OR NONE]

DELIVERABLE: Produce a tailored header and footer specification for this project. Begin with a concise diagnosis or goal, then provide a prioritized step-by-step plan, implementation examples (code/configuration only where appropriate), validation tests, rollback options, and a client-facing summary. Explain assumptions and mark missing inputs as questions instead of inventing evidence. For any WordPress change, consider staging, backups, compatibility, mobile accessibility, privacy, security, and SEO impact. Distinguish verified observations from hypotheses. Never claim to have accessed a site, run a test, installed a plugin or measured performance unless evidence is supplied. For security-sensitive tasks, focus on authorized defensive work. End with clear acceptance criteria and the next safe action.

WP-029

Reusable template governance

Use this when handling reusable template governance for a WordPress client. Replace the bracketed project inputs, attach sanitized evidence, and verify all outputs before deployment.

Act as a senior WordPress developer and AI-assisted website optimization specialist. TASK: Reusable template governance.

PROJECT INPUTS (replace every bracket):
- Website or staging URL: [URL or sanitized description]
- Business type and target audience: [DETAILS]
- WordPress version, theme, builder and relevant plugins: [VERIFIED STACK]
- Current behavior and desired outcome: [CURRENT / TARGET]
- Constraints (budget, hosting, deadlines, permissions): [CONSTRAINTS]
- Evidence supplied (screenshots, logs, analytics or brief): [EVIDENCE OR NONE]

DELIVERABLE: Produce a tailored reusable template governance for this project. Begin with a concise diagnosis or goal, then provide a prioritized step-by-step plan, implementation examples (code/configuration only where appropriate), validation tests, rollback options, and a client-facing summary. Explain assumptions and mark missing inputs as questions instead of inventing evidence. For any WordPress change, consider staging, backups, compatibility, mobile accessibility, privacy, security, and SEO impact. Distinguish verified observations from hypotheses. Never claim to have accessed a site, run a test, installed a plugin or measured performance unless evidence is supplied. For security-sensitive tasks, focus on authorized defensive work. End with clear acceptance criteria and the next safe action.

WP-030

Builder handoff checklist

Use this when handling builder handoff checklist for a WordPress client. Replace the bracketed project inputs, attach sanitized evidence, and verify all outputs before deployment.

Act as a senior WordPress developer and AI-assisted website optimization specialist. TASK: Builder handoff checklist.

PROJECT INPUTS (replace every bracket):
- Website or staging URL: [URL or sanitized description]
- Business type and target audience: [DETAILS]
- WordPress version, theme, builder and relevant plugins: [VERIFIED STACK]
- Current behavior and desired outcome: [CURRENT / TARGET]
- Constraints (budget, hosting, deadlines, permissions): [CONSTRAINTS]
- Evidence supplied (screenshots, logs, analytics or brief): [EVIDENCE OR NONE]

DELIVERABLE: Produce a tailored builder handoff checklist for this project. Begin with a concise diagnosis or goal, then provide a prioritized step-by-step plan, implementation examples (code/configuration only where appropriate), validation tests, rollback options, and a client-facing summary. Explain assumptions and mark missing inputs as questions instead of inventing evidence. For any WordPress change, consider staging, backups, compatibility, mobile accessibility, privacy, security, and SEO impact. Distinguish verified observations from hypotheses. Never claim to have accessed a site, run a test, installed a plugin or measured performance unless evidence is supplied. For security-sensitive tasks, focus on authorized defensive work. End with clear acceptance criteria and the next safe action.

04. Themes & Frontend

WP-031

Child theme implementation plan

Use this when handling child theme implementation plan for a WordPress client. Replace the bracketed project inputs, attach sanitized evidence, and verify all outputs before deployment.

Act as a senior WordPress developer and AI-assisted website optimization specialist. TASK: Child theme implementation plan.

PROJECT INPUTS (replace every bracket):
- Website or staging URL: [URL or sanitized description]
- Business type and target audience: [DETAILS]
- WordPress version, theme, builder and relevant plugins: [VERIFIED STACK]
- Current behavior and desired outcome: [CURRENT / TARGET]
- Constraints (budget, hosting, deadlines, permissions): [CONSTRAINTS]
- Evidence supplied (screenshots, logs, analytics or brief): [EVIDENCE OR NONE]

DELIVERABLE: Produce a tailored child theme implementation plan for this project. Begin with a concise diagnosis or goal, then provide a prioritized step-by-step plan, implementation examples (code/configuration only where appropriate), validation tests, rollback options, and a client-facing summary. Explain assumptions and mark missing inputs as questions instead of inventing evidence. For any WordPress change, consider staging, backups, compatibility, mobile accessibility, privacy, security, and SEO impact. Distinguish verified observations from hypotheses. Never claim to have accessed a site, run a test, installed a plugin or measured performance unless evidence is supplied. For security-sensitive tasks, focus on authorized defensive work. End with clear acceptance criteria and the next safe action.

WP-032

Template hierarchy explanation

Use this when handling template hierarchy explanation for a WordPress client. Replace the bracketed project inputs, attach sanitized evidence, and verify all outputs before deployment.

Act as a senior WordPress developer and AI-assisted website optimization specialist. TASK: Template hierarchy explanation.

PROJECT INPUTS (replace every bracket):
- Website or staging URL: [URL or sanitized description]
- Business type and target audience: [DETAILS]
- WordPress version, theme, builder and relevant plugins: [VERIFIED STACK]
- Current behavior and desired outcome: [CURRENT / TARGET]
- Constraints (budget, hosting, deadlines, permissions): [CONSTRAINTS]
- Evidence supplied (screenshots, logs, analytics or brief): [EVIDENCE OR NONE]

DELIVERABLE: Produce a tailored template hierarchy explanation for this project. Begin with a concise diagnosis or goal, then provide a prioritized step-by-step plan, implementation examples (code/configuration only where appropriate), validation tests, rollback options, and a client-facing summary. Explain assumptions and mark missing inputs as questions instead of inventing evidence. For any WordPress change, consider staging, backups, compatibility, mobile accessibility, privacy, security, and SEO impact. Distinguish verified observations from hypotheses. Never claim to have accessed a site, run a test, installed a plugin or measured performance unless evidence is supplied. For security-sensitive tasks, focus on authorized defensive work. End with clear acceptance criteria and the next safe action.

WP-033

Theme.json configuration

Use this when handling theme.json configuration for a WordPress client. Replace the bracketed project inputs, attach sanitized evidence, and verify all outputs before deployment.

Act as a senior WordPress developer and AI-assisted website optimization specialist. TASK: Theme.json configuration.

PROJECT INPUTS (replace every bracket):
- Website or staging URL: [URL or sanitized description]
- Business type and target audience: [DETAILS]
- WordPress version, theme, builder and relevant plugins: [VERIFIED STACK]
- Current behavior and desired outcome: [CURRENT / TARGET]
- Constraints (budget, hosting, deadlines, permissions): [CONSTRAINTS]
- Evidence supplied (screenshots, logs, analytics or brief): [EVIDENCE OR NONE]

DELIVERABLE: Produce a tailored theme.json configuration for this project. Begin with a concise diagnosis or goal, then provide a prioritized step-by-step plan, implementation examples (code/configuration only where appropriate), validation tests, rollback options, and a client-facing summary. Explain assumptions and mark missing inputs as questions instead of inventing evidence. For any WordPress change, consider staging, backups, compatibility, mobile accessibility, privacy, security, and SEO impact. Distinguish verified observations from hypotheses. Never claim to have accessed a site, run a test, installed a plugin or measured performance unless evidence is supplied. For security-sensitive tasks, focus on authorized defensive work. End with clear acceptance criteria and the next safe action.

WP-034

Semantic HTML review

Use this when handling semantic html review for a WordPress client. Replace the bracketed project inputs, attach sanitized evidence, and verify all outputs before deployment.

Act as a senior WordPress developer and AI-assisted website optimization specialist. TASK: Semantic HTML review.

PROJECT INPUTS (replace every bracket):
- Website or staging URL: [URL or sanitized description]
- Business type and target audience: [DETAILS]
- WordPress version, theme, builder and relevant plugins: [VERIFIED STACK]
- Current behavior and desired outcome: [CURRENT / TARGET]
- Constraints (budget, hosting, deadlines, permissions): [CONSTRAINTS]
- Evidence supplied (screenshots, logs, analytics or brief): [EVIDENCE OR NONE]

DELIVERABLE: Produce a tailored semantic html review for this project. Begin with a concise diagnosis or goal, then provide a prioritized step-by-step plan, implementation examples (code/configuration only where appropriate), validation tests, rollback options, and a client-facing summary. Explain assumptions and mark missing inputs as questions instead of inventing evidence. For any WordPress change, consider staging, backups, compatibility, mobile accessibility, privacy, security, and SEO impact. Distinguish verified observations from hypotheses. Never claim to have accessed a site, run a test, installed a plugin or measured performance unless evidence is supplied. For security-sensitive tasks, focus on authorized defensive work. End with clear acceptance criteria and the next safe action.

WP-035

Responsive CSS refactoring

Use this when handling responsive css refactoring for a WordPress client. Replace the bracketed project inputs, attach sanitized evidence, and verify all outputs before deployment.

Act as a senior WordPress developer and AI-assisted website optimization specialist. TASK: Responsive CSS refactoring.

PROJECT INPUTS (replace every bracket):
- Website or staging URL: [URL or sanitized description]
- Business type and target audience: [DETAILS]
- WordPress version, theme, builder and relevant plugins: [VERIFIED STACK]
- Current behavior and desired outcome: [CURRENT / TARGET]
- Constraints (budget, hosting, deadlines, permissions): [CONSTRAINTS]
- Evidence supplied (screenshots, logs, analytics or brief): [EVIDENCE OR NONE]

DELIVERABLE: Produce a tailored responsive css refactoring for this project. Begin with a concise diagnosis or goal, then provide a prioritized step-by-step plan, implementation examples (code/configuration only where appropriate), validation tests, rollback options, and a client-facing summary. Explain assumptions and mark missing inputs as questions instead of inventing evidence. For any WordPress change, consider staging, backups, compatibility, mobile accessibility, privacy, security, and SEO impact. Distinguish verified observations from hypotheses. Never claim to have accessed a site, run a test, installed a plugin or measured performance unless evidence is supplied. For security-sensitive tasks, focus on authorized defensive work. End with clear acceptance criteria and the next safe action.

WP-036

JavaScript interaction review

Use this when handling javascript interaction review for a WordPress client. Replace the bracketed project inputs, attach sanitized evidence, and verify all outputs before deployment.

Act as a senior WordPress developer and AI-assisted website optimization specialist. TASK: JavaScript interaction review.

PROJECT INPUTS (replace every bracket):
- Website or staging URL: [URL or sanitized description]
- Business type and target audience: [DETAILS]
- WordPress version, theme, builder and relevant plugins: [VERIFIED STACK]
- Current behavior and desired outcome: [CURRENT / TARGET]
- Constraints (budget, hosting, deadlines, permissions): [CONSTRAINTS]
- Evidence supplied (screenshots, logs, analytics or brief): [EVIDENCE OR NONE]

DELIVERABLE: Produce a tailored javascript interaction review for this project. Begin with a concise diagnosis or goal, then provide a prioritized step-by-step plan, implementation examples (code/configuration only where appropriate), validation tests, rollback options, and a client-facing summary. Explain assumptions and mark missing inputs as questions instead of inventing evidence. For any WordPress change, consider staging, backups, compatibility, mobile accessibility, privacy, security, and SEO impact. Distinguish verified observations from hypotheses. Never claim to have accessed a site, run a test, installed a plugin or measured performance unless evidence is supplied. For security-sensitive tasks, focus on authorized defensive work. End with clear acceptance criteria and the next safe action.

WP-037

Design token system

Use this when handling design token system for a WordPress client. Replace the bracketed project inputs, attach sanitized evidence, and verify all outputs before deployment.

Act as a senior WordPress developer and AI-assisted website optimization specialist. TASK: Design token system.

PROJECT INPUTS (replace every bracket):
- Website or staging URL: [URL or sanitized description]
- Business type and target audience: [DETAILS]
- WordPress version, theme, builder and relevant plugins: [VERIFIED STACK]
- Current behavior and desired outcome: [CURRENT / TARGET]
- Constraints (budget, hosting, deadlines, permissions): [CONSTRAINTS]
- Evidence supplied (screenshots, logs, analytics or brief): [EVIDENCE OR NONE]

DELIVERABLE: Produce a tailored design token system for this project. Begin with a concise diagnosis or goal, then provide a prioritized step-by-step plan, implementation examples (code/configuration only where appropriate), validation tests, rollback options, and a client-facing summary. Explain assumptions and mark missing inputs as questions instead of inventing evidence. For any WordPress change, consider staging, backups, compatibility, mobile accessibility, privacy, security, and SEO impact. Distinguish verified observations from hypotheses. Never claim to have accessed a site, run a test, installed a plugin or measured performance unless evidence is supplied. For security-sensitive tasks, focus on authorized defensive work. End with clear acceptance criteria and the next safe action.

WP-038

Custom block implementation brief

Use this when handling custom block implementation brief for a WordPress client. Replace the bracketed project inputs, attach sanitized evidence, and verify all outputs before deployment.

Act as a senior WordPress developer and AI-assisted website optimization specialist. TASK: Custom block implementation brief.

PROJECT INPUTS (replace every bracket):
- Website or staging URL: [URL or sanitized description]
- Business type and target audience: [DETAILS]
- WordPress version, theme, builder and relevant plugins: [VERIFIED STACK]
- Current behavior and desired outcome: [CURRENT / TARGET]
- Constraints (budget, hosting, deadlines, permissions): [CONSTRAINTS]
- Evidence supplied (screenshots, logs, analytics or brief): [EVIDENCE OR NONE]

DELIVERABLE: Produce a tailored custom block implementation brief for this project. Begin with a concise diagnosis or goal, then provide a prioritized step-by-step plan, implementation examples (code/configuration only where appropriate), validation tests, rollback options, and a client-facing summary. Explain assumptions and mark missing inputs as questions instead of inventing evidence. For any WordPress change, consider staging, backups, compatibility, mobile accessibility, privacy, security, and SEO impact. Distinguish verified observations from hypotheses. Never claim to have accessed a site, run a test, installed a plugin or measured performance unless evidence is supplied. For security-sensitive tasks, focus on authorized defensive work. End with clear acceptance criteria and the next safe action.

WP-039

Cross-browser compatibility matrix

Use this when handling cross-browser compatibility matrix for a WordPress client. Replace the bracketed project inputs, attach sanitized evidence, and verify all outputs before deployment.

Act as a senior WordPress developer and AI-assisted website optimization specialist. TASK: Cross-browser compatibility matrix.

PROJECT INPUTS (replace every bracket):
- Website or staging URL: [URL or sanitized description]
- Business type and target audience: [DETAILS]
- WordPress version, theme, builder and relevant plugins: [VERIFIED STACK]
- Current behavior and desired outcome: [CURRENT / TARGET]
- Constraints (budget, hosting, deadlines, permissions): [CONSTRAINTS]
- Evidence supplied (screenshots, logs, analytics or brief): [EVIDENCE OR NONE]

DELIVERABLE: Produce a tailored cross-browser compatibility matrix for this project. Begin with a concise diagnosis or goal, then provide a prioritized step-by-step plan, implementation examples (code/configuration only where appropriate), validation tests, rollback options, and a client-facing summary. Explain assumptions and mark missing inputs as questions instead of inventing evidence. For any WordPress change, consider staging, backups, compatibility, mobile accessibility, privacy, security, and SEO impact. Distinguish verified observations from hypotheses. Never claim to have accessed a site, run a test, installed a plugin or measured performance unless evidence is supplied. For security-sensitive tasks, focus on authorized defensive work. End with clear acceptance criteria and the next safe action.

WP-040

Frontend visual regression plan

Use this when handling frontend visual regression plan for a WordPress client. Replace the bracketed project inputs, attach sanitized evidence, and verify all outputs before deployment.

Act as a senior WordPress developer and AI-assisted website optimization specialist. TASK: Frontend visual regression plan.

PROJECT INPUTS (replace every bracket):
- Website or staging URL: [URL or sanitized description]
- Business type and target audience: [DETAILS]
- WordPress version, theme, builder and relevant plugins: [VERIFIED STACK]
- Current behavior and desired outcome: [CURRENT / TARGET]
- Constraints (budget, hosting, deadlines, permissions): [CONSTRAINTS]
- Evidence supplied (screenshots, logs, analytics or brief): [EVIDENCE OR NONE]

DELIVERABLE: Produce a tailored frontend visual regression plan for this project. Begin with a concise diagnosis or goal, then provide a prioritized step-by-step plan, implementation examples (code/configuration only where appropriate), validation tests, rollback options, and a client-facing summary. Explain assumptions and mark missing inputs as questions instead of inventing evidence. For any WordPress change, consider staging, backups, compatibility, mobile accessibility, privacy, security, and SEO impact. Distinguish verified observations from hypotheses. Never claim to have accessed a site, run a test, installed a plugin or measured performance unless evidence is supplied. For security-sensitive tasks, focus on authorized defensive work. End with clear acceptance criteria and the next safe action.

05. Plugins & PHP

WP-041

Custom plugin specification

Use this when handling custom plugin specification for a WordPress client. Replace the bracketed project inputs, attach sanitized evidence, and verify all outputs before deployment.

Act as a senior WordPress developer and AI-assisted website optimization specialist. TASK: Custom plugin specification.

PROJECT INPUTS (replace every bracket):
- Website or staging URL: [URL or sanitized description]
- Business type and target audience: [DETAILS]
- WordPress version, theme, builder and relevant plugins: [VERIFIED STACK]
- Current behavior and desired outcome: [CURRENT / TARGET]
- Constraints (budget, hosting, deadlines, permissions): [CONSTRAINTS]
- Evidence supplied (screenshots, logs, analytics or brief): [EVIDENCE OR NONE]

DELIVERABLE: Produce a tailored custom plugin specification for this project. Begin with a concise diagnosis or goal, then provide a prioritized step-by-step plan, implementation examples (code/configuration only where appropriate), validation tests, rollback options, and a client-facing summary. Explain assumptions and mark missing inputs as questions instead of inventing evidence. For any WordPress change, consider staging, backups, compatibility, mobile accessibility, privacy, security, and SEO impact. Distinguish verified observations from hypotheses. Never claim to have accessed a site, run a test, installed a plugin or measured performance unless evidence is supplied. For security-sensitive tasks, focus on authorized defensive work. End with clear acceptance criteria and the next safe action.

WP-042

WordPress hook selection

Use this when handling wordpress hook selection for a WordPress client. Replace the bracketed project inputs, attach sanitized evidence, and verify all outputs before deployment.

Act as a senior WordPress developer and AI-assisted website optimization specialist. TASK: WordPress hook selection.

PROJECT INPUTS (replace every bracket):
- Website or staging URL: [URL or sanitized description]
- Business type and target audience: [DETAILS]
- WordPress version, theme, builder and relevant plugins: [VERIFIED STACK]
- Current behavior and desired outcome: [CURRENT / TARGET]
- Constraints (budget, hosting, deadlines, permissions): [CONSTRAINTS]
- Evidence supplied (screenshots, logs, analytics or brief): [EVIDENCE OR NONE]

DELIVERABLE: Produce a tailored wordpress hook selection for this project. Begin with a concise diagnosis or goal, then provide a prioritized step-by-step plan, implementation examples (code/configuration only where appropriate), validation tests, rollback options, and a client-facing summary. Explain assumptions and mark missing inputs as questions instead of inventing evidence. For any WordPress change, consider staging, backups, compatibility, mobile accessibility, privacy, security, and SEO impact. Distinguish verified observations from hypotheses. Never claim to have accessed a site, run a test, installed a plugin or measured performance unless evidence is supplied. For security-sensitive tasks, focus on authorized defensive work. End with clear acceptance criteria and the next safe action.

WP-043

PHP code review

Use this when handling php code review for a WordPress client. Replace the bracketed project inputs, attach sanitized evidence, and verify all outputs before deployment.

Act as a senior WordPress developer and AI-assisted website optimization specialist. TASK: PHP code review.

PROJECT INPUTS (replace every bracket):
- Website or staging URL: [URL or sanitized description]
- Business type and target audience: [DETAILS]
- WordPress version, theme, builder and relevant plugins: [VERIFIED STACK]
- Current behavior and desired outcome: [CURRENT / TARGET]
- Constraints (budget, hosting, deadlines, permissions): [CONSTRAINTS]
- Evidence supplied (screenshots, logs, analytics or brief): [EVIDENCE OR NONE]

DELIVERABLE: Produce a tailored php code review for this project. Begin with a concise diagnosis or goal, then provide a prioritized step-by-step plan, implementation examples (code/configuration only where appropriate), validation tests, rollback options, and a client-facing summary. Explain assumptions and mark missing inputs as questions instead of inventing evidence. For any WordPress change, consider staging, backups, compatibility, mobile accessibility, privacy, security, and SEO impact. Distinguish verified observations from hypotheses. Never claim to have accessed a site, run a test, installed a plugin or measured performance unless evidence is supplied. For security-sensitive tasks, focus on authorized defensive work. End with clear acceptance criteria and the next safe action.

WP-044

Nonce and capability validation

Use this when handling nonce and capability validation for a WordPress client. Replace the bracketed project inputs, attach sanitized evidence, and verify all outputs before deployment.

Act as a senior WordPress developer and AI-assisted website optimization specialist. TASK: Nonce and capability validation.

PROJECT INPUTS (replace every bracket):
- Website or staging URL: [URL or sanitized description]
- Business type and target audience: [DETAILS]
- WordPress version, theme, builder and relevant plugins: [VERIFIED STACK]
- Current behavior and desired outcome: [CURRENT / TARGET]
- Constraints (budget, hosting, deadlines, permissions): [CONSTRAINTS]
- Evidence supplied (screenshots, logs, analytics or brief): [EVIDENCE OR NONE]

DELIVERABLE: Produce a tailored nonce and capability validation for this project. Begin with a concise diagnosis or goal, then provide a prioritized step-by-step plan, implementation examples (code/configuration only where appropriate), validation tests, rollback options, and a client-facing summary. Explain assumptions and mark missing inputs as questions instead of inventing evidence. For any WordPress change, consider staging, backups, compatibility, mobile accessibility, privacy, security, and SEO impact. Distinguish verified observations from hypotheses. Never claim to have accessed a site, run a test, installed a plugin or measured performance unless evidence is supplied. For security-sensitive tasks, focus on authorized defensive work. End with clear acceptance criteria and the next safe action.

WP-045

REST API endpoint design

Use this when handling rest api endpoint design for a WordPress client. Replace the bracketed project inputs, attach sanitized evidence, and verify all outputs before deployment.

Act as a senior WordPress developer and AI-assisted website optimization specialist. TASK: REST API endpoint design.

PROJECT INPUTS (replace every bracket):
- Website or staging URL: [URL or sanitized description]
- Business type and target audience: [DETAILS]
- WordPress version, theme, builder and relevant plugins: [VERIFIED STACK]
- Current behavior and desired outcome: [CURRENT / TARGET]
- Constraints (budget, hosting, deadlines, permissions): [CONSTRAINTS]
- Evidence supplied (screenshots, logs, analytics or brief): [EVIDENCE OR NONE]

DELIVERABLE: Produce a tailored rest api endpoint design for this project. Begin with a concise diagnosis or goal, then provide a prioritized step-by-step plan, implementation examples (code/configuration only where appropriate), validation tests, rollback options, and a client-facing summary. Explain assumptions and mark missing inputs as questions instead of inventing evidence. For any WordPress change, consider staging, backups, compatibility, mobile accessibility, privacy, security, and SEO impact. Distinguish verified observations from hypotheses. Never claim to have accessed a site, run a test, installed a plugin or measured performance unless evidence is supplied. For security-sensitive tasks, focus on authorized defensive work. End with clear acceptance criteria and the next safe action.

WP-046

Form handling and validation

Use this when handling form handling and validation for a WordPress client. Replace the bracketed project inputs, attach sanitized evidence, and verify all outputs before deployment.

Act as a senior WordPress developer and AI-assisted website optimization specialist. TASK: Form handling and validation.

PROJECT INPUTS (replace every bracket):
- Website or staging URL: [URL or sanitized description]
- Business type and target audience: [DETAILS]
- WordPress version, theme, builder and relevant plugins: [VERIFIED STACK]
- Current behavior and desired outcome: [CURRENT / TARGET]
- Constraints (budget, hosting, deadlines, permissions): [CONSTRAINTS]
- Evidence supplied (screenshots, logs, analytics or brief): [EVIDENCE OR NONE]

DELIVERABLE: Produce a tailored form handling and validation for this project. Begin with a concise diagnosis or goal, then provide a prioritized step-by-step plan, implementation examples (code/configuration only where appropriate), validation tests, rollback options, and a client-facing summary. Explain assumptions and mark missing inputs as questions instead of inventing evidence. For any WordPress change, consider staging, backups, compatibility, mobile accessibility, privacy, security, and SEO impact. Distinguish verified observations from hypotheses. Never claim to have accessed a site, run a test, installed a plugin or measured performance unless evidence is supplied. For security-sensitive tasks, focus on authorized defensive work. End with clear acceptance criteria and the next safe action.

WP-047

Database query safety review

Use this when handling database query safety review for a WordPress client. Replace the bracketed project inputs, attach sanitized evidence, and verify all outputs before deployment.

Act as a senior WordPress developer and AI-assisted website optimization specialist. TASK: Database query safety review.

PROJECT INPUTS (replace every bracket):
- Website or staging URL: [URL or sanitized description]
- Business type and target audience: [DETAILS]
- WordPress version, theme, builder and relevant plugins: [VERIFIED STACK]
- Current behavior and desired outcome: [CURRENT / TARGET]
- Constraints (budget, hosting, deadlines, permissions): [CONSTRAINTS]
- Evidence supplied (screenshots, logs, analytics or brief): [EVIDENCE OR NONE]

DELIVERABLE: Produce a tailored database query safety review for this project. Begin with a concise diagnosis or goal, then provide a prioritized step-by-step plan, implementation examples (code/configuration only where appropriate), validation tests, rollback options, and a client-facing summary. Explain assumptions and mark missing inputs as questions instead of inventing evidence. For any WordPress change, consider staging, backups, compatibility, mobile accessibility, privacy, security, and SEO impact. Distinguish verified observations from hypotheses. Never claim to have accessed a site, run a test, installed a plugin or measured performance unless evidence is supplied. For security-sensitive tasks, focus on authorized defensive work. End with clear acceptance criteria and the next safe action.

WP-048

Plugin conflict investigation

Use this when handling plugin conflict investigation for a WordPress client. Replace the bracketed project inputs, attach sanitized evidence, and verify all outputs before deployment.

Act as a senior WordPress developer and AI-assisted website optimization specialist. TASK: Plugin conflict investigation.

PROJECT INPUTS (replace every bracket):
- Website or staging URL: [URL or sanitized description]
- Business type and target audience: [DETAILS]
- WordPress version, theme, builder and relevant plugins: [VERIFIED STACK]
- Current behavior and desired outcome: [CURRENT / TARGET]
- Constraints (budget, hosting, deadlines, permissions): [CONSTRAINTS]
- Evidence supplied (screenshots, logs, analytics or brief): [EVIDENCE OR NONE]

DELIVERABLE: Produce a tailored plugin conflict investigation for this project. Begin with a concise diagnosis or goal, then provide a prioritized step-by-step plan, implementation examples (code/configuration only where appropriate), validation tests, rollback options, and a client-facing summary. Explain assumptions and mark missing inputs as questions instead of inventing evidence. For any WordPress change, consider staging, backups, compatibility, mobile accessibility, privacy, security, and SEO impact. Distinguish verified observations from hypotheses. Never claim to have accessed a site, run a test, installed a plugin or measured performance unless evidence is supplied. For security-sensitive tasks, focus on authorized defensive work. End with clear acceptance criteria and the next safe action.

WP-049

WP-CLI operations plan

Use this when handling wp-cli operations plan for a WordPress client. Replace the bracketed project inputs, attach sanitized evidence, and verify all outputs before deployment.

Act as a senior WordPress developer and AI-assisted website optimization specialist. TASK: WP-CLI operations plan.

PROJECT INPUTS (replace every bracket):
- Website or staging URL: [URL or sanitized description]
- Business type and target audience: [DETAILS]
- WordPress version, theme, builder and relevant plugins: [VERIFIED STACK]
- Current behavior and desired outcome: [CURRENT / TARGET]
- Constraints (budget, hosting, deadlines, permissions): [CONSTRAINTS]
- Evidence supplied (screenshots, logs, analytics or brief): [EVIDENCE OR NONE]

DELIVERABLE: Produce a tailored wp-cli operations plan for this project. Begin with a concise diagnosis or goal, then provide a prioritized step-by-step plan, implementation examples (code/configuration only where appropriate), validation tests, rollback options, and a client-facing summary. Explain assumptions and mark missing inputs as questions instead of inventing evidence. For any WordPress change, consider staging, backups, compatibility, mobile accessibility, privacy, security, and SEO impact. Distinguish verified observations from hypotheses. Never claim to have accessed a site, run a test, installed a plugin or measured performance unless evidence is supplied. For security-sensitive tasks, focus on authorized defensive work. End with clear acceptance criteria and the next safe action.

WP-050

Plugin update rollback procedure

Use this when handling plugin update rollback procedure for a WordPress client. Replace the bracketed project inputs, attach sanitized evidence, and verify all outputs before deployment.

Act as a senior WordPress developer and AI-assisted website optimization specialist. TASK: Plugin update rollback procedure.

PROJECT INPUTS (replace every bracket):
- Website or staging URL: [URL or sanitized description]
- Business type and target audience: [DETAILS]
- WordPress version, theme, builder and relevant plugins: [VERIFIED STACK]
- Current behavior and desired outcome: [CURRENT / TARGET]
- Constraints (budget, hosting, deadlines, permissions): [CONSTRAINTS]
- Evidence supplied (screenshots, logs, analytics or brief): [EVIDENCE OR NONE]

DELIVERABLE: Produce a tailored plugin update rollback procedure for this project. Begin with a concise diagnosis or goal, then provide a prioritized step-by-step plan, implementation examples (code/configuration only where appropriate), validation tests, rollback options, and a client-facing summary. Explain assumptions and mark missing inputs as questions instead of inventing evidence. For any WordPress change, consider staging, backups, compatibility, mobile accessibility, privacy, security, and SEO impact. Distinguish verified observations from hypotheses. Never claim to have accessed a site, run a test, installed a plugin or measured performance unless evidence is supplied. For security-sensitive tasks, focus on authorized defensive work. End with clear acceptance criteria and the next safe action.

06. WooCommerce & Commerce

WP-051

Store requirements checklist

Use this when handling store requirements checklist for a WordPress client. Replace the bracketed project inputs, attach sanitized evidence, and verify all outputs before deployment.

Act as a senior WordPress developer and AI-assisted website optimization specialist. TASK: Store requirements checklist.

PROJECT INPUTS (replace every bracket):
- Website or staging URL: [URL or sanitized description]
- Business type and target audience: [DETAILS]
- WordPress version, theme, builder and relevant plugins: [VERIFIED STACK]
- Current behavior and desired outcome: [CURRENT / TARGET]
- Constraints (budget, hosting, deadlines, permissions): [CONSTRAINTS]
- Evidence supplied (screenshots, logs, analytics or brief): [EVIDENCE OR NONE]

DELIVERABLE: Produce a tailored store requirements checklist for this project. Begin with a concise diagnosis or goal, then provide a prioritized step-by-step plan, implementation examples (code/configuration only where appropriate), validation tests, rollback options, and a client-facing summary. Explain assumptions and mark missing inputs as questions instead of inventing evidence. For any WordPress change, consider staging, backups, compatibility, mobile accessibility, privacy, security, and SEO impact. Distinguish verified observations from hypotheses. Never claim to have accessed a site, run a test, installed a plugin or measured performance unless evidence is supplied. For security-sensitive tasks, focus on authorized defensive work. End with clear acceptance criteria and the next safe action.

WP-052

Product data schema

Use this when handling product data schema for a WordPress client. Replace the bracketed project inputs, attach sanitized evidence, and verify all outputs before deployment.

Act as a senior WordPress developer and AI-assisted website optimization specialist. TASK: Product data schema.

PROJECT INPUTS (replace every bracket):
- Website or staging URL: [URL or sanitized description]
- Business type and target audience: [DETAILS]
- WordPress version, theme, builder and relevant plugins: [VERIFIED STACK]
- Current behavior and desired outcome: [CURRENT / TARGET]
- Constraints (budget, hosting, deadlines, permissions): [CONSTRAINTS]
- Evidence supplied (screenshots, logs, analytics or brief): [EVIDENCE OR NONE]

DELIVERABLE: Produce a tailored product data schema for this project. Begin with a concise diagnosis or goal, then provide a prioritized step-by-step plan, implementation examples (code/configuration only where appropriate), validation tests, rollback options, and a client-facing summary. Explain assumptions and mark missing inputs as questions instead of inventing evidence. For any WordPress change, consider staging, backups, compatibility, mobile accessibility, privacy, security, and SEO impact. Distinguish verified observations from hypotheses. Never claim to have accessed a site, run a test, installed a plugin or measured performance unless evidence is supplied. For security-sensitive tasks, focus on authorized defensive work. End with clear acceptance criteria and the next safe action.

WP-053

Variable products setup

Use this when handling variable products setup for a WordPress client. Replace the bracketed project inputs, attach sanitized evidence, and verify all outputs before deployment.

Act as a senior WordPress developer and AI-assisted website optimization specialist. TASK: Variable products setup.

PROJECT INPUTS (replace every bracket):
- Website or staging URL: [URL or sanitized description]
- Business type and target audience: [DETAILS]
- WordPress version, theme, builder and relevant plugins: [VERIFIED STACK]
- Current behavior and desired outcome: [CURRENT / TARGET]
- Constraints (budget, hosting, deadlines, permissions): [CONSTRAINTS]
- Evidence supplied (screenshots, logs, analytics or brief): [EVIDENCE OR NONE]

DELIVERABLE: Produce a tailored variable products setup for this project. Begin with a concise diagnosis or goal, then provide a prioritized step-by-step plan, implementation examples (code/configuration only where appropriate), validation tests, rollback options, and a client-facing summary. Explain assumptions and mark missing inputs as questions instead of inventing evidence. For any WordPress change, consider staging, backups, compatibility, mobile accessibility, privacy, security, and SEO impact. Distinguish verified observations from hypotheses. Never claim to have accessed a site, run a test, installed a plugin or measured performance unless evidence is supplied. For security-sensitive tasks, focus on authorized defensive work. End with clear acceptance criteria and the next safe action.

WP-054

Cart and checkout UX audit

Use this when handling cart and checkout ux audit for a WordPress client. Replace the bracketed project inputs, attach sanitized evidence, and verify all outputs before deployment.

Act as a senior WordPress developer and AI-assisted website optimization specialist. TASK: Cart and checkout UX audit.

PROJECT INPUTS (replace every bracket):
- Website or staging URL: [URL or sanitized description]
- Business type and target audience: [DETAILS]
- WordPress version, theme, builder and relevant plugins: [VERIFIED STACK]
- Current behavior and desired outcome: [CURRENT / TARGET]
- Constraints (budget, hosting, deadlines, permissions): [CONSTRAINTS]
- Evidence supplied (screenshots, logs, analytics or brief): [EVIDENCE OR NONE]

DELIVERABLE: Produce a tailored cart and checkout ux audit for this project. Begin with a concise diagnosis or goal, then provide a prioritized step-by-step plan, implementation examples (code/configuration only where appropriate), validation tests, rollback options, and a client-facing summary. Explain assumptions and mark missing inputs as questions instead of inventing evidence. For any WordPress change, consider staging, backups, compatibility, mobile accessibility, privacy, security, and SEO impact. Distinguish verified observations from hypotheses. Never claim to have accessed a site, run a test, installed a plugin or measured performance unless evidence is supplied. For security-sensitive tasks, focus on authorized defensive work. End with clear acceptance criteria and the next safe action.

WP-055

Shipping zone configuration plan

Use this when handling shipping zone configuration plan for a WordPress client. Replace the bracketed project inputs, attach sanitized evidence, and verify all outputs before deployment.

Act as a senior WordPress developer and AI-assisted website optimization specialist. TASK: Shipping zone configuration plan.

PROJECT INPUTS (replace every bracket):
- Website or staging URL: [URL or sanitized description]
- Business type and target audience: [DETAILS]
- WordPress version, theme, builder and relevant plugins: [VERIFIED STACK]
- Current behavior and desired outcome: [CURRENT / TARGET]
- Constraints (budget, hosting, deadlines, permissions): [CONSTRAINTS]
- Evidence supplied (screenshots, logs, analytics or brief): [EVIDENCE OR NONE]

DELIVERABLE: Produce a tailored shipping zone configuration plan for this project. Begin with a concise diagnosis or goal, then provide a prioritized step-by-step plan, implementation examples (code/configuration only where appropriate), validation tests, rollback options, and a client-facing summary. Explain assumptions and mark missing inputs as questions instead of inventing evidence. For any WordPress change, consider staging, backups, compatibility, mobile accessibility, privacy, security, and SEO impact. Distinguish verified observations from hypotheses. Never claim to have accessed a site, run a test, installed a plugin or measured performance unless evidence is supplied. For security-sensitive tasks, focus on authorized defensive work. End with clear acceptance criteria and the next safe action.

WP-056

Tax configuration questions

Use this when handling tax configuration questions for a WordPress client. Replace the bracketed project inputs, attach sanitized evidence, and verify all outputs before deployment.

Act as a senior WordPress developer and AI-assisted website optimization specialist. TASK: Tax configuration questions.

PROJECT INPUTS (replace every bracket):
- Website or staging URL: [URL or sanitized description]
- Business type and target audience: [DETAILS]
- WordPress version, theme, builder and relevant plugins: [VERIFIED STACK]
- Current behavior and desired outcome: [CURRENT / TARGET]
- Constraints (budget, hosting, deadlines, permissions): [CONSTRAINTS]
- Evidence supplied (screenshots, logs, analytics or brief): [EVIDENCE OR NONE]

DELIVERABLE: Produce a tailored tax configuration questions for this project. Begin with a concise diagnosis or goal, then provide a prioritized step-by-step plan, implementation examples (code/configuration only where appropriate), validation tests, rollback options, and a client-facing summary. Explain assumptions and mark missing inputs as questions instead of inventing evidence. For any WordPress change, consider staging, backups, compatibility, mobile accessibility, privacy, security, and SEO impact. Distinguish verified observations from hypotheses. Never claim to have accessed a site, run a test, installed a plugin or measured performance unless evidence is supplied. For security-sensitive tasks, focus on authorized defensive work. End with clear acceptance criteria and the next safe action.

WP-057

Order lifecycle documentation

Use this when handling order lifecycle documentation for a WordPress client. Replace the bracketed project inputs, attach sanitized evidence, and verify all outputs before deployment.

Act as a senior WordPress developer and AI-assisted website optimization specialist. TASK: Order lifecycle documentation.

PROJECT INPUTS (replace every bracket):
- Website or staging URL: [URL or sanitized description]
- Business type and target audience: [DETAILS]
- WordPress version, theme, builder and relevant plugins: [VERIFIED STACK]
- Current behavior and desired outcome: [CURRENT / TARGET]
- Constraints (budget, hosting, deadlines, permissions): [CONSTRAINTS]
- Evidence supplied (screenshots, logs, analytics or brief): [EVIDENCE OR NONE]

DELIVERABLE: Produce a tailored order lifecycle documentation for this project. Begin with a concise diagnosis or goal, then provide a prioritized step-by-step plan, implementation examples (code/configuration only where appropriate), validation tests, rollback options, and a client-facing summary. Explain assumptions and mark missing inputs as questions instead of inventing evidence. For any WordPress change, consider staging, backups, compatibility, mobile accessibility, privacy, security, and SEO impact. Distinguish verified observations from hypotheses. Never claim to have accessed a site, run a test, installed a plugin or measured performance unless evidence is supplied. For security-sensitive tasks, focus on authorized defensive work. End with clear acceptance criteria and the next safe action.

WP-058

Store email customization brief

Use this when handling store email customization brief for a WordPress client. Replace the bracketed project inputs, attach sanitized evidence, and verify all outputs before deployment.

Act as a senior WordPress developer and AI-assisted website optimization specialist. TASK: Store email customization brief.

PROJECT INPUTS (replace every bracket):
- Website or staging URL: [URL or sanitized description]
- Business type and target audience: [DETAILS]
- WordPress version, theme, builder and relevant plugins: [VERIFIED STACK]
- Current behavior and desired outcome: [CURRENT / TARGET]
- Constraints (budget, hosting, deadlines, permissions): [CONSTRAINTS]
- Evidence supplied (screenshots, logs, analytics or brief): [EVIDENCE OR NONE]

DELIVERABLE: Produce a tailored store email customization brief for this project. Begin with a concise diagnosis or goal, then provide a prioritized step-by-step plan, implementation examples (code/configuration only where appropriate), validation tests, rollback options, and a client-facing summary. Explain assumptions and mark missing inputs as questions instead of inventing evidence. For any WordPress change, consider staging, backups, compatibility, mobile accessibility, privacy, security, and SEO impact. Distinguish verified observations from hypotheses. Never claim to have accessed a site, run a test, installed a plugin or measured performance unless evidence is supplied. For security-sensitive tasks, focus on authorized defensive work. End with clear acceptance criteria and the next safe action.

WP-059

WooCommerce performance audit

Use this when handling woocommerce performance audit for a WordPress client. Replace the bracketed project inputs, attach sanitized evidence, and verify all outputs before deployment.

Act as a senior WordPress developer and AI-assisted website optimization specialist. TASK: WooCommerce performance audit.

PROJECT INPUTS (replace every bracket):
- Website or staging URL: [URL or sanitized description]
- Business type and target audience: [DETAILS]
- WordPress version, theme, builder and relevant plugins: [VERIFIED STACK]
- Current behavior and desired outcome: [CURRENT / TARGET]
- Constraints (budget, hosting, deadlines, permissions): [CONSTRAINTS]
- Evidence supplied (screenshots, logs, analytics or brief): [EVIDENCE OR NONE]

DELIVERABLE: Produce a tailored woocommerce performance audit for this project. Begin with a concise diagnosis or goal, then provide a prioritized step-by-step plan, implementation examples (code/configuration only where appropriate), validation tests, rollback options, and a client-facing summary. Explain assumptions and mark missing inputs as questions instead of inventing evidence. For any WordPress change, consider staging, backups, compatibility, mobile accessibility, privacy, security, and SEO impact. Distinguish verified observations from hypotheses. Never claim to have accessed a site, run a test, installed a plugin or measured performance unless evidence is supplied. For security-sensitive tasks, focus on authorized defensive work. End with clear acceptance criteria and the next safe action.

WP-060

Commerce launch verification

Use this when handling commerce launch verification for a WordPress client. Replace the bracketed project inputs, attach sanitized evidence, and verify all outputs before deployment.

Act as a senior WordPress developer and AI-assisted website optimization specialist. TASK: Commerce launch verification.

PROJECT INPUTS (replace every bracket):
- Website or staging URL: [URL or sanitized description]
- Business type and target audience: [DETAILS]
- WordPress version, theme, builder and relevant plugins: [VERIFIED STACK]
- Current behavior and desired outcome: [CURRENT / TARGET]
- Constraints (budget, hosting, deadlines, permissions): [CONSTRAINTS]
- Evidence supplied (screenshots, logs, analytics or brief): [EVIDENCE OR NONE]

DELIVERABLE: Produce a tailored commerce launch verification for this project. Begin with a concise diagnosis or goal, then provide a prioritized step-by-step plan, implementation examples (code/configuration only where appropriate), validation tests, rollback options, and a client-facing summary. Explain assumptions and mark missing inputs as questions instead of inventing evidence. For any WordPress change, consider staging, backups, compatibility, mobile accessibility, privacy, security, and SEO impact. Distinguish verified observations from hypotheses. Never claim to have accessed a site, run a test, installed a plugin or measured performance unless evidence is supplied. For security-sensitive tasks, focus on authorized defensive work. End with clear acceptance criteria and the next safe action.

07. SEO & Content Structure

WP-061

Technical SEO site audit

Use this when handling technical seo site audit for a WordPress client. Replace the bracketed project inputs, attach sanitized evidence, and verify all outputs before deployment.

Act as a senior WordPress developer and AI-assisted website optimization specialist. TASK: Technical SEO site audit.

PROJECT INPUTS (replace every bracket):
- Website or staging URL: [URL or sanitized description]
- Business type and target audience: [DETAILS]
- WordPress version, theme, builder and relevant plugins: [VERIFIED STACK]
- Current behavior and desired outcome: [CURRENT / TARGET]
- Constraints (budget, hosting, deadlines, permissions): [CONSTRAINTS]
- Evidence supplied (screenshots, logs, analytics or brief): [EVIDENCE OR NONE]

DELIVERABLE: Produce a tailored technical seo site audit for this project. Begin with a concise diagnosis or goal, then provide a prioritized step-by-step plan, implementation examples (code/configuration only where appropriate), validation tests, rollback options, and a client-facing summary. Explain assumptions and mark missing inputs as questions instead of inventing evidence. For any WordPress change, consider staging, backups, compatibility, mobile accessibility, privacy, security, and SEO impact. Distinguish verified observations from hypotheses. Never claim to have accessed a site, run a test, installed a plugin or measured performance unless evidence is supplied. For security-sensitive tasks, focus on authorized defensive work. End with clear acceptance criteria and the next safe action.

WP-062

Search intent page map

Use this when handling search intent page map for a WordPress client. Replace the bracketed project inputs, attach sanitized evidence, and verify all outputs before deployment.

Act as a senior WordPress developer and AI-assisted website optimization specialist. TASK: Search intent page map.

PROJECT INPUTS (replace every bracket):
- Website or staging URL: [URL or sanitized description]
- Business type and target audience: [DETAILS]
- WordPress version, theme, builder and relevant plugins: [VERIFIED STACK]
- Current behavior and desired outcome: [CURRENT / TARGET]
- Constraints (budget, hosting, deadlines, permissions): [CONSTRAINTS]
- Evidence supplied (screenshots, logs, analytics or brief): [EVIDENCE OR NONE]

DELIVERABLE: Produce a tailored search intent page map for this project. Begin with a concise diagnosis or goal, then provide a prioritized step-by-step plan, implementation examples (code/configuration only where appropriate), validation tests, rollback options, and a client-facing summary. Explain assumptions and mark missing inputs as questions instead of inventing evidence. For any WordPress change, consider staging, backups, compatibility, mobile accessibility, privacy, security, and SEO impact. Distinguish verified observations from hypotheses. Never claim to have accessed a site, run a test, installed a plugin or measured performance unless evidence is supplied. For security-sensitive tasks, focus on authorized defensive work. End with clear acceptance criteria and the next safe action.

WP-063

Title and meta optimization

Use this when handling title and meta optimization for a WordPress client. Replace the bracketed project inputs, attach sanitized evidence, and verify all outputs before deployment.

Act as a senior WordPress developer and AI-assisted website optimization specialist. TASK: Title and meta optimization.

PROJECT INPUTS (replace every bracket):
- Website or staging URL: [URL or sanitized description]
- Business type and target audience: [DETAILS]
- WordPress version, theme, builder and relevant plugins: [VERIFIED STACK]
- Current behavior and desired outcome: [CURRENT / TARGET]
- Constraints (budget, hosting, deadlines, permissions): [CONSTRAINTS]
- Evidence supplied (screenshots, logs, analytics or brief): [EVIDENCE OR NONE]

DELIVERABLE: Produce a tailored title and meta optimization for this project. Begin with a concise diagnosis or goal, then provide a prioritized step-by-step plan, implementation examples (code/configuration only where appropriate), validation tests, rollback options, and a client-facing summary. Explain assumptions and mark missing inputs as questions instead of inventing evidence. For any WordPress change, consider staging, backups, compatibility, mobile accessibility, privacy, security, and SEO impact. Distinguish verified observations from hypotheses. Never claim to have accessed a site, run a test, installed a plugin or measured performance unless evidence is supplied. For security-sensitive tasks, focus on authorized defensive work. End with clear acceptance criteria and the next safe action.

WP-064

Internal linking plan

Use this when handling internal linking plan for a WordPress client. Replace the bracketed project inputs, attach sanitized evidence, and verify all outputs before deployment.

Act as a senior WordPress developer and AI-assisted website optimization specialist. TASK: Internal linking plan.

PROJECT INPUTS (replace every bracket):
- Website or staging URL: [URL or sanitized description]
- Business type and target audience: [DETAILS]
- WordPress version, theme, builder and relevant plugins: [VERIFIED STACK]
- Current behavior and desired outcome: [CURRENT / TARGET]
- Constraints (budget, hosting, deadlines, permissions): [CONSTRAINTS]
- Evidence supplied (screenshots, logs, analytics or brief): [EVIDENCE OR NONE]

DELIVERABLE: Produce a tailored internal linking plan for this project. Begin with a concise diagnosis or goal, then provide a prioritized step-by-step plan, implementation examples (code/configuration only where appropriate), validation tests, rollback options, and a client-facing summary. Explain assumptions and mark missing inputs as questions instead of inventing evidence. For any WordPress change, consider staging, backups, compatibility, mobile accessibility, privacy, security, and SEO impact. Distinguish verified observations from hypotheses. Never claim to have accessed a site, run a test, installed a plugin or measured performance unless evidence is supplied. For security-sensitive tasks, focus on authorized defensive work. End with clear acceptance criteria and the next safe action.

WP-065

Schema eligibility review

Use this when handling schema eligibility review for a WordPress client. Replace the bracketed project inputs, attach sanitized evidence, and verify all outputs before deployment.

Act as a senior WordPress developer and AI-assisted website optimization specialist. TASK: Schema eligibility review.

PROJECT INPUTS (replace every bracket):
- Website or staging URL: [URL or sanitized description]
- Business type and target audience: [DETAILS]
- WordPress version, theme, builder and relevant plugins: [VERIFIED STACK]
- Current behavior and desired outcome: [CURRENT / TARGET]
- Constraints (budget, hosting, deadlines, permissions): [CONSTRAINTS]
- Evidence supplied (screenshots, logs, analytics or brief): [EVIDENCE OR NONE]

DELIVERABLE: Produce a tailored schema eligibility review for this project. Begin with a concise diagnosis or goal, then provide a prioritized step-by-step plan, implementation examples (code/configuration only where appropriate), validation tests, rollback options, and a client-facing summary. Explain assumptions and mark missing inputs as questions instead of inventing evidence. For any WordPress change, consider staging, backups, compatibility, mobile accessibility, privacy, security, and SEO impact. Distinguish verified observations from hypotheses. Never claim to have accessed a site, run a test, installed a plugin or measured performance unless evidence is supplied. For security-sensitive tasks, focus on authorized defensive work. End with clear acceptance criteria and the next safe action.

WP-066

XML sitemap audit

Use this when handling xml sitemap audit for a WordPress client. Replace the bracketed project inputs, attach sanitized evidence, and verify all outputs before deployment.

Act as a senior WordPress developer and AI-assisted website optimization specialist. TASK: XML sitemap audit.

PROJECT INPUTS (replace every bracket):
- Website or staging URL: [URL or sanitized description]
- Business type and target audience: [DETAILS]
- WordPress version, theme, builder and relevant plugins: [VERIFIED STACK]
- Current behavior and desired outcome: [CURRENT / TARGET]
- Constraints (budget, hosting, deadlines, permissions): [CONSTRAINTS]
- Evidence supplied (screenshots, logs, analytics or brief): [EVIDENCE OR NONE]

DELIVERABLE: Produce a tailored xml sitemap audit for this project. Begin with a concise diagnosis or goal, then provide a prioritized step-by-step plan, implementation examples (code/configuration only where appropriate), validation tests, rollback options, and a client-facing summary. Explain assumptions and mark missing inputs as questions instead of inventing evidence. For any WordPress change, consider staging, backups, compatibility, mobile accessibility, privacy, security, and SEO impact. Distinguish verified observations from hypotheses. Never claim to have accessed a site, run a test, installed a plugin or measured performance unless evidence is supplied. For security-sensitive tasks, focus on authorized defensive work. End with clear acceptance criteria and the next safe action.

WP-067

Canonical and indexation review

Use this when handling canonical and indexation review for a WordPress client. Replace the bracketed project inputs, attach sanitized evidence, and verify all outputs before deployment.

Act as a senior WordPress developer and AI-assisted website optimization specialist. TASK: Canonical and indexation review.

PROJECT INPUTS (replace every bracket):
- Website or staging URL: [URL or sanitized description]
- Business type and target audience: [DETAILS]
- WordPress version, theme, builder and relevant plugins: [VERIFIED STACK]
- Current behavior and desired outcome: [CURRENT / TARGET]
- Constraints (budget, hosting, deadlines, permissions): [CONSTRAINTS]
- Evidence supplied (screenshots, logs, analytics or brief): [EVIDENCE OR NONE]

DELIVERABLE: Produce a tailored canonical and indexation review for this project. Begin with a concise diagnosis or goal, then provide a prioritized step-by-step plan, implementation examples (code/configuration only where appropriate), validation tests, rollback options, and a client-facing summary. Explain assumptions and mark missing inputs as questions instead of inventing evidence. For any WordPress change, consider staging, backups, compatibility, mobile accessibility, privacy, security, and SEO impact. Distinguish verified observations from hypotheses. Never claim to have accessed a site, run a test, installed a plugin or measured performance unless evidence is supplied. For security-sensitive tasks, focus on authorized defensive work. End with clear acceptance criteria and the next safe action.

WP-068

Redirect migration plan

Use this when handling redirect migration plan for a WordPress client. Replace the bracketed project inputs, attach sanitized evidence, and verify all outputs before deployment.

Act as a senior WordPress developer and AI-assisted website optimization specialist. TASK: Redirect migration plan.

PROJECT INPUTS (replace every bracket):
- Website or staging URL: [URL or sanitized description]
- Business type and target audience: [DETAILS]
- WordPress version, theme, builder and relevant plugins: [VERIFIED STACK]
- Current behavior and desired outcome: [CURRENT / TARGET]
- Constraints (budget, hosting, deadlines, permissions): [CONSTRAINTS]
- Evidence supplied (screenshots, logs, analytics or brief): [EVIDENCE OR NONE]

DELIVERABLE: Produce a tailored redirect migration plan for this project. Begin with a concise diagnosis or goal, then provide a prioritized step-by-step plan, implementation examples (code/configuration only where appropriate), validation tests, rollback options, and a client-facing summary. Explain assumptions and mark missing inputs as questions instead of inventing evidence. For any WordPress change, consider staging, backups, compatibility, mobile accessibility, privacy, security, and SEO impact. Distinguish verified observations from hypotheses. Never claim to have accessed a site, run a test, installed a plugin or measured performance unless evidence is supplied. For security-sensitive tasks, focus on authorized defensive work. End with clear acceptance criteria and the next safe action.

WP-069

Image alt text workflow

Use this when handling image alt text workflow for a WordPress client. Replace the bracketed project inputs, attach sanitized evidence, and verify all outputs before deployment.

Act as a senior WordPress developer and AI-assisted website optimization specialist. TASK: Image alt text workflow.

PROJECT INPUTS (replace every bracket):
- Website or staging URL: [URL or sanitized description]
- Business type and target audience: [DETAILS]
- WordPress version, theme, builder and relevant plugins: [VERIFIED STACK]
- Current behavior and desired outcome: [CURRENT / TARGET]
- Constraints (budget, hosting, deadlines, permissions): [CONSTRAINTS]
- Evidence supplied (screenshots, logs, analytics or brief): [EVIDENCE OR NONE]

DELIVERABLE: Produce a tailored image alt text workflow for this project. Begin with a concise diagnosis or goal, then provide a prioritized step-by-step plan, implementation examples (code/configuration only where appropriate), validation tests, rollback options, and a client-facing summary. Explain assumptions and mark missing inputs as questions instead of inventing evidence. For any WordPress change, consider staging, backups, compatibility, mobile accessibility, privacy, security, and SEO impact. Distinguish verified observations from hypotheses. Never claim to have accessed a site, run a test, installed a plugin or measured performance unless evidence is supplied. For security-sensitive tasks, focus on authorized defensive work. End with clear acceptance criteria and the next safe action.

WP-070

AEO and GEO content structure

Use this when handling aeo and geo content structure for a WordPress client. Replace the bracketed project inputs, attach sanitized evidence, and verify all outputs before deployment.

Act as a senior WordPress developer and AI-assisted website optimization specialist. TASK: AEO and GEO content structure.

PROJECT INPUTS (replace every bracket):
- Website or staging URL: [URL or sanitized description]
- Business type and target audience: [DETAILS]
- WordPress version, theme, builder and relevant plugins: [VERIFIED STACK]
- Current behavior and desired outcome: [CURRENT / TARGET]
- Constraints (budget, hosting, deadlines, permissions): [CONSTRAINTS]
- Evidence supplied (screenshots, logs, analytics or brief): [EVIDENCE OR NONE]

DELIVERABLE: Produce a tailored aeo and geo content structure for this project. Begin with a concise diagnosis or goal, then provide a prioritized step-by-step plan, implementation examples (code/configuration only where appropriate), validation tests, rollback options, and a client-facing summary. Explain assumptions and mark missing inputs as questions instead of inventing evidence. For any WordPress change, consider staging, backups, compatibility, mobile accessibility, privacy, security, and SEO impact. Distinguish verified observations from hypotheses. Never claim to have accessed a site, run a test, installed a plugin or measured performance unless evidence is supplied. For security-sensitive tasks, focus on authorized defensive work. End with clear acceptance criteria and the next safe action.

08. Performance & Core Web Vitals

WP-071

Performance measurement plan

Use this when handling performance measurement plan for a WordPress client. Replace the bracketed project inputs, attach sanitized evidence, and verify all outputs before deployment.

Act as a senior WordPress developer and AI-assisted website optimization specialist. TASK: Performance measurement plan.

PROJECT INPUTS (replace every bracket):
- Website or staging URL: [URL or sanitized description]
- Business type and target audience: [DETAILS]
- WordPress version, theme, builder and relevant plugins: [VERIFIED STACK]
- Current behavior and desired outcome: [CURRENT / TARGET]
- Constraints (budget, hosting, deadlines, permissions): [CONSTRAINTS]
- Evidence supplied (screenshots, logs, analytics or brief): [EVIDENCE OR NONE]

DELIVERABLE: Produce a tailored performance measurement plan for this project. Begin with a concise diagnosis or goal, then provide a prioritized step-by-step plan, implementation examples (code/configuration only where appropriate), validation tests, rollback options, and a client-facing summary. Explain assumptions and mark missing inputs as questions instead of inventing evidence. For any WordPress change, consider staging, backups, compatibility, mobile accessibility, privacy, security, and SEO impact. Distinguish verified observations from hypotheses. Never claim to have accessed a site, run a test, installed a plugin or measured performance unless evidence is supplied. For security-sensitive tasks, focus on authorized defensive work. End with clear acceptance criteria and the next safe action.

WP-072

LCP bottleneck diagnosis

Use this when handling lcp bottleneck diagnosis for a WordPress client. Replace the bracketed project inputs, attach sanitized evidence, and verify all outputs before deployment.

Act as a senior WordPress developer and AI-assisted website optimization specialist. TASK: LCP bottleneck diagnosis.

PROJECT INPUTS (replace every bracket):
- Website or staging URL: [URL or sanitized description]
- Business type and target audience: [DETAILS]
- WordPress version, theme, builder and relevant plugins: [VERIFIED STACK]
- Current behavior and desired outcome: [CURRENT / TARGET]
- Constraints (budget, hosting, deadlines, permissions): [CONSTRAINTS]
- Evidence supplied (screenshots, logs, analytics or brief): [EVIDENCE OR NONE]

DELIVERABLE: Produce a tailored lcp bottleneck diagnosis for this project. Begin with a concise diagnosis or goal, then provide a prioritized step-by-step plan, implementation examples (code/configuration only where appropriate), validation tests, rollback options, and a client-facing summary. Explain assumptions and mark missing inputs as questions instead of inventing evidence. For any WordPress change, consider staging, backups, compatibility, mobile accessibility, privacy, security, and SEO impact. Distinguish verified observations from hypotheses. Never claim to have accessed a site, run a test, installed a plugin or measured performance unless evidence is supplied. For security-sensitive tasks, focus on authorized defensive work. End with clear acceptance criteria and the next safe action.

WP-073

CLS remediation plan

Use this when handling cls remediation plan for a WordPress client. Replace the bracketed project inputs, attach sanitized evidence, and verify all outputs before deployment.

Act as a senior WordPress developer and AI-assisted website optimization specialist. TASK: CLS remediation plan.

PROJECT INPUTS (replace every bracket):
- Website or staging URL: [URL or sanitized description]
- Business type and target audience: [DETAILS]
- WordPress version, theme, builder and relevant plugins: [VERIFIED STACK]
- Current behavior and desired outcome: [CURRENT / TARGET]
- Constraints (budget, hosting, deadlines, permissions): [CONSTRAINTS]
- Evidence supplied (screenshots, logs, analytics or brief): [EVIDENCE OR NONE]

DELIVERABLE: Produce a tailored cls remediation plan for this project. Begin with a concise diagnosis or goal, then provide a prioritized step-by-step plan, implementation examples (code/configuration only where appropriate), validation tests, rollback options, and a client-facing summary. Explain assumptions and mark missing inputs as questions instead of inventing evidence. For any WordPress change, consider staging, backups, compatibility, mobile accessibility, privacy, security, and SEO impact. Distinguish verified observations from hypotheses. Never claim to have accessed a site, run a test, installed a plugin or measured performance unless evidence is supplied. For security-sensitive tasks, focus on authorized defensive work. End with clear acceptance criteria and the next safe action.

WP-074

INP interaction analysis

Use this when handling inp interaction analysis for a WordPress client. Replace the bracketed project inputs, attach sanitized evidence, and verify all outputs before deployment.

Act as a senior WordPress developer and AI-assisted website optimization specialist. TASK: INP interaction analysis.

PROJECT INPUTS (replace every bracket):
- Website or staging URL: [URL or sanitized description]
- Business type and target audience: [DETAILS]
- WordPress version, theme, builder and relevant plugins: [VERIFIED STACK]
- Current behavior and desired outcome: [CURRENT / TARGET]
- Constraints (budget, hosting, deadlines, permissions): [CONSTRAINTS]
- Evidence supplied (screenshots, logs, analytics or brief): [EVIDENCE OR NONE]

DELIVERABLE: Produce a tailored inp interaction analysis for this project. Begin with a concise diagnosis or goal, then provide a prioritized step-by-step plan, implementation examples (code/configuration only where appropriate), validation tests, rollback options, and a client-facing summary. Explain assumptions and mark missing inputs as questions instead of inventing evidence. For any WordPress change, consider staging, backups, compatibility, mobile accessibility, privacy, security, and SEO impact. Distinguish verified observations from hypotheses. Never claim to have accessed a site, run a test, installed a plugin or measured performance unless evidence is supplied. For security-sensitive tasks, focus on authorized defensive work. End with clear acceptance criteria and the next safe action.

WP-075

Caching strategy comparison

Use this when handling caching strategy comparison for a WordPress client. Replace the bracketed project inputs, attach sanitized evidence, and verify all outputs before deployment.

Act as a senior WordPress developer and AI-assisted website optimization specialist. TASK: Caching strategy comparison.

PROJECT INPUTS (replace every bracket):
- Website or staging URL: [URL or sanitized description]
- Business type and target audience: [DETAILS]
- WordPress version, theme, builder and relevant plugins: [VERIFIED STACK]
- Current behavior and desired outcome: [CURRENT / TARGET]
- Constraints (budget, hosting, deadlines, permissions): [CONSTRAINTS]
- Evidence supplied (screenshots, logs, analytics or brief): [EVIDENCE OR NONE]

DELIVERABLE: Produce a tailored caching strategy comparison for this project. Begin with a concise diagnosis or goal, then provide a prioritized step-by-step plan, implementation examples (code/configuration only where appropriate), validation tests, rollback options, and a client-facing summary. Explain assumptions and mark missing inputs as questions instead of inventing evidence. For any WordPress change, consider staging, backups, compatibility, mobile accessibility, privacy, security, and SEO impact. Distinguish verified observations from hypotheses. Never claim to have accessed a site, run a test, installed a plugin or measured performance unless evidence is supplied. For security-sensitive tasks, focus on authorized defensive work. End with clear acceptance criteria and the next safe action.

WP-076

Image compression and sizing

Use this when handling image compression and sizing for a WordPress client. Replace the bracketed project inputs, attach sanitized evidence, and verify all outputs before deployment.

Act as a senior WordPress developer and AI-assisted website optimization specialist. TASK: Image compression and sizing.

PROJECT INPUTS (replace every bracket):
- Website or staging URL: [URL or sanitized description]
- Business type and target audience: [DETAILS]
- WordPress version, theme, builder and relevant plugins: [VERIFIED STACK]
- Current behavior and desired outcome: [CURRENT / TARGET]
- Constraints (budget, hosting, deadlines, permissions): [CONSTRAINTS]
- Evidence supplied (screenshots, logs, analytics or brief): [EVIDENCE OR NONE]

DELIVERABLE: Produce a tailored image compression and sizing for this project. Begin with a concise diagnosis or goal, then provide a prioritized step-by-step plan, implementation examples (code/configuration only where appropriate), validation tests, rollback options, and a client-facing summary. Explain assumptions and mark missing inputs as questions instead of inventing evidence. For any WordPress change, consider staging, backups, compatibility, mobile accessibility, privacy, security, and SEO impact. Distinguish verified observations from hypotheses. Never claim to have accessed a site, run a test, installed a plugin or measured performance unless evidence is supplied. For security-sensitive tasks, focus on authorized defensive work. End with clear acceptance criteria and the next safe action.

WP-077

Font loading audit

Use this when handling font loading audit for a WordPress client. Replace the bracketed project inputs, attach sanitized evidence, and verify all outputs before deployment.

Act as a senior WordPress developer and AI-assisted website optimization specialist. TASK: Font loading audit.

PROJECT INPUTS (replace every bracket):
- Website or staging URL: [URL or sanitized description]
- Business type and target audience: [DETAILS]
- WordPress version, theme, builder and relevant plugins: [VERIFIED STACK]
- Current behavior and desired outcome: [CURRENT / TARGET]
- Constraints (budget, hosting, deadlines, permissions): [CONSTRAINTS]
- Evidence supplied (screenshots, logs, analytics or brief): [EVIDENCE OR NONE]

DELIVERABLE: Produce a tailored font loading audit for this project. Begin with a concise diagnosis or goal, then provide a prioritized step-by-step plan, implementation examples (code/configuration only where appropriate), validation tests, rollback options, and a client-facing summary. Explain assumptions and mark missing inputs as questions instead of inventing evidence. For any WordPress change, consider staging, backups, compatibility, mobile accessibility, privacy, security, and SEO impact. Distinguish verified observations from hypotheses. Never claim to have accessed a site, run a test, installed a plugin or measured performance unless evidence is supplied. For security-sensitive tasks, focus on authorized defensive work. End with clear acceptance criteria and the next safe action.

WP-078

Critical CSS assessment

Use this when handling critical css assessment for a WordPress client. Replace the bracketed project inputs, attach sanitized evidence, and verify all outputs before deployment.

Act as a senior WordPress developer and AI-assisted website optimization specialist. TASK: Critical CSS assessment.

PROJECT INPUTS (replace every bracket):
- Website or staging URL: [URL or sanitized description]
- Business type and target audience: [DETAILS]
- WordPress version, theme, builder and relevant plugins: [VERIFIED STACK]
- Current behavior and desired outcome: [CURRENT / TARGET]
- Constraints (budget, hosting, deadlines, permissions): [CONSTRAINTS]
- Evidence supplied (screenshots, logs, analytics or brief): [EVIDENCE OR NONE]

DELIVERABLE: Produce a tailored critical css assessment for this project. Begin with a concise diagnosis or goal, then provide a prioritized step-by-step plan, implementation examples (code/configuration only where appropriate), validation tests, rollback options, and a client-facing summary. Explain assumptions and mark missing inputs as questions instead of inventing evidence. For any WordPress change, consider staging, backups, compatibility, mobile accessibility, privacy, security, and SEO impact. Distinguish verified observations from hypotheses. Never claim to have accessed a site, run a test, installed a plugin or measured performance unless evidence is supplied. For security-sensitive tasks, focus on authorized defensive work. End with clear acceptance criteria and the next safe action.

WP-079

Plugin performance isolation

Use this when handling plugin performance isolation for a WordPress client. Replace the bracketed project inputs, attach sanitized evidence, and verify all outputs before deployment.

Act as a senior WordPress developer and AI-assisted website optimization specialist. TASK: Plugin performance isolation.

PROJECT INPUTS (replace every bracket):
- Website or staging URL: [URL or sanitized description]
- Business type and target audience: [DETAILS]
- WordPress version, theme, builder and relevant plugins: [VERIFIED STACK]
- Current behavior and desired outcome: [CURRENT / TARGET]
- Constraints (budget, hosting, deadlines, permissions): [CONSTRAINTS]
- Evidence supplied (screenshots, logs, analytics or brief): [EVIDENCE OR NONE]

DELIVERABLE: Produce a tailored plugin performance isolation for this project. Begin with a concise diagnosis or goal, then provide a prioritized step-by-step plan, implementation examples (code/configuration only where appropriate), validation tests, rollback options, and a client-facing summary. Explain assumptions and mark missing inputs as questions instead of inventing evidence. For any WordPress change, consider staging, backups, compatibility, mobile accessibility, privacy, security, and SEO impact. Distinguish verified observations from hypotheses. Never claim to have accessed a site, run a test, installed a plugin or measured performance unless evidence is supplied. For security-sensitive tasks, focus on authorized defensive work. End with clear acceptance criteria and the next safe action.

WP-080

Post-optimization regression checklist

Use this when handling post-optimization regression checklist for a WordPress client. Replace the bracketed project inputs, attach sanitized evidence, and verify all outputs before deployment.

Act as a senior WordPress developer and AI-assisted website optimization specialist. TASK: Post-optimization regression checklist.

PROJECT INPUTS (replace every bracket):
- Website or staging URL: [URL or sanitized description]
- Business type and target audience: [DETAILS]
- WordPress version, theme, builder and relevant plugins: [VERIFIED STACK]
- Current behavior and desired outcome: [CURRENT / TARGET]
- Constraints (budget, hosting, deadlines, permissions): [CONSTRAINTS]
- Evidence supplied (screenshots, logs, analytics or brief): [EVIDENCE OR NONE]

DELIVERABLE: Produce a tailored post-optimization regression checklist for this project. Begin with a concise diagnosis or goal, then provide a prioritized step-by-step plan, implementation examples (code/configuration only where appropriate), validation tests, rollback options, and a client-facing summary. Explain assumptions and mark missing inputs as questions instead of inventing evidence. For any WordPress change, consider staging, backups, compatibility, mobile accessibility, privacy, security, and SEO impact. Distinguish verified observations from hypotheses. Never claim to have accessed a site, run a test, installed a plugin or measured performance unless evidence is supplied. For security-sensitive tasks, focus on authorized defensive work. End with clear acceptance criteria and the next safe action.

09. Security & Privacy

WP-081

Least privilege access audit

Use this when handling least privilege access audit for a WordPress client. Replace the bracketed project inputs, attach sanitized evidence, and verify all outputs before deployment.

Act as a senior WordPress developer and AI-assisted website optimization specialist. TASK: Least privilege access audit.

PROJECT INPUTS (replace every bracket):
- Website or staging URL: [URL or sanitized description]
- Business type and target audience: [DETAILS]
- WordPress version, theme, builder and relevant plugins: [VERIFIED STACK]
- Current behavior and desired outcome: [CURRENT / TARGET]
- Constraints (budget, hosting, deadlines, permissions): [CONSTRAINTS]
- Evidence supplied (screenshots, logs, analytics or brief): [EVIDENCE OR NONE]

DELIVERABLE: Produce a tailored least privilege access audit for this project. Begin with a concise diagnosis or goal, then provide a prioritized step-by-step plan, implementation examples (code/configuration only where appropriate), validation tests, rollback options, and a client-facing summary. Explain assumptions and mark missing inputs as questions instead of inventing evidence. For any WordPress change, consider staging, backups, compatibility, mobile accessibility, privacy, security, and SEO impact. Distinguish verified observations from hypotheses. Never claim to have accessed a site, run a test, installed a plugin or measured performance unless evidence is supplied. For security-sensitive tasks, focus on authorized defensive work. End with clear acceptance criteria and the next safe action.

WP-082

WordPress hardening checklist

Use this when handling wordpress hardening checklist for a WordPress client. Replace the bracketed project inputs, attach sanitized evidence, and verify all outputs before deployment.

Act as a senior WordPress developer and AI-assisted website optimization specialist. TASK: WordPress hardening checklist.

PROJECT INPUTS (replace every bracket):
- Website or staging URL: [URL or sanitized description]
- Business type and target audience: [DETAILS]
- WordPress version, theme, builder and relevant plugins: [VERIFIED STACK]
- Current behavior and desired outcome: [CURRENT / TARGET]
- Constraints (budget, hosting, deadlines, permissions): [CONSTRAINTS]
- Evidence supplied (screenshots, logs, analytics or brief): [EVIDENCE OR NONE]

DELIVERABLE: Produce a tailored wordpress hardening checklist for this project. Begin with a concise diagnosis or goal, then provide a prioritized step-by-step plan, implementation examples (code/configuration only where appropriate), validation tests, rollback options, and a client-facing summary. Explain assumptions and mark missing inputs as questions instead of inventing evidence. For any WordPress change, consider staging, backups, compatibility, mobile accessibility, privacy, security, and SEO impact. Distinguish verified observations from hypotheses. Never claim to have accessed a site, run a test, installed a plugin or measured performance unless evidence is supplied. For security-sensitive tasks, focus on authorized defensive work. End with clear acceptance criteria and the next safe action.

WP-083

Backup and restore drill

Use this when handling backup and restore drill for a WordPress client. Replace the bracketed project inputs, attach sanitized evidence, and verify all outputs before deployment.

Act as a senior WordPress developer and AI-assisted website optimization specialist. TASK: Backup and restore drill.

PROJECT INPUTS (replace every bracket):
- Website or staging URL: [URL or sanitized description]
- Business type and target audience: [DETAILS]
- WordPress version, theme, builder and relevant plugins: [VERIFIED STACK]
- Current behavior and desired outcome: [CURRENT / TARGET]
- Constraints (budget, hosting, deadlines, permissions): [CONSTRAINTS]
- Evidence supplied (screenshots, logs, analytics or brief): [EVIDENCE OR NONE]

DELIVERABLE: Produce a tailored backup and restore drill for this project. Begin with a concise diagnosis or goal, then provide a prioritized step-by-step plan, implementation examples (code/configuration only where appropriate), validation tests, rollback options, and a client-facing summary. Explain assumptions and mark missing inputs as questions instead of inventing evidence. For any WordPress change, consider staging, backups, compatibility, mobile accessibility, privacy, security, and SEO impact. Distinguish verified observations from hypotheses. Never claim to have accessed a site, run a test, installed a plugin or measured performance unless evidence is supplied. For security-sensitive tasks, focus on authorized defensive work. End with clear acceptance criteria and the next safe action.

WP-084

Malware incident triage

Use this when handling malware incident triage for a WordPress client. Replace the bracketed project inputs, attach sanitized evidence, and verify all outputs before deployment.

Act as a senior WordPress developer and AI-assisted website optimization specialist. TASK: Malware incident triage.

PROJECT INPUTS (replace every bracket):
- Website or staging URL: [URL or sanitized description]
- Business type and target audience: [DETAILS]
- WordPress version, theme, builder and relevant plugins: [VERIFIED STACK]
- Current behavior and desired outcome: [CURRENT / TARGET]
- Constraints (budget, hosting, deadlines, permissions): [CONSTRAINTS]
- Evidence supplied (screenshots, logs, analytics or brief): [EVIDENCE OR NONE]

DELIVERABLE: Produce a tailored malware incident triage for this project. Begin with a concise diagnosis or goal, then provide a prioritized step-by-step plan, implementation examples (code/configuration only where appropriate), validation tests, rollback options, and a client-facing summary. Explain assumptions and mark missing inputs as questions instead of inventing evidence. For any WordPress change, consider staging, backups, compatibility, mobile accessibility, privacy, security, and SEO impact. Distinguish verified observations from hypotheses. Never claim to have accessed a site, run a test, installed a plugin or measured performance unless evidence is supplied. For security-sensitive tasks, focus on authorized defensive work. End with clear acceptance criteria and the next safe action.

WP-085

Login protection design

Use this when handling login protection design for a WordPress client. Replace the bracketed project inputs, attach sanitized evidence, and verify all outputs before deployment.

Act as a senior WordPress developer and AI-assisted website optimization specialist. TASK: Login protection design.

PROJECT INPUTS (replace every bracket):
- Website or staging URL: [URL or sanitized description]
- Business type and target audience: [DETAILS]
- WordPress version, theme, builder and relevant plugins: [VERIFIED STACK]
- Current behavior and desired outcome: [CURRENT / TARGET]
- Constraints (budget, hosting, deadlines, permissions): [CONSTRAINTS]
- Evidence supplied (screenshots, logs, analytics or brief): [EVIDENCE OR NONE]

DELIVERABLE: Produce a tailored login protection design for this project. Begin with a concise diagnosis or goal, then provide a prioritized step-by-step plan, implementation examples (code/configuration only where appropriate), validation tests, rollback options, and a client-facing summary. Explain assumptions and mark missing inputs as questions instead of inventing evidence. For any WordPress change, consider staging, backups, compatibility, mobile accessibility, privacy, security, and SEO impact. Distinguish verified observations from hypotheses. Never claim to have accessed a site, run a test, installed a plugin or measured performance unless evidence is supplied. For security-sensitive tasks, focus on authorized defensive work. End with clear acceptance criteria and the next safe action.

WP-086

Vulnerability patch prioritization

Use this when handling vulnerability patch prioritization for a WordPress client. Replace the bracketed project inputs, attach sanitized evidence, and verify all outputs before deployment.

Act as a senior WordPress developer and AI-assisted website optimization specialist. TASK: Vulnerability patch prioritization.

PROJECT INPUTS (replace every bracket):
- Website or staging URL: [URL or sanitized description]
- Business type and target audience: [DETAILS]
- WordPress version, theme, builder and relevant plugins: [VERIFIED STACK]
- Current behavior and desired outcome: [CURRENT / TARGET]
- Constraints (budget, hosting, deadlines, permissions): [CONSTRAINTS]
- Evidence supplied (screenshots, logs, analytics or brief): [EVIDENCE OR NONE]

DELIVERABLE: Produce a tailored vulnerability patch prioritization for this project. Begin with a concise diagnosis or goal, then provide a prioritized step-by-step plan, implementation examples (code/configuration only where appropriate), validation tests, rollback options, and a client-facing summary. Explain assumptions and mark missing inputs as questions instead of inventing evidence. For any WordPress change, consider staging, backups, compatibility, mobile accessibility, privacy, security, and SEO impact. Distinguish verified observations from hypotheses. Never claim to have accessed a site, run a test, installed a plugin or measured performance unless evidence is supplied. For security-sensitive tasks, focus on authorized defensive work. End with clear acceptance criteria and the next safe action.

WP-087

Privacy data flow map

Use this when handling privacy data flow map for a WordPress client. Replace the bracketed project inputs, attach sanitized evidence, and verify all outputs before deployment.

Act as a senior WordPress developer and AI-assisted website optimization specialist. TASK: Privacy data flow map.

PROJECT INPUTS (replace every bracket):
- Website or staging URL: [URL or sanitized description]
- Business type and target audience: [DETAILS]
- WordPress version, theme, builder and relevant plugins: [VERIFIED STACK]
- Current behavior and desired outcome: [CURRENT / TARGET]
- Constraints (budget, hosting, deadlines, permissions): [CONSTRAINTS]
- Evidence supplied (screenshots, logs, analytics or brief): [EVIDENCE OR NONE]

DELIVERABLE: Produce a tailored privacy data flow map for this project. Begin with a concise diagnosis or goal, then provide a prioritized step-by-step plan, implementation examples (code/configuration only where appropriate), validation tests, rollback options, and a client-facing summary. Explain assumptions and mark missing inputs as questions instead of inventing evidence. For any WordPress change, consider staging, backups, compatibility, mobile accessibility, privacy, security, and SEO impact. Distinguish verified observations from hypotheses. Never claim to have accessed a site, run a test, installed a plugin or measured performance unless evidence is supplied. For security-sensitive tasks, focus on authorized defensive work. End with clear acceptance criteria and the next safe action.

WP-088

Secure API credentials handling

Use this when handling secure api credentials handling for a WordPress client. Replace the bracketed project inputs, attach sanitized evidence, and verify all outputs before deployment.

Act as a senior WordPress developer and AI-assisted website optimization specialist. TASK: Secure API credentials handling.

PROJECT INPUTS (replace every bracket):
- Website or staging URL: [URL or sanitized description]
- Business type and target audience: [DETAILS]
- WordPress version, theme, builder and relevant plugins: [VERIFIED STACK]
- Current behavior and desired outcome: [CURRENT / TARGET]
- Constraints (budget, hosting, deadlines, permissions): [CONSTRAINTS]
- Evidence supplied (screenshots, logs, analytics or brief): [EVIDENCE OR NONE]

DELIVERABLE: Produce a tailored secure api credentials handling for this project. Begin with a concise diagnosis or goal, then provide a prioritized step-by-step plan, implementation examples (code/configuration only where appropriate), validation tests, rollback options, and a client-facing summary. Explain assumptions and mark missing inputs as questions instead of inventing evidence. For any WordPress change, consider staging, backups, compatibility, mobile accessibility, privacy, security, and SEO impact. Distinguish verified observations from hypotheses. Never claim to have accessed a site, run a test, installed a plugin or measured performance unless evidence is supplied. For security-sensitive tasks, focus on authorized defensive work. End with clear acceptance criteria and the next safe action.

WP-089

Security logging plan

Use this when handling security logging plan for a WordPress client. Replace the bracketed project inputs, attach sanitized evidence, and verify all outputs before deployment.

Act as a senior WordPress developer and AI-assisted website optimization specialist. TASK: Security logging plan.

PROJECT INPUTS (replace every bracket):
- Website or staging URL: [URL or sanitized description]
- Business type and target audience: [DETAILS]
- WordPress version, theme, builder and relevant plugins: [VERIFIED STACK]
- Current behavior and desired outcome: [CURRENT / TARGET]
- Constraints (budget, hosting, deadlines, permissions): [CONSTRAINTS]
- Evidence supplied (screenshots, logs, analytics or brief): [EVIDENCE OR NONE]

DELIVERABLE: Produce a tailored security logging plan for this project. Begin with a concise diagnosis or goal, then provide a prioritized step-by-step plan, implementation examples (code/configuration only where appropriate), validation tests, rollback options, and a client-facing summary. Explain assumptions and mark missing inputs as questions instead of inventing evidence. For any WordPress change, consider staging, backups, compatibility, mobile accessibility, privacy, security, and SEO impact. Distinguish verified observations from hypotheses. Never claim to have accessed a site, run a test, installed a plugin or measured performance unless evidence is supplied. For security-sensitive tasks, focus on authorized defensive work. End with clear acceptance criteria and the next safe action.

WP-090

Incident communication template

Use this when handling incident communication template for a WordPress client. Replace the bracketed project inputs, attach sanitized evidence, and verify all outputs before deployment.

Act as a senior WordPress developer and AI-assisted website optimization specialist. TASK: Incident communication template.

PROJECT INPUTS (replace every bracket):
- Website or staging URL: [URL or sanitized description]
- Business type and target audience: [DETAILS]
- WordPress version, theme, builder and relevant plugins: [VERIFIED STACK]
- Current behavior and desired outcome: [CURRENT / TARGET]
- Constraints (budget, hosting, deadlines, permissions): [CONSTRAINTS]
- Evidence supplied (screenshots, logs, analytics or brief): [EVIDENCE OR NONE]

DELIVERABLE: Produce a tailored incident communication template for this project. Begin with a concise diagnosis or goal, then provide a prioritized step-by-step plan, implementation examples (code/configuration only where appropriate), validation tests, rollback options, and a client-facing summary. Explain assumptions and mark missing inputs as questions instead of inventing evidence. For any WordPress change, consider staging, backups, compatibility, mobile accessibility, privacy, security, and SEO impact. Distinguish verified observations from hypotheses. Never claim to have accessed a site, run a test, installed a plugin or measured performance unless evidence is supplied. For security-sensitive tasks, focus on authorized defensive work. End with clear acceptance criteria and the next safe action.

10. Testing & Debugging

WP-091

Bug reproduction template

Use this when handling bug reproduction template for a WordPress client. Replace the bracketed project inputs, attach sanitized evidence, and verify all outputs before deployment.

Act as a senior WordPress developer and AI-assisted website optimization specialist. TASK: Bug reproduction template.

PROJECT INPUTS (replace every bracket):
- Website or staging URL: [URL or sanitized description]
- Business type and target audience: [DETAILS]
- WordPress version, theme, builder and relevant plugins: [VERIFIED STACK]
- Current behavior and desired outcome: [CURRENT / TARGET]
- Constraints (budget, hosting, deadlines, permissions): [CONSTRAINTS]
- Evidence supplied (screenshots, logs, analytics or brief): [EVIDENCE OR NONE]

DELIVERABLE: Produce a tailored bug reproduction template for this project. Begin with a concise diagnosis or goal, then provide a prioritized step-by-step plan, implementation examples (code/configuration only where appropriate), validation tests, rollback options, and a client-facing summary. Explain assumptions and mark missing inputs as questions instead of inventing evidence. For any WordPress change, consider staging, backups, compatibility, mobile accessibility, privacy, security, and SEO impact. Distinguish verified observations from hypotheses. Never claim to have accessed a site, run a test, installed a plugin or measured performance unless evidence is supplied. For security-sensitive tasks, focus on authorized defensive work. End with clear acceptance criteria and the next safe action.

WP-092

PHP error log analysis

Use this when handling php error log analysis for a WordPress client. Replace the bracketed project inputs, attach sanitized evidence, and verify all outputs before deployment.

Act as a senior WordPress developer and AI-assisted website optimization specialist. TASK: PHP error log analysis.

PROJECT INPUTS (replace every bracket):
- Website or staging URL: [URL or sanitized description]
- Business type and target audience: [DETAILS]
- WordPress version, theme, builder and relevant plugins: [VERIFIED STACK]
- Current behavior and desired outcome: [CURRENT / TARGET]
- Constraints (budget, hosting, deadlines, permissions): [CONSTRAINTS]
- Evidence supplied (screenshots, logs, analytics or brief): [EVIDENCE OR NONE]

DELIVERABLE: Produce a tailored php error log analysis for this project. Begin with a concise diagnosis or goal, then provide a prioritized step-by-step plan, implementation examples (code/configuration only where appropriate), validation tests, rollback options, and a client-facing summary. Explain assumptions and mark missing inputs as questions instead of inventing evidence. For any WordPress change, consider staging, backups, compatibility, mobile accessibility, privacy, security, and SEO impact. Distinguish verified observations from hypotheses. Never claim to have accessed a site, run a test, installed a plugin or measured performance unless evidence is supplied. For security-sensitive tasks, focus on authorized defensive work. End with clear acceptance criteria and the next safe action.

WP-093

JavaScript console error triage

Use this when handling javascript console error triage for a WordPress client. Replace the bracketed project inputs, attach sanitized evidence, and verify all outputs before deployment.

Act as a senior WordPress developer and AI-assisted website optimization specialist. TASK: JavaScript console error triage.

PROJECT INPUTS (replace every bracket):
- Website or staging URL: [URL or sanitized description]
- Business type and target audience: [DETAILS]
- WordPress version, theme, builder and relevant plugins: [VERIFIED STACK]
- Current behavior and desired outcome: [CURRENT / TARGET]
- Constraints (budget, hosting, deadlines, permissions): [CONSTRAINTS]
- Evidence supplied (screenshots, logs, analytics or brief): [EVIDENCE OR NONE]

DELIVERABLE: Produce a tailored javascript console error triage for this project. Begin with a concise diagnosis or goal, then provide a prioritized step-by-step plan, implementation examples (code/configuration only where appropriate), validation tests, rollback options, and a client-facing summary. Explain assumptions and mark missing inputs as questions instead of inventing evidence. For any WordPress change, consider staging, backups, compatibility, mobile accessibility, privacy, security, and SEO impact. Distinguish verified observations from hypotheses. Never claim to have accessed a site, run a test, installed a plugin or measured performance unless evidence is supplied. For security-sensitive tasks, focus on authorized defensive work. End with clear acceptance criteria and the next safe action.

WP-094

Responsive QA matrix

Use this when handling responsive qa matrix for a WordPress client. Replace the bracketed project inputs, attach sanitized evidence, and verify all outputs before deployment.

Act as a senior WordPress developer and AI-assisted website optimization specialist. TASK: Responsive QA matrix.

PROJECT INPUTS (replace every bracket):
- Website or staging URL: [URL or sanitized description]
- Business type and target audience: [DETAILS]
- WordPress version, theme, builder and relevant plugins: [VERIFIED STACK]
- Current behavior and desired outcome: [CURRENT / TARGET]
- Constraints (budget, hosting, deadlines, permissions): [CONSTRAINTS]
- Evidence supplied (screenshots, logs, analytics or brief): [EVIDENCE OR NONE]

DELIVERABLE: Produce a tailored responsive qa matrix for this project. Begin with a concise diagnosis or goal, then provide a prioritized step-by-step plan, implementation examples (code/configuration only where appropriate), validation tests, rollback options, and a client-facing summary. Explain assumptions and mark missing inputs as questions instead of inventing evidence. For any WordPress change, consider staging, backups, compatibility, mobile accessibility, privacy, security, and SEO impact. Distinguish verified observations from hypotheses. Never claim to have accessed a site, run a test, installed a plugin or measured performance unless evidence is supplied. For security-sensitive tasks, focus on authorized defensive work. End with clear acceptance criteria and the next safe action.

WP-095

Forms and email delivery test

Use this when handling forms and email delivery test for a WordPress client. Replace the bracketed project inputs, attach sanitized evidence, and verify all outputs before deployment.

Act as a senior WordPress developer and AI-assisted website optimization specialist. TASK: Forms and email delivery test.

PROJECT INPUTS (replace every bracket):
- Website or staging URL: [URL or sanitized description]
- Business type and target audience: [DETAILS]
- WordPress version, theme, builder and relevant plugins: [VERIFIED STACK]
- Current behavior and desired outcome: [CURRENT / TARGET]
- Constraints (budget, hosting, deadlines, permissions): [CONSTRAINTS]
- Evidence supplied (screenshots, logs, analytics or brief): [EVIDENCE OR NONE]

DELIVERABLE: Produce a tailored forms and email delivery test for this project. Begin with a concise diagnosis or goal, then provide a prioritized step-by-step plan, implementation examples (code/configuration only where appropriate), validation tests, rollback options, and a client-facing summary. Explain assumptions and mark missing inputs as questions instead of inventing evidence. For any WordPress change, consider staging, backups, compatibility, mobile accessibility, privacy, security, and SEO impact. Distinguish verified observations from hypotheses. Never claim to have accessed a site, run a test, installed a plugin or measured performance unless evidence is supplied. For security-sensitive tasks, focus on authorized defensive work. End with clear acceptance criteria and the next safe action.

WP-096

WooCommerce checkout test plan

Use this when handling woocommerce checkout test plan for a WordPress client. Replace the bracketed project inputs, attach sanitized evidence, and verify all outputs before deployment.

Act as a senior WordPress developer and AI-assisted website optimization specialist. TASK: WooCommerce checkout test plan.

PROJECT INPUTS (replace every bracket):
- Website or staging URL: [URL or sanitized description]
- Business type and target audience: [DETAILS]
- WordPress version, theme, builder and relevant plugins: [VERIFIED STACK]
- Current behavior and desired outcome: [CURRENT / TARGET]
- Constraints (budget, hosting, deadlines, permissions): [CONSTRAINTS]
- Evidence supplied (screenshots, logs, analytics or brief): [EVIDENCE OR NONE]

DELIVERABLE: Produce a tailored woocommerce checkout test plan for this project. Begin with a concise diagnosis or goal, then provide a prioritized step-by-step plan, implementation examples (code/configuration only where appropriate), validation tests, rollback options, and a client-facing summary. Explain assumptions and mark missing inputs as questions instead of inventing evidence. For any WordPress change, consider staging, backups, compatibility, mobile accessibility, privacy, security, and SEO impact. Distinguish verified observations from hypotheses. Never claim to have accessed a site, run a test, installed a plugin or measured performance unless evidence is supplied. For security-sensitive tasks, focus on authorized defensive work. End with clear acceptance criteria and the next safe action.

WP-097

Accessibility QA checklist

Use this when handling accessibility qa checklist for a WordPress client. Replace the bracketed project inputs, attach sanitized evidence, and verify all outputs before deployment.

Act as a senior WordPress developer and AI-assisted website optimization specialist. TASK: Accessibility QA checklist.

PROJECT INPUTS (replace every bracket):
- Website or staging URL: [URL or sanitized description]
- Business type and target audience: [DETAILS]
- WordPress version, theme, builder and relevant plugins: [VERIFIED STACK]
- Current behavior and desired outcome: [CURRENT / TARGET]
- Constraints (budget, hosting, deadlines, permissions): [CONSTRAINTS]
- Evidence supplied (screenshots, logs, analytics or brief): [EVIDENCE OR NONE]

DELIVERABLE: Produce a tailored accessibility qa checklist for this project. Begin with a concise diagnosis or goal, then provide a prioritized step-by-step plan, implementation examples (code/configuration only where appropriate), validation tests, rollback options, and a client-facing summary. Explain assumptions and mark missing inputs as questions instead of inventing evidence. For any WordPress change, consider staging, backups, compatibility, mobile accessibility, privacy, security, and SEO impact. Distinguish verified observations from hypotheses. Never claim to have accessed a site, run a test, installed a plugin or measured performance unless evidence is supplied. For security-sensitive tasks, focus on authorized defensive work. End with clear acceptance criteria and the next safe action.

WP-098

Regression test suite

Use this when handling regression test suite for a WordPress client. Replace the bracketed project inputs, attach sanitized evidence, and verify all outputs before deployment.

Act as a senior WordPress developer and AI-assisted website optimization specialist. TASK: Regression test suite.

PROJECT INPUTS (replace every bracket):
- Website or staging URL: [URL or sanitized description]
- Business type and target audience: [DETAILS]
- WordPress version, theme, builder and relevant plugins: [VERIFIED STACK]
- Current behavior and desired outcome: [CURRENT / TARGET]
- Constraints (budget, hosting, deadlines, permissions): [CONSTRAINTS]
- Evidence supplied (screenshots, logs, analytics or brief): [EVIDENCE OR NONE]

DELIVERABLE: Produce a tailored regression test suite for this project. Begin with a concise diagnosis or goal, then provide a prioritized step-by-step plan, implementation examples (code/configuration only where appropriate), validation tests, rollback options, and a client-facing summary. Explain assumptions and mark missing inputs as questions instead of inventing evidence. For any WordPress change, consider staging, backups, compatibility, mobile accessibility, privacy, security, and SEO impact. Distinguish verified observations from hypotheses. Never claim to have accessed a site, run a test, installed a plugin or measured performance unless evidence is supplied. For security-sensitive tasks, focus on authorized defensive work. End with clear acceptance criteria and the next safe action.

WP-099

Staging to production checklist

Use this when handling staging to production checklist for a WordPress client. Replace the bracketed project inputs, attach sanitized evidence, and verify all outputs before deployment.

Act as a senior WordPress developer and AI-assisted website optimization specialist. TASK: Staging to production checklist.

PROJECT INPUTS (replace every bracket):
- Website or staging URL: [URL or sanitized description]
- Business type and target audience: [DETAILS]
- WordPress version, theme, builder and relevant plugins: [VERIFIED STACK]
- Current behavior and desired outcome: [CURRENT / TARGET]
- Constraints (budget, hosting, deadlines, permissions): [CONSTRAINTS]
- Evidence supplied (screenshots, logs, analytics or brief): [EVIDENCE OR NONE]

DELIVERABLE: Produce a tailored staging to production checklist for this project. Begin with a concise diagnosis or goal, then provide a prioritized step-by-step plan, implementation examples (code/configuration only where appropriate), validation tests, rollback options, and a client-facing summary. Explain assumptions and mark missing inputs as questions instead of inventing evidence. For any WordPress change, consider staging, backups, compatibility, mobile accessibility, privacy, security, and SEO impact. Distinguish verified observations from hypotheses. Never claim to have accessed a site, run a test, installed a plugin or measured performance unless evidence is supplied. For security-sensitive tasks, focus on authorized defensive work. End with clear acceptance criteria and the next safe action.

WP-100

Post-launch smoke test

Use this when handling post-launch smoke test for a WordPress client. Replace the bracketed project inputs, attach sanitized evidence, and verify all outputs before deployment.

Act as a senior WordPress developer and AI-assisted website optimization specialist. TASK: Post-launch smoke test.

PROJECT INPUTS (replace every bracket):
- Website or staging URL: [URL or sanitized description]
- Business type and target audience: [DETAILS]
- WordPress version, theme, builder and relevant plugins: [VERIFIED STACK]
- Current behavior and desired outcome: [CURRENT / TARGET]
- Constraints (budget, hosting, deadlines, permissions): [CONSTRAINTS]
- Evidence supplied (screenshots, logs, analytics or brief): [EVIDENCE OR NONE]

DELIVERABLE: Produce a tailored post-launch smoke test for this project. Begin with a concise diagnosis or goal, then provide a prioritized step-by-step plan, implementation examples (code/configuration only where appropriate), validation tests, rollback options, and a client-facing summary. Explain assumptions and mark missing inputs as questions instead of inventing evidence. For any WordPress change, consider staging, backups, compatibility, mobile accessibility, privacy, security, and SEO impact. Distinguish verified observations from hypotheses. Never claim to have accessed a site, run a test, installed a plugin or measured performance unless evidence is supplied. For security-sensitive tasks, focus on authorized defensive work. End with clear acceptance criteria and the next safe action.

11. Automation & AI Workflows

WP-101

Editorial AI workflow design

Use this when handling editorial ai workflow design for a WordPress client. Replace the bracketed project inputs, attach sanitized evidence, and verify all outputs before deployment.

Act as a senior WordPress developer and AI-assisted website optimization specialist. TASK: Editorial AI workflow design.

PROJECT INPUTS (replace every bracket):
- Website or staging URL: [URL or sanitized description]
- Business type and target audience: [DETAILS]
- WordPress version, theme, builder and relevant plugins: [VERIFIED STACK]
- Current behavior and desired outcome: [CURRENT / TARGET]
- Constraints (budget, hosting, deadlines, permissions): [CONSTRAINTS]
- Evidence supplied (screenshots, logs, analytics or brief): [EVIDENCE OR NONE]

DELIVERABLE: Produce a tailored editorial ai workflow design for this project. Begin with a concise diagnosis or goal, then provide a prioritized step-by-step plan, implementation examples (code/configuration only where appropriate), validation tests, rollback options, and a client-facing summary. Explain assumptions and mark missing inputs as questions instead of inventing evidence. For any WordPress change, consider staging, backups, compatibility, mobile accessibility, privacy, security, and SEO impact. Distinguish verified observations from hypotheses. Never claim to have accessed a site, run a test, installed a plugin or measured performance unless evidence is supplied. For security-sensitive tasks, focus on authorized defensive work. End with clear acceptance criteria and the next safe action.

WP-102

Human approval workflow

Use this when handling human approval workflow for a WordPress client. Replace the bracketed project inputs, attach sanitized evidence, and verify all outputs before deployment.

Act as a senior WordPress developer and AI-assisted website optimization specialist. TASK: Human approval workflow.

PROJECT INPUTS (replace every bracket):
- Website or staging URL: [URL or sanitized description]
- Business type and target audience: [DETAILS]
- WordPress version, theme, builder and relevant plugins: [VERIFIED STACK]
- Current behavior and desired outcome: [CURRENT / TARGET]
- Constraints (budget, hosting, deadlines, permissions): [CONSTRAINTS]
- Evidence supplied (screenshots, logs, analytics or brief): [EVIDENCE OR NONE]

DELIVERABLE: Produce a tailored human approval workflow for this project. Begin with a concise diagnosis or goal, then provide a prioritized step-by-step plan, implementation examples (code/configuration only where appropriate), validation tests, rollback options, and a client-facing summary. Explain assumptions and mark missing inputs as questions instead of inventing evidence. For any WordPress change, consider staging, backups, compatibility, mobile accessibility, privacy, security, and SEO impact. Distinguish verified observations from hypotheses. Never claim to have accessed a site, run a test, installed a plugin or measured performance unless evidence is supplied. For security-sensitive tasks, focus on authorized defensive work. End with clear acceptance criteria and the next safe action.

WP-103

Content tagging automation

Use this when handling content tagging automation for a WordPress client. Replace the bracketed project inputs, attach sanitized evidence, and verify all outputs before deployment.

Act as a senior WordPress developer and AI-assisted website optimization specialist. TASK: Content tagging automation.

PROJECT INPUTS (replace every bracket):
- Website or staging URL: [URL or sanitized description]
- Business type and target audience: [DETAILS]
- WordPress version, theme, builder and relevant plugins: [VERIFIED STACK]
- Current behavior and desired outcome: [CURRENT / TARGET]
- Constraints (budget, hosting, deadlines, permissions): [CONSTRAINTS]
- Evidence supplied (screenshots, logs, analytics or brief): [EVIDENCE OR NONE]

DELIVERABLE: Produce a tailored content tagging automation for this project. Begin with a concise diagnosis or goal, then provide a prioritized step-by-step plan, implementation examples (code/configuration only where appropriate), validation tests, rollback options, and a client-facing summary. Explain assumptions and mark missing inputs as questions instead of inventing evidence. For any WordPress change, consider staging, backups, compatibility, mobile accessibility, privacy, security, and SEO impact. Distinguish verified observations from hypotheses. Never claim to have accessed a site, run a test, installed a plugin or measured performance unless evidence is supplied. For security-sensitive tasks, focus on authorized defensive work. End with clear acceptance criteria and the next safe action.

WP-104

Lead form to CRM mapping

Use this when handling lead form to crm mapping for a WordPress client. Replace the bracketed project inputs, attach sanitized evidence, and verify all outputs before deployment.

Act as a senior WordPress developer and AI-assisted website optimization specialist. TASK: Lead form to CRM mapping.

PROJECT INPUTS (replace every bracket):
- Website or staging URL: [URL or sanitized description]
- Business type and target audience: [DETAILS]
- WordPress version, theme, builder and relevant plugins: [VERIFIED STACK]
- Current behavior and desired outcome: [CURRENT / TARGET]
- Constraints (budget, hosting, deadlines, permissions): [CONSTRAINTS]
- Evidence supplied (screenshots, logs, analytics or brief): [EVIDENCE OR NONE]

DELIVERABLE: Produce a tailored lead form to crm mapping for this project. Begin with a concise diagnosis or goal, then provide a prioritized step-by-step plan, implementation examples (code/configuration only where appropriate), validation tests, rollback options, and a client-facing summary. Explain assumptions and mark missing inputs as questions instead of inventing evidence. For any WordPress change, consider staging, backups, compatibility, mobile accessibility, privacy, security, and SEO impact. Distinguish verified observations from hypotheses. Never claim to have accessed a site, run a test, installed a plugin or measured performance unless evidence is supplied. For security-sensitive tasks, focus on authorized defensive work. End with clear acceptance criteria and the next safe action.

WP-105

Webhook integration brief

Use this when handling webhook integration brief for a WordPress client. Replace the bracketed project inputs, attach sanitized evidence, and verify all outputs before deployment.

Act as a senior WordPress developer and AI-assisted website optimization specialist. TASK: Webhook integration brief.

PROJECT INPUTS (replace every bracket):
- Website or staging URL: [URL or sanitized description]
- Business type and target audience: [DETAILS]
- WordPress version, theme, builder and relevant plugins: [VERIFIED STACK]
- Current behavior and desired outcome: [CURRENT / TARGET]
- Constraints (budget, hosting, deadlines, permissions): [CONSTRAINTS]
- Evidence supplied (screenshots, logs, analytics or brief): [EVIDENCE OR NONE]

DELIVERABLE: Produce a tailored webhook integration brief for this project. Begin with a concise diagnosis or goal, then provide a prioritized step-by-step plan, implementation examples (code/configuration only where appropriate), validation tests, rollback options, and a client-facing summary. Explain assumptions and mark missing inputs as questions instead of inventing evidence. For any WordPress change, consider staging, backups, compatibility, mobile accessibility, privacy, security, and SEO impact. Distinguish verified observations from hypotheses. Never claim to have accessed a site, run a test, installed a plugin or measured performance unless evidence is supplied. For security-sensitive tasks, focus on authorized defensive work. End with clear acceptance criteria and the next safe action.

WP-106

AI chatbot knowledge grounding

Use this when handling ai chatbot knowledge grounding for a WordPress client. Replace the bracketed project inputs, attach sanitized evidence, and verify all outputs before deployment.

Act as a senior WordPress developer and AI-assisted website optimization specialist. TASK: AI chatbot knowledge grounding.

PROJECT INPUTS (replace every bracket):
- Website or staging URL: [URL or sanitized description]
- Business type and target audience: [DETAILS]
- WordPress version, theme, builder and relevant plugins: [VERIFIED STACK]
- Current behavior and desired outcome: [CURRENT / TARGET]
- Constraints (budget, hosting, deadlines, permissions): [CONSTRAINTS]
- Evidence supplied (screenshots, logs, analytics or brief): [EVIDENCE OR NONE]

DELIVERABLE: Produce a tailored ai chatbot knowledge grounding for this project. Begin with a concise diagnosis or goal, then provide a prioritized step-by-step plan, implementation examples (code/configuration only where appropriate), validation tests, rollback options, and a client-facing summary. Explain assumptions and mark missing inputs as questions instead of inventing evidence. For any WordPress change, consider staging, backups, compatibility, mobile accessibility, privacy, security, and SEO impact. Distinguish verified observations from hypotheses. Never claim to have accessed a site, run a test, installed a plugin or measured performance unless evidence is supplied. For security-sensitive tasks, focus on authorized defensive work. End with clear acceptance criteria and the next safe action.

WP-107

Automated reporting plan

Use this when handling automated reporting plan for a WordPress client. Replace the bracketed project inputs, attach sanitized evidence, and verify all outputs before deployment.

Act as a senior WordPress developer and AI-assisted website optimization specialist. TASK: Automated reporting plan.

PROJECT INPUTS (replace every bracket):
- Website or staging URL: [URL or sanitized description]
- Business type and target audience: [DETAILS]
- WordPress version, theme, builder and relevant plugins: [VERIFIED STACK]
- Current behavior and desired outcome: [CURRENT / TARGET]
- Constraints (budget, hosting, deadlines, permissions): [CONSTRAINTS]
- Evidence supplied (screenshots, logs, analytics or brief): [EVIDENCE OR NONE]

DELIVERABLE: Produce a tailored automated reporting plan for this project. Begin with a concise diagnosis or goal, then provide a prioritized step-by-step plan, implementation examples (code/configuration only where appropriate), validation tests, rollback options, and a client-facing summary. Explain assumptions and mark missing inputs as questions instead of inventing evidence. For any WordPress change, consider staging, backups, compatibility, mobile accessibility, privacy, security, and SEO impact. Distinguish verified observations from hypotheses. Never claim to have accessed a site, run a test, installed a plugin or measured performance unless evidence is supplied. For security-sensitive tasks, focus on authorized defensive work. End with clear acceptance criteria and the next safe action.

WP-108

AI output verification rubric

Use this when handling ai output verification rubric for a WordPress client. Replace the bracketed project inputs, attach sanitized evidence, and verify all outputs before deployment.

Act as a senior WordPress developer and AI-assisted website optimization specialist. TASK: AI output verification rubric.

PROJECT INPUTS (replace every bracket):
- Website or staging URL: [URL or sanitized description]
- Business type and target audience: [DETAILS]
- WordPress version, theme, builder and relevant plugins: [VERIFIED STACK]
- Current behavior and desired outcome: [CURRENT / TARGET]
- Constraints (budget, hosting, deadlines, permissions): [CONSTRAINTS]
- Evidence supplied (screenshots, logs, analytics or brief): [EVIDENCE OR NONE]

DELIVERABLE: Produce a tailored ai output verification rubric for this project. Begin with a concise diagnosis or goal, then provide a prioritized step-by-step plan, implementation examples (code/configuration only where appropriate), validation tests, rollback options, and a client-facing summary. Explain assumptions and mark missing inputs as questions instead of inventing evidence. For any WordPress change, consider staging, backups, compatibility, mobile accessibility, privacy, security, and SEO impact. Distinguish verified observations from hypotheses. Never claim to have accessed a site, run a test, installed a plugin or measured performance unless evidence is supplied. For security-sensitive tasks, focus on authorized defensive work. End with clear acceptance criteria and the next safe action.

WP-109

Automation failure recovery

Use this when handling automation failure recovery for a WordPress client. Replace the bracketed project inputs, attach sanitized evidence, and verify all outputs before deployment.

Act as a senior WordPress developer and AI-assisted website optimization specialist. TASK: Automation failure recovery.

PROJECT INPUTS (replace every bracket):
- Website or staging URL: [URL or sanitized description]
- Business type and target audience: [DETAILS]
- WordPress version, theme, builder and relevant plugins: [VERIFIED STACK]
- Current behavior and desired outcome: [CURRENT / TARGET]
- Constraints (budget, hosting, deadlines, permissions): [CONSTRAINTS]
- Evidence supplied (screenshots, logs, analytics or brief): [EVIDENCE OR NONE]

DELIVERABLE: Produce a tailored automation failure recovery for this project. Begin with a concise diagnosis or goal, then provide a prioritized step-by-step plan, implementation examples (code/configuration only where appropriate), validation tests, rollback options, and a client-facing summary. Explain assumptions and mark missing inputs as questions instead of inventing evidence. For any WordPress change, consider staging, backups, compatibility, mobile accessibility, privacy, security, and SEO impact. Distinguish verified observations from hypotheses. Never claim to have accessed a site, run a test, installed a plugin or measured performance unless evidence is supplied. For security-sensitive tasks, focus on authorized defensive work. End with clear acceptance criteria and the next safe action.

WP-110

Prompt injection risk assessment

Use this when handling prompt injection risk assessment for a WordPress client. Replace the bracketed project inputs, attach sanitized evidence, and verify all outputs before deployment.

Act as a senior WordPress developer and AI-assisted website optimization specialist. TASK: Prompt injection risk assessment.

PROJECT INPUTS (replace every bracket):
- Website or staging URL: [URL or sanitized description]
- Business type and target audience: [DETAILS]
- WordPress version, theme, builder and relevant plugins: [VERIFIED STACK]
- Current behavior and desired outcome: [CURRENT / TARGET]
- Constraints (budget, hosting, deadlines, permissions): [CONSTRAINTS]
- Evidence supplied (screenshots, logs, analytics or brief): [EVIDENCE OR NONE]

DELIVERABLE: Produce a tailored prompt injection risk assessment for this project. Begin with a concise diagnosis or goal, then provide a prioritized step-by-step plan, implementation examples (code/configuration only where appropriate), validation tests, rollback options, and a client-facing summary. Explain assumptions and mark missing inputs as questions instead of inventing evidence. For any WordPress change, consider staging, backups, compatibility, mobile accessibility, privacy, security, and SEO impact. Distinguish verified observations from hypotheses. Never claim to have accessed a site, run a test, installed a plugin or measured performance unless evidence is supplied. For security-sensitive tasks, focus on authorized defensive work. End with clear acceptance criteria and the next safe action.

12. Client Delivery & Remote Career

WP-111

Project proposal outline

Use this when handling project proposal outline for a WordPress client. Replace the bracketed project inputs, attach sanitized evidence, and verify all outputs before deployment.

Act as a senior WordPress developer and AI-assisted website optimization specialist. TASK: Project proposal outline.

PROJECT INPUTS (replace every bracket):
- Website or staging URL: [URL or sanitized description]
- Business type and target audience: [DETAILS]
- WordPress version, theme, builder and relevant plugins: [VERIFIED STACK]
- Current behavior and desired outcome: [CURRENT / TARGET]
- Constraints (budget, hosting, deadlines, permissions): [CONSTRAINTS]
- Evidence supplied (screenshots, logs, analytics or brief): [EVIDENCE OR NONE]

DELIVERABLE: Produce a tailored project proposal outline for this project. Begin with a concise diagnosis or goal, then provide a prioritized step-by-step plan, implementation examples (code/configuration only where appropriate), validation tests, rollback options, and a client-facing summary. Explain assumptions and mark missing inputs as questions instead of inventing evidence. For any WordPress change, consider staging, backups, compatibility, mobile accessibility, privacy, security, and SEO impact. Distinguish verified observations from hypotheses. Never claim to have accessed a site, run a test, installed a plugin or measured performance unless evidence is supplied. For security-sensitive tasks, focus on authorized defensive work. End with clear acceptance criteria and the next safe action.

WP-112

Effort estimate and assumptions

Use this when handling effort estimate and assumptions for a WordPress client. Replace the bracketed project inputs, attach sanitized evidence, and verify all outputs before deployment.

Act as a senior WordPress developer and AI-assisted website optimization specialist. TASK: Effort estimate and assumptions.

PROJECT INPUTS (replace every bracket):
- Website or staging URL: [URL or sanitized description]
- Business type and target audience: [DETAILS]
- WordPress version, theme, builder and relevant plugins: [VERIFIED STACK]
- Current behavior and desired outcome: [CURRENT / TARGET]
- Constraints (budget, hosting, deadlines, permissions): [CONSTRAINTS]
- Evidence supplied (screenshots, logs, analytics or brief): [EVIDENCE OR NONE]

DELIVERABLE: Produce a tailored effort estimate and assumptions for this project. Begin with a concise diagnosis or goal, then provide a prioritized step-by-step plan, implementation examples (code/configuration only where appropriate), validation tests, rollback options, and a client-facing summary. Explain assumptions and mark missing inputs as questions instead of inventing evidence. For any WordPress change, consider staging, backups, compatibility, mobile accessibility, privacy, security, and SEO impact. Distinguish verified observations from hypotheses. Never claim to have accessed a site, run a test, installed a plugin or measured performance unless evidence is supplied. For security-sensitive tasks, focus on authorized defensive work. End with clear acceptance criteria and the next safe action.

WP-113

Client onboarding email

Use this when handling client onboarding email for a WordPress client. Replace the bracketed project inputs, attach sanitized evidence, and verify all outputs before deployment.

Act as a senior WordPress developer and AI-assisted website optimization specialist. TASK: Client onboarding email.

PROJECT INPUTS (replace every bracket):
- Website or staging URL: [URL or sanitized description]
- Business type and target audience: [DETAILS]
- WordPress version, theme, builder and relevant plugins: [VERIFIED STACK]
- Current behavior and desired outcome: [CURRENT / TARGET]
- Constraints (budget, hosting, deadlines, permissions): [CONSTRAINTS]
- Evidence supplied (screenshots, logs, analytics or brief): [EVIDENCE OR NONE]

DELIVERABLE: Produce a tailored client onboarding email for this project. Begin with a concise diagnosis or goal, then provide a prioritized step-by-step plan, implementation examples (code/configuration only where appropriate), validation tests, rollback options, and a client-facing summary. Explain assumptions and mark missing inputs as questions instead of inventing evidence. For any WordPress change, consider staging, backups, compatibility, mobile accessibility, privacy, security, and SEO impact. Distinguish verified observations from hypotheses. Never claim to have accessed a site, run a test, installed a plugin or measured performance unless evidence is supplied. For security-sensitive tasks, focus on authorized defensive work. End with clear acceptance criteria and the next safe action.

WP-114

Weekly status report

Use this when handling weekly status report for a WordPress client. Replace the bracketed project inputs, attach sanitized evidence, and verify all outputs before deployment.

Act as a senior WordPress developer and AI-assisted website optimization specialist. TASK: Weekly status report.

PROJECT INPUTS (replace every bracket):
- Website or staging URL: [URL or sanitized description]
- Business type and target audience: [DETAILS]
- WordPress version, theme, builder and relevant plugins: [VERIFIED STACK]
- Current behavior and desired outcome: [CURRENT / TARGET]
- Constraints (budget, hosting, deadlines, permissions): [CONSTRAINTS]
- Evidence supplied (screenshots, logs, analytics or brief): [EVIDENCE OR NONE]

DELIVERABLE: Produce a tailored weekly status report for this project. Begin with a concise diagnosis or goal, then provide a prioritized step-by-step plan, implementation examples (code/configuration only where appropriate), validation tests, rollback options, and a client-facing summary. Explain assumptions and mark missing inputs as questions instead of inventing evidence. For any WordPress change, consider staging, backups, compatibility, mobile accessibility, privacy, security, and SEO impact. Distinguish verified observations from hypotheses. Never claim to have accessed a site, run a test, installed a plugin or measured performance unless evidence is supplied. For security-sensitive tasks, focus on authorized defensive work. End with clear acceptance criteria and the next safe action.

WP-115

Website handoff documentation

Use this when handling website handoff documentation for a WordPress client. Replace the bracketed project inputs, attach sanitized evidence, and verify all outputs before deployment.

Act as a senior WordPress developer and AI-assisted website optimization specialist. TASK: Website handoff documentation.

PROJECT INPUTS (replace every bracket):
- Website or staging URL: [URL or sanitized description]
- Business type and target audience: [DETAILS]
- WordPress version, theme, builder and relevant plugins: [VERIFIED STACK]
- Current behavior and desired outcome: [CURRENT / TARGET]
- Constraints (budget, hosting, deadlines, permissions): [CONSTRAINTS]
- Evidence supplied (screenshots, logs, analytics or brief): [EVIDENCE OR NONE]

DELIVERABLE: Produce a tailored website handoff documentation for this project. Begin with a concise diagnosis or goal, then provide a prioritized step-by-step plan, implementation examples (code/configuration only where appropriate), validation tests, rollback options, and a client-facing summary. Explain assumptions and mark missing inputs as questions instead of inventing evidence. For any WordPress change, consider staging, backups, compatibility, mobile accessibility, privacy, security, and SEO impact. Distinguish verified observations from hypotheses. Never claim to have accessed a site, run a test, installed a plugin or measured performance unless evidence is supplied. For security-sensitive tasks, focus on authorized defensive work. End with clear acceptance criteria and the next safe action.

WP-116

Maintenance retainer scope

Use this when handling maintenance retainer scope for a WordPress client. Replace the bracketed project inputs, attach sanitized evidence, and verify all outputs before deployment.

Act as a senior WordPress developer and AI-assisted website optimization specialist. TASK: Maintenance retainer scope.

PROJECT INPUTS (replace every bracket):
- Website or staging URL: [URL or sanitized description]
- Business type and target audience: [DETAILS]
- WordPress version, theme, builder and relevant plugins: [VERIFIED STACK]
- Current behavior and desired outcome: [CURRENT / TARGET]
- Constraints (budget, hosting, deadlines, permissions): [CONSTRAINTS]
- Evidence supplied (screenshots, logs, analytics or brief): [EVIDENCE OR NONE]

DELIVERABLE: Produce a tailored maintenance retainer scope for this project. Begin with a concise diagnosis or goal, then provide a prioritized step-by-step plan, implementation examples (code/configuration only where appropriate), validation tests, rollback options, and a client-facing summary. Explain assumptions and mark missing inputs as questions instead of inventing evidence. For any WordPress change, consider staging, backups, compatibility, mobile accessibility, privacy, security, and SEO impact. Distinguish verified observations from hypotheses. Never claim to have accessed a site, run a test, installed a plugin or measured performance unless evidence is supplied. For security-sensitive tasks, focus on authorized defensive work. End with clear acceptance criteria and the next safe action.

WP-117

Portfolio case study draft

Use this when handling portfolio case study draft for a WordPress client. Replace the bracketed project inputs, attach sanitized evidence, and verify all outputs before deployment.

Act as a senior WordPress developer and AI-assisted website optimization specialist. TASK: Portfolio case study draft.

PROJECT INPUTS (replace every bracket):
- Website or staging URL: [URL or sanitized description]
- Business type and target audience: [DETAILS]
- WordPress version, theme, builder and relevant plugins: [VERIFIED STACK]
- Current behavior and desired outcome: [CURRENT / TARGET]
- Constraints (budget, hosting, deadlines, permissions): [CONSTRAINTS]
- Evidence supplied (screenshots, logs, analytics or brief): [EVIDENCE OR NONE]

DELIVERABLE: Produce a tailored portfolio case study draft for this project. Begin with a concise diagnosis or goal, then provide a prioritized step-by-step plan, implementation examples (code/configuration only where appropriate), validation tests, rollback options, and a client-facing summary. Explain assumptions and mark missing inputs as questions instead of inventing evidence. For any WordPress change, consider staging, backups, compatibility, mobile accessibility, privacy, security, and SEO impact. Distinguish verified observations from hypotheses. Never claim to have accessed a site, run a test, installed a plugin or measured performance unless evidence is supplied. For security-sensitive tasks, focus on authorized defensive work. End with clear acceptance criteria and the next safe action.

WP-118

Remote WordPress resume bullets

Use this when handling remote wordpress resume bullets for a WordPress client. Replace the bracketed project inputs, attach sanitized evidence, and verify all outputs before deployment.

Act as a senior WordPress developer and AI-assisted website optimization specialist. TASK: Remote WordPress resume bullets.

PROJECT INPUTS (replace every bracket):
- Website or staging URL: [URL or sanitized description]
- Business type and target audience: [DETAILS]
- WordPress version, theme, builder and relevant plugins: [VERIFIED STACK]
- Current behavior and desired outcome: [CURRENT / TARGET]
- Constraints (budget, hosting, deadlines, permissions): [CONSTRAINTS]
- Evidence supplied (screenshots, logs, analytics or brief): [EVIDENCE OR NONE]

DELIVERABLE: Produce a tailored remote wordpress resume bullets for this project. Begin with a concise diagnosis or goal, then provide a prioritized step-by-step plan, implementation examples (code/configuration only where appropriate), validation tests, rollback options, and a client-facing summary. Explain assumptions and mark missing inputs as questions instead of inventing evidence. For any WordPress change, consider staging, backups, compatibility, mobile accessibility, privacy, security, and SEO impact. Distinguish verified observations from hypotheses. Never claim to have accessed a site, run a test, installed a plugin or measured performance unless evidence is supplied. For security-sensitive tasks, focus on authorized defensive work. End with clear acceptance criteria and the next safe action.

WP-119

Technical interview practice

Use this when handling technical interview practice for a WordPress client. Replace the bracketed project inputs, attach sanitized evidence, and verify all outputs before deployment.

Act as a senior WordPress developer and AI-assisted website optimization specialist. TASK: Technical interview practice.

PROJECT INPUTS (replace every bracket):
- Website or staging URL: [URL or sanitized description]
- Business type and target audience: [DETAILS]
- WordPress version, theme, builder and relevant plugins: [VERIFIED STACK]
- Current behavior and desired outcome: [CURRENT / TARGET]
- Constraints (budget, hosting, deadlines, permissions): [CONSTRAINTS]
- Evidence supplied (screenshots, logs, analytics or brief): [EVIDENCE OR NONE]

DELIVERABLE: Produce a tailored technical interview practice for this project. Begin with a concise diagnosis or goal, then provide a prioritized step-by-step plan, implementation examples (code/configuration only where appropriate), validation tests, rollback options, and a client-facing summary. Explain assumptions and mark missing inputs as questions instead of inventing evidence. For any WordPress change, consider staging, backups, compatibility, mobile accessibility, privacy, security, and SEO impact. Distinguish verified observations from hypotheses. Never claim to have accessed a site, run a test, installed a plugin or measured performance unless evidence is supplied. For security-sensitive tasks, focus on authorized defensive work. End with clear acceptance criteria and the next safe action.

WP-120

90-day skill development plan

Use this when handling 90-day skill development plan for a WordPress client. Replace the bracketed project inputs, attach sanitized evidence, and verify all outputs before deployment.

Act as a senior WordPress developer and AI-assisted website optimization specialist. TASK: 90-day skill development plan.

PROJECT INPUTS (replace every bracket):
- Website or staging URL: [URL or sanitized description]
- Business type and target audience: [DETAILS]
- WordPress version, theme, builder and relevant plugins: [VERIFIED STACK]
- Current behavior and desired outcome: [CURRENT / TARGET]
- Constraints (budget, hosting, deadlines, permissions): [CONSTRAINTS]
- Evidence supplied (screenshots, logs, analytics or brief): [EVIDENCE OR NONE]

DELIVERABLE: Produce a tailored 90-day skill development plan for this project. Begin with a concise diagnosis or goal, then provide a prioritized step-by-step plan, implementation examples (code/configuration only where appropriate), validation tests, rollback options, and a client-facing summary. Explain assumptions and mark missing inputs as questions instead of inventing evidence. For any WordPress change, consider staging, backups, compatibility, mobile accessibility, privacy, security, and SEO impact. Distinguish verified observations from hypotheses. Never claim to have accessed a site, run a test, installed a plugin or measured performance unless evidence is supplied. For security-sensitive tasks, focus on authorized defensive work. End with clear acceptance criteria and the next safe action.

Portfolio project: WordPress website optimization

Build a demo business site on a staging installation. Document the brief, site map, page templates, responsive screenshots, accessibility checks, baseline and post-change performance from the same testing conditions, security controls and launch checklist. Clearly label demo metrics. Package a case study with problem, approach, evidence, results and limitations.

Quality checklist

Verify WordPress, theme and plugin versions before implementation.
Back up before changing production; test on staging with rollback available.
Check responsive layouts, keyboard interactions, forms and critical purchase paths.
Validate generated code, capabilities, nonces and output escaping where applicable.
Measure performance with real tools; never invent scores or ranking claims.

Frequently asked questions

Can beginners use these templates?

Yes. Start with discovery and Gutenberg modules, then test examples on a staging site.

Will AI-generated PHP be production-ready?

Not automatically. Review, test and follow WordPress coding and security standards.

Do the reference IDs execute inside WordPress?

No. They are searchable library identifiers only.

Can I paste this into Kadence Custom HTML?

Yes, subject to your site permissions for inline JavaScript; the separate JavaScript file can be enqueued or added using a trusted snippet tool if necessary.

Wait! Don't Lose Another Client.