Profession 36 · Advanced WordPress implementation library
260 Kadence Theme, Kadence Blocks & WPCode Prompts for WordPress Developers
Build straightforward landing pages and challenging production websites with a searchable, copy-ready implementation handbook. Each KWP-### reference is a custom library ID, not a registered/executable WordPress shortcode.
260 prompts26 modulesNative-first buildsResponsive and accessible
How to use this library
- Pick a module or search by feature, task, tool or KWP reference ID.
- Copy the prompt, replace all [BRACKETED INPUTS], and provide actual version numbers and sanitized context.
- Ask your AI assistant for its blueprint, exact Kadence settings, complete WPCode snippet where relevant, and rollback process.
- Use a staging clone and a verified backup before deploying PHP, JavaScript, integrations, dynamic queries or store changes.
- Run desktop, tablet, mobile, keyboard and functional checks; request a corrected prompt or fix with evidence.
Native-first rule: Use Kadence Theme and Kadence Blocks settings when they solve the task. Introduce WPCode only when necessary and test snippets individually. PHP, CSS and JS generated from prompts are not automatically safe or production-ready.
01. Discovery & Project Strategy
Business goals audit
Create a tested, client-ready outcome for business goals audit.
Act as a senior WordPress solution architect and Kadence Theme/Kadence Blocks/WPCode specialist. TASK: Business goals audit. PROJECT INPUTS - Website type and business goal: [SITE TYPE + GOAL] - Audience, locale and key conversion: [AUDIENCE + LOCALE + CTA] - Current stack (WordPress/PHP, Kadence Theme, Kadence Blocks, WPCode, plugins): [VERIFIED VERSIONS] - Current page, screenshot, issue or reference: [URL OR SANITIZED DETAILS] - Constraints (budget, editor skill, hosting, launch date): [CONSTRAINTS] - Existing content, brand styles and approved data: [SOURCE MATERIAL] SPECIFIC OBJECTIVE Develop a practical, results-oriented solution for business goals audit in the context of this website. State business assumptions separately from facts and ask up to five decision-critical questions. Explain what should be done with Kadence Theme settings, what should be built with Kadence Blocks, and when WPCode is warranted. Do not invent installed plugin capabilities or pretend you accessed the live site. DELIVER EXACTLY 1. A task-specific implementation blueprint for “Business goals audit” with exact WordPress/Kadence navigation or WPCode placement when relevant. 2. An ordered action checklist with dependencies and who owns each action. 3. Copy-ready artifacts where relevant (block hierarchy, settings matrix, sample copy, scoped CSS, PHP or vanilla JavaScript), with code fences and placement instructions. 4. Desktop/tablet/mobile acceptance tests, accessibility and security checks relevant to the task. 5. Failure cases, troubleshooting clues, rollback steps and final client-facing completion criteria. IMPLEMENTATION SAFETY Flag assumptions; favor native block controls over custom code; do not hardcode credentials or private data. For PHP/JS/CSS, provide exact location, activation scope, prerequisite checks, staging test, and undo method. If a plugin or version-specific behavior is uncertain, say what to verify first. Finish with a concise Definition of Done and a measurable business or UX outcome, without promising a result unsupported by data.
Client intake questionnaire
Create a tested, client-ready outcome for client intake questionnaire.
Act as a senior WordPress solution architect and Kadence Theme/Kadence Blocks/WPCode specialist. TASK: Client intake questionnaire. PROJECT INPUTS - Website type and business goal: [SITE TYPE + GOAL] - Audience, locale and key conversion: [AUDIENCE + LOCALE + CTA] - Current stack (WordPress/PHP, Kadence Theme, Kadence Blocks, WPCode, plugins): [VERIFIED VERSIONS] - Current page, screenshot, issue or reference: [URL OR SANITIZED DETAILS] - Constraints (budget, editor skill, hosting, launch date): [CONSTRAINTS] - Existing content, brand styles and approved data: [SOURCE MATERIAL] SPECIFIC OBJECTIVE Develop a practical, results-oriented solution for client intake questionnaire in the context of this website. State business assumptions separately from facts and ask up to five decision-critical questions. Explain what should be done with Kadence Theme settings, what should be built with Kadence Blocks, and when WPCode is warranted. Do not invent installed plugin capabilities or pretend you accessed the live site. DELIVER EXACTLY 1. A task-specific implementation blueprint for “Client intake questionnaire” with exact WordPress/Kadence navigation or WPCode placement when relevant. 2. An ordered action checklist with dependencies and who owns each action. 3. Copy-ready artifacts where relevant (block hierarchy, settings matrix, sample copy, scoped CSS, PHP or vanilla JavaScript), with code fences and placement instructions. 4. Desktop/tablet/mobile acceptance tests, accessibility and security checks relevant to the task. 5. Failure cases, troubleshooting clues, rollback steps and final client-facing completion criteria. IMPLEMENTATION SAFETY Flag assumptions; favor native block controls over custom code; do not hardcode credentials or private data. For PHP/JS/CSS, provide exact location, activation scope, prerequisite checks, staging test, and undo method. If a plugin or version-specific behavior is uncertain, say what to verify first. Finish with a concise Definition of Done and a measurable business or UX outcome, without promising a result unsupported by data.
Audience and intent mapping
Create a tested, client-ready outcome for audience and intent mapping.
Act as a senior WordPress solution architect and Kadence Theme/Kadence Blocks/WPCode specialist. TASK: Audience and intent mapping. PROJECT INPUTS - Website type and business goal: [SITE TYPE + GOAL] - Audience, locale and key conversion: [AUDIENCE + LOCALE + CTA] - Current stack (WordPress/PHP, Kadence Theme, Kadence Blocks, WPCode, plugins): [VERIFIED VERSIONS] - Current page, screenshot, issue or reference: [URL OR SANITIZED DETAILS] - Constraints (budget, editor skill, hosting, launch date): [CONSTRAINTS] - Existing content, brand styles and approved data: [SOURCE MATERIAL] SPECIFIC OBJECTIVE Develop a practical, results-oriented solution for audience and intent mapping in the context of this website. State business assumptions separately from facts and ask up to five decision-critical questions. Explain what should be done with Kadence Theme settings, what should be built with Kadence Blocks, and when WPCode is warranted. Do not invent installed plugin capabilities or pretend you accessed the live site. DELIVER EXACTLY 1. A task-specific implementation blueprint for “Audience and intent mapping” with exact WordPress/Kadence navigation or WPCode placement when relevant. 2. An ordered action checklist with dependencies and who owns each action. 3. Copy-ready artifacts where relevant (block hierarchy, settings matrix, sample copy, scoped CSS, PHP or vanilla JavaScript), with code fences and placement instructions. 4. Desktop/tablet/mobile acceptance tests, accessibility and security checks relevant to the task. 5. Failure cases, troubleshooting clues, rollback steps and final client-facing completion criteria. IMPLEMENTATION SAFETY Flag assumptions; favor native block controls over custom code; do not hardcode credentials or private data. For PHP/JS/CSS, provide exact location, activation scope, prerequisite checks, staging test, and undo method. If a plugin or version-specific behavior is uncertain, say what to verify first. Finish with a concise Definition of Done and a measurable business or UX outcome, without promising a result unsupported by data.
Competitor site teardown
Create a tested, client-ready outcome for competitor site teardown.
Act as a senior WordPress solution architect and Kadence Theme/Kadence Blocks/WPCode specialist. TASK: Competitor site teardown. PROJECT INPUTS - Website type and business goal: [SITE TYPE + GOAL] - Audience, locale and key conversion: [AUDIENCE + LOCALE + CTA] - Current stack (WordPress/PHP, Kadence Theme, Kadence Blocks, WPCode, plugins): [VERIFIED VERSIONS] - Current page, screenshot, issue or reference: [URL OR SANITIZED DETAILS] - Constraints (budget, editor skill, hosting, launch date): [CONSTRAINTS] - Existing content, brand styles and approved data: [SOURCE MATERIAL] SPECIFIC OBJECTIVE Develop a practical, results-oriented solution for competitor site teardown in the context of this website. State business assumptions separately from facts and ask up to five decision-critical questions. Explain what should be done with Kadence Theme settings, what should be built with Kadence Blocks, and when WPCode is warranted. Do not invent installed plugin capabilities or pretend you accessed the live site. DELIVER EXACTLY 1. A task-specific implementation blueprint for “Competitor site teardown” with exact WordPress/Kadence navigation or WPCode placement when relevant. 2. An ordered action checklist with dependencies and who owns each action. 3. Copy-ready artifacts where relevant (block hierarchy, settings matrix, sample copy, scoped CSS, PHP or vanilla JavaScript), with code fences and placement instructions. 4. Desktop/tablet/mobile acceptance tests, accessibility and security checks relevant to the task. 5. Failure cases, troubleshooting clues, rollback steps and final client-facing completion criteria. IMPLEMENTATION SAFETY Flag assumptions; favor native block controls over custom code; do not hardcode credentials or private data. For PHP/JS/CSS, provide exact location, activation scope, prerequisite checks, staging test, and undo method. If a plugin or version-specific behavior is uncertain, say what to verify first. Finish with a concise Definition of Done and a measurable business or UX outcome, without promising a result unsupported by data.
Project scope and exclusions
Create a tested, client-ready outcome for project scope and exclusions.
Act as a senior WordPress solution architect and Kadence Theme/Kadence Blocks/WPCode specialist. TASK: Project scope and exclusions. PROJECT INPUTS - Website type and business goal: [SITE TYPE + GOAL] - Audience, locale and key conversion: [AUDIENCE + LOCALE + CTA] - Current stack (WordPress/PHP, Kadence Theme, Kadence Blocks, WPCode, plugins): [VERIFIED VERSIONS] - Current page, screenshot, issue or reference: [URL OR SANITIZED DETAILS] - Constraints (budget, editor skill, hosting, launch date): [CONSTRAINTS] - Existing content, brand styles and approved data: [SOURCE MATERIAL] SPECIFIC OBJECTIVE Develop a practical, results-oriented solution for project scope and exclusions in the context of this website. State business assumptions separately from facts and ask up to five decision-critical questions. Explain what should be done with Kadence Theme settings, what should be built with Kadence Blocks, and when WPCode is warranted. Do not invent installed plugin capabilities or pretend you accessed the live site. DELIVER EXACTLY 1. A task-specific implementation blueprint for “Project scope and exclusions” with exact WordPress/Kadence navigation or WPCode placement when relevant. 2. An ordered action checklist with dependencies and who owns each action. 3. Copy-ready artifacts where relevant (block hierarchy, settings matrix, sample copy, scoped CSS, PHP or vanilla JavaScript), with code fences and placement instructions. 4. Desktop/tablet/mobile acceptance tests, accessibility and security checks relevant to the task. 5. Failure cases, troubleshooting clues, rollback steps and final client-facing completion criteria. IMPLEMENTATION SAFETY Flag assumptions; favor native block controls over custom code; do not hardcode credentials or private data. For PHP/JS/CSS, provide exact location, activation scope, prerequisite checks, staging test, and undo method. If a plugin or version-specific behavior is uncertain, say what to verify first. Finish with a concise Definition of Done and a measurable business or UX outcome, without promising a result unsupported by data.
Feature prioritization matrix
Create a tested, client-ready outcome for feature prioritization matrix.
Act as a senior WordPress solution architect and Kadence Theme/Kadence Blocks/WPCode specialist. TASK: Feature prioritization matrix. PROJECT INPUTS - Website type and business goal: [SITE TYPE + GOAL] - Audience, locale and key conversion: [AUDIENCE + LOCALE + CTA] - Current stack (WordPress/PHP, Kadence Theme, Kadence Blocks, WPCode, plugins): [VERIFIED VERSIONS] - Current page, screenshot, issue or reference: [URL OR SANITIZED DETAILS] - Constraints (budget, editor skill, hosting, launch date): [CONSTRAINTS] - Existing content, brand styles and approved data: [SOURCE MATERIAL] SPECIFIC OBJECTIVE Develop a practical, results-oriented solution for feature prioritization matrix in the context of this website. State business assumptions separately from facts and ask up to five decision-critical questions. Explain what should be done with Kadence Theme settings, what should be built with Kadence Blocks, and when WPCode is warranted. Do not invent installed plugin capabilities or pretend you accessed the live site. DELIVER EXACTLY 1. A task-specific implementation blueprint for “Feature prioritization matrix” with exact WordPress/Kadence navigation or WPCode placement when relevant. 2. An ordered action checklist with dependencies and who owns each action. 3. Copy-ready artifacts where relevant (block hierarchy, settings matrix, sample copy, scoped CSS, PHP or vanilla JavaScript), with code fences and placement instructions. 4. Desktop/tablet/mobile acceptance tests, accessibility and security checks relevant to the task. 5. Failure cases, troubleshooting clues, rollback steps and final client-facing completion criteria. IMPLEMENTATION SAFETY Flag assumptions; favor native block controls over custom code; do not hardcode credentials or private data. For PHP/JS/CSS, provide exact location, activation scope, prerequisite checks, staging test, and undo method. If a plugin or version-specific behavior is uncertain, say what to verify first. Finish with a concise Definition of Done and a measurable business or UX outcome, without promising a result unsupported by data.
Content inventory audit
Create a tested, client-ready outcome for content inventory audit.
Act as a senior WordPress solution architect and Kadence Theme/Kadence Blocks/WPCode specialist. TASK: Content inventory audit. PROJECT INPUTS - Website type and business goal: [SITE TYPE + GOAL] - Audience, locale and key conversion: [AUDIENCE + LOCALE + CTA] - Current stack (WordPress/PHP, Kadence Theme, Kadence Blocks, WPCode, plugins): [VERIFIED VERSIONS] - Current page, screenshot, issue or reference: [URL OR SANITIZED DETAILS] - Constraints (budget, editor skill, hosting, launch date): [CONSTRAINTS] - Existing content, brand styles and approved data: [SOURCE MATERIAL] SPECIFIC OBJECTIVE Develop a practical, results-oriented solution for content inventory audit in the context of this website. State business assumptions separately from facts and ask up to five decision-critical questions. Explain what should be done with Kadence Theme settings, what should be built with Kadence Blocks, and when WPCode is warranted. Do not invent installed plugin capabilities or pretend you accessed the live site. DELIVER EXACTLY 1. A task-specific implementation blueprint for “Content inventory audit” with exact WordPress/Kadence navigation or WPCode placement when relevant. 2. An ordered action checklist with dependencies and who owns each action. 3. Copy-ready artifacts where relevant (block hierarchy, settings matrix, sample copy, scoped CSS, PHP or vanilla JavaScript), with code fences and placement instructions. 4. Desktop/tablet/mobile acceptance tests, accessibility and security checks relevant to the task. 5. Failure cases, troubleshooting clues, rollback steps and final client-facing completion criteria. IMPLEMENTATION SAFETY Flag assumptions; favor native block controls over custom code; do not hardcode credentials or private data. For PHP/JS/CSS, provide exact location, activation scope, prerequisite checks, staging test, and undo method. If a plugin or version-specific behavior is uncertain, say what to verify first. Finish with a concise Definition of Done and a measurable business or UX outcome, without promising a result unsupported by data.
Conversion journey map
Create a tested, client-ready outcome for conversion journey map.
Act as a senior WordPress solution architect and Kadence Theme/Kadence Blocks/WPCode specialist. TASK: Conversion journey map. PROJECT INPUTS - Website type and business goal: [SITE TYPE + GOAL] - Audience, locale and key conversion: [AUDIENCE + LOCALE + CTA] - Current stack (WordPress/PHP, Kadence Theme, Kadence Blocks, WPCode, plugins): [VERIFIED VERSIONS] - Current page, screenshot, issue or reference: [URL OR SANITIZED DETAILS] - Constraints (budget, editor skill, hosting, launch date): [CONSTRAINTS] - Existing content, brand styles and approved data: [SOURCE MATERIAL] SPECIFIC OBJECTIVE Develop a practical, results-oriented solution for conversion journey map in the context of this website. State business assumptions separately from facts and ask up to five decision-critical questions. Explain what should be done with Kadence Theme settings, what should be built with Kadence Blocks, and when WPCode is warranted. Do not invent installed plugin capabilities or pretend you accessed the live site. DELIVER EXACTLY 1. A task-specific implementation blueprint for “Conversion journey map” with exact WordPress/Kadence navigation or WPCode placement when relevant. 2. An ordered action checklist with dependencies and who owns each action. 3. Copy-ready artifacts where relevant (block hierarchy, settings matrix, sample copy, scoped CSS, PHP or vanilla JavaScript), with code fences and placement instructions. 4. Desktop/tablet/mobile acceptance tests, accessibility and security checks relevant to the task. 5. Failure cases, troubleshooting clues, rollback steps and final client-facing completion criteria. IMPLEMENTATION SAFETY Flag assumptions; favor native block controls over custom code; do not hardcode credentials or private data. For PHP/JS/CSS, provide exact location, activation scope, prerequisite checks, staging test, and undo method. If a plugin or version-specific behavior is uncertain, say what to verify first. Finish with a concise Definition of Done and a measurable business or UX outcome, without promising a result unsupported by data.
Acceptance criteria matrix
Create a tested, client-ready outcome for acceptance criteria matrix.
Act as a senior WordPress solution architect and Kadence Theme/Kadence Blocks/WPCode specialist. TASK: Acceptance criteria matrix. PROJECT INPUTS - Website type and business goal: [SITE TYPE + GOAL] - Audience, locale and key conversion: [AUDIENCE + LOCALE + CTA] - Current stack (WordPress/PHP, Kadence Theme, Kadence Blocks, WPCode, plugins): [VERIFIED VERSIONS] - Current page, screenshot, issue or reference: [URL OR SANITIZED DETAILS] - Constraints (budget, editor skill, hosting, launch date): [CONSTRAINTS] - Existing content, brand styles and approved data: [SOURCE MATERIAL] SPECIFIC OBJECTIVE Develop a practical, results-oriented solution for acceptance criteria matrix in the context of this website. State business assumptions separately from facts and ask up to five decision-critical questions. Explain what should be done with Kadence Theme settings, what should be built with Kadence Blocks, and when WPCode is warranted. Do not invent installed plugin capabilities or pretend you accessed the live site. DELIVER EXACTLY 1. A task-specific implementation blueprint for “Acceptance criteria matrix” with exact WordPress/Kadence navigation or WPCode placement when relevant. 2. An ordered action checklist with dependencies and who owns each action. 3. Copy-ready artifacts where relevant (block hierarchy, settings matrix, sample copy, scoped CSS, PHP or vanilla JavaScript), with code fences and placement instructions. 4. Desktop/tablet/mobile acceptance tests, accessibility and security checks relevant to the task. 5. Failure cases, troubleshooting clues, rollback steps and final client-facing completion criteria. IMPLEMENTATION SAFETY Flag assumptions; favor native block controls over custom code; do not hardcode credentials or private data. For PHP/JS/CSS, provide exact location, activation scope, prerequisite checks, staging test, and undo method. If a plugin or version-specific behavior is uncertain, say what to verify first. Finish with a concise Definition of Done and a measurable business or UX outcome, without promising a result unsupported by data.
Risk and dependency register
Create a tested, client-ready outcome for risk and dependency register.
Act as a senior WordPress solution architect and Kadence Theme/Kadence Blocks/WPCode specialist. TASK: Risk and dependency register. PROJECT INPUTS - Website type and business goal: [SITE TYPE + GOAL] - Audience, locale and key conversion: [AUDIENCE + LOCALE + CTA] - Current stack (WordPress/PHP, Kadence Theme, Kadence Blocks, WPCode, plugins): [VERIFIED VERSIONS] - Current page, screenshot, issue or reference: [URL OR SANITIZED DETAILS] - Constraints (budget, editor skill, hosting, launch date): [CONSTRAINTS] - Existing content, brand styles and approved data: [SOURCE MATERIAL] SPECIFIC OBJECTIVE Develop a practical, results-oriented solution for risk and dependency register in the context of this website. State business assumptions separately from facts and ask up to five decision-critical questions. Explain what should be done with Kadence Theme settings, what should be built with Kadence Blocks, and when WPCode is warranted. Do not invent installed plugin capabilities or pretend you accessed the live site. DELIVER EXACTLY 1. A task-specific implementation blueprint for “Risk and dependency register” with exact WordPress/Kadence navigation or WPCode placement when relevant. 2. An ordered action checklist with dependencies and who owns each action. 3. Copy-ready artifacts where relevant (block hierarchy, settings matrix, sample copy, scoped CSS, PHP or vanilla JavaScript), with code fences and placement instructions. 4. Desktop/tablet/mobile acceptance tests, accessibility and security checks relevant to the task. 5. Failure cases, troubleshooting clues, rollback steps and final client-facing completion criteria. IMPLEMENTATION SAFETY Flag assumptions; favor native block controls over custom code; do not hardcode credentials or private data. For PHP/JS/CSS, provide exact location, activation scope, prerequisite checks, staging test, and undo method. If a plugin or version-specific behavior is uncertain, say what to verify first. Finish with a concise Definition of Done and a measurable business or UX outcome, without promising a result unsupported by data.
02. Hosting, Staging & WordPress Setup
Hosting compatibility checklist
Create a tested, client-ready outcome for hosting compatibility checklist.
Act as a senior WordPress solution architect and Kadence Theme/Kadence Blocks/WPCode specialist. TASK: Hosting compatibility checklist. PROJECT INPUTS - Website type and business goal: [SITE TYPE + GOAL] - Audience, locale and key conversion: [AUDIENCE + LOCALE + CTA] - Current stack (WordPress/PHP, Kadence Theme, Kadence Blocks, WPCode, plugins): [VERIFIED VERSIONS] - Current page, screenshot, issue or reference: [URL OR SANITIZED DETAILS] - Constraints (budget, editor skill, hosting, launch date): [CONSTRAINTS] - Existing content, brand styles and approved data: [SOURCE MATERIAL] SPECIFIC OBJECTIVE Develop a practical, results-oriented solution for hosting compatibility checklist in the context of this website. Specify environment prerequisites and do not change production before backup and staging approval. Explain what should be done with Kadence Theme settings, what should be built with Kadence Blocks, and when WPCode is warranted. Do not invent installed plugin capabilities or pretend you accessed the live site. DELIVER EXACTLY 1. A task-specific implementation blueprint for “Hosting compatibility checklist” with exact WordPress/Kadence navigation or WPCode placement when relevant. 2. An ordered action checklist with dependencies and who owns each action. 3. Copy-ready artifacts where relevant (block hierarchy, settings matrix, sample copy, scoped CSS, PHP or vanilla JavaScript), with code fences and placement instructions. 4. Desktop/tablet/mobile acceptance tests, accessibility and security checks relevant to the task. 5. Failure cases, troubleshooting clues, rollback steps and final client-facing completion criteria. IMPLEMENTATION SAFETY Flag assumptions; favor native block controls over custom code; do not hardcode credentials or private data. For PHP/JS/CSS, provide exact location, activation scope, prerequisite checks, staging test, and undo method. If a plugin or version-specific behavior is uncertain, say what to verify first. Finish with a concise Definition of Done and a measurable business or UX outcome, without promising a result unsupported by data.
DNS and SSL launch plan
Create a tested, client-ready outcome for dns and ssl launch plan.
Act as a senior WordPress solution architect and Kadence Theme/Kadence Blocks/WPCode specialist. TASK: DNS and SSL launch plan. PROJECT INPUTS - Website type and business goal: [SITE TYPE + GOAL] - Audience, locale and key conversion: [AUDIENCE + LOCALE + CTA] - Current stack (WordPress/PHP, Kadence Theme, Kadence Blocks, WPCode, plugins): [VERIFIED VERSIONS] - Current page, screenshot, issue or reference: [URL OR SANITIZED DETAILS] - Constraints (budget, editor skill, hosting, launch date): [CONSTRAINTS] - Existing content, brand styles and approved data: [SOURCE MATERIAL] SPECIFIC OBJECTIVE Develop a practical, results-oriented solution for dns and ssl launch plan in the context of this website. Specify environment prerequisites and do not change production before backup and staging approval. Explain what should be done with Kadence Theme settings, what should be built with Kadence Blocks, and when WPCode is warranted. Do not invent installed plugin capabilities or pretend you accessed the live site. DELIVER EXACTLY 1. A task-specific implementation blueprint for “DNS and SSL launch plan” with exact WordPress/Kadence navigation or WPCode placement when relevant. 2. An ordered action checklist with dependencies and who owns each action. 3. Copy-ready artifacts where relevant (block hierarchy, settings matrix, sample copy, scoped CSS, PHP or vanilla JavaScript), with code fences and placement instructions. 4. Desktop/tablet/mobile acceptance tests, accessibility and security checks relevant to the task. 5. Failure cases, troubleshooting clues, rollback steps and final client-facing completion criteria. IMPLEMENTATION SAFETY Flag assumptions; favor native block controls over custom code; do not hardcode credentials or private data. For PHP/JS/CSS, provide exact location, activation scope, prerequisite checks, staging test, and undo method. If a plugin or version-specific behavior is uncertain, say what to verify first. Finish with a concise Definition of Done and a measurable business or UX outcome, without promising a result unsupported by data.
Staging site setup
Create a tested, client-ready outcome for staging site setup.
Act as a senior WordPress solution architect and Kadence Theme/Kadence Blocks/WPCode specialist. TASK: Staging site setup. PROJECT INPUTS - Website type and business goal: [SITE TYPE + GOAL] - Audience, locale and key conversion: [AUDIENCE + LOCALE + CTA] - Current stack (WordPress/PHP, Kadence Theme, Kadence Blocks, WPCode, plugins): [VERIFIED VERSIONS] - Current page, screenshot, issue or reference: [URL OR SANITIZED DETAILS] - Constraints (budget, editor skill, hosting, launch date): [CONSTRAINTS] - Existing content, brand styles and approved data: [SOURCE MATERIAL] SPECIFIC OBJECTIVE Develop a practical, results-oriented solution for staging site setup in the context of this website. Specify environment prerequisites and do not change production before backup and staging approval. Explain what should be done with Kadence Theme settings, what should be built with Kadence Blocks, and when WPCode is warranted. Do not invent installed plugin capabilities or pretend you accessed the live site. DELIVER EXACTLY 1. A task-specific implementation blueprint for “Staging site setup” with exact WordPress/Kadence navigation or WPCode placement when relevant. 2. An ordered action checklist with dependencies and who owns each action. 3. Copy-ready artifacts where relevant (block hierarchy, settings matrix, sample copy, scoped CSS, PHP or vanilla JavaScript), with code fences and placement instructions. 4. Desktop/tablet/mobile acceptance tests, accessibility and security checks relevant to the task. 5. Failure cases, troubleshooting clues, rollback steps and final client-facing completion criteria. IMPLEMENTATION SAFETY Flag assumptions; favor native block controls over custom code; do not hardcode credentials or private data. For PHP/JS/CSS, provide exact location, activation scope, prerequisite checks, staging test, and undo method. If a plugin or version-specific behavior is uncertain, say what to verify first. Finish with a concise Definition of Done and a measurable business or UX outcome, without promising a result unsupported by data.
Clean WordPress installation
Create a tested, client-ready outcome for clean wordpress installation.
Act as a senior WordPress solution architect and Kadence Theme/Kadence Blocks/WPCode specialist. TASK: Clean WordPress installation. PROJECT INPUTS - Website type and business goal: [SITE TYPE + GOAL] - Audience, locale and key conversion: [AUDIENCE + LOCALE + CTA] - Current stack (WordPress/PHP, Kadence Theme, Kadence Blocks, WPCode, plugins): [VERIFIED VERSIONS] - Current page, screenshot, issue or reference: [URL OR SANITIZED DETAILS] - Constraints (budget, editor skill, hosting, launch date): [CONSTRAINTS] - Existing content, brand styles and approved data: [SOURCE MATERIAL] SPECIFIC OBJECTIVE Develop a practical, results-oriented solution for clean wordpress installation in the context of this website. Specify environment prerequisites and do not change production before backup and staging approval. Explain what should be done with Kadence Theme settings, what should be built with Kadence Blocks, and when WPCode is warranted. Do not invent installed plugin capabilities or pretend you accessed the live site. DELIVER EXACTLY 1. A task-specific implementation blueprint for “Clean WordPress installation” with exact WordPress/Kadence navigation or WPCode placement when relevant. 2. An ordered action checklist with dependencies and who owns each action. 3. Copy-ready artifacts where relevant (block hierarchy, settings matrix, sample copy, scoped CSS, PHP or vanilla JavaScript), with code fences and placement instructions. 4. Desktop/tablet/mobile acceptance tests, accessibility and security checks relevant to the task. 5. Failure cases, troubleshooting clues, rollback steps and final client-facing completion criteria. IMPLEMENTATION SAFETY Flag assumptions; favor native block controls over custom code; do not hardcode credentials or private data. For PHP/JS/CSS, provide exact location, activation scope, prerequisite checks, staging test, and undo method. If a plugin or version-specific behavior is uncertain, say what to verify first. Finish with a concise Definition of Done and a measurable business or UX outcome, without promising a result unsupported by data.
Environment configuration
Create a tested, client-ready outcome for environment configuration.
Act as a senior WordPress solution architect and Kadence Theme/Kadence Blocks/WPCode specialist. TASK: Environment configuration. PROJECT INPUTS - Website type and business goal: [SITE TYPE + GOAL] - Audience, locale and key conversion: [AUDIENCE + LOCALE + CTA] - Current stack (WordPress/PHP, Kadence Theme, Kadence Blocks, WPCode, plugins): [VERIFIED VERSIONS] - Current page, screenshot, issue or reference: [URL OR SANITIZED DETAILS] - Constraints (budget, editor skill, hosting, launch date): [CONSTRAINTS] - Existing content, brand styles and approved data: [SOURCE MATERIAL] SPECIFIC OBJECTIVE Develop a practical, results-oriented solution for environment configuration in the context of this website. Specify environment prerequisites and do not change production before backup and staging approval. Explain what should be done with Kadence Theme settings, what should be built with Kadence Blocks, and when WPCode is warranted. Do not invent installed plugin capabilities or pretend you accessed the live site. DELIVER EXACTLY 1. A task-specific implementation blueprint for “Environment configuration” with exact WordPress/Kadence navigation or WPCode placement when relevant. 2. An ordered action checklist with dependencies and who owns each action. 3. Copy-ready artifacts where relevant (block hierarchy, settings matrix, sample copy, scoped CSS, PHP or vanilla JavaScript), with code fences and placement instructions. 4. Desktop/tablet/mobile acceptance tests, accessibility and security checks relevant to the task. 5. Failure cases, troubleshooting clues, rollback steps and final client-facing completion criteria. IMPLEMENTATION SAFETY Flag assumptions; favor native block controls over custom code; do not hardcode credentials or private data. For PHP/JS/CSS, provide exact location, activation scope, prerequisite checks, staging test, and undo method. If a plugin or version-specific behavior is uncertain, say what to verify first. Finish with a concise Definition of Done and a measurable business or UX outcome, without promising a result unsupported by data.
Role and permissions matrix
Create a tested, client-ready outcome for role and permissions matrix.
Act as a senior WordPress solution architect and Kadence Theme/Kadence Blocks/WPCode specialist. TASK: Role and permissions matrix. PROJECT INPUTS - Website type and business goal: [SITE TYPE + GOAL] - Audience, locale and key conversion: [AUDIENCE + LOCALE + CTA] - Current stack (WordPress/PHP, Kadence Theme, Kadence Blocks, WPCode, plugins): [VERIFIED VERSIONS] - Current page, screenshot, issue or reference: [URL OR SANITIZED DETAILS] - Constraints (budget, editor skill, hosting, launch date): [CONSTRAINTS] - Existing content, brand styles and approved data: [SOURCE MATERIAL] SPECIFIC OBJECTIVE Develop a practical, results-oriented solution for role and permissions matrix in the context of this website. Specify environment prerequisites and do not change production before backup and staging approval. Explain what should be done with Kadence Theme settings, what should be built with Kadence Blocks, and when WPCode is warranted. Do not invent installed plugin capabilities or pretend you accessed the live site. DELIVER EXACTLY 1. A task-specific implementation blueprint for “Role and permissions matrix” with exact WordPress/Kadence navigation or WPCode placement when relevant. 2. An ordered action checklist with dependencies and who owns each action. 3. Copy-ready artifacts where relevant (block hierarchy, settings matrix, sample copy, scoped CSS, PHP or vanilla JavaScript), with code fences and placement instructions. 4. Desktop/tablet/mobile acceptance tests, accessibility and security checks relevant to the task. 5. Failure cases, troubleshooting clues, rollback steps and final client-facing completion criteria. IMPLEMENTATION SAFETY Flag assumptions; favor native block controls over custom code; do not hardcode credentials or private data. For PHP/JS/CSS, provide exact location, activation scope, prerequisite checks, staging test, and undo method. If a plugin or version-specific behavior is uncertain, say what to verify first. Finish with a concise Definition of Done and a measurable business or UX outcome, without promising a result unsupported by data.
Backup and restore rehearsal
Create a tested, client-ready outcome for backup and restore rehearsal.
Act as a senior WordPress solution architect and Kadence Theme/Kadence Blocks/WPCode specialist. TASK: Backup and restore rehearsal. PROJECT INPUTS - Website type and business goal: [SITE TYPE + GOAL] - Audience, locale and key conversion: [AUDIENCE + LOCALE + CTA] - Current stack (WordPress/PHP, Kadence Theme, Kadence Blocks, WPCode, plugins): [VERIFIED VERSIONS] - Current page, screenshot, issue or reference: [URL OR SANITIZED DETAILS] - Constraints (budget, editor skill, hosting, launch date): [CONSTRAINTS] - Existing content, brand styles and approved data: [SOURCE MATERIAL] SPECIFIC OBJECTIVE Develop a practical, results-oriented solution for backup and restore rehearsal in the context of this website. Specify environment prerequisites and do not change production before backup and staging approval. Explain what should be done with Kadence Theme settings, what should be built with Kadence Blocks, and when WPCode is warranted. Do not invent installed plugin capabilities or pretend you accessed the live site. DELIVER EXACTLY 1. A task-specific implementation blueprint for “Backup and restore rehearsal” with exact WordPress/Kadence navigation or WPCode placement when relevant. 2. An ordered action checklist with dependencies and who owns each action. 3. Copy-ready artifacts where relevant (block hierarchy, settings matrix, sample copy, scoped CSS, PHP or vanilla JavaScript), with code fences and placement instructions. 4. Desktop/tablet/mobile acceptance tests, accessibility and security checks relevant to the task. 5. Failure cases, troubleshooting clues, rollback steps and final client-facing completion criteria. IMPLEMENTATION SAFETY Flag assumptions; favor native block controls over custom code; do not hardcode credentials or private data. For PHP/JS/CSS, provide exact location, activation scope, prerequisite checks, staging test, and undo method. If a plugin or version-specific behavior is uncertain, say what to verify first. Finish with a concise Definition of Done and a measurable business or UX outcome, without promising a result unsupported by data.
Migration readiness audit
Create a tested, client-ready outcome for migration readiness audit.
Act as a senior WordPress solution architect and Kadence Theme/Kadence Blocks/WPCode specialist. TASK: Migration readiness audit. PROJECT INPUTS - Website type and business goal: [SITE TYPE + GOAL] - Audience, locale and key conversion: [AUDIENCE + LOCALE + CTA] - Current stack (WordPress/PHP, Kadence Theme, Kadence Blocks, WPCode, plugins): [VERIFIED VERSIONS] - Current page, screenshot, issue or reference: [URL OR SANITIZED DETAILS] - Constraints (budget, editor skill, hosting, launch date): [CONSTRAINTS] - Existing content, brand styles and approved data: [SOURCE MATERIAL] SPECIFIC OBJECTIVE Develop a practical, results-oriented solution for migration readiness audit in the context of this website. Specify environment prerequisites and do not change production before backup and staging approval. Explain what should be done with Kadence Theme settings, what should be built with Kadence Blocks, and when WPCode is warranted. Do not invent installed plugin capabilities or pretend you accessed the live site. DELIVER EXACTLY 1. A task-specific implementation blueprint for “Migration readiness audit” with exact WordPress/Kadence navigation or WPCode placement when relevant. 2. An ordered action checklist with dependencies and who owns each action. 3. Copy-ready artifacts where relevant (block hierarchy, settings matrix, sample copy, scoped CSS, PHP or vanilla JavaScript), with code fences and placement instructions. 4. Desktop/tablet/mobile acceptance tests, accessibility and security checks relevant to the task. 5. Failure cases, troubleshooting clues, rollback steps and final client-facing completion criteria. IMPLEMENTATION SAFETY Flag assumptions; favor native block controls over custom code; do not hardcode credentials or private data. For PHP/JS/CSS, provide exact location, activation scope, prerequisite checks, staging test, and undo method. If a plugin or version-specific behavior is uncertain, say what to verify first. Finish with a concise Definition of Done and a measurable business or UX outcome, without promising a result unsupported by data.
Multisite suitability assessment
Create a tested, client-ready outcome for multisite suitability assessment.
Act as a senior WordPress solution architect and Kadence Theme/Kadence Blocks/WPCode specialist. TASK: Multisite suitability assessment. PROJECT INPUTS - Website type and business goal: [SITE TYPE + GOAL] - Audience, locale and key conversion: [AUDIENCE + LOCALE + CTA] - Current stack (WordPress/PHP, Kadence Theme, Kadence Blocks, WPCode, plugins): [VERIFIED VERSIONS] - Current page, screenshot, issue or reference: [URL OR SANITIZED DETAILS] - Constraints (budget, editor skill, hosting, launch date): [CONSTRAINTS] - Existing content, brand styles and approved data: [SOURCE MATERIAL] SPECIFIC OBJECTIVE Develop a practical, results-oriented solution for multisite suitability assessment in the context of this website. Specify environment prerequisites and do not change production before backup and staging approval. Explain what should be done with Kadence Theme settings, what should be built with Kadence Blocks, and when WPCode is warranted. Do not invent installed plugin capabilities or pretend you accessed the live site. DELIVER EXACTLY 1. A task-specific implementation blueprint for “Multisite suitability assessment” with exact WordPress/Kadence navigation or WPCode placement when relevant. 2. An ordered action checklist with dependencies and who owns each action. 3. Copy-ready artifacts where relevant (block hierarchy, settings matrix, sample copy, scoped CSS, PHP or vanilla JavaScript), with code fences and placement instructions. 4. Desktop/tablet/mobile acceptance tests, accessibility and security checks relevant to the task. 5. Failure cases, troubleshooting clues, rollback steps and final client-facing completion criteria. IMPLEMENTATION SAFETY Flag assumptions; favor native block controls over custom code; do not hardcode credentials or private data. For PHP/JS/CSS, provide exact location, activation scope, prerequisite checks, staging test, and undo method. If a plugin or version-specific behavior is uncertain, say what to verify first. Finish with a concise Definition of Done and a measurable business or UX outcome, without promising a result unsupported by data.
Update and maintenance policy
Create a tested, client-ready outcome for update and maintenance policy.
Act as a senior WordPress solution architect and Kadence Theme/Kadence Blocks/WPCode specialist. TASK: Update and maintenance policy. PROJECT INPUTS - Website type and business goal: [SITE TYPE + GOAL] - Audience, locale and key conversion: [AUDIENCE + LOCALE + CTA] - Current stack (WordPress/PHP, Kadence Theme, Kadence Blocks, WPCode, plugins): [VERIFIED VERSIONS] - Current page, screenshot, issue or reference: [URL OR SANITIZED DETAILS] - Constraints (budget, editor skill, hosting, launch date): [CONSTRAINTS] - Existing content, brand styles and approved data: [SOURCE MATERIAL] SPECIFIC OBJECTIVE Develop a practical, results-oriented solution for update and maintenance policy in the context of this website. Specify environment prerequisites and do not change production before backup and staging approval. Explain what should be done with Kadence Theme settings, what should be built with Kadence Blocks, and when WPCode is warranted. Do not invent installed plugin capabilities or pretend you accessed the live site. DELIVER EXACTLY 1. A task-specific implementation blueprint for “Update and maintenance policy” with exact WordPress/Kadence navigation or WPCode placement when relevant. 2. An ordered action checklist with dependencies and who owns each action. 3. Copy-ready artifacts where relevant (block hierarchy, settings matrix, sample copy, scoped CSS, PHP or vanilla JavaScript), with code fences and placement instructions. 4. Desktop/tablet/mobile acceptance tests, accessibility and security checks relevant to the task. 5. Failure cases, troubleshooting clues, rollback steps and final client-facing completion criteria. IMPLEMENTATION SAFETY Flag assumptions; favor native block controls over custom code; do not hardcode credentials or private data. For PHP/JS/CSS, provide exact location, activation scope, prerequisite checks, staging test, and undo method. If a plugin or version-specific behavior is uncertain, say what to verify first. Finish with a concise Definition of Done and a measurable business or UX outcome, without promising a result unsupported by data.
03. Kadence Theme Foundations
Global palette configuration
Create a tested, client-ready outcome for global palette configuration.
Act as a senior WordPress solution architect and Kadence Theme/Kadence Blocks/WPCode specialist. TASK: Global palette configuration. PROJECT INPUTS - Website type and business goal: [SITE TYPE + GOAL] - Audience, locale and key conversion: [AUDIENCE + LOCALE + CTA] - Current stack (WordPress/PHP, Kadence Theme, Kadence Blocks, WPCode, plugins): [VERIFIED VERSIONS] - Current page, screenshot, issue or reference: [URL OR SANITIZED DETAILS] - Constraints (budget, editor skill, hosting, launch date): [CONSTRAINTS] - Existing content, brand styles and approved data: [SOURCE MATERIAL] SPECIFIC OBJECTIVE Develop a practical, results-oriented solution for global palette configuration in the context of this website. Prefer kadence theme native settings and document exact customizer or builder locations. Explain what should be done with Kadence Theme settings, what should be built with Kadence Blocks, and when WPCode is warranted. Do not invent installed plugin capabilities or pretend you accessed the live site. DELIVER EXACTLY 1. A task-specific implementation blueprint for “Global palette configuration” with exact WordPress/Kadence navigation or WPCode placement when relevant. 2. An ordered action checklist with dependencies and who owns each action. 3. Copy-ready artifacts where relevant (block hierarchy, settings matrix, sample copy, scoped CSS, PHP or vanilla JavaScript), with code fences and placement instructions. 4. Desktop/tablet/mobile acceptance tests, accessibility and security checks relevant to the task. 5. Failure cases, troubleshooting clues, rollback steps and final client-facing completion criteria. IMPLEMENTATION SAFETY Flag assumptions; favor native block controls over custom code; do not hardcode credentials or private data. For PHP/JS/CSS, provide exact location, activation scope, prerequisite checks, staging test, and undo method. If a plugin or version-specific behavior is uncertain, say what to verify first. Finish with a concise Definition of Done and a measurable business or UX outcome, without promising a result unsupported by data.
Typography scale system
Create a tested, client-ready outcome for typography scale system.
Act as a senior WordPress solution architect and Kadence Theme/Kadence Blocks/WPCode specialist. TASK: Typography scale system. PROJECT INPUTS - Website type and business goal: [SITE TYPE + GOAL] - Audience, locale and key conversion: [AUDIENCE + LOCALE + CTA] - Current stack (WordPress/PHP, Kadence Theme, Kadence Blocks, WPCode, plugins): [VERIFIED VERSIONS] - Current page, screenshot, issue or reference: [URL OR SANITIZED DETAILS] - Constraints (budget, editor skill, hosting, launch date): [CONSTRAINTS] - Existing content, brand styles and approved data: [SOURCE MATERIAL] SPECIFIC OBJECTIVE Develop a practical, results-oriented solution for typography scale system in the context of this website. Prefer kadence theme native settings and document exact customizer or builder locations. Explain what should be done with Kadence Theme settings, what should be built with Kadence Blocks, and when WPCode is warranted. Do not invent installed plugin capabilities or pretend you accessed the live site. DELIVER EXACTLY 1. A task-specific implementation blueprint for “Typography scale system” with exact WordPress/Kadence navigation or WPCode placement when relevant. 2. An ordered action checklist with dependencies and who owns each action. 3. Copy-ready artifacts where relevant (block hierarchy, settings matrix, sample copy, scoped CSS, PHP or vanilla JavaScript), with code fences and placement instructions. 4. Desktop/tablet/mobile acceptance tests, accessibility and security checks relevant to the task. 5. Failure cases, troubleshooting clues, rollback steps and final client-facing completion criteria. IMPLEMENTATION SAFETY Flag assumptions; favor native block controls over custom code; do not hardcode credentials or private data. For PHP/JS/CSS, provide exact location, activation scope, prerequisite checks, staging test, and undo method. If a plugin or version-specific behavior is uncertain, say what to verify first. Finish with a concise Definition of Done and a measurable business or UX outcome, without promising a result unsupported by data.
Content width and spacing
Create a tested, client-ready outcome for content width and spacing.
Act as a senior WordPress solution architect and Kadence Theme/Kadence Blocks/WPCode specialist. TASK: Content width and spacing. PROJECT INPUTS - Website type and business goal: [SITE TYPE + GOAL] - Audience, locale and key conversion: [AUDIENCE + LOCALE + CTA] - Current stack (WordPress/PHP, Kadence Theme, Kadence Blocks, WPCode, plugins): [VERIFIED VERSIONS] - Current page, screenshot, issue or reference: [URL OR SANITIZED DETAILS] - Constraints (budget, editor skill, hosting, launch date): [CONSTRAINTS] - Existing content, brand styles and approved data: [SOURCE MATERIAL] SPECIFIC OBJECTIVE Develop a practical, results-oriented solution for content width and spacing in the context of this website. Prefer kadence theme native settings and document exact customizer or builder locations. Explain what should be done with Kadence Theme settings, what should be built with Kadence Blocks, and when WPCode is warranted. Do not invent installed plugin capabilities or pretend you accessed the live site. DELIVER EXACTLY 1. A task-specific implementation blueprint for “Content width and spacing” with exact WordPress/Kadence navigation or WPCode placement when relevant. 2. An ordered action checklist with dependencies and who owns each action. 3. Copy-ready artifacts where relevant (block hierarchy, settings matrix, sample copy, scoped CSS, PHP or vanilla JavaScript), with code fences and placement instructions. 4. Desktop/tablet/mobile acceptance tests, accessibility and security checks relevant to the task. 5. Failure cases, troubleshooting clues, rollback steps and final client-facing completion criteria. IMPLEMENTATION SAFETY Flag assumptions; favor native block controls over custom code; do not hardcode credentials or private data. For PHP/JS/CSS, provide exact location, activation scope, prerequisite checks, staging test, and undo method. If a plugin or version-specific behavior is uncertain, say what to verify first. Finish with a concise Definition of Done and a measurable business or UX outcome, without promising a result unsupported by data.
Header builder blueprint
Create a tested, client-ready outcome for header builder blueprint.
Act as a senior WordPress solution architect and Kadence Theme/Kadence Blocks/WPCode specialist. TASK: Header builder blueprint. PROJECT INPUTS - Website type and business goal: [SITE TYPE + GOAL] - Audience, locale and key conversion: [AUDIENCE + LOCALE + CTA] - Current stack (WordPress/PHP, Kadence Theme, Kadence Blocks, WPCode, plugins): [VERIFIED VERSIONS] - Current page, screenshot, issue or reference: [URL OR SANITIZED DETAILS] - Constraints (budget, editor skill, hosting, launch date): [CONSTRAINTS] - Existing content, brand styles and approved data: [SOURCE MATERIAL] SPECIFIC OBJECTIVE Develop a practical, results-oriented solution for header builder blueprint in the context of this website. Prefer kadence theme native settings and document exact customizer or builder locations. Explain what should be done with Kadence Theme settings, what should be built with Kadence Blocks, and when WPCode is warranted. Do not invent installed plugin capabilities or pretend you accessed the live site. DELIVER EXACTLY 1. A task-specific implementation blueprint for “Header builder blueprint” with exact WordPress/Kadence navigation or WPCode placement when relevant. 2. An ordered action checklist with dependencies and who owns each action. 3. Copy-ready artifacts where relevant (block hierarchy, settings matrix, sample copy, scoped CSS, PHP or vanilla JavaScript), with code fences and placement instructions. 4. Desktop/tablet/mobile acceptance tests, accessibility and security checks relevant to the task. 5. Failure cases, troubleshooting clues, rollback steps and final client-facing completion criteria. IMPLEMENTATION SAFETY Flag assumptions; favor native block controls over custom code; do not hardcode credentials or private data. For PHP/JS/CSS, provide exact location, activation scope, prerequisite checks, staging test, and undo method. If a plugin or version-specific behavior is uncertain, say what to verify first. Finish with a concise Definition of Done and a measurable business or UX outcome, without promising a result unsupported by data.
Mobile header and drawer
Create a tested, client-ready outcome for mobile header and drawer.
Act as a senior WordPress solution architect and Kadence Theme/Kadence Blocks/WPCode specialist. TASK: Mobile header and drawer. PROJECT INPUTS - Website type and business goal: [SITE TYPE + GOAL] - Audience, locale and key conversion: [AUDIENCE + LOCALE + CTA] - Current stack (WordPress/PHP, Kadence Theme, Kadence Blocks, WPCode, plugins): [VERIFIED VERSIONS] - Current page, screenshot, issue or reference: [URL OR SANITIZED DETAILS] - Constraints (budget, editor skill, hosting, launch date): [CONSTRAINTS] - Existing content, brand styles and approved data: [SOURCE MATERIAL] SPECIFIC OBJECTIVE Develop a practical, results-oriented solution for mobile header and drawer in the context of this website. Prefer kadence theme native settings and document exact customizer or builder locations. Explain what should be done with Kadence Theme settings, what should be built with Kadence Blocks, and when WPCode is warranted. Do not invent installed plugin capabilities or pretend you accessed the live site. DELIVER EXACTLY 1. A task-specific implementation blueprint for “Mobile header and drawer” with exact WordPress/Kadence navigation or WPCode placement when relevant. 2. An ordered action checklist with dependencies and who owns each action. 3. Copy-ready artifacts where relevant (block hierarchy, settings matrix, sample copy, scoped CSS, PHP or vanilla JavaScript), with code fences and placement instructions. 4. Desktop/tablet/mobile acceptance tests, accessibility and security checks relevant to the task. 5. Failure cases, troubleshooting clues, rollback steps and final client-facing completion criteria. IMPLEMENTATION SAFETY Flag assumptions; favor native block controls over custom code; do not hardcode credentials or private data. For PHP/JS/CSS, provide exact location, activation scope, prerequisite checks, staging test, and undo method. If a plugin or version-specific behavior is uncertain, say what to verify first. Finish with a concise Definition of Done and a measurable business or UX outcome, without promising a result unsupported by data.
Footer builder architecture
Create a tested, client-ready outcome for footer builder architecture.
Act as a senior WordPress solution architect and Kadence Theme/Kadence Blocks/WPCode specialist. TASK: Footer builder architecture. PROJECT INPUTS - Website type and business goal: [SITE TYPE + GOAL] - Audience, locale and key conversion: [AUDIENCE + LOCALE + CTA] - Current stack (WordPress/PHP, Kadence Theme, Kadence Blocks, WPCode, plugins): [VERIFIED VERSIONS] - Current page, screenshot, issue or reference: [URL OR SANITIZED DETAILS] - Constraints (budget, editor skill, hosting, launch date): [CONSTRAINTS] - Existing content, brand styles and approved data: [SOURCE MATERIAL] SPECIFIC OBJECTIVE Develop a practical, results-oriented solution for footer builder architecture in the context of this website. Prefer kadence theme native settings and document exact customizer or builder locations. Explain what should be done with Kadence Theme settings, what should be built with Kadence Blocks, and when WPCode is warranted. Do not invent installed plugin capabilities or pretend you accessed the live site. DELIVER EXACTLY 1. A task-specific implementation blueprint for “Footer builder architecture” with exact WordPress/Kadence navigation or WPCode placement when relevant. 2. An ordered action checklist with dependencies and who owns each action. 3. Copy-ready artifacts where relevant (block hierarchy, settings matrix, sample copy, scoped CSS, PHP or vanilla JavaScript), with code fences and placement instructions. 4. Desktop/tablet/mobile acceptance tests, accessibility and security checks relevant to the task. 5. Failure cases, troubleshooting clues, rollback steps and final client-facing completion criteria. IMPLEMENTATION SAFETY Flag assumptions; favor native block controls over custom code; do not hardcode credentials or private data. For PHP/JS/CSS, provide exact location, activation scope, prerequisite checks, staging test, and undo method. If a plugin or version-specific behavior is uncertain, say what to verify first. Finish with a concise Definition of Done and a measurable business or UX outcome, without promising a result unsupported by data.
Transparent and sticky header
Create a tested, client-ready outcome for transparent and sticky header.
Act as a senior WordPress solution architect and Kadence Theme/Kadence Blocks/WPCode specialist. TASK: Transparent and sticky header. PROJECT INPUTS - Website type and business goal: [SITE TYPE + GOAL] - Audience, locale and key conversion: [AUDIENCE + LOCALE + CTA] - Current stack (WordPress/PHP, Kadence Theme, Kadence Blocks, WPCode, plugins): [VERIFIED VERSIONS] - Current page, screenshot, issue or reference: [URL OR SANITIZED DETAILS] - Constraints (budget, editor skill, hosting, launch date): [CONSTRAINTS] - Existing content, brand styles and approved data: [SOURCE MATERIAL] SPECIFIC OBJECTIVE Develop a practical, results-oriented solution for transparent and sticky header in the context of this website. Prefer kadence theme native settings and document exact customizer or builder locations. Explain what should be done with Kadence Theme settings, what should be built with Kadence Blocks, and when WPCode is warranted. Do not invent installed plugin capabilities or pretend you accessed the live site. DELIVER EXACTLY 1. A task-specific implementation blueprint for “Transparent and sticky header” with exact WordPress/Kadence navigation or WPCode placement when relevant. 2. An ordered action checklist with dependencies and who owns each action. 3. Copy-ready artifacts where relevant (block hierarchy, settings matrix, sample copy, scoped CSS, PHP or vanilla JavaScript), with code fences and placement instructions. 4. Desktop/tablet/mobile acceptance tests, accessibility and security checks relevant to the task. 5. Failure cases, troubleshooting clues, rollback steps and final client-facing completion criteria. IMPLEMENTATION SAFETY Flag assumptions; favor native block controls over custom code; do not hardcode credentials or private data. For PHP/JS/CSS, provide exact location, activation scope, prerequisite checks, staging test, and undo method. If a plugin or version-specific behavior is uncertain, say what to verify first. Finish with a concise Definition of Done and a measurable business or UX outcome, without promising a result unsupported by data.
Page template hierarchy
Create a tested, client-ready outcome for page template hierarchy.
Act as a senior WordPress solution architect and Kadence Theme/Kadence Blocks/WPCode specialist. TASK: Page template hierarchy. PROJECT INPUTS - Website type and business goal: [SITE TYPE + GOAL] - Audience, locale and key conversion: [AUDIENCE + LOCALE + CTA] - Current stack (WordPress/PHP, Kadence Theme, Kadence Blocks, WPCode, plugins): [VERIFIED VERSIONS] - Current page, screenshot, issue or reference: [URL OR SANITIZED DETAILS] - Constraints (budget, editor skill, hosting, launch date): [CONSTRAINTS] - Existing content, brand styles and approved data: [SOURCE MATERIAL] SPECIFIC OBJECTIVE Develop a practical, results-oriented solution for page template hierarchy in the context of this website. Prefer kadence theme native settings and document exact customizer or builder locations. Explain what should be done with Kadence Theme settings, what should be built with Kadence Blocks, and when WPCode is warranted. Do not invent installed plugin capabilities or pretend you accessed the live site. DELIVER EXACTLY 1. A task-specific implementation blueprint for “Page template hierarchy” with exact WordPress/Kadence navigation or WPCode placement when relevant. 2. An ordered action checklist with dependencies and who owns each action. 3. Copy-ready artifacts where relevant (block hierarchy, settings matrix, sample copy, scoped CSS, PHP or vanilla JavaScript), with code fences and placement instructions. 4. Desktop/tablet/mobile acceptance tests, accessibility and security checks relevant to the task. 5. Failure cases, troubleshooting clues, rollback steps and final client-facing completion criteria. IMPLEMENTATION SAFETY Flag assumptions; favor native block controls over custom code; do not hardcode credentials or private data. For PHP/JS/CSS, provide exact location, activation scope, prerequisite checks, staging test, and undo method. If a plugin or version-specific behavior is uncertain, say what to verify first. Finish with a concise Definition of Done and a measurable business or UX outcome, without promising a result unsupported by data.
Kadence hooks placement plan
Create a tested, client-ready outcome for kadence hooks placement plan.
Act as a senior WordPress solution architect and Kadence Theme/Kadence Blocks/WPCode specialist. TASK: Kadence hooks placement plan. PROJECT INPUTS - Website type and business goal: [SITE TYPE + GOAL] - Audience, locale and key conversion: [AUDIENCE + LOCALE + CTA] - Current stack (WordPress/PHP, Kadence Theme, Kadence Blocks, WPCode, plugins): [VERIFIED VERSIONS] - Current page, screenshot, issue or reference: [URL OR SANITIZED DETAILS] - Constraints (budget, editor skill, hosting, launch date): [CONSTRAINTS] - Existing content, brand styles and approved data: [SOURCE MATERIAL] SPECIFIC OBJECTIVE Develop a practical, results-oriented solution for kadence hooks placement plan in the context of this website. Prefer kadence theme native settings and document exact customizer or builder locations. Explain what should be done with Kadence Theme settings, what should be built with Kadence Blocks, and when WPCode is warranted. Do not invent installed plugin capabilities or pretend you accessed the live site. DELIVER EXACTLY 1. A task-specific implementation blueprint for “Kadence hooks placement plan” with exact WordPress/Kadence navigation or WPCode placement when relevant. 2. An ordered action checklist with dependencies and who owns each action. 3. Copy-ready artifacts where relevant (block hierarchy, settings matrix, sample copy, scoped CSS, PHP or vanilla JavaScript), with code fences and placement instructions. 4. Desktop/tablet/mobile acceptance tests, accessibility and security checks relevant to the task. 5. Failure cases, troubleshooting clues, rollback steps and final client-facing completion criteria. IMPLEMENTATION SAFETY Flag assumptions; favor native block controls over custom code; do not hardcode credentials or private data. For PHP/JS/CSS, provide exact location, activation scope, prerequisite checks, staging test, and undo method. If a plugin or version-specific behavior is uncertain, say what to verify first. Finish with a concise Definition of Done and a measurable business or UX outcome, without promising a result unsupported by data.
Child-theme versus WPCode decision
Create a tested, client-ready outcome for child-theme versus wpcode decision.
Act as a senior WordPress solution architect and Kadence Theme/Kadence Blocks/WPCode specialist. TASK: Child-theme versus WPCode decision. PROJECT INPUTS - Website type and business goal: [SITE TYPE + GOAL] - Audience, locale and key conversion: [AUDIENCE + LOCALE + CTA] - Current stack (WordPress/PHP, Kadence Theme, Kadence Blocks, WPCode, plugins): [VERIFIED VERSIONS] - Current page, screenshot, issue or reference: [URL OR SANITIZED DETAILS] - Constraints (budget, editor skill, hosting, launch date): [CONSTRAINTS] - Existing content, brand styles and approved data: [SOURCE MATERIAL] SPECIFIC OBJECTIVE Develop a practical, results-oriented solution for child-theme versus wpcode decision in the context of this website. Prefer kadence theme native settings and document exact customizer or builder locations. Explain what should be done with Kadence Theme settings, what should be built with Kadence Blocks, and when WPCode is warranted. Do not invent installed plugin capabilities or pretend you accessed the live site. DELIVER EXACTLY 1. A task-specific implementation blueprint for “Child-theme versus WPCode decision” with exact WordPress/Kadence navigation or WPCode placement when relevant. 2. An ordered action checklist with dependencies and who owns each action. 3. Copy-ready artifacts where relevant (block hierarchy, settings matrix, sample copy, scoped CSS, PHP or vanilla JavaScript), with code fences and placement instructions. 4. Desktop/tablet/mobile acceptance tests, accessibility and security checks relevant to the task. 5. Failure cases, troubleshooting clues, rollback steps and final client-facing completion criteria. IMPLEMENTATION SAFETY Flag assumptions; favor native block controls over custom code; do not hardcode credentials or private data. For PHP/JS/CSS, provide exact location, activation scope, prerequisite checks, staging test, and undo method. If a plugin or version-specific behavior is uncertain, say what to verify first. Finish with a concise Definition of Done and a measurable business or UX outcome, without promising a result unsupported by data.
04. Kadence Blocks Design System
Reusable section patterns
Create a tested, client-ready outcome for reusable section patterns.
Act as a senior WordPress solution architect and Kadence Theme/Kadence Blocks/WPCode specialist. TASK: Reusable section patterns. PROJECT INPUTS - Website type and business goal: [SITE TYPE + GOAL] - Audience, locale and key conversion: [AUDIENCE + LOCALE + CTA] - Current stack (WordPress/PHP, Kadence Theme, Kadence Blocks, WPCode, plugins): [VERIFIED VERSIONS] - Current page, screenshot, issue or reference: [URL OR SANITIZED DETAILS] - Constraints (budget, editor skill, hosting, launch date): [CONSTRAINTS] - Existing content, brand styles and approved data: [SOURCE MATERIAL] SPECIFIC OBJECTIVE Develop a practical, results-oriented solution for reusable section patterns in the context of this website. Prefer kadence blocks native controls; document mobile stacking and reusable pattern naming. Explain what should be done with Kadence Theme settings, what should be built with Kadence Blocks, and when WPCode is warranted. Do not invent installed plugin capabilities or pretend you accessed the live site. DELIVER EXACTLY 1. A task-specific implementation blueprint for “Reusable section patterns” with exact WordPress/Kadence navigation or WPCode placement when relevant. 2. An ordered action checklist with dependencies and who owns each action. 3. Copy-ready artifacts where relevant (block hierarchy, settings matrix, sample copy, scoped CSS, PHP or vanilla JavaScript), with code fences and placement instructions. 4. Desktop/tablet/mobile acceptance tests, accessibility and security checks relevant to the task. 5. Failure cases, troubleshooting clues, rollback steps and final client-facing completion criteria. IMPLEMENTATION SAFETY Flag assumptions; favor native block controls over custom code; do not hardcode credentials or private data. For PHP/JS/CSS, provide exact location, activation scope, prerequisite checks, staging test, and undo method. If a plugin or version-specific behavior is uncertain, say what to verify first. Finish with a concise Definition of Done and a measurable business or UX outcome, without promising a result unsupported by data.
Row Layout grid strategy
Create a tested, client-ready outcome for row layout grid strategy.
Act as a senior WordPress solution architect and Kadence Theme/Kadence Blocks/WPCode specialist. TASK: Row Layout grid strategy. PROJECT INPUTS - Website type and business goal: [SITE TYPE + GOAL] - Audience, locale and key conversion: [AUDIENCE + LOCALE + CTA] - Current stack (WordPress/PHP, Kadence Theme, Kadence Blocks, WPCode, plugins): [VERIFIED VERSIONS] - Current page, screenshot, issue or reference: [URL OR SANITIZED DETAILS] - Constraints (budget, editor skill, hosting, launch date): [CONSTRAINTS] - Existing content, brand styles and approved data: [SOURCE MATERIAL] SPECIFIC OBJECTIVE Develop a practical, results-oriented solution for row layout grid strategy in the context of this website. Prefer kadence blocks native controls; document mobile stacking and reusable pattern naming. Explain what should be done with Kadence Theme settings, what should be built with Kadence Blocks, and when WPCode is warranted. Do not invent installed plugin capabilities or pretend you accessed the live site. DELIVER EXACTLY 1. A task-specific implementation blueprint for “Row Layout grid strategy” with exact WordPress/Kadence navigation or WPCode placement when relevant. 2. An ordered action checklist with dependencies and who owns each action. 3. Copy-ready artifacts where relevant (block hierarchy, settings matrix, sample copy, scoped CSS, PHP or vanilla JavaScript), with code fences and placement instructions. 4. Desktop/tablet/mobile acceptance tests, accessibility and security checks relevant to the task. 5. Failure cases, troubleshooting clues, rollback steps and final client-facing completion criteria. IMPLEMENTATION SAFETY Flag assumptions; favor native block controls over custom code; do not hardcode credentials or private data. For PHP/JS/CSS, provide exact location, activation scope, prerequisite checks, staging test, and undo method. If a plugin or version-specific behavior is uncertain, say what to verify first. Finish with a concise Definition of Done and a measurable business or UX outcome, without promising a result unsupported by data.
Advanced Heading hierarchy
Create a tested, client-ready outcome for advanced heading hierarchy.
Act as a senior WordPress solution architect and Kadence Theme/Kadence Blocks/WPCode specialist. TASK: Advanced Heading hierarchy. PROJECT INPUTS - Website type and business goal: [SITE TYPE + GOAL] - Audience, locale and key conversion: [AUDIENCE + LOCALE + CTA] - Current stack (WordPress/PHP, Kadence Theme, Kadence Blocks, WPCode, plugins): [VERIFIED VERSIONS] - Current page, screenshot, issue or reference: [URL OR SANITIZED DETAILS] - Constraints (budget, editor skill, hosting, launch date): [CONSTRAINTS] - Existing content, brand styles and approved data: [SOURCE MATERIAL] SPECIFIC OBJECTIVE Develop a practical, results-oriented solution for advanced heading hierarchy in the context of this website. Prefer kadence blocks native controls; document mobile stacking and reusable pattern naming. Explain what should be done with Kadence Theme settings, what should be built with Kadence Blocks, and when WPCode is warranted. Do not invent installed plugin capabilities or pretend you accessed the live site. DELIVER EXACTLY 1. A task-specific implementation blueprint for “Advanced Heading hierarchy” with exact WordPress/Kadence navigation or WPCode placement when relevant. 2. An ordered action checklist with dependencies and who owns each action. 3. Copy-ready artifacts where relevant (block hierarchy, settings matrix, sample copy, scoped CSS, PHP or vanilla JavaScript), with code fences and placement instructions. 4. Desktop/tablet/mobile acceptance tests, accessibility and security checks relevant to the task. 5. Failure cases, troubleshooting clues, rollback steps and final client-facing completion criteria. IMPLEMENTATION SAFETY Flag assumptions; favor native block controls over custom code; do not hardcode credentials or private data. For PHP/JS/CSS, provide exact location, activation scope, prerequisite checks, staging test, and undo method. If a plugin or version-specific behavior is uncertain, say what to verify first. Finish with a concise Definition of Done and a measurable business or UX outcome, without promising a result unsupported by data.
Advanced Button states
Create a tested, client-ready outcome for advanced button states.
Act as a senior WordPress solution architect and Kadence Theme/Kadence Blocks/WPCode specialist. TASK: Advanced Button states. PROJECT INPUTS - Website type and business goal: [SITE TYPE + GOAL] - Audience, locale and key conversion: [AUDIENCE + LOCALE + CTA] - Current stack (WordPress/PHP, Kadence Theme, Kadence Blocks, WPCode, plugins): [VERIFIED VERSIONS] - Current page, screenshot, issue or reference: [URL OR SANITIZED DETAILS] - Constraints (budget, editor skill, hosting, launch date): [CONSTRAINTS] - Existing content, brand styles and approved data: [SOURCE MATERIAL] SPECIFIC OBJECTIVE Develop a practical, results-oriented solution for advanced button states in the context of this website. Prefer kadence blocks native controls; document mobile stacking and reusable pattern naming. Explain what should be done with Kadence Theme settings, what should be built with Kadence Blocks, and when WPCode is warranted. Do not invent installed plugin capabilities or pretend you accessed the live site. DELIVER EXACTLY 1. A task-specific implementation blueprint for “Advanced Button states” with exact WordPress/Kadence navigation or WPCode placement when relevant. 2. An ordered action checklist with dependencies and who owns each action. 3. Copy-ready artifacts where relevant (block hierarchy, settings matrix, sample copy, scoped CSS, PHP or vanilla JavaScript), with code fences and placement instructions. 4. Desktop/tablet/mobile acceptance tests, accessibility and security checks relevant to the task. 5. Failure cases, troubleshooting clues, rollback steps and final client-facing completion criteria. IMPLEMENTATION SAFETY Flag assumptions; favor native block controls over custom code; do not hardcode credentials or private data. For PHP/JS/CSS, provide exact location, activation scope, prerequisite checks, staging test, and undo method. If a plugin or version-specific behavior is uncertain, say what to verify first. Finish with a concise Definition of Done and a measurable business or UX outcome, without promising a result unsupported by data.
Icon and Info Box patterns
Create a tested, client-ready outcome for icon and info box patterns.
Act as a senior WordPress solution architect and Kadence Theme/Kadence Blocks/WPCode specialist. TASK: Icon and Info Box patterns. PROJECT INPUTS - Website type and business goal: [SITE TYPE + GOAL] - Audience, locale and key conversion: [AUDIENCE + LOCALE + CTA] - Current stack (WordPress/PHP, Kadence Theme, Kadence Blocks, WPCode, plugins): [VERIFIED VERSIONS] - Current page, screenshot, issue or reference: [URL OR SANITIZED DETAILS] - Constraints (budget, editor skill, hosting, launch date): [CONSTRAINTS] - Existing content, brand styles and approved data: [SOURCE MATERIAL] SPECIFIC OBJECTIVE Develop a practical, results-oriented solution for icon and info box patterns in the context of this website. Prefer kadence blocks native controls; document mobile stacking and reusable pattern naming. Explain what should be done with Kadence Theme settings, what should be built with Kadence Blocks, and when WPCode is warranted. Do not invent installed plugin capabilities or pretend you accessed the live site. DELIVER EXACTLY 1. A task-specific implementation blueprint for “Icon and Info Box patterns” with exact WordPress/Kadence navigation or WPCode placement when relevant. 2. An ordered action checklist with dependencies and who owns each action. 3. Copy-ready artifacts where relevant (block hierarchy, settings matrix, sample copy, scoped CSS, PHP or vanilla JavaScript), with code fences and placement instructions. 4. Desktop/tablet/mobile acceptance tests, accessibility and security checks relevant to the task. 5. Failure cases, troubleshooting clues, rollback steps and final client-facing completion criteria. IMPLEMENTATION SAFETY Flag assumptions; favor native block controls over custom code; do not hardcode credentials or private data. For PHP/JS/CSS, provide exact location, activation scope, prerequisite checks, staging test, and undo method. If a plugin or version-specific behavior is uncertain, say what to verify first. Finish with a concise Definition of Done and a measurable business or UX outcome, without promising a result unsupported by data.
Tabs and accordion accessibility
Create a tested, client-ready outcome for tabs and accordion accessibility.
Act as a senior WordPress solution architect and Kadence Theme/Kadence Blocks/WPCode specialist. TASK: Tabs and accordion accessibility. PROJECT INPUTS - Website type and business goal: [SITE TYPE + GOAL] - Audience, locale and key conversion: [AUDIENCE + LOCALE + CTA] - Current stack (WordPress/PHP, Kadence Theme, Kadence Blocks, WPCode, plugins): [VERIFIED VERSIONS] - Current page, screenshot, issue or reference: [URL OR SANITIZED DETAILS] - Constraints (budget, editor skill, hosting, launch date): [CONSTRAINTS] - Existing content, brand styles and approved data: [SOURCE MATERIAL] SPECIFIC OBJECTIVE Develop a practical, results-oriented solution for tabs and accordion accessibility in the context of this website. Prefer kadence blocks native controls; document mobile stacking and reusable pattern naming. Explain what should be done with Kadence Theme settings, what should be built with Kadence Blocks, and when WPCode is warranted. Do not invent installed plugin capabilities or pretend you accessed the live site. DELIVER EXACTLY 1. A task-specific implementation blueprint for “Tabs and accordion accessibility” with exact WordPress/Kadence navigation or WPCode placement when relevant. 2. An ordered action checklist with dependencies and who owns each action. 3. Copy-ready artifacts where relevant (block hierarchy, settings matrix, sample copy, scoped CSS, PHP or vanilla JavaScript), with code fences and placement instructions. 4. Desktop/tablet/mobile acceptance tests, accessibility and security checks relevant to the task. 5. Failure cases, troubleshooting clues, rollback steps and final client-facing completion criteria. IMPLEMENTATION SAFETY Flag assumptions; favor native block controls over custom code; do not hardcode credentials or private data. For PHP/JS/CSS, provide exact location, activation scope, prerequisite checks, staging test, and undo method. If a plugin or version-specific behavior is uncertain, say what to verify first. Finish with a concise Definition of Done and a measurable business or UX outcome, without promising a result unsupported by data.
Testimonials and review cards
Create a tested, client-ready outcome for testimonials and review cards.
Act as a senior WordPress solution architect and Kadence Theme/Kadence Blocks/WPCode specialist. TASK: Testimonials and review cards. PROJECT INPUTS - Website type and business goal: [SITE TYPE + GOAL] - Audience, locale and key conversion: [AUDIENCE + LOCALE + CTA] - Current stack (WordPress/PHP, Kadence Theme, Kadence Blocks, WPCode, plugins): [VERIFIED VERSIONS] - Current page, screenshot, issue or reference: [URL OR SANITIZED DETAILS] - Constraints (budget, editor skill, hosting, launch date): [CONSTRAINTS] - Existing content, brand styles and approved data: [SOURCE MATERIAL] SPECIFIC OBJECTIVE Develop a practical, results-oriented solution for testimonials and review cards in the context of this website. Prefer kadence blocks native controls; document mobile stacking and reusable pattern naming. Explain what should be done with Kadence Theme settings, what should be built with Kadence Blocks, and when WPCode is warranted. Do not invent installed plugin capabilities or pretend you accessed the live site. DELIVER EXACTLY 1. A task-specific implementation blueprint for “Testimonials and review cards” with exact WordPress/Kadence navigation or WPCode placement when relevant. 2. An ordered action checklist with dependencies and who owns each action. 3. Copy-ready artifacts where relevant (block hierarchy, settings matrix, sample copy, scoped CSS, PHP or vanilla JavaScript), with code fences and placement instructions. 4. Desktop/tablet/mobile acceptance tests, accessibility and security checks relevant to the task. 5. Failure cases, troubleshooting clues, rollback steps and final client-facing completion criteria. IMPLEMENTATION SAFETY Flag assumptions; favor native block controls over custom code; do not hardcode credentials or private data. For PHP/JS/CSS, provide exact location, activation scope, prerequisite checks, staging test, and undo method. If a plugin or version-specific behavior is uncertain, say what to verify first. Finish with a concise Definition of Done and a measurable business or UX outcome, without promising a result unsupported by data.
Form block layout blueprint
Create a tested, client-ready outcome for form block layout blueprint.
Act as a senior WordPress solution architect and Kadence Theme/Kadence Blocks/WPCode specialist. TASK: Form block layout blueprint. PROJECT INPUTS - Website type and business goal: [SITE TYPE + GOAL] - Audience, locale and key conversion: [AUDIENCE + LOCALE + CTA] - Current stack (WordPress/PHP, Kadence Theme, Kadence Blocks, WPCode, plugins): [VERIFIED VERSIONS] - Current page, screenshot, issue or reference: [URL OR SANITIZED DETAILS] - Constraints (budget, editor skill, hosting, launch date): [CONSTRAINTS] - Existing content, brand styles and approved data: [SOURCE MATERIAL] SPECIFIC OBJECTIVE Develop a practical, results-oriented solution for form block layout blueprint in the context of this website. Prefer kadence blocks native controls; document mobile stacking and reusable pattern naming. Explain what should be done with Kadence Theme settings, what should be built with Kadence Blocks, and when WPCode is warranted. Do not invent installed plugin capabilities or pretend you accessed the live site. DELIVER EXACTLY 1. A task-specific implementation blueprint for “Form block layout blueprint” with exact WordPress/Kadence navigation or WPCode placement when relevant. 2. An ordered action checklist with dependencies and who owns each action. 3. Copy-ready artifacts where relevant (block hierarchy, settings matrix, sample copy, scoped CSS, PHP or vanilla JavaScript), with code fences and placement instructions. 4. Desktop/tablet/mobile acceptance tests, accessibility and security checks relevant to the task. 5. Failure cases, troubleshooting clues, rollback steps and final client-facing completion criteria. IMPLEMENTATION SAFETY Flag assumptions; favor native block controls over custom code; do not hardcode credentials or private data. For PHP/JS/CSS, provide exact location, activation scope, prerequisite checks, staging test, and undo method. If a plugin or version-specific behavior is uncertain, say what to verify first. Finish with a concise Definition of Done and a measurable business or UX outcome, without promising a result unsupported by data.
Conditional display planning
Create a tested, client-ready outcome for conditional display planning.
Act as a senior WordPress solution architect and Kadence Theme/Kadence Blocks/WPCode specialist. TASK: Conditional display planning. PROJECT INPUTS - Website type and business goal: [SITE TYPE + GOAL] - Audience, locale and key conversion: [AUDIENCE + LOCALE + CTA] - Current stack (WordPress/PHP, Kadence Theme, Kadence Blocks, WPCode, plugins): [VERIFIED VERSIONS] - Current page, screenshot, issue or reference: [URL OR SANITIZED DETAILS] - Constraints (budget, editor skill, hosting, launch date): [CONSTRAINTS] - Existing content, brand styles and approved data: [SOURCE MATERIAL] SPECIFIC OBJECTIVE Develop a practical, results-oriented solution for conditional display planning in the context of this website. Prefer kadence blocks native controls; document mobile stacking and reusable pattern naming. Explain what should be done with Kadence Theme settings, what should be built with Kadence Blocks, and when WPCode is warranted. Do not invent installed plugin capabilities or pretend you accessed the live site. DELIVER EXACTLY 1. A task-specific implementation blueprint for “Conditional display planning” with exact WordPress/Kadence navigation or WPCode placement when relevant. 2. An ordered action checklist with dependencies and who owns each action. 3. Copy-ready artifacts where relevant (block hierarchy, settings matrix, sample copy, scoped CSS, PHP or vanilla JavaScript), with code fences and placement instructions. 4. Desktop/tablet/mobile acceptance tests, accessibility and security checks relevant to the task. 5. Failure cases, troubleshooting clues, rollback steps and final client-facing completion criteria. IMPLEMENTATION SAFETY Flag assumptions; favor native block controls over custom code; do not hardcode credentials or private data. For PHP/JS/CSS, provide exact location, activation scope, prerequisite checks, staging test, and undo method. If a plugin or version-specific behavior is uncertain, say what to verify first. Finish with a concise Definition of Done and a measurable business or UX outcome, without promising a result unsupported by data.
Pattern library governance
Create a tested, client-ready outcome for pattern library governance.
Act as a senior WordPress solution architect and Kadence Theme/Kadence Blocks/WPCode specialist. TASK: Pattern library governance. PROJECT INPUTS - Website type and business goal: [SITE TYPE + GOAL] - Audience, locale and key conversion: [AUDIENCE + LOCALE + CTA] - Current stack (WordPress/PHP, Kadence Theme, Kadence Blocks, WPCode, plugins): [VERIFIED VERSIONS] - Current page, screenshot, issue or reference: [URL OR SANITIZED DETAILS] - Constraints (budget, editor skill, hosting, launch date): [CONSTRAINTS] - Existing content, brand styles and approved data: [SOURCE MATERIAL] SPECIFIC OBJECTIVE Develop a practical, results-oriented solution for pattern library governance in the context of this website. Prefer kadence blocks native controls; document mobile stacking and reusable pattern naming. Explain what should be done with Kadence Theme settings, what should be built with Kadence Blocks, and when WPCode is warranted. Do not invent installed plugin capabilities or pretend you accessed the live site. DELIVER EXACTLY 1. A task-specific implementation blueprint for “Pattern library governance” with exact WordPress/Kadence navigation or WPCode placement when relevant. 2. An ordered action checklist with dependencies and who owns each action. 3. Copy-ready artifacts where relevant (block hierarchy, settings matrix, sample copy, scoped CSS, PHP or vanilla JavaScript), with code fences and placement instructions. 4. Desktop/tablet/mobile acceptance tests, accessibility and security checks relevant to the task. 5. Failure cases, troubleshooting clues, rollback steps and final client-facing completion criteria. IMPLEMENTATION SAFETY Flag assumptions; favor native block controls over custom code; do not hardcode credentials or private data. For PHP/JS/CSS, provide exact location, activation scope, prerequisite checks, staging test, and undo method. If a plugin or version-specific behavior is uncertain, say what to verify first. Finish with a concise Definition of Done and a measurable business or UX outcome, without promising a result unsupported by data.
05. Homepage & High-Converting Landing Pages
Hero value proposition
Create a tested, client-ready outcome for hero value proposition.
Act as a senior WordPress solution architect and Kadence Theme/Kadence Blocks/WPCode specialist. TASK: Hero value proposition. PROJECT INPUTS - Website type and business goal: [SITE TYPE + GOAL] - Audience, locale and key conversion: [AUDIENCE + LOCALE + CTA] - Current stack (WordPress/PHP, Kadence Theme, Kadence Blocks, WPCode, plugins): [VERIFIED VERSIONS] - Current page, screenshot, issue or reference: [URL OR SANITIZED DETAILS] - Constraints (budget, editor skill, hosting, launch date): [CONSTRAINTS] - Existing content, brand styles and approved data: [SOURCE MATERIAL] SPECIFIC OBJECTIVE Develop a practical, results-oriented solution for hero value proposition in the context of this website. Tie each block to one visitor intent and measurable cta. Explain what should be done with Kadence Theme settings, what should be built with Kadence Blocks, and when WPCode is warranted. Do not invent installed plugin capabilities or pretend you accessed the live site. DELIVER EXACTLY 1. A task-specific implementation blueprint for “Hero value proposition” with exact WordPress/Kadence navigation or WPCode placement when relevant. 2. An ordered action checklist with dependencies and who owns each action. 3. Copy-ready artifacts where relevant (block hierarchy, settings matrix, sample copy, scoped CSS, PHP or vanilla JavaScript), with code fences and placement instructions. 4. Desktop/tablet/mobile acceptance tests, accessibility and security checks relevant to the task. 5. Failure cases, troubleshooting clues, rollback steps and final client-facing completion criteria. IMPLEMENTATION SAFETY Flag assumptions; favor native block controls over custom code; do not hardcode credentials or private data. For PHP/JS/CSS, provide exact location, activation scope, prerequisite checks, staging test, and undo method. If a plugin or version-specific behavior is uncertain, say what to verify first. Finish with a concise Definition of Done and a measurable business or UX outcome, without promising a result unsupported by data.
Above-fold CTA testing
Create a tested, client-ready outcome for above-fold cta testing.
Act as a senior WordPress solution architect and Kadence Theme/Kadence Blocks/WPCode specialist. TASK: Above-fold CTA testing. PROJECT INPUTS - Website type and business goal: [SITE TYPE + GOAL] - Audience, locale and key conversion: [AUDIENCE + LOCALE + CTA] - Current stack (WordPress/PHP, Kadence Theme, Kadence Blocks, WPCode, plugins): [VERIFIED VERSIONS] - Current page, screenshot, issue or reference: [URL OR SANITIZED DETAILS] - Constraints (budget, editor skill, hosting, launch date): [CONSTRAINTS] - Existing content, brand styles and approved data: [SOURCE MATERIAL] SPECIFIC OBJECTIVE Develop a practical, results-oriented solution for above-fold cta testing in the context of this website. Tie each block to one visitor intent and measurable cta. Explain what should be done with Kadence Theme settings, what should be built with Kadence Blocks, and when WPCode is warranted. Do not invent installed plugin capabilities or pretend you accessed the live site. DELIVER EXACTLY 1. A task-specific implementation blueprint for “Above-fold CTA testing” with exact WordPress/Kadence navigation or WPCode placement when relevant. 2. An ordered action checklist with dependencies and who owns each action. 3. Copy-ready artifacts where relevant (block hierarchy, settings matrix, sample copy, scoped CSS, PHP or vanilla JavaScript), with code fences and placement instructions. 4. Desktop/tablet/mobile acceptance tests, accessibility and security checks relevant to the task. 5. Failure cases, troubleshooting clues, rollback steps and final client-facing completion criteria. IMPLEMENTATION SAFETY Flag assumptions; favor native block controls over custom code; do not hardcode credentials or private data. For PHP/JS/CSS, provide exact location, activation scope, prerequisite checks, staging test, and undo method. If a plugin or version-specific behavior is uncertain, say what to verify first. Finish with a concise Definition of Done and a measurable business or UX outcome, without promising a result unsupported by data.
Service proof section
Create a tested, client-ready outcome for service proof section.
Act as a senior WordPress solution architect and Kadence Theme/Kadence Blocks/WPCode specialist. TASK: Service proof section. PROJECT INPUTS - Website type and business goal: [SITE TYPE + GOAL] - Audience, locale and key conversion: [AUDIENCE + LOCALE + CTA] - Current stack (WordPress/PHP, Kadence Theme, Kadence Blocks, WPCode, plugins): [VERIFIED VERSIONS] - Current page, screenshot, issue or reference: [URL OR SANITIZED DETAILS] - Constraints (budget, editor skill, hosting, launch date): [CONSTRAINTS] - Existing content, brand styles and approved data: [SOURCE MATERIAL] SPECIFIC OBJECTIVE Develop a practical, results-oriented solution for service proof section in the context of this website. Tie each block to one visitor intent and measurable cta. Explain what should be done with Kadence Theme settings, what should be built with Kadence Blocks, and when WPCode is warranted. Do not invent installed plugin capabilities or pretend you accessed the live site. DELIVER EXACTLY 1. A task-specific implementation blueprint for “Service proof section” with exact WordPress/Kadence navigation or WPCode placement when relevant. 2. An ordered action checklist with dependencies and who owns each action. 3. Copy-ready artifacts where relevant (block hierarchy, settings matrix, sample copy, scoped CSS, PHP or vanilla JavaScript), with code fences and placement instructions. 4. Desktop/tablet/mobile acceptance tests, accessibility and security checks relevant to the task. 5. Failure cases, troubleshooting clues, rollback steps and final client-facing completion criteria. IMPLEMENTATION SAFETY Flag assumptions; favor native block controls over custom code; do not hardcode credentials or private data. For PHP/JS/CSS, provide exact location, activation scope, prerequisite checks, staging test, and undo method. If a plugin or version-specific behavior is uncertain, say what to verify first. Finish with a concise Definition of Done and a measurable business or UX outcome, without promising a result unsupported by data.
Benefits versus features section
Create a tested, client-ready outcome for benefits versus features section.
Act as a senior WordPress solution architect and Kadence Theme/Kadence Blocks/WPCode specialist. TASK: Benefits versus features section. PROJECT INPUTS - Website type and business goal: [SITE TYPE + GOAL] - Audience, locale and key conversion: [AUDIENCE + LOCALE + CTA] - Current stack (WordPress/PHP, Kadence Theme, Kadence Blocks, WPCode, plugins): [VERIFIED VERSIONS] - Current page, screenshot, issue or reference: [URL OR SANITIZED DETAILS] - Constraints (budget, editor skill, hosting, launch date): [CONSTRAINTS] - Existing content, brand styles and approved data: [SOURCE MATERIAL] SPECIFIC OBJECTIVE Develop a practical, results-oriented solution for benefits versus features section in the context of this website. Tie each block to one visitor intent and measurable cta. Explain what should be done with Kadence Theme settings, what should be built with Kadence Blocks, and when WPCode is warranted. Do not invent installed plugin capabilities or pretend you accessed the live site. DELIVER EXACTLY 1. A task-specific implementation blueprint for “Benefits versus features section” with exact WordPress/Kadence navigation or WPCode placement when relevant. 2. An ordered action checklist with dependencies and who owns each action. 3. Copy-ready artifacts where relevant (block hierarchy, settings matrix, sample copy, scoped CSS, PHP or vanilla JavaScript), with code fences and placement instructions. 4. Desktop/tablet/mobile acceptance tests, accessibility and security checks relevant to the task. 5. Failure cases, troubleshooting clues, rollback steps and final client-facing completion criteria. IMPLEMENTATION SAFETY Flag assumptions; favor native block controls over custom code; do not hardcode credentials or private data. For PHP/JS/CSS, provide exact location, activation scope, prerequisite checks, staging test, and undo method. If a plugin or version-specific behavior is uncertain, say what to verify first. Finish with a concise Definition of Done and a measurable business or UX outcome, without promising a result unsupported by data.
Trust and credentials block
Create a tested, client-ready outcome for trust and credentials block.
Act as a senior WordPress solution architect and Kadence Theme/Kadence Blocks/WPCode specialist. TASK: Trust and credentials block. PROJECT INPUTS - Website type and business goal: [SITE TYPE + GOAL] - Audience, locale and key conversion: [AUDIENCE + LOCALE + CTA] - Current stack (WordPress/PHP, Kadence Theme, Kadence Blocks, WPCode, plugins): [VERIFIED VERSIONS] - Current page, screenshot, issue or reference: [URL OR SANITIZED DETAILS] - Constraints (budget, editor skill, hosting, launch date): [CONSTRAINTS] - Existing content, brand styles and approved data: [SOURCE MATERIAL] SPECIFIC OBJECTIVE Develop a practical, results-oriented solution for trust and credentials block in the context of this website. Tie each block to one visitor intent and measurable cta. Explain what should be done with Kadence Theme settings, what should be built with Kadence Blocks, and when WPCode is warranted. Do not invent installed plugin capabilities or pretend you accessed the live site. DELIVER EXACTLY 1. A task-specific implementation blueprint for “Trust and credentials block” with exact WordPress/Kadence navigation or WPCode placement when relevant. 2. An ordered action checklist with dependencies and who owns each action. 3. Copy-ready artifacts where relevant (block hierarchy, settings matrix, sample copy, scoped CSS, PHP or vanilla JavaScript), with code fences and placement instructions. 4. Desktop/tablet/mobile acceptance tests, accessibility and security checks relevant to the task. 5. Failure cases, troubleshooting clues, rollback steps and final client-facing completion criteria. IMPLEMENTATION SAFETY Flag assumptions; favor native block controls over custom code; do not hardcode credentials or private data. For PHP/JS/CSS, provide exact location, activation scope, prerequisite checks, staging test, and undo method. If a plugin or version-specific behavior is uncertain, say what to verify first. Finish with a concise Definition of Done and a measurable business or UX outcome, without promising a result unsupported by data.
Pricing teaser layout
Create a tested, client-ready outcome for pricing teaser layout.
Act as a senior WordPress solution architect and Kadence Theme/Kadence Blocks/WPCode specialist. TASK: Pricing teaser layout. PROJECT INPUTS - Website type and business goal: [SITE TYPE + GOAL] - Audience, locale and key conversion: [AUDIENCE + LOCALE + CTA] - Current stack (WordPress/PHP, Kadence Theme, Kadence Blocks, WPCode, plugins): [VERIFIED VERSIONS] - Current page, screenshot, issue or reference: [URL OR SANITIZED DETAILS] - Constraints (budget, editor skill, hosting, launch date): [CONSTRAINTS] - Existing content, brand styles and approved data: [SOURCE MATERIAL] SPECIFIC OBJECTIVE Develop a practical, results-oriented solution for pricing teaser layout in the context of this website. Tie each block to one visitor intent and measurable cta. Explain what should be done with Kadence Theme settings, what should be built with Kadence Blocks, and when WPCode is warranted. Do not invent installed plugin capabilities or pretend you accessed the live site. DELIVER EXACTLY 1. A task-specific implementation blueprint for “Pricing teaser layout” with exact WordPress/Kadence navigation or WPCode placement when relevant. 2. An ordered action checklist with dependencies and who owns each action. 3. Copy-ready artifacts where relevant (block hierarchy, settings matrix, sample copy, scoped CSS, PHP or vanilla JavaScript), with code fences and placement instructions. 4. Desktop/tablet/mobile acceptance tests, accessibility and security checks relevant to the task. 5. Failure cases, troubleshooting clues, rollback steps and final client-facing completion criteria. IMPLEMENTATION SAFETY Flag assumptions; favor native block controls over custom code; do not hardcode credentials or private data. For PHP/JS/CSS, provide exact location, activation scope, prerequisite checks, staging test, and undo method. If a plugin or version-specific behavior is uncertain, say what to verify first. Finish with a concise Definition of Done and a measurable business or UX outcome, without promising a result unsupported by data.
Lead form placement
Create a tested, client-ready outcome for lead form placement.
Act as a senior WordPress solution architect and Kadence Theme/Kadence Blocks/WPCode specialist. TASK: Lead form placement. PROJECT INPUTS - Website type and business goal: [SITE TYPE + GOAL] - Audience, locale and key conversion: [AUDIENCE + LOCALE + CTA] - Current stack (WordPress/PHP, Kadence Theme, Kadence Blocks, WPCode, plugins): [VERIFIED VERSIONS] - Current page, screenshot, issue or reference: [URL OR SANITIZED DETAILS] - Constraints (budget, editor skill, hosting, launch date): [CONSTRAINTS] - Existing content, brand styles and approved data: [SOURCE MATERIAL] SPECIFIC OBJECTIVE Develop a practical, results-oriented solution for lead form placement in the context of this website. Tie each block to one visitor intent and measurable cta. Explain what should be done with Kadence Theme settings, what should be built with Kadence Blocks, and when WPCode is warranted. Do not invent installed plugin capabilities or pretend you accessed the live site. DELIVER EXACTLY 1. A task-specific implementation blueprint for “Lead form placement” with exact WordPress/Kadence navigation or WPCode placement when relevant. 2. An ordered action checklist with dependencies and who owns each action. 3. Copy-ready artifacts where relevant (block hierarchy, settings matrix, sample copy, scoped CSS, PHP or vanilla JavaScript), with code fences and placement instructions. 4. Desktop/tablet/mobile acceptance tests, accessibility and security checks relevant to the task. 5. Failure cases, troubleshooting clues, rollback steps and final client-facing completion criteria. IMPLEMENTATION SAFETY Flag assumptions; favor native block controls over custom code; do not hardcode credentials or private data. For PHP/JS/CSS, provide exact location, activation scope, prerequisite checks, staging test, and undo method. If a plugin or version-specific behavior is uncertain, say what to verify first. Finish with a concise Definition of Done and a measurable business or UX outcome, without promising a result unsupported by data.
Landing page objection handling
Create a tested, client-ready outcome for landing page objection handling.
Act as a senior WordPress solution architect and Kadence Theme/Kadence Blocks/WPCode specialist. TASK: Landing page objection handling. PROJECT INPUTS - Website type and business goal: [SITE TYPE + GOAL] - Audience, locale and key conversion: [AUDIENCE + LOCALE + CTA] - Current stack (WordPress/PHP, Kadence Theme, Kadence Blocks, WPCode, plugins): [VERIFIED VERSIONS] - Current page, screenshot, issue or reference: [URL OR SANITIZED DETAILS] - Constraints (budget, editor skill, hosting, launch date): [CONSTRAINTS] - Existing content, brand styles and approved data: [SOURCE MATERIAL] SPECIFIC OBJECTIVE Develop a practical, results-oriented solution for landing page objection handling in the context of this website. Tie each block to one visitor intent and measurable cta. Explain what should be done with Kadence Theme settings, what should be built with Kadence Blocks, and when WPCode is warranted. Do not invent installed plugin capabilities or pretend you accessed the live site. DELIVER EXACTLY 1. A task-specific implementation blueprint for “Landing page objection handling” with exact WordPress/Kadence navigation or WPCode placement when relevant. 2. An ordered action checklist with dependencies and who owns each action. 3. Copy-ready artifacts where relevant (block hierarchy, settings matrix, sample copy, scoped CSS, PHP or vanilla JavaScript), with code fences and placement instructions. 4. Desktop/tablet/mobile acceptance tests, accessibility and security checks relevant to the task. 5. Failure cases, troubleshooting clues, rollback steps and final client-facing completion criteria. IMPLEMENTATION SAFETY Flag assumptions; favor native block controls over custom code; do not hardcode credentials or private data. For PHP/JS/CSS, provide exact location, activation scope, prerequisite checks, staging test, and undo method. If a plugin or version-specific behavior is uncertain, say what to verify first. Finish with a concise Definition of Done and a measurable business or UX outcome, without promising a result unsupported by data.
Thank-you page plan
Create a tested, client-ready outcome for thank-you page plan.
Act as a senior WordPress solution architect and Kadence Theme/Kadence Blocks/WPCode specialist. TASK: Thank-you page plan. PROJECT INPUTS - Website type and business goal: [SITE TYPE + GOAL] - Audience, locale and key conversion: [AUDIENCE + LOCALE + CTA] - Current stack (WordPress/PHP, Kadence Theme, Kadence Blocks, WPCode, plugins): [VERIFIED VERSIONS] - Current page, screenshot, issue or reference: [URL OR SANITIZED DETAILS] - Constraints (budget, editor skill, hosting, launch date): [CONSTRAINTS] - Existing content, brand styles and approved data: [SOURCE MATERIAL] SPECIFIC OBJECTIVE Develop a practical, results-oriented solution for thank-you page plan in the context of this website. Tie each block to one visitor intent and measurable cta. Explain what should be done with Kadence Theme settings, what should be built with Kadence Blocks, and when WPCode is warranted. Do not invent installed plugin capabilities or pretend you accessed the live site. DELIVER EXACTLY 1. A task-specific implementation blueprint for “Thank-you page plan” with exact WordPress/Kadence navigation or WPCode placement when relevant. 2. An ordered action checklist with dependencies and who owns each action. 3. Copy-ready artifacts where relevant (block hierarchy, settings matrix, sample copy, scoped CSS, PHP or vanilla JavaScript), with code fences and placement instructions. 4. Desktop/tablet/mobile acceptance tests, accessibility and security checks relevant to the task. 5. Failure cases, troubleshooting clues, rollback steps and final client-facing completion criteria. IMPLEMENTATION SAFETY Flag assumptions; favor native block controls over custom code; do not hardcode credentials or private data. For PHP/JS/CSS, provide exact location, activation scope, prerequisite checks, staging test, and undo method. If a plugin or version-specific behavior is uncertain, say what to verify first. Finish with a concise Definition of Done and a measurable business or UX outcome, without promising a result unsupported by data.
Mobile conversion audit
Create a tested, client-ready outcome for mobile conversion audit.
Act as a senior WordPress solution architect and Kadence Theme/Kadence Blocks/WPCode specialist. TASK: Mobile conversion audit. PROJECT INPUTS - Website type and business goal: [SITE TYPE + GOAL] - Audience, locale and key conversion: [AUDIENCE + LOCALE + CTA] - Current stack (WordPress/PHP, Kadence Theme, Kadence Blocks, WPCode, plugins): [VERIFIED VERSIONS] - Current page, screenshot, issue or reference: [URL OR SANITIZED DETAILS] - Constraints (budget, editor skill, hosting, launch date): [CONSTRAINTS] - Existing content, brand styles and approved data: [SOURCE MATERIAL] SPECIFIC OBJECTIVE Develop a practical, results-oriented solution for mobile conversion audit in the context of this website. Tie each block to one visitor intent and measurable cta. Explain what should be done with Kadence Theme settings, what should be built with Kadence Blocks, and when WPCode is warranted. Do not invent installed plugin capabilities or pretend you accessed the live site. DELIVER EXACTLY 1. A task-specific implementation blueprint for “Mobile conversion audit” with exact WordPress/Kadence navigation or WPCode placement when relevant. 2. An ordered action checklist with dependencies and who owns each action. 3. Copy-ready artifacts where relevant (block hierarchy, settings matrix, sample copy, scoped CSS, PHP or vanilla JavaScript), with code fences and placement instructions. 4. Desktop/tablet/mobile acceptance tests, accessibility and security checks relevant to the task. 5. Failure cases, troubleshooting clues, rollback steps and final client-facing completion criteria. IMPLEMENTATION SAFETY Flag assumptions; favor native block controls over custom code; do not hardcode credentials or private data. For PHP/JS/CSS, provide exact location, activation scope, prerequisite checks, staging test, and undo method. If a plugin or version-specific behavior is uncertain, say what to verify first. Finish with a concise Definition of Done and a measurable business or UX outcome, without promising a result unsupported by data.
06. Local Service Websites
Service area site hierarchy
Create a tested, client-ready outcome for service area site hierarchy.
Act as a senior WordPress solution architect and Kadence Theme/Kadence Blocks/WPCode specialist. TASK: Service area site hierarchy. PROJECT INPUTS - Website type and business goal: [SITE TYPE + GOAL] - Audience, locale and key conversion: [AUDIENCE + LOCALE + CTA] - Current stack (WordPress/PHP, Kadence Theme, Kadence Blocks, WPCode, plugins): [VERIFIED VERSIONS] - Current page, screenshot, issue or reference: [URL OR SANITIZED DETAILS] - Constraints (budget, editor skill, hosting, launch date): [CONSTRAINTS] - Existing content, brand styles and approved data: [SOURCE MATERIAL] SPECIFIC OBJECTIVE Develop a practical, results-oriented solution for service area site hierarchy in the context of this website. Do not create doorway pages or invent local experience, addresses, ratings, or endorsements. Explain what should be done with Kadence Theme settings, what should be built with Kadence Blocks, and when WPCode is warranted. Do not invent installed plugin capabilities or pretend you accessed the live site. DELIVER EXACTLY 1. A task-specific implementation blueprint for “Service area site hierarchy” with exact WordPress/Kadence navigation or WPCode placement when relevant. 2. An ordered action checklist with dependencies and who owns each action. 3. Copy-ready artifacts where relevant (block hierarchy, settings matrix, sample copy, scoped CSS, PHP or vanilla JavaScript), with code fences and placement instructions. 4. Desktop/tablet/mobile acceptance tests, accessibility and security checks relevant to the task. 5. Failure cases, troubleshooting clues, rollback steps and final client-facing completion criteria. IMPLEMENTATION SAFETY Flag assumptions; favor native block controls over custom code; do not hardcode credentials or private data. For PHP/JS/CSS, provide exact location, activation scope, prerequisite checks, staging test, and undo method. If a plugin or version-specific behavior is uncertain, say what to verify first. Finish with a concise Definition of Done and a measurable business or UX outcome, without promising a result unsupported by data.
Location landing page template
Create a tested, client-ready outcome for location landing page template.
Act as a senior WordPress solution architect and Kadence Theme/Kadence Blocks/WPCode specialist. TASK: Location landing page template. PROJECT INPUTS - Website type and business goal: [SITE TYPE + GOAL] - Audience, locale and key conversion: [AUDIENCE + LOCALE + CTA] - Current stack (WordPress/PHP, Kadence Theme, Kadence Blocks, WPCode, plugins): [VERIFIED VERSIONS] - Current page, screenshot, issue or reference: [URL OR SANITIZED DETAILS] - Constraints (budget, editor skill, hosting, launch date): [CONSTRAINTS] - Existing content, brand styles and approved data: [SOURCE MATERIAL] SPECIFIC OBJECTIVE Develop a practical, results-oriented solution for location landing page template in the context of this website. Do not create doorway pages or invent local experience, addresses, ratings, or endorsements. Explain what should be done with Kadence Theme settings, what should be built with Kadence Blocks, and when WPCode is warranted. Do not invent installed plugin capabilities or pretend you accessed the live site. DELIVER EXACTLY 1. A task-specific implementation blueprint for “Location landing page template” with exact WordPress/Kadence navigation or WPCode placement when relevant. 2. An ordered action checklist with dependencies and who owns each action. 3. Copy-ready artifacts where relevant (block hierarchy, settings matrix, sample copy, scoped CSS, PHP or vanilla JavaScript), with code fences and placement instructions. 4. Desktop/tablet/mobile acceptance tests, accessibility and security checks relevant to the task. 5. Failure cases, troubleshooting clues, rollback steps and final client-facing completion criteria. IMPLEMENTATION SAFETY Flag assumptions; favor native block controls over custom code; do not hardcode credentials or private data. For PHP/JS/CSS, provide exact location, activation scope, prerequisite checks, staging test, and undo method. If a plugin or version-specific behavior is uncertain, say what to verify first. Finish with a concise Definition of Done and a measurable business or UX outcome, without promising a result unsupported by data.
NAP consistency module
Create a tested, client-ready outcome for nap consistency module.
Act as a senior WordPress solution architect and Kadence Theme/Kadence Blocks/WPCode specialist. TASK: NAP consistency module. PROJECT INPUTS - Website type and business goal: [SITE TYPE + GOAL] - Audience, locale and key conversion: [AUDIENCE + LOCALE + CTA] - Current stack (WordPress/PHP, Kadence Theme, Kadence Blocks, WPCode, plugins): [VERIFIED VERSIONS] - Current page, screenshot, issue or reference: [URL OR SANITIZED DETAILS] - Constraints (budget, editor skill, hosting, launch date): [CONSTRAINTS] - Existing content, brand styles and approved data: [SOURCE MATERIAL] SPECIFIC OBJECTIVE Develop a practical, results-oriented solution for nap consistency module in the context of this website. Do not create doorway pages or invent local experience, addresses, ratings, or endorsements. Explain what should be done with Kadence Theme settings, what should be built with Kadence Blocks, and when WPCode is warranted. Do not invent installed plugin capabilities or pretend you accessed the live site. DELIVER EXACTLY 1. A task-specific implementation blueprint for “NAP consistency module” with exact WordPress/Kadence navigation or WPCode placement when relevant. 2. An ordered action checklist with dependencies and who owns each action. 3. Copy-ready artifacts where relevant (block hierarchy, settings matrix, sample copy, scoped CSS, PHP or vanilla JavaScript), with code fences and placement instructions. 4. Desktop/tablet/mobile acceptance tests, accessibility and security checks relevant to the task. 5. Failure cases, troubleshooting clues, rollback steps and final client-facing completion criteria. IMPLEMENTATION SAFETY Flag assumptions; favor native block controls over custom code; do not hardcode credentials or private data. For PHP/JS/CSS, provide exact location, activation scope, prerequisite checks, staging test, and undo method. If a plugin or version-specific behavior is uncertain, say what to verify first. Finish with a concise Definition of Done and a measurable business or UX outcome, without promising a result unsupported by data.
Local service CTA
Create a tested, client-ready outcome for local service cta.
Act as a senior WordPress solution architect and Kadence Theme/Kadence Blocks/WPCode specialist. TASK: Local service CTA. PROJECT INPUTS - Website type and business goal: [SITE TYPE + GOAL] - Audience, locale and key conversion: [AUDIENCE + LOCALE + CTA] - Current stack (WordPress/PHP, Kadence Theme, Kadence Blocks, WPCode, plugins): [VERIFIED VERSIONS] - Current page, screenshot, issue or reference: [URL OR SANITIZED DETAILS] - Constraints (budget, editor skill, hosting, launch date): [CONSTRAINTS] - Existing content, brand styles and approved data: [SOURCE MATERIAL] SPECIFIC OBJECTIVE Develop a practical, results-oriented solution for local service cta in the context of this website. Do not create doorway pages or invent local experience, addresses, ratings, or endorsements. Explain what should be done with Kadence Theme settings, what should be built with Kadence Blocks, and when WPCode is warranted. Do not invent installed plugin capabilities or pretend you accessed the live site. DELIVER EXACTLY 1. A task-specific implementation blueprint for “Local service CTA” with exact WordPress/Kadence navigation or WPCode placement when relevant. 2. An ordered action checklist with dependencies and who owns each action. 3. Copy-ready artifacts where relevant (block hierarchy, settings matrix, sample copy, scoped CSS, PHP or vanilla JavaScript), with code fences and placement instructions. 4. Desktop/tablet/mobile acceptance tests, accessibility and security checks relevant to the task. 5. Failure cases, troubleshooting clues, rollback steps and final client-facing completion criteria. IMPLEMENTATION SAFETY Flag assumptions; favor native block controls over custom code; do not hardcode credentials or private data. For PHP/JS/CSS, provide exact location, activation scope, prerequisite checks, staging test, and undo method. If a plugin or version-specific behavior is uncertain, say what to verify first. Finish with a concise Definition of Done and a measurable business or UX outcome, without promising a result unsupported by data.
Service plus city content brief
Create a tested, client-ready outcome for service plus city content brief.
Act as a senior WordPress solution architect and Kadence Theme/Kadence Blocks/WPCode specialist. TASK: Service plus city content brief. PROJECT INPUTS - Website type and business goal: [SITE TYPE + GOAL] - Audience, locale and key conversion: [AUDIENCE + LOCALE + CTA] - Current stack (WordPress/PHP, Kadence Theme, Kadence Blocks, WPCode, plugins): [VERIFIED VERSIONS] - Current page, screenshot, issue or reference: [URL OR SANITIZED DETAILS] - Constraints (budget, editor skill, hosting, launch date): [CONSTRAINTS] - Existing content, brand styles and approved data: [SOURCE MATERIAL] SPECIFIC OBJECTIVE Develop a practical, results-oriented solution for service plus city content brief in the context of this website. Do not create doorway pages or invent local experience, addresses, ratings, or endorsements. Explain what should be done with Kadence Theme settings, what should be built with Kadence Blocks, and when WPCode is warranted. Do not invent installed plugin capabilities or pretend you accessed the live site. DELIVER EXACTLY 1. A task-specific implementation blueprint for “Service plus city content brief” with exact WordPress/Kadence navigation or WPCode placement when relevant. 2. An ordered action checklist with dependencies and who owns each action. 3. Copy-ready artifacts where relevant (block hierarchy, settings matrix, sample copy, scoped CSS, PHP or vanilla JavaScript), with code fences and placement instructions. 4. Desktop/tablet/mobile acceptance tests, accessibility and security checks relevant to the task. 5. Failure cases, troubleshooting clues, rollback steps and final client-facing completion criteria. IMPLEMENTATION SAFETY Flag assumptions; favor native block controls over custom code; do not hardcode credentials or private data. For PHP/JS/CSS, provide exact location, activation scope, prerequisite checks, staging test, and undo method. If a plugin or version-specific behavior is uncertain, say what to verify first. Finish with a concise Definition of Done and a measurable business or UX outcome, without promising a result unsupported by data.
Location FAQ design
Create a tested, client-ready outcome for location faq design.
Act as a senior WordPress solution architect and Kadence Theme/Kadence Blocks/WPCode specialist. TASK: Location FAQ design. PROJECT INPUTS - Website type and business goal: [SITE TYPE + GOAL] - Audience, locale and key conversion: [AUDIENCE + LOCALE + CTA] - Current stack (WordPress/PHP, Kadence Theme, Kadence Blocks, WPCode, plugins): [VERIFIED VERSIONS] - Current page, screenshot, issue or reference: [URL OR SANITIZED DETAILS] - Constraints (budget, editor skill, hosting, launch date): [CONSTRAINTS] - Existing content, brand styles and approved data: [SOURCE MATERIAL] SPECIFIC OBJECTIVE Develop a practical, results-oriented solution for location faq design in the context of this website. Do not create doorway pages or invent local experience, addresses, ratings, or endorsements. Explain what should be done with Kadence Theme settings, what should be built with Kadence Blocks, and when WPCode is warranted. Do not invent installed plugin capabilities or pretend you accessed the live site. DELIVER EXACTLY 1. A task-specific implementation blueprint for “Location FAQ design” with exact WordPress/Kadence navigation or WPCode placement when relevant. 2. An ordered action checklist with dependencies and who owns each action. 3. Copy-ready artifacts where relevant (block hierarchy, settings matrix, sample copy, scoped CSS, PHP or vanilla JavaScript), with code fences and placement instructions. 4. Desktop/tablet/mobile acceptance tests, accessibility and security checks relevant to the task. 5. Failure cases, troubleshooting clues, rollback steps and final client-facing completion criteria. IMPLEMENTATION SAFETY Flag assumptions; favor native block controls over custom code; do not hardcode credentials or private data. For PHP/JS/CSS, provide exact location, activation scope, prerequisite checks, staging test, and undo method. If a plugin or version-specific behavior is uncertain, say what to verify first. Finish with a concise Definition of Done and a measurable business or UX outcome, without promising a result unsupported by data.
Contact and directions section
Create a tested, client-ready outcome for contact and directions section.
Act as a senior WordPress solution architect and Kadence Theme/Kadence Blocks/WPCode specialist. TASK: Contact and directions section. PROJECT INPUTS - Website type and business goal: [SITE TYPE + GOAL] - Audience, locale and key conversion: [AUDIENCE + LOCALE + CTA] - Current stack (WordPress/PHP, Kadence Theme, Kadence Blocks, WPCode, plugins): [VERIFIED VERSIONS] - Current page, screenshot, issue or reference: [URL OR SANITIZED DETAILS] - Constraints (budget, editor skill, hosting, launch date): [CONSTRAINTS] - Existing content, brand styles and approved data: [SOURCE MATERIAL] SPECIFIC OBJECTIVE Develop a practical, results-oriented solution for contact and directions section in the context of this website. Do not create doorway pages or invent local experience, addresses, ratings, or endorsements. Explain what should be done with Kadence Theme settings, what should be built with Kadence Blocks, and when WPCode is warranted. Do not invent installed plugin capabilities or pretend you accessed the live site. DELIVER EXACTLY 1. A task-specific implementation blueprint for “Contact and directions section” with exact WordPress/Kadence navigation or WPCode placement when relevant. 2. An ordered action checklist with dependencies and who owns each action. 3. Copy-ready artifacts where relevant (block hierarchy, settings matrix, sample copy, scoped CSS, PHP or vanilla JavaScript), with code fences and placement instructions. 4. Desktop/tablet/mobile acceptance tests, accessibility and security checks relevant to the task. 5. Failure cases, troubleshooting clues, rollback steps and final client-facing completion criteria. IMPLEMENTATION SAFETY Flag assumptions; favor native block controls over custom code; do not hardcode credentials or private data. For PHP/JS/CSS, provide exact location, activation scope, prerequisite checks, staging test, and undo method. If a plugin or version-specific behavior is uncertain, say what to verify first. Finish with a concise Definition of Done and a measurable business or UX outcome, without promising a result unsupported by data.
Review evidence presentation
Create a tested, client-ready outcome for review evidence presentation.
Act as a senior WordPress solution architect and Kadence Theme/Kadence Blocks/WPCode specialist. TASK: Review evidence presentation. PROJECT INPUTS - Website type and business goal: [SITE TYPE + GOAL] - Audience, locale and key conversion: [AUDIENCE + LOCALE + CTA] - Current stack (WordPress/PHP, Kadence Theme, Kadence Blocks, WPCode, plugins): [VERIFIED VERSIONS] - Current page, screenshot, issue or reference: [URL OR SANITIZED DETAILS] - Constraints (budget, editor skill, hosting, launch date): [CONSTRAINTS] - Existing content, brand styles and approved data: [SOURCE MATERIAL] SPECIFIC OBJECTIVE Develop a practical, results-oriented solution for review evidence presentation in the context of this website. Do not create doorway pages or invent local experience, addresses, ratings, or endorsements. Explain what should be done with Kadence Theme settings, what should be built with Kadence Blocks, and when WPCode is warranted. Do not invent installed plugin capabilities or pretend you accessed the live site. DELIVER EXACTLY 1. A task-specific implementation blueprint for “Review evidence presentation” with exact WordPress/Kadence navigation or WPCode placement when relevant. 2. An ordered action checklist with dependencies and who owns each action. 3. Copy-ready artifacts where relevant (block hierarchy, settings matrix, sample copy, scoped CSS, PHP or vanilla JavaScript), with code fences and placement instructions. 4. Desktop/tablet/mobile acceptance tests, accessibility and security checks relevant to the task. 5. Failure cases, troubleshooting clues, rollback steps and final client-facing completion criteria. IMPLEMENTATION SAFETY Flag assumptions; favor native block controls over custom code; do not hardcode credentials or private data. For PHP/JS/CSS, provide exact location, activation scope, prerequisite checks, staging test, and undo method. If a plugin or version-specific behavior is uncertain, say what to verify first. Finish with a concise Definition of Done and a measurable business or UX outcome, without promising a result unsupported by data.
Emergency service landing page
Create a tested, client-ready outcome for emergency service landing page.
Act as a senior WordPress solution architect and Kadence Theme/Kadence Blocks/WPCode specialist. TASK: Emergency service landing page. PROJECT INPUTS - Website type and business goal: [SITE TYPE + GOAL] - Audience, locale and key conversion: [AUDIENCE + LOCALE + CTA] - Current stack (WordPress/PHP, Kadence Theme, Kadence Blocks, WPCode, plugins): [VERIFIED VERSIONS] - Current page, screenshot, issue or reference: [URL OR SANITIZED DETAILS] - Constraints (budget, editor skill, hosting, launch date): [CONSTRAINTS] - Existing content, brand styles and approved data: [SOURCE MATERIAL] SPECIFIC OBJECTIVE Develop a practical, results-oriented solution for emergency service landing page in the context of this website. Do not create doorway pages or invent local experience, addresses, ratings, or endorsements. Explain what should be done with Kadence Theme settings, what should be built with Kadence Blocks, and when WPCode is warranted. Do not invent installed plugin capabilities or pretend you accessed the live site. DELIVER EXACTLY 1. A task-specific implementation blueprint for “Emergency service landing page” with exact WordPress/Kadence navigation or WPCode placement when relevant. 2. An ordered action checklist with dependencies and who owns each action. 3. Copy-ready artifacts where relevant (block hierarchy, settings matrix, sample copy, scoped CSS, PHP or vanilla JavaScript), with code fences and placement instructions. 4. Desktop/tablet/mobile acceptance tests, accessibility and security checks relevant to the task. 5. Failure cases, troubleshooting clues, rollback steps and final client-facing completion criteria. IMPLEMENTATION SAFETY Flag assumptions; favor native block controls over custom code; do not hardcode credentials or private data. For PHP/JS/CSS, provide exact location, activation scope, prerequisite checks, staging test, and undo method. If a plugin or version-specific behavior is uncertain, say what to verify first. Finish with a concise Definition of Done and a measurable business or UX outcome, without promising a result unsupported by data.
Multi-location navigation
Create a tested, client-ready outcome for multi-location navigation.
Act as a senior WordPress solution architect and Kadence Theme/Kadence Blocks/WPCode specialist. TASK: Multi-location navigation. PROJECT INPUTS - Website type and business goal: [SITE TYPE + GOAL] - Audience, locale and key conversion: [AUDIENCE + LOCALE + CTA] - Current stack (WordPress/PHP, Kadence Theme, Kadence Blocks, WPCode, plugins): [VERIFIED VERSIONS] - Current page, screenshot, issue or reference: [URL OR SANITIZED DETAILS] - Constraints (budget, editor skill, hosting, launch date): [CONSTRAINTS] - Existing content, brand styles and approved data: [SOURCE MATERIAL] SPECIFIC OBJECTIVE Develop a practical, results-oriented solution for multi-location navigation in the context of this website. Do not create doorway pages or invent local experience, addresses, ratings, or endorsements. Explain what should be done with Kadence Theme settings, what should be built with Kadence Blocks, and when WPCode is warranted. Do not invent installed plugin capabilities or pretend you accessed the live site. DELIVER EXACTLY 1. A task-specific implementation blueprint for “Multi-location navigation” with exact WordPress/Kadence navigation or WPCode placement when relevant. 2. An ordered action checklist with dependencies and who owns each action. 3. Copy-ready artifacts where relevant (block hierarchy, settings matrix, sample copy, scoped CSS, PHP or vanilla JavaScript), with code fences and placement instructions. 4. Desktop/tablet/mobile acceptance tests, accessibility and security checks relevant to the task. 5. Failure cases, troubleshooting clues, rollback steps and final client-facing completion criteria. IMPLEMENTATION SAFETY Flag assumptions; favor native block controls over custom code; do not hardcode credentials or private data. For PHP/JS/CSS, provide exact location, activation scope, prerequisite checks, staging test, and undo method. If a plugin or version-specific behavior is uncertain, say what to verify first. Finish with a concise Definition of Done and a measurable business or UX outcome, without promising a result unsupported by data.
07. Professional & B2B Websites
Consultant positioning page
Create a tested, client-ready outcome for consultant positioning page.
Act as a senior WordPress solution architect and Kadence Theme/Kadence Blocks/WPCode specialist. TASK: Consultant positioning page. PROJECT INPUTS - Website type and business goal: [SITE TYPE + GOAL] - Audience, locale and key conversion: [AUDIENCE + LOCALE + CTA] - Current stack (WordPress/PHP, Kadence Theme, Kadence Blocks, WPCode, plugins): [VERIFIED VERSIONS] - Current page, screenshot, issue or reference: [URL OR SANITIZED DETAILS] - Constraints (budget, editor skill, hosting, launch date): [CONSTRAINTS] - Existing content, brand styles and approved data: [SOURCE MATERIAL] SPECIFIC OBJECTIVE Develop a practical, results-oriented solution for consultant positioning page in the context of this website. Avoid unsupported professional or regulated-service claims and identify review-required wording. Explain what should be done with Kadence Theme settings, what should be built with Kadence Blocks, and when WPCode is warranted. Do not invent installed plugin capabilities or pretend you accessed the live site. DELIVER EXACTLY 1. A task-specific implementation blueprint for “Consultant positioning page” with exact WordPress/Kadence navigation or WPCode placement when relevant. 2. An ordered action checklist with dependencies and who owns each action. 3. Copy-ready artifacts where relevant (block hierarchy, settings matrix, sample copy, scoped CSS, PHP or vanilla JavaScript), with code fences and placement instructions. 4. Desktop/tablet/mobile acceptance tests, accessibility and security checks relevant to the task. 5. Failure cases, troubleshooting clues, rollback steps and final client-facing completion criteria. IMPLEMENTATION SAFETY Flag assumptions; favor native block controls over custom code; do not hardcode credentials or private data. For PHP/JS/CSS, provide exact location, activation scope, prerequisite checks, staging test, and undo method. If a plugin or version-specific behavior is uncertain, say what to verify first. Finish with a concise Definition of Done and a measurable business or UX outcome, without promising a result unsupported by data.
Agency service architecture
Create a tested, client-ready outcome for agency service architecture.
Act as a senior WordPress solution architect and Kadence Theme/Kadence Blocks/WPCode specialist. TASK: Agency service architecture. PROJECT INPUTS - Website type and business goal: [SITE TYPE + GOAL] - Audience, locale and key conversion: [AUDIENCE + LOCALE + CTA] - Current stack (WordPress/PHP, Kadence Theme, Kadence Blocks, WPCode, plugins): [VERIFIED VERSIONS] - Current page, screenshot, issue or reference: [URL OR SANITIZED DETAILS] - Constraints (budget, editor skill, hosting, launch date): [CONSTRAINTS] - Existing content, brand styles and approved data: [SOURCE MATERIAL] SPECIFIC OBJECTIVE Develop a practical, results-oriented solution for agency service architecture in the context of this website. Avoid unsupported professional or regulated-service claims and identify review-required wording. Explain what should be done with Kadence Theme settings, what should be built with Kadence Blocks, and when WPCode is warranted. Do not invent installed plugin capabilities or pretend you accessed the live site. DELIVER EXACTLY 1. A task-specific implementation blueprint for “Agency service architecture” with exact WordPress/Kadence navigation or WPCode placement when relevant. 2. An ordered action checklist with dependencies and who owns each action. 3. Copy-ready artifacts where relevant (block hierarchy, settings matrix, sample copy, scoped CSS, PHP or vanilla JavaScript), with code fences and placement instructions. 4. Desktop/tablet/mobile acceptance tests, accessibility and security checks relevant to the task. 5. Failure cases, troubleshooting clues, rollback steps and final client-facing completion criteria. IMPLEMENTATION SAFETY Flag assumptions; favor native block controls over custom code; do not hardcode credentials or private data. For PHP/JS/CSS, provide exact location, activation scope, prerequisite checks, staging test, and undo method. If a plugin or version-specific behavior is uncertain, say what to verify first. Finish with a concise Definition of Done and a measurable business or UX outcome, without promising a result unsupported by data.
Law firm informational structure
Create a tested, client-ready outcome for law firm informational structure.
Act as a senior WordPress solution architect and Kadence Theme/Kadence Blocks/WPCode specialist. TASK: Law firm informational structure. PROJECT INPUTS - Website type and business goal: [SITE TYPE + GOAL] - Audience, locale and key conversion: [AUDIENCE + LOCALE + CTA] - Current stack (WordPress/PHP, Kadence Theme, Kadence Blocks, WPCode, plugins): [VERIFIED VERSIONS] - Current page, screenshot, issue or reference: [URL OR SANITIZED DETAILS] - Constraints (budget, editor skill, hosting, launch date): [CONSTRAINTS] - Existing content, brand styles and approved data: [SOURCE MATERIAL] SPECIFIC OBJECTIVE Develop a practical, results-oriented solution for law firm informational structure in the context of this website. Avoid unsupported professional or regulated-service claims and identify review-required wording. Explain what should be done with Kadence Theme settings, what should be built with Kadence Blocks, and when WPCode is warranted. Do not invent installed plugin capabilities or pretend you accessed the live site. DELIVER EXACTLY 1. A task-specific implementation blueprint for “Law firm informational structure” with exact WordPress/Kadence navigation or WPCode placement when relevant. 2. An ordered action checklist with dependencies and who owns each action. 3. Copy-ready artifacts where relevant (block hierarchy, settings matrix, sample copy, scoped CSS, PHP or vanilla JavaScript), with code fences and placement instructions. 4. Desktop/tablet/mobile acceptance tests, accessibility and security checks relevant to the task. 5. Failure cases, troubleshooting clues, rollback steps and final client-facing completion criteria. IMPLEMENTATION SAFETY Flag assumptions; favor native block controls over custom code; do not hardcode credentials or private data. For PHP/JS/CSS, provide exact location, activation scope, prerequisite checks, staging test, and undo method. If a plugin or version-specific behavior is uncertain, say what to verify first. Finish with a concise Definition of Done and a measurable business or UX outcome, without promising a result unsupported by data.
Clinic site UX safeguards
Create a tested, client-ready outcome for clinic site ux safeguards.
Act as a senior WordPress solution architect and Kadence Theme/Kadence Blocks/WPCode specialist. TASK: Clinic site UX safeguards. PROJECT INPUTS - Website type and business goal: [SITE TYPE + GOAL] - Audience, locale and key conversion: [AUDIENCE + LOCALE + CTA] - Current stack (WordPress/PHP, Kadence Theme, Kadence Blocks, WPCode, plugins): [VERIFIED VERSIONS] - Current page, screenshot, issue or reference: [URL OR SANITIZED DETAILS] - Constraints (budget, editor skill, hosting, launch date): [CONSTRAINTS] - Existing content, brand styles and approved data: [SOURCE MATERIAL] SPECIFIC OBJECTIVE Develop a practical, results-oriented solution for clinic site ux safeguards in the context of this website. Avoid unsupported professional or regulated-service claims and identify review-required wording. Explain what should be done with Kadence Theme settings, what should be built with Kadence Blocks, and when WPCode is warranted. Do not invent installed plugin capabilities or pretend you accessed the live site. DELIVER EXACTLY 1. A task-specific implementation blueprint for “Clinic site UX safeguards” with exact WordPress/Kadence navigation or WPCode placement when relevant. 2. An ordered action checklist with dependencies and who owns each action. 3. Copy-ready artifacts where relevant (block hierarchy, settings matrix, sample copy, scoped CSS, PHP or vanilla JavaScript), with code fences and placement instructions. 4. Desktop/tablet/mobile acceptance tests, accessibility and security checks relevant to the task. 5. Failure cases, troubleshooting clues, rollback steps and final client-facing completion criteria. IMPLEMENTATION SAFETY Flag assumptions; favor native block controls over custom code; do not hardcode credentials or private data. For PHP/JS/CSS, provide exact location, activation scope, prerequisite checks, staging test, and undo method. If a plugin or version-specific behavior is uncertain, say what to verify first. Finish with a concise Definition of Done and a measurable business or UX outcome, without promising a result unsupported by data.
Accounting firm trust layout
Create a tested, client-ready outcome for accounting firm trust layout.
Act as a senior WordPress solution architect and Kadence Theme/Kadence Blocks/WPCode specialist. TASK: Accounting firm trust layout. PROJECT INPUTS - Website type and business goal: [SITE TYPE + GOAL] - Audience, locale and key conversion: [AUDIENCE + LOCALE + CTA] - Current stack (WordPress/PHP, Kadence Theme, Kadence Blocks, WPCode, plugins): [VERIFIED VERSIONS] - Current page, screenshot, issue or reference: [URL OR SANITIZED DETAILS] - Constraints (budget, editor skill, hosting, launch date): [CONSTRAINTS] - Existing content, brand styles and approved data: [SOURCE MATERIAL] SPECIFIC OBJECTIVE Develop a practical, results-oriented solution for accounting firm trust layout in the context of this website. Avoid unsupported professional or regulated-service claims and identify review-required wording. Explain what should be done with Kadence Theme settings, what should be built with Kadence Blocks, and when WPCode is warranted. Do not invent installed plugin capabilities or pretend you accessed the live site. DELIVER EXACTLY 1. A task-specific implementation blueprint for “Accounting firm trust layout” with exact WordPress/Kadence navigation or WPCode placement when relevant. 2. An ordered action checklist with dependencies and who owns each action. 3. Copy-ready artifacts where relevant (block hierarchy, settings matrix, sample copy, scoped CSS, PHP or vanilla JavaScript), with code fences and placement instructions. 4. Desktop/tablet/mobile acceptance tests, accessibility and security checks relevant to the task. 5. Failure cases, troubleshooting clues, rollback steps and final client-facing completion criteria. IMPLEMENTATION SAFETY Flag assumptions; favor native block controls over custom code; do not hardcode credentials or private data. For PHP/JS/CSS, provide exact location, activation scope, prerequisite checks, staging test, and undo method. If a plugin or version-specific behavior is uncertain, say what to verify first. Finish with a concise Definition of Done and a measurable business or UX outcome, without promising a result unsupported by data.
Portfolio case study template
Create a tested, client-ready outcome for portfolio case study template.
Act as a senior WordPress solution architect and Kadence Theme/Kadence Blocks/WPCode specialist. TASK: Portfolio case study template. PROJECT INPUTS - Website type and business goal: [SITE TYPE + GOAL] - Audience, locale and key conversion: [AUDIENCE + LOCALE + CTA] - Current stack (WordPress/PHP, Kadence Theme, Kadence Blocks, WPCode, plugins): [VERIFIED VERSIONS] - Current page, screenshot, issue or reference: [URL OR SANITIZED DETAILS] - Constraints (budget, editor skill, hosting, launch date): [CONSTRAINTS] - Existing content, brand styles and approved data: [SOURCE MATERIAL] SPECIFIC OBJECTIVE Develop a practical, results-oriented solution for portfolio case study template in the context of this website. Avoid unsupported professional or regulated-service claims and identify review-required wording. Explain what should be done with Kadence Theme settings, what should be built with Kadence Blocks, and when WPCode is warranted. Do not invent installed plugin capabilities or pretend you accessed the live site. DELIVER EXACTLY 1. A task-specific implementation blueprint for “Portfolio case study template” with exact WordPress/Kadence navigation or WPCode placement when relevant. 2. An ordered action checklist with dependencies and who owns each action. 3. Copy-ready artifacts where relevant (block hierarchy, settings matrix, sample copy, scoped CSS, PHP or vanilla JavaScript), with code fences and placement instructions. 4. Desktop/tablet/mobile acceptance tests, accessibility and security checks relevant to the task. 5. Failure cases, troubleshooting clues, rollback steps and final client-facing completion criteria. IMPLEMENTATION SAFETY Flag assumptions; favor native block controls over custom code; do not hardcode credentials or private data. For PHP/JS/CSS, provide exact location, activation scope, prerequisite checks, staging test, and undo method. If a plugin or version-specific behavior is uncertain, say what to verify first. Finish with a concise Definition of Done and a measurable business or UX outcome, without promising a result unsupported by data.
Book a consultation funnel
Create a tested, client-ready outcome for book a consultation funnel.
Act as a senior WordPress solution architect and Kadence Theme/Kadence Blocks/WPCode specialist. TASK: Book a consultation funnel. PROJECT INPUTS - Website type and business goal: [SITE TYPE + GOAL] - Audience, locale and key conversion: [AUDIENCE + LOCALE + CTA] - Current stack (WordPress/PHP, Kadence Theme, Kadence Blocks, WPCode, plugins): [VERIFIED VERSIONS] - Current page, screenshot, issue or reference: [URL OR SANITIZED DETAILS] - Constraints (budget, editor skill, hosting, launch date): [CONSTRAINTS] - Existing content, brand styles and approved data: [SOURCE MATERIAL] SPECIFIC OBJECTIVE Develop a practical, results-oriented solution for book a consultation funnel in the context of this website. Avoid unsupported professional or regulated-service claims and identify review-required wording. Explain what should be done with Kadence Theme settings, what should be built with Kadence Blocks, and when WPCode is warranted. Do not invent installed plugin capabilities or pretend you accessed the live site. DELIVER EXACTLY 1. A task-specific implementation blueprint for “Book a consultation funnel” with exact WordPress/Kadence navigation or WPCode placement when relevant. 2. An ordered action checklist with dependencies and who owns each action. 3. Copy-ready artifacts where relevant (block hierarchy, settings matrix, sample copy, scoped CSS, PHP or vanilla JavaScript), with code fences and placement instructions. 4. Desktop/tablet/mobile acceptance tests, accessibility and security checks relevant to the task. 5. Failure cases, troubleshooting clues, rollback steps and final client-facing completion criteria. IMPLEMENTATION SAFETY Flag assumptions; favor native block controls over custom code; do not hardcode credentials or private data. For PHP/JS/CSS, provide exact location, activation scope, prerequisite checks, staging test, and undo method. If a plugin or version-specific behavior is uncertain, say what to verify first. Finish with a concise Definition of Done and a measurable business or UX outcome, without promising a result unsupported by data.
Team bio component
Create a tested, client-ready outcome for team bio component.
Act as a senior WordPress solution architect and Kadence Theme/Kadence Blocks/WPCode specialist. TASK: Team bio component. PROJECT INPUTS - Website type and business goal: [SITE TYPE + GOAL] - Audience, locale and key conversion: [AUDIENCE + LOCALE + CTA] - Current stack (WordPress/PHP, Kadence Theme, Kadence Blocks, WPCode, plugins): [VERIFIED VERSIONS] - Current page, screenshot, issue or reference: [URL OR SANITIZED DETAILS] - Constraints (budget, editor skill, hosting, launch date): [CONSTRAINTS] - Existing content, brand styles and approved data: [SOURCE MATERIAL] SPECIFIC OBJECTIVE Develop a practical, results-oriented solution for team bio component in the context of this website. Avoid unsupported professional or regulated-service claims and identify review-required wording. Explain what should be done with Kadence Theme settings, what should be built with Kadence Blocks, and when WPCode is warranted. Do not invent installed plugin capabilities or pretend you accessed the live site. DELIVER EXACTLY 1. A task-specific implementation blueprint for “Team bio component” with exact WordPress/Kadence navigation or WPCode placement when relevant. 2. An ordered action checklist with dependencies and who owns each action. 3. Copy-ready artifacts where relevant (block hierarchy, settings matrix, sample copy, scoped CSS, PHP or vanilla JavaScript), with code fences and placement instructions. 4. Desktop/tablet/mobile acceptance tests, accessibility and security checks relevant to the task. 5. Failure cases, troubleshooting clues, rollback steps and final client-facing completion criteria. IMPLEMENTATION SAFETY Flag assumptions; favor native block controls over custom code; do not hardcode credentials or private data. For PHP/JS/CSS, provide exact location, activation scope, prerequisite checks, staging test, and undo method. If a plugin or version-specific behavior is uncertain, say what to verify first. Finish with a concise Definition of Done and a measurable business or UX outcome, without promising a result unsupported by data.
Resources center taxonomy
Create a tested, client-ready outcome for resources center taxonomy.
Act as a senior WordPress solution architect and Kadence Theme/Kadence Blocks/WPCode specialist. TASK: Resources center taxonomy. PROJECT INPUTS - Website type and business goal: [SITE TYPE + GOAL] - Audience, locale and key conversion: [AUDIENCE + LOCALE + CTA] - Current stack (WordPress/PHP, Kadence Theme, Kadence Blocks, WPCode, plugins): [VERIFIED VERSIONS] - Current page, screenshot, issue or reference: [URL OR SANITIZED DETAILS] - Constraints (budget, editor skill, hosting, launch date): [CONSTRAINTS] - Existing content, brand styles and approved data: [SOURCE MATERIAL] SPECIFIC OBJECTIVE Develop a practical, results-oriented solution for resources center taxonomy in the context of this website. Avoid unsupported professional or regulated-service claims and identify review-required wording. Explain what should be done with Kadence Theme settings, what should be built with Kadence Blocks, and when WPCode is warranted. Do not invent installed plugin capabilities or pretend you accessed the live site. DELIVER EXACTLY 1. A task-specific implementation blueprint for “Resources center taxonomy” with exact WordPress/Kadence navigation or WPCode placement when relevant. 2. An ordered action checklist with dependencies and who owns each action. 3. Copy-ready artifacts where relevant (block hierarchy, settings matrix, sample copy, scoped CSS, PHP or vanilla JavaScript), with code fences and placement instructions. 4. Desktop/tablet/mobile acceptance tests, accessibility and security checks relevant to the task. 5. Failure cases, troubleshooting clues, rollback steps and final client-facing completion criteria. IMPLEMENTATION SAFETY Flag assumptions; favor native block controls over custom code; do not hardcode credentials or private data. For PHP/JS/CSS, provide exact location, activation scope, prerequisite checks, staging test, and undo method. If a plugin or version-specific behavior is uncertain, say what to verify first. Finish with a concise Definition of Done and a measurable business or UX outcome, without promising a result unsupported by data.
B2B lead qualification page
Create a tested, client-ready outcome for b2b lead qualification page.
Act as a senior WordPress solution architect and Kadence Theme/Kadence Blocks/WPCode specialist. TASK: B2B lead qualification page. PROJECT INPUTS - Website type and business goal: [SITE TYPE + GOAL] - Audience, locale and key conversion: [AUDIENCE + LOCALE + CTA] - Current stack (WordPress/PHP, Kadence Theme, Kadence Blocks, WPCode, plugins): [VERIFIED VERSIONS] - Current page, screenshot, issue or reference: [URL OR SANITIZED DETAILS] - Constraints (budget, editor skill, hosting, launch date): [CONSTRAINTS] - Existing content, brand styles and approved data: [SOURCE MATERIAL] SPECIFIC OBJECTIVE Develop a practical, results-oriented solution for b2b lead qualification page in the context of this website. Avoid unsupported professional or regulated-service claims and identify review-required wording. Explain what should be done with Kadence Theme settings, what should be built with Kadence Blocks, and when WPCode is warranted. Do not invent installed plugin capabilities or pretend you accessed the live site. DELIVER EXACTLY 1. A task-specific implementation blueprint for “B2B lead qualification page” with exact WordPress/Kadence navigation or WPCode placement when relevant. 2. An ordered action checklist with dependencies and who owns each action. 3. Copy-ready artifacts where relevant (block hierarchy, settings matrix, sample copy, scoped CSS, PHP or vanilla JavaScript), with code fences and placement instructions. 4. Desktop/tablet/mobile acceptance tests, accessibility and security checks relevant to the task. 5. Failure cases, troubleshooting clues, rollback steps and final client-facing completion criteria. IMPLEMENTATION SAFETY Flag assumptions; favor native block controls over custom code; do not hardcode credentials or private data. For PHP/JS/CSS, provide exact location, activation scope, prerequisite checks, staging test, and undo method. If a plugin or version-specific behavior is uncertain, say what to verify first. Finish with a concise Definition of Done and a measurable business or UX outcome, without promising a result unsupported by data.
08. Blogs, Publishers & Education
Editorial taxonomy map
Create a tested, client-ready outcome for editorial taxonomy map.
Act as a senior WordPress solution architect and Kadence Theme/Kadence Blocks/WPCode specialist. TASK: Editorial taxonomy map. PROJECT INPUTS - Website type and business goal: [SITE TYPE + GOAL] - Audience, locale and key conversion: [AUDIENCE + LOCALE + CTA] - Current stack (WordPress/PHP, Kadence Theme, Kadence Blocks, WPCode, plugins): [VERIFIED VERSIONS] - Current page, screenshot, issue or reference: [URL OR SANITIZED DETAILS] - Constraints (budget, editor skill, hosting, launch date): [CONSTRAINTS] - Existing content, brand styles and approved data: [SOURCE MATERIAL] SPECIFIC OBJECTIVE Develop a practical, results-oriented solution for editorial taxonomy map in the context of this website. Separate editorial content from presentation and include source-checking steps. Explain what should be done with Kadence Theme settings, what should be built with Kadence Blocks, and when WPCode is warranted. Do not invent installed plugin capabilities or pretend you accessed the live site. DELIVER EXACTLY 1. A task-specific implementation blueprint for “Editorial taxonomy map” with exact WordPress/Kadence navigation or WPCode placement when relevant. 2. An ordered action checklist with dependencies and who owns each action. 3. Copy-ready artifacts where relevant (block hierarchy, settings matrix, sample copy, scoped CSS, PHP or vanilla JavaScript), with code fences and placement instructions. 4. Desktop/tablet/mobile acceptance tests, accessibility and security checks relevant to the task. 5. Failure cases, troubleshooting clues, rollback steps and final client-facing completion criteria. IMPLEMENTATION SAFETY Flag assumptions; favor native block controls over custom code; do not hardcode credentials or private data. For PHP/JS/CSS, provide exact location, activation scope, prerequisite checks, staging test, and undo method. If a plugin or version-specific behavior is uncertain, say what to verify first. Finish with a concise Definition of Done and a measurable business or UX outcome, without promising a result unsupported by data.
Archive layout design
Create a tested, client-ready outcome for archive layout design.
Act as a senior WordPress solution architect and Kadence Theme/Kadence Blocks/WPCode specialist. TASK: Archive layout design. PROJECT INPUTS - Website type and business goal: [SITE TYPE + GOAL] - Audience, locale and key conversion: [AUDIENCE + LOCALE + CTA] - Current stack (WordPress/PHP, Kadence Theme, Kadence Blocks, WPCode, plugins): [VERIFIED VERSIONS] - Current page, screenshot, issue or reference: [URL OR SANITIZED DETAILS] - Constraints (budget, editor skill, hosting, launch date): [CONSTRAINTS] - Existing content, brand styles and approved data: [SOURCE MATERIAL] SPECIFIC OBJECTIVE Develop a practical, results-oriented solution for archive layout design in the context of this website. Separate editorial content from presentation and include source-checking steps. Explain what should be done with Kadence Theme settings, what should be built with Kadence Blocks, and when WPCode is warranted. Do not invent installed plugin capabilities or pretend you accessed the live site. DELIVER EXACTLY 1. A task-specific implementation blueprint for “Archive layout design” with exact WordPress/Kadence navigation or WPCode placement when relevant. 2. An ordered action checklist with dependencies and who owns each action. 3. Copy-ready artifacts where relevant (block hierarchy, settings matrix, sample copy, scoped CSS, PHP or vanilla JavaScript), with code fences and placement instructions. 4. Desktop/tablet/mobile acceptance tests, accessibility and security checks relevant to the task. 5. Failure cases, troubleshooting clues, rollback steps and final client-facing completion criteria. IMPLEMENTATION SAFETY Flag assumptions; favor native block controls over custom code; do not hardcode credentials or private data. For PHP/JS/CSS, provide exact location, activation scope, prerequisite checks, staging test, and undo method. If a plugin or version-specific behavior is uncertain, say what to verify first. Finish with a concise Definition of Done and a measurable business or UX outcome, without promising a result unsupported by data.
Single post readability
Create a tested, client-ready outcome for single post readability.
Act as a senior WordPress solution architect and Kadence Theme/Kadence Blocks/WPCode specialist. TASK: Single post readability. PROJECT INPUTS - Website type and business goal: [SITE TYPE + GOAL] - Audience, locale and key conversion: [AUDIENCE + LOCALE + CTA] - Current stack (WordPress/PHP, Kadence Theme, Kadence Blocks, WPCode, plugins): [VERIFIED VERSIONS] - Current page, screenshot, issue or reference: [URL OR SANITIZED DETAILS] - Constraints (budget, editor skill, hosting, launch date): [CONSTRAINTS] - Existing content, brand styles and approved data: [SOURCE MATERIAL] SPECIFIC OBJECTIVE Develop a practical, results-oriented solution for single post readability in the context of this website. Separate editorial content from presentation and include source-checking steps. Explain what should be done with Kadence Theme settings, what should be built with Kadence Blocks, and when WPCode is warranted. Do not invent installed plugin capabilities or pretend you accessed the live site. DELIVER EXACTLY 1. A task-specific implementation blueprint for “Single post readability” with exact WordPress/Kadence navigation or WPCode placement when relevant. 2. An ordered action checklist with dependencies and who owns each action. 3. Copy-ready artifacts where relevant (block hierarchy, settings matrix, sample copy, scoped CSS, PHP or vanilla JavaScript), with code fences and placement instructions. 4. Desktop/tablet/mobile acceptance tests, accessibility and security checks relevant to the task. 5. Failure cases, troubleshooting clues, rollback steps and final client-facing completion criteria. IMPLEMENTATION SAFETY Flag assumptions; favor native block controls over custom code; do not hardcode credentials or private data. For PHP/JS/CSS, provide exact location, activation scope, prerequisite checks, staging test, and undo method. If a plugin or version-specific behavior is uncertain, say what to verify first. Finish with a concise Definition of Done and a measurable business or UX outcome, without promising a result unsupported by data.
Table of contents pattern
Create a tested, client-ready outcome for table of contents pattern.
Act as a senior WordPress solution architect and Kadence Theme/Kadence Blocks/WPCode specialist. TASK: Table of contents pattern. PROJECT INPUTS - Website type and business goal: [SITE TYPE + GOAL] - Audience, locale and key conversion: [AUDIENCE + LOCALE + CTA] - Current stack (WordPress/PHP, Kadence Theme, Kadence Blocks, WPCode, plugins): [VERIFIED VERSIONS] - Current page, screenshot, issue or reference: [URL OR SANITIZED DETAILS] - Constraints (budget, editor skill, hosting, launch date): [CONSTRAINTS] - Existing content, brand styles and approved data: [SOURCE MATERIAL] SPECIFIC OBJECTIVE Develop a practical, results-oriented solution for table of contents pattern in the context of this website. Separate editorial content from presentation and include source-checking steps. Explain what should be done with Kadence Theme settings, what should be built with Kadence Blocks, and when WPCode is warranted. Do not invent installed plugin capabilities or pretend you accessed the live site. DELIVER EXACTLY 1. A task-specific implementation blueprint for “Table of contents pattern” with exact WordPress/Kadence navigation or WPCode placement when relevant. 2. An ordered action checklist with dependencies and who owns each action. 3. Copy-ready artifacts where relevant (block hierarchy, settings matrix, sample copy, scoped CSS, PHP or vanilla JavaScript), with code fences and placement instructions. 4. Desktop/tablet/mobile acceptance tests, accessibility and security checks relevant to the task. 5. Failure cases, troubleshooting clues, rollback steps and final client-facing completion criteria. IMPLEMENTATION SAFETY Flag assumptions; favor native block controls over custom code; do not hardcode credentials or private data. For PHP/JS/CSS, provide exact location, activation scope, prerequisite checks, staging test, and undo method. If a plugin or version-specific behavior is uncertain, say what to verify first. Finish with a concise Definition of Done and a measurable business or UX outcome, without promising a result unsupported by data.
Author expertise box
Create a tested, client-ready outcome for author expertise box.
Act as a senior WordPress solution architect and Kadence Theme/Kadence Blocks/WPCode specialist. TASK: Author expertise box. PROJECT INPUTS - Website type and business goal: [SITE TYPE + GOAL] - Audience, locale and key conversion: [AUDIENCE + LOCALE + CTA] - Current stack (WordPress/PHP, Kadence Theme, Kadence Blocks, WPCode, plugins): [VERIFIED VERSIONS] - Current page, screenshot, issue or reference: [URL OR SANITIZED DETAILS] - Constraints (budget, editor skill, hosting, launch date): [CONSTRAINTS] - Existing content, brand styles and approved data: [SOURCE MATERIAL] SPECIFIC OBJECTIVE Develop a practical, results-oriented solution for author expertise box in the context of this website. Separate editorial content from presentation and include source-checking steps. Explain what should be done with Kadence Theme settings, what should be built with Kadence Blocks, and when WPCode is warranted. Do not invent installed plugin capabilities or pretend you accessed the live site. DELIVER EXACTLY 1. A task-specific implementation blueprint for “Author expertise box” with exact WordPress/Kadence navigation or WPCode placement when relevant. 2. An ordered action checklist with dependencies and who owns each action. 3. Copy-ready artifacts where relevant (block hierarchy, settings matrix, sample copy, scoped CSS, PHP or vanilla JavaScript), with code fences and placement instructions. 4. Desktop/tablet/mobile acceptance tests, accessibility and security checks relevant to the task. 5. Failure cases, troubleshooting clues, rollback steps and final client-facing completion criteria. IMPLEMENTATION SAFETY Flag assumptions; favor native block controls over custom code; do not hardcode credentials or private data. For PHP/JS/CSS, provide exact location, activation scope, prerequisite checks, staging test, and undo method. If a plugin or version-specific behavior is uncertain, say what to verify first. Finish with a concise Definition of Done and a measurable business or UX outcome, without promising a result unsupported by data.
Related posts logic
Create a tested, client-ready outcome for related posts logic.
Act as a senior WordPress solution architect and Kadence Theme/Kadence Blocks/WPCode specialist. TASK: Related posts logic. PROJECT INPUTS - Website type and business goal: [SITE TYPE + GOAL] - Audience, locale and key conversion: [AUDIENCE + LOCALE + CTA] - Current stack (WordPress/PHP, Kadence Theme, Kadence Blocks, WPCode, plugins): [VERIFIED VERSIONS] - Current page, screenshot, issue or reference: [URL OR SANITIZED DETAILS] - Constraints (budget, editor skill, hosting, launch date): [CONSTRAINTS] - Existing content, brand styles and approved data: [SOURCE MATERIAL] SPECIFIC OBJECTIVE Develop a practical, results-oriented solution for related posts logic in the context of this website. Separate editorial content from presentation and include source-checking steps. Explain what should be done with Kadence Theme settings, what should be built with Kadence Blocks, and when WPCode is warranted. Do not invent installed plugin capabilities or pretend you accessed the live site. DELIVER EXACTLY 1. A task-specific implementation blueprint for “Related posts logic” with exact WordPress/Kadence navigation or WPCode placement when relevant. 2. An ordered action checklist with dependencies and who owns each action. 3. Copy-ready artifacts where relevant (block hierarchy, settings matrix, sample copy, scoped CSS, PHP or vanilla JavaScript), with code fences and placement instructions. 4. Desktop/tablet/mobile acceptance tests, accessibility and security checks relevant to the task. 5. Failure cases, troubleshooting clues, rollback steps and final client-facing completion criteria. IMPLEMENTATION SAFETY Flag assumptions; favor native block controls over custom code; do not hardcode credentials or private data. For PHP/JS/CSS, provide exact location, activation scope, prerequisite checks, staging test, and undo method. If a plugin or version-specific behavior is uncertain, say what to verify first. Finish with a concise Definition of Done and a measurable business or UX outcome, without promising a result unsupported by data.
Course overview layout
Create a tested, client-ready outcome for course overview layout.
Act as a senior WordPress solution architect and Kadence Theme/Kadence Blocks/WPCode specialist. TASK: Course overview layout. PROJECT INPUTS - Website type and business goal: [SITE TYPE + GOAL] - Audience, locale and key conversion: [AUDIENCE + LOCALE + CTA] - Current stack (WordPress/PHP, Kadence Theme, Kadence Blocks, WPCode, plugins): [VERIFIED VERSIONS] - Current page, screenshot, issue or reference: [URL OR SANITIZED DETAILS] - Constraints (budget, editor skill, hosting, launch date): [CONSTRAINTS] - Existing content, brand styles and approved data: [SOURCE MATERIAL] SPECIFIC OBJECTIVE Develop a practical, results-oriented solution for course overview layout in the context of this website. Separate editorial content from presentation and include source-checking steps. Explain what should be done with Kadence Theme settings, what should be built with Kadence Blocks, and when WPCode is warranted. Do not invent installed plugin capabilities or pretend you accessed the live site. DELIVER EXACTLY 1. A task-specific implementation blueprint for “Course overview layout” with exact WordPress/Kadence navigation or WPCode placement when relevant. 2. An ordered action checklist with dependencies and who owns each action. 3. Copy-ready artifacts where relevant (block hierarchy, settings matrix, sample copy, scoped CSS, PHP or vanilla JavaScript), with code fences and placement instructions. 4. Desktop/tablet/mobile acceptance tests, accessibility and security checks relevant to the task. 5. Failure cases, troubleshooting clues, rollback steps and final client-facing completion criteria. IMPLEMENTATION SAFETY Flag assumptions; favor native block controls over custom code; do not hardcode credentials or private data. For PHP/JS/CSS, provide exact location, activation scope, prerequisite checks, staging test, and undo method. If a plugin or version-specific behavior is uncertain, say what to verify first. Finish with a concise Definition of Done and a measurable business or UX outcome, without promising a result unsupported by data.
Resource download library
Create a tested, client-ready outcome for resource download library.
Act as a senior WordPress solution architect and Kadence Theme/Kadence Blocks/WPCode specialist. TASK: Resource download library. PROJECT INPUTS - Website type and business goal: [SITE TYPE + GOAL] - Audience, locale and key conversion: [AUDIENCE + LOCALE + CTA] - Current stack (WordPress/PHP, Kadence Theme, Kadence Blocks, WPCode, plugins): [VERIFIED VERSIONS] - Current page, screenshot, issue or reference: [URL OR SANITIZED DETAILS] - Constraints (budget, editor skill, hosting, launch date): [CONSTRAINTS] - Existing content, brand styles and approved data: [SOURCE MATERIAL] SPECIFIC OBJECTIVE Develop a practical, results-oriented solution for resource download library in the context of this website. Separate editorial content from presentation and include source-checking steps. Explain what should be done with Kadence Theme settings, what should be built with Kadence Blocks, and when WPCode is warranted. Do not invent installed plugin capabilities or pretend you accessed the live site. DELIVER EXACTLY 1. A task-specific implementation blueprint for “Resource download library” with exact WordPress/Kadence navigation or WPCode placement when relevant. 2. An ordered action checklist with dependencies and who owns each action. 3. Copy-ready artifacts where relevant (block hierarchy, settings matrix, sample copy, scoped CSS, PHP or vanilla JavaScript), with code fences and placement instructions. 4. Desktop/tablet/mobile acceptance tests, accessibility and security checks relevant to the task. 5. Failure cases, troubleshooting clues, rollback steps and final client-facing completion criteria. IMPLEMENTATION SAFETY Flag assumptions; favor native block controls over custom code; do not hardcode credentials or private data. For PHP/JS/CSS, provide exact location, activation scope, prerequisite checks, staging test, and undo method. If a plugin or version-specific behavior is uncertain, say what to verify first. Finish with a concise Definition of Done and a measurable business or UX outcome, without promising a result unsupported by data.
Editorial content workflow
Create a tested, client-ready outcome for editorial content workflow.
Act as a senior WordPress solution architect and Kadence Theme/Kadence Blocks/WPCode specialist. TASK: Editorial content workflow. PROJECT INPUTS - Website type and business goal: [SITE TYPE + GOAL] - Audience, locale and key conversion: [AUDIENCE + LOCALE + CTA] - Current stack (WordPress/PHP, Kadence Theme, Kadence Blocks, WPCode, plugins): [VERIFIED VERSIONS] - Current page, screenshot, issue or reference: [URL OR SANITIZED DETAILS] - Constraints (budget, editor skill, hosting, launch date): [CONSTRAINTS] - Existing content, brand styles and approved data: [SOURCE MATERIAL] SPECIFIC OBJECTIVE Develop a practical, results-oriented solution for editorial content workflow in the context of this website. Separate editorial content from presentation and include source-checking steps. Explain what should be done with Kadence Theme settings, what should be built with Kadence Blocks, and when WPCode is warranted. Do not invent installed plugin capabilities or pretend you accessed the live site. DELIVER EXACTLY 1. A task-specific implementation blueprint for “Editorial content workflow” with exact WordPress/Kadence navigation or WPCode placement when relevant. 2. An ordered action checklist with dependencies and who owns each action. 3. Copy-ready artifacts where relevant (block hierarchy, settings matrix, sample copy, scoped CSS, PHP or vanilla JavaScript), with code fences and placement instructions. 4. Desktop/tablet/mobile acceptance tests, accessibility and security checks relevant to the task. 5. Failure cases, troubleshooting clues, rollback steps and final client-facing completion criteria. IMPLEMENTATION SAFETY Flag assumptions; favor native block controls over custom code; do not hardcode credentials or private data. For PHP/JS/CSS, provide exact location, activation scope, prerequisite checks, staging test, and undo method. If a plugin or version-specific behavior is uncertain, say what to verify first. Finish with a concise Definition of Done and a measurable business or UX outcome, without promising a result unsupported by data.
Search and filter specification
Create a tested, client-ready outcome for search and filter specification.
Act as a senior WordPress solution architect and Kadence Theme/Kadence Blocks/WPCode specialist. TASK: Search and filter specification. PROJECT INPUTS - Website type and business goal: [SITE TYPE + GOAL] - Audience, locale and key conversion: [AUDIENCE + LOCALE + CTA] - Current stack (WordPress/PHP, Kadence Theme, Kadence Blocks, WPCode, plugins): [VERIFIED VERSIONS] - Current page, screenshot, issue or reference: [URL OR SANITIZED DETAILS] - Constraints (budget, editor skill, hosting, launch date): [CONSTRAINTS] - Existing content, brand styles and approved data: [SOURCE MATERIAL] SPECIFIC OBJECTIVE Develop a practical, results-oriented solution for search and filter specification in the context of this website. Separate editorial content from presentation and include source-checking steps. Explain what should be done with Kadence Theme settings, what should be built with Kadence Blocks, and when WPCode is warranted. Do not invent installed plugin capabilities or pretend you accessed the live site. DELIVER EXACTLY 1. A task-specific implementation blueprint for “Search and filter specification” with exact WordPress/Kadence navigation or WPCode placement when relevant. 2. An ordered action checklist with dependencies and who owns each action. 3. Copy-ready artifacts where relevant (block hierarchy, settings matrix, sample copy, scoped CSS, PHP or vanilla JavaScript), with code fences and placement instructions. 4. Desktop/tablet/mobile acceptance tests, accessibility and security checks relevant to the task. 5. Failure cases, troubleshooting clues, rollback steps and final client-facing completion criteria. IMPLEMENTATION SAFETY Flag assumptions; favor native block controls over custom code; do not hardcode credentials or private data. For PHP/JS/CSS, provide exact location, activation scope, prerequisite checks, staging test, and undo method. If a plugin or version-specific behavior is uncertain, say what to verify first. Finish with a concise Definition of Done and a measurable business or UX outcome, without promising a result unsupported by data.
09. WooCommerce Storefronts
Shop category architecture
Create a tested, client-ready outcome for shop category architecture.
Act as a senior WordPress solution architect and Kadence Theme/Kadence Blocks/WPCode specialist. TASK: Shop category architecture. PROJECT INPUTS - Website type and business goal: [SITE TYPE + GOAL] - Audience, locale and key conversion: [AUDIENCE + LOCALE + CTA] - Current stack (WordPress/PHP, Kadence Theme, Kadence Blocks, WPCode, plugins): [VERIFIED VERSIONS] - Current page, screenshot, issue or reference: [URL OR SANITIZED DETAILS] - Constraints (budget, editor skill, hosting, launch date): [CONSTRAINTS] - Existing content, brand styles and approved data: [SOURCE MATERIAL] SPECIFIC OBJECTIVE Develop a practical, results-oriented solution for shop category architecture in the context of this website. Respect store pricing, stock, tax, payment and shipping facts; never fabricate social proof. Explain what should be done with Kadence Theme settings, what should be built with Kadence Blocks, and when WPCode is warranted. Do not invent installed plugin capabilities or pretend you accessed the live site. DELIVER EXACTLY 1. A task-specific implementation blueprint for “Shop category architecture” with exact WordPress/Kadence navigation or WPCode placement when relevant. 2. An ordered action checklist with dependencies and who owns each action. 3. Copy-ready artifacts where relevant (block hierarchy, settings matrix, sample copy, scoped CSS, PHP or vanilla JavaScript), with code fences and placement instructions. 4. Desktop/tablet/mobile acceptance tests, accessibility and security checks relevant to the task. 5. Failure cases, troubleshooting clues, rollback steps and final client-facing completion criteria. IMPLEMENTATION SAFETY Flag assumptions; favor native block controls over custom code; do not hardcode credentials or private data. For PHP/JS/CSS, provide exact location, activation scope, prerequisite checks, staging test, and undo method. If a plugin or version-specific behavior is uncertain, say what to verify first. Finish with a concise Definition of Done and a measurable business or UX outcome, without promising a result unsupported by data.
Product page information hierarchy
Create a tested, client-ready outcome for product page information hierarchy.
Act as a senior WordPress solution architect and Kadence Theme/Kadence Blocks/WPCode specialist. TASK: Product page information hierarchy. PROJECT INPUTS - Website type and business goal: [SITE TYPE + GOAL] - Audience, locale and key conversion: [AUDIENCE + LOCALE + CTA] - Current stack (WordPress/PHP, Kadence Theme, Kadence Blocks, WPCode, plugins): [VERIFIED VERSIONS] - Current page, screenshot, issue or reference: [URL OR SANITIZED DETAILS] - Constraints (budget, editor skill, hosting, launch date): [CONSTRAINTS] - Existing content, brand styles and approved data: [SOURCE MATERIAL] SPECIFIC OBJECTIVE Develop a practical, results-oriented solution for product page information hierarchy in the context of this website. Respect store pricing, stock, tax, payment and shipping facts; never fabricate social proof. Explain what should be done with Kadence Theme settings, what should be built with Kadence Blocks, and when WPCode is warranted. Do not invent installed plugin capabilities or pretend you accessed the live site. DELIVER EXACTLY 1. A task-specific implementation blueprint for “Product page information hierarchy” with exact WordPress/Kadence navigation or WPCode placement when relevant. 2. An ordered action checklist with dependencies and who owns each action. 3. Copy-ready artifacts where relevant (block hierarchy, settings matrix, sample copy, scoped CSS, PHP or vanilla JavaScript), with code fences and placement instructions. 4. Desktop/tablet/mobile acceptance tests, accessibility and security checks relevant to the task. 5. Failure cases, troubleshooting clues, rollback steps and final client-facing completion criteria. IMPLEMENTATION SAFETY Flag assumptions; favor native block controls over custom code; do not hardcode credentials or private data. For PHP/JS/CSS, provide exact location, activation scope, prerequisite checks, staging test, and undo method. If a plugin or version-specific behavior is uncertain, say what to verify first. Finish with a concise Definition of Done and a measurable business or UX outcome, without promising a result unsupported by data.
Variable product UX
Create a tested, client-ready outcome for variable product ux.
Act as a senior WordPress solution architect and Kadence Theme/Kadence Blocks/WPCode specialist. TASK: Variable product UX. PROJECT INPUTS - Website type and business goal: [SITE TYPE + GOAL] - Audience, locale and key conversion: [AUDIENCE + LOCALE + CTA] - Current stack (WordPress/PHP, Kadence Theme, Kadence Blocks, WPCode, plugins): [VERIFIED VERSIONS] - Current page, screenshot, issue or reference: [URL OR SANITIZED DETAILS] - Constraints (budget, editor skill, hosting, launch date): [CONSTRAINTS] - Existing content, brand styles and approved data: [SOURCE MATERIAL] SPECIFIC OBJECTIVE Develop a practical, results-oriented solution for variable product ux in the context of this website. Respect store pricing, stock, tax, payment and shipping facts; never fabricate social proof. Explain what should be done with Kadence Theme settings, what should be built with Kadence Blocks, and when WPCode is warranted. Do not invent installed plugin capabilities or pretend you accessed the live site. DELIVER EXACTLY 1. A task-specific implementation blueprint for “Variable product UX” with exact WordPress/Kadence navigation or WPCode placement when relevant. 2. An ordered action checklist with dependencies and who owns each action. 3. Copy-ready artifacts where relevant (block hierarchy, settings matrix, sample copy, scoped CSS, PHP or vanilla JavaScript), with code fences and placement instructions. 4. Desktop/tablet/mobile acceptance tests, accessibility and security checks relevant to the task. 5. Failure cases, troubleshooting clues, rollback steps and final client-facing completion criteria. IMPLEMENTATION SAFETY Flag assumptions; favor native block controls over custom code; do not hardcode credentials or private data. For PHP/JS/CSS, provide exact location, activation scope, prerequisite checks, staging test, and undo method. If a plugin or version-specific behavior is uncertain, say what to verify first. Finish with a concise Definition of Done and a measurable business or UX outcome, without promising a result unsupported by data.
Cart friction audit
Create a tested, client-ready outcome for cart friction audit.
Act as a senior WordPress solution architect and Kadence Theme/Kadence Blocks/WPCode specialist. TASK: Cart friction audit. PROJECT INPUTS - Website type and business goal: [SITE TYPE + GOAL] - Audience, locale and key conversion: [AUDIENCE + LOCALE + CTA] - Current stack (WordPress/PHP, Kadence Theme, Kadence Blocks, WPCode, plugins): [VERIFIED VERSIONS] - Current page, screenshot, issue or reference: [URL OR SANITIZED DETAILS] - Constraints (budget, editor skill, hosting, launch date): [CONSTRAINTS] - Existing content, brand styles and approved data: [SOURCE MATERIAL] SPECIFIC OBJECTIVE Develop a practical, results-oriented solution for cart friction audit in the context of this website. Respect store pricing, stock, tax, payment and shipping facts; never fabricate social proof. Explain what should be done with Kadence Theme settings, what should be built with Kadence Blocks, and when WPCode is warranted. Do not invent installed plugin capabilities or pretend you accessed the live site. DELIVER EXACTLY 1. A task-specific implementation blueprint for “Cart friction audit” with exact WordPress/Kadence navigation or WPCode placement when relevant. 2. An ordered action checklist with dependencies and who owns each action. 3. Copy-ready artifacts where relevant (block hierarchy, settings matrix, sample copy, scoped CSS, PHP or vanilla JavaScript), with code fences and placement instructions. 4. Desktop/tablet/mobile acceptance tests, accessibility and security checks relevant to the task. 5. Failure cases, troubleshooting clues, rollback steps and final client-facing completion criteria. IMPLEMENTATION SAFETY Flag assumptions; favor native block controls over custom code; do not hardcode credentials or private data. For PHP/JS/CSS, provide exact location, activation scope, prerequisite checks, staging test, and undo method. If a plugin or version-specific behavior is uncertain, say what to verify first. Finish with a concise Definition of Done and a measurable business or UX outcome, without promising a result unsupported by data.
Checkout experience review
Create a tested, client-ready outcome for checkout experience review.
Act as a senior WordPress solution architect and Kadence Theme/Kadence Blocks/WPCode specialist. TASK: Checkout experience review. PROJECT INPUTS - Website type and business goal: [SITE TYPE + GOAL] - Audience, locale and key conversion: [AUDIENCE + LOCALE + CTA] - Current stack (WordPress/PHP, Kadence Theme, Kadence Blocks, WPCode, plugins): [VERIFIED VERSIONS] - Current page, screenshot, issue or reference: [URL OR SANITIZED DETAILS] - Constraints (budget, editor skill, hosting, launch date): [CONSTRAINTS] - Existing content, brand styles and approved data: [SOURCE MATERIAL] SPECIFIC OBJECTIVE Develop a practical, results-oriented solution for checkout experience review in the context of this website. Respect store pricing, stock, tax, payment and shipping facts; never fabricate social proof. Explain what should be done with Kadence Theme settings, what should be built with Kadence Blocks, and when WPCode is warranted. Do not invent installed plugin capabilities or pretend you accessed the live site. DELIVER EXACTLY 1. A task-specific implementation blueprint for “Checkout experience review” with exact WordPress/Kadence navigation or WPCode placement when relevant. 2. An ordered action checklist with dependencies and who owns each action. 3. Copy-ready artifacts where relevant (block hierarchy, settings matrix, sample copy, scoped CSS, PHP or vanilla JavaScript), with code fences and placement instructions. 4. Desktop/tablet/mobile acceptance tests, accessibility and security checks relevant to the task. 5. Failure cases, troubleshooting clues, rollback steps and final client-facing completion criteria. IMPLEMENTATION SAFETY Flag assumptions; favor native block controls over custom code; do not hardcode credentials or private data. For PHP/JS/CSS, provide exact location, activation scope, prerequisite checks, staging test, and undo method. If a plugin or version-specific behavior is uncertain, say what to verify first. Finish with a concise Definition of Done and a measurable business or UX outcome, without promising a result unsupported by data.
Shipping and returns clarity
Create a tested, client-ready outcome for shipping and returns clarity.
Act as a senior WordPress solution architect and Kadence Theme/Kadence Blocks/WPCode specialist. TASK: Shipping and returns clarity. PROJECT INPUTS - Website type and business goal: [SITE TYPE + GOAL] - Audience, locale and key conversion: [AUDIENCE + LOCALE + CTA] - Current stack (WordPress/PHP, Kadence Theme, Kadence Blocks, WPCode, plugins): [VERIFIED VERSIONS] - Current page, screenshot, issue or reference: [URL OR SANITIZED DETAILS] - Constraints (budget, editor skill, hosting, launch date): [CONSTRAINTS] - Existing content, brand styles and approved data: [SOURCE MATERIAL] SPECIFIC OBJECTIVE Develop a practical, results-oriented solution for shipping and returns clarity in the context of this website. Respect store pricing, stock, tax, payment and shipping facts; never fabricate social proof. Explain what should be done with Kadence Theme settings, what should be built with Kadence Blocks, and when WPCode is warranted. Do not invent installed plugin capabilities or pretend you accessed the live site. DELIVER EXACTLY 1. A task-specific implementation blueprint for “Shipping and returns clarity” with exact WordPress/Kadence navigation or WPCode placement when relevant. 2. An ordered action checklist with dependencies and who owns each action. 3. Copy-ready artifacts where relevant (block hierarchy, settings matrix, sample copy, scoped CSS, PHP or vanilla JavaScript), with code fences and placement instructions. 4. Desktop/tablet/mobile acceptance tests, accessibility and security checks relevant to the task. 5. Failure cases, troubleshooting clues, rollback steps and final client-facing completion criteria. IMPLEMENTATION SAFETY Flag assumptions; favor native block controls over custom code; do not hardcode credentials or private data. For PHP/JS/CSS, provide exact location, activation scope, prerequisite checks, staging test, and undo method. If a plugin or version-specific behavior is uncertain, say what to verify first. Finish with a concise Definition of Done and a measurable business or UX outcome, without promising a result unsupported by data.
Product comparison design
Create a tested, client-ready outcome for product comparison design.
Act as a senior WordPress solution architect and Kadence Theme/Kadence Blocks/WPCode specialist. TASK: Product comparison design. PROJECT INPUTS - Website type and business goal: [SITE TYPE + GOAL] - Audience, locale and key conversion: [AUDIENCE + LOCALE + CTA] - Current stack (WordPress/PHP, Kadence Theme, Kadence Blocks, WPCode, plugins): [VERIFIED VERSIONS] - Current page, screenshot, issue or reference: [URL OR SANITIZED DETAILS] - Constraints (budget, editor skill, hosting, launch date): [CONSTRAINTS] - Existing content, brand styles and approved data: [SOURCE MATERIAL] SPECIFIC OBJECTIVE Develop a practical, results-oriented solution for product comparison design in the context of this website. Respect store pricing, stock, tax, payment and shipping facts; never fabricate social proof. Explain what should be done with Kadence Theme settings, what should be built with Kadence Blocks, and when WPCode is warranted. Do not invent installed plugin capabilities or pretend you accessed the live site. DELIVER EXACTLY 1. A task-specific implementation blueprint for “Product comparison design” with exact WordPress/Kadence navigation or WPCode placement when relevant. 2. An ordered action checklist with dependencies and who owns each action. 3. Copy-ready artifacts where relevant (block hierarchy, settings matrix, sample copy, scoped CSS, PHP or vanilla JavaScript), with code fences and placement instructions. 4. Desktop/tablet/mobile acceptance tests, accessibility and security checks relevant to the task. 5. Failure cases, troubleshooting clues, rollback steps and final client-facing completion criteria. IMPLEMENTATION SAFETY Flag assumptions; favor native block controls over custom code; do not hardcode credentials or private data. For PHP/JS/CSS, provide exact location, activation scope, prerequisite checks, staging test, and undo method. If a plugin or version-specific behavior is uncertain, say what to verify first. Finish with a concise Definition of Done and a measurable business or UX outcome, without promising a result unsupported by data.
Trust badges evidence policy
Create a tested, client-ready outcome for trust badges evidence policy.
Act as a senior WordPress solution architect and Kadence Theme/Kadence Blocks/WPCode specialist. TASK: Trust badges evidence policy. PROJECT INPUTS - Website type and business goal: [SITE TYPE + GOAL] - Audience, locale and key conversion: [AUDIENCE + LOCALE + CTA] - Current stack (WordPress/PHP, Kadence Theme, Kadence Blocks, WPCode, plugins): [VERIFIED VERSIONS] - Current page, screenshot, issue or reference: [URL OR SANITIZED DETAILS] - Constraints (budget, editor skill, hosting, launch date): [CONSTRAINTS] - Existing content, brand styles and approved data: [SOURCE MATERIAL] SPECIFIC OBJECTIVE Develop a practical, results-oriented solution for trust badges evidence policy in the context of this website. Respect store pricing, stock, tax, payment and shipping facts; never fabricate social proof. Explain what should be done with Kadence Theme settings, what should be built with Kadence Blocks, and when WPCode is warranted. Do not invent installed plugin capabilities or pretend you accessed the live site. DELIVER EXACTLY 1. A task-specific implementation blueprint for “Trust badges evidence policy” with exact WordPress/Kadence navigation or WPCode placement when relevant. 2. An ordered action checklist with dependencies and who owns each action. 3. Copy-ready artifacts where relevant (block hierarchy, settings matrix, sample copy, scoped CSS, PHP or vanilla JavaScript), with code fences and placement instructions. 4. Desktop/tablet/mobile acceptance tests, accessibility and security checks relevant to the task. 5. Failure cases, troubleshooting clues, rollback steps and final client-facing completion criteria. IMPLEMENTATION SAFETY Flag assumptions; favor native block controls over custom code; do not hardcode credentials or private data. For PHP/JS/CSS, provide exact location, activation scope, prerequisite checks, staging test, and undo method. If a plugin or version-specific behavior is uncertain, say what to verify first. Finish with a concise Definition of Done and a measurable business or UX outcome, without promising a result unsupported by data.
Upsell and cross-sell map
Create a tested, client-ready outcome for upsell and cross-sell map.
Act as a senior WordPress solution architect and Kadence Theme/Kadence Blocks/WPCode specialist. TASK: Upsell and cross-sell map. PROJECT INPUTS - Website type and business goal: [SITE TYPE + GOAL] - Audience, locale and key conversion: [AUDIENCE + LOCALE + CTA] - Current stack (WordPress/PHP, Kadence Theme, Kadence Blocks, WPCode, plugins): [VERIFIED VERSIONS] - Current page, screenshot, issue or reference: [URL OR SANITIZED DETAILS] - Constraints (budget, editor skill, hosting, launch date): [CONSTRAINTS] - Existing content, brand styles and approved data: [SOURCE MATERIAL] SPECIFIC OBJECTIVE Develop a practical, results-oriented solution for upsell and cross-sell map in the context of this website. Respect store pricing, stock, tax, payment and shipping facts; never fabricate social proof. Explain what should be done with Kadence Theme settings, what should be built with Kadence Blocks, and when WPCode is warranted. Do not invent installed plugin capabilities or pretend you accessed the live site. DELIVER EXACTLY 1. A task-specific implementation blueprint for “Upsell and cross-sell map” with exact WordPress/Kadence navigation or WPCode placement when relevant. 2. An ordered action checklist with dependencies and who owns each action. 3. Copy-ready artifacts where relevant (block hierarchy, settings matrix, sample copy, scoped CSS, PHP or vanilla JavaScript), with code fences and placement instructions. 4. Desktop/tablet/mobile acceptance tests, accessibility and security checks relevant to the task. 5. Failure cases, troubleshooting clues, rollback steps and final client-facing completion criteria. IMPLEMENTATION SAFETY Flag assumptions; favor native block controls over custom code; do not hardcode credentials or private data. For PHP/JS/CSS, provide exact location, activation scope, prerequisite checks, staging test, and undo method. If a plugin or version-specific behavior is uncertain, say what to verify first. Finish with a concise Definition of Done and a measurable business or UX outcome, without promising a result unsupported by data.
Store mobile QA
Create a tested, client-ready outcome for store mobile qa.
Act as a senior WordPress solution architect and Kadence Theme/Kadence Blocks/WPCode specialist. TASK: Store mobile QA. PROJECT INPUTS - Website type and business goal: [SITE TYPE + GOAL] - Audience, locale and key conversion: [AUDIENCE + LOCALE + CTA] - Current stack (WordPress/PHP, Kadence Theme, Kadence Blocks, WPCode, plugins): [VERIFIED VERSIONS] - Current page, screenshot, issue or reference: [URL OR SANITIZED DETAILS] - Constraints (budget, editor skill, hosting, launch date): [CONSTRAINTS] - Existing content, brand styles and approved data: [SOURCE MATERIAL] SPECIFIC OBJECTIVE Develop a practical, results-oriented solution for store mobile qa in the context of this website. Respect store pricing, stock, tax, payment and shipping facts; never fabricate social proof. Explain what should be done with Kadence Theme settings, what should be built with Kadence Blocks, and when WPCode is warranted. Do not invent installed plugin capabilities or pretend you accessed the live site. DELIVER EXACTLY 1. A task-specific implementation blueprint for “Store mobile QA” with exact WordPress/Kadence navigation or WPCode placement when relevant. 2. An ordered action checklist with dependencies and who owns each action. 3. Copy-ready artifacts where relevant (block hierarchy, settings matrix, sample copy, scoped CSS, PHP or vanilla JavaScript), with code fences and placement instructions. 4. Desktop/tablet/mobile acceptance tests, accessibility and security checks relevant to the task. 5. Failure cases, troubleshooting clues, rollback steps and final client-facing completion criteria. IMPLEMENTATION SAFETY Flag assumptions; favor native block controls over custom code; do not hardcode credentials or private data. For PHP/JS/CSS, provide exact location, activation scope, prerequisite checks, staging test, and undo method. If a plugin or version-specific behavior is uncertain, say what to verify first. Finish with a concise Definition of Done and a measurable business or UX outcome, without promising a result unsupported by data.
10. Booking, Events & Membership
Appointment flow requirements
Create a tested, client-ready outcome for appointment flow requirements.
Act as a senior WordPress solution architect and Kadence Theme/Kadence Blocks/WPCode specialist. TASK: Appointment flow requirements. PROJECT INPUTS - Website type and business goal: [SITE TYPE + GOAL] - Audience, locale and key conversion: [AUDIENCE + LOCALE + CTA] - Current stack (WordPress/PHP, Kadence Theme, Kadence Blocks, WPCode, plugins): [VERIFIED VERSIONS] - Current page, screenshot, issue or reference: [URL OR SANITIZED DETAILS] - Constraints (budget, editor skill, hosting, launch date): [CONSTRAINTS] - Existing content, brand styles and approved data: [SOURCE MATERIAL] SPECIFIC OBJECTIVE Develop a practical, results-oriented solution for appointment flow requirements in the context of this website. Distinguish content access, payments, consent and third-party plugin responsibilities. Explain what should be done with Kadence Theme settings, what should be built with Kadence Blocks, and when WPCode is warranted. Do not invent installed plugin capabilities or pretend you accessed the live site. DELIVER EXACTLY 1. A task-specific implementation blueprint for “Appointment flow requirements” with exact WordPress/Kadence navigation or WPCode placement when relevant. 2. An ordered action checklist with dependencies and who owns each action. 3. Copy-ready artifacts where relevant (block hierarchy, settings matrix, sample copy, scoped CSS, PHP or vanilla JavaScript), with code fences and placement instructions. 4. Desktop/tablet/mobile acceptance tests, accessibility and security checks relevant to the task. 5. Failure cases, troubleshooting clues, rollback steps and final client-facing completion criteria. IMPLEMENTATION SAFETY Flag assumptions; favor native block controls over custom code; do not hardcode credentials or private data. For PHP/JS/CSS, provide exact location, activation scope, prerequisite checks, staging test, and undo method. If a plugin or version-specific behavior is uncertain, say what to verify first. Finish with a concise Definition of Done and a measurable business or UX outcome, without promising a result unsupported by data.
Booking plugin evaluation
Create a tested, client-ready outcome for booking plugin evaluation.
Act as a senior WordPress solution architect and Kadence Theme/Kadence Blocks/WPCode specialist. TASK: Booking plugin evaluation. PROJECT INPUTS - Website type and business goal: [SITE TYPE + GOAL] - Audience, locale and key conversion: [AUDIENCE + LOCALE + CTA] - Current stack (WordPress/PHP, Kadence Theme, Kadence Blocks, WPCode, plugins): [VERIFIED VERSIONS] - Current page, screenshot, issue or reference: [URL OR SANITIZED DETAILS] - Constraints (budget, editor skill, hosting, launch date): [CONSTRAINTS] - Existing content, brand styles and approved data: [SOURCE MATERIAL] SPECIFIC OBJECTIVE Develop a practical, results-oriented solution for booking plugin evaluation in the context of this website. Distinguish content access, payments, consent and third-party plugin responsibilities. Explain what should be done with Kadence Theme settings, what should be built with Kadence Blocks, and when WPCode is warranted. Do not invent installed plugin capabilities or pretend you accessed the live site. DELIVER EXACTLY 1. A task-specific implementation blueprint for “Booking plugin evaluation” with exact WordPress/Kadence navigation or WPCode placement when relevant. 2. An ordered action checklist with dependencies and who owns each action. 3. Copy-ready artifacts where relevant (block hierarchy, settings matrix, sample copy, scoped CSS, PHP or vanilla JavaScript), with code fences and placement instructions. 4. Desktop/tablet/mobile acceptance tests, accessibility and security checks relevant to the task. 5. Failure cases, troubleshooting clues, rollback steps and final client-facing completion criteria. IMPLEMENTATION SAFETY Flag assumptions; favor native block controls over custom code; do not hardcode credentials or private data. For PHP/JS/CSS, provide exact location, activation scope, prerequisite checks, staging test, and undo method. If a plugin or version-specific behavior is uncertain, say what to verify first. Finish with a concise Definition of Done and a measurable business or UX outcome, without promising a result unsupported by data.
Class schedule information
Create a tested, client-ready outcome for class schedule information.
Act as a senior WordPress solution architect and Kadence Theme/Kadence Blocks/WPCode specialist. TASK: Class schedule information. PROJECT INPUTS - Website type and business goal: [SITE TYPE + GOAL] - Audience, locale and key conversion: [AUDIENCE + LOCALE + CTA] - Current stack (WordPress/PHP, Kadence Theme, Kadence Blocks, WPCode, plugins): [VERIFIED VERSIONS] - Current page, screenshot, issue or reference: [URL OR SANITIZED DETAILS] - Constraints (budget, editor skill, hosting, launch date): [CONSTRAINTS] - Existing content, brand styles and approved data: [SOURCE MATERIAL] SPECIFIC OBJECTIVE Develop a practical, results-oriented solution for class schedule information in the context of this website. Distinguish content access, payments, consent and third-party plugin responsibilities. Explain what should be done with Kadence Theme settings, what should be built with Kadence Blocks, and when WPCode is warranted. Do not invent installed plugin capabilities or pretend you accessed the live site. DELIVER EXACTLY 1. A task-specific implementation blueprint for “Class schedule information” with exact WordPress/Kadence navigation or WPCode placement when relevant. 2. An ordered action checklist with dependencies and who owns each action. 3. Copy-ready artifacts where relevant (block hierarchy, settings matrix, sample copy, scoped CSS, PHP or vanilla JavaScript), with code fences and placement instructions. 4. Desktop/tablet/mobile acceptance tests, accessibility and security checks relevant to the task. 5. Failure cases, troubleshooting clues, rollback steps and final client-facing completion criteria. IMPLEMENTATION SAFETY Flag assumptions; favor native block controls over custom code; do not hardcode credentials or private data. For PHP/JS/CSS, provide exact location, activation scope, prerequisite checks, staging test, and undo method. If a plugin or version-specific behavior is uncertain, say what to verify first. Finish with a concise Definition of Done and a measurable business or UX outcome, without promising a result unsupported by data.
Event detail template
Create a tested, client-ready outcome for event detail template.
Act as a senior WordPress solution architect and Kadence Theme/Kadence Blocks/WPCode specialist. TASK: Event detail template. PROJECT INPUTS - Website type and business goal: [SITE TYPE + GOAL] - Audience, locale and key conversion: [AUDIENCE + LOCALE + CTA] - Current stack (WordPress/PHP, Kadence Theme, Kadence Blocks, WPCode, plugins): [VERIFIED VERSIONS] - Current page, screenshot, issue or reference: [URL OR SANITIZED DETAILS] - Constraints (budget, editor skill, hosting, launch date): [CONSTRAINTS] - Existing content, brand styles and approved data: [SOURCE MATERIAL] SPECIFIC OBJECTIVE Develop a practical, results-oriented solution for event detail template in the context of this website. Distinguish content access, payments, consent and third-party plugin responsibilities. Explain what should be done with Kadence Theme settings, what should be built with Kadence Blocks, and when WPCode is warranted. Do not invent installed plugin capabilities or pretend you accessed the live site. DELIVER EXACTLY 1. A task-specific implementation blueprint for “Event detail template” with exact WordPress/Kadence navigation or WPCode placement when relevant. 2. An ordered action checklist with dependencies and who owns each action. 3. Copy-ready artifacts where relevant (block hierarchy, settings matrix, sample copy, scoped CSS, PHP or vanilla JavaScript), with code fences and placement instructions. 4. Desktop/tablet/mobile acceptance tests, accessibility and security checks relevant to the task. 5. Failure cases, troubleshooting clues, rollback steps and final client-facing completion criteria. IMPLEMENTATION SAFETY Flag assumptions; favor native block controls over custom code; do not hardcode credentials or private data. For PHP/JS/CSS, provide exact location, activation scope, prerequisite checks, staging test, and undo method. If a plugin or version-specific behavior is uncertain, say what to verify first. Finish with a concise Definition of Done and a measurable business or UX outcome, without promising a result unsupported by data.
Registration form UX
Create a tested, client-ready outcome for registration form ux.
Act as a senior WordPress solution architect and Kadence Theme/Kadence Blocks/WPCode specialist. TASK: Registration form UX. PROJECT INPUTS - Website type and business goal: [SITE TYPE + GOAL] - Audience, locale and key conversion: [AUDIENCE + LOCALE + CTA] - Current stack (WordPress/PHP, Kadence Theme, Kadence Blocks, WPCode, plugins): [VERIFIED VERSIONS] - Current page, screenshot, issue or reference: [URL OR SANITIZED DETAILS] - Constraints (budget, editor skill, hosting, launch date): [CONSTRAINTS] - Existing content, brand styles and approved data: [SOURCE MATERIAL] SPECIFIC OBJECTIVE Develop a practical, results-oriented solution for registration form ux in the context of this website. Distinguish content access, payments, consent and third-party plugin responsibilities. Explain what should be done with Kadence Theme settings, what should be built with Kadence Blocks, and when WPCode is warranted. Do not invent installed plugin capabilities or pretend you accessed the live site. DELIVER EXACTLY 1. A task-specific implementation blueprint for “Registration form UX” with exact WordPress/Kadence navigation or WPCode placement when relevant. 2. An ordered action checklist with dependencies and who owns each action. 3. Copy-ready artifacts where relevant (block hierarchy, settings matrix, sample copy, scoped CSS, PHP or vanilla JavaScript), with code fences and placement instructions. 4. Desktop/tablet/mobile acceptance tests, accessibility and security checks relevant to the task. 5. Failure cases, troubleshooting clues, rollback steps and final client-facing completion criteria. IMPLEMENTATION SAFETY Flag assumptions; favor native block controls over custom code; do not hardcode credentials or private data. For PHP/JS/CSS, provide exact location, activation scope, prerequisite checks, staging test, and undo method. If a plugin or version-specific behavior is uncertain, say what to verify first. Finish with a concise Definition of Done and a measurable business or UX outcome, without promising a result unsupported by data.
Membership tiers architecture
Create a tested, client-ready outcome for membership tiers architecture.
Act as a senior WordPress solution architect and Kadence Theme/Kadence Blocks/WPCode specialist. TASK: Membership tiers architecture. PROJECT INPUTS - Website type and business goal: [SITE TYPE + GOAL] - Audience, locale and key conversion: [AUDIENCE + LOCALE + CTA] - Current stack (WordPress/PHP, Kadence Theme, Kadence Blocks, WPCode, plugins): [VERIFIED VERSIONS] - Current page, screenshot, issue or reference: [URL OR SANITIZED DETAILS] - Constraints (budget, editor skill, hosting, launch date): [CONSTRAINTS] - Existing content, brand styles and approved data: [SOURCE MATERIAL] SPECIFIC OBJECTIVE Develop a practical, results-oriented solution for membership tiers architecture in the context of this website. Distinguish content access, payments, consent and third-party plugin responsibilities. Explain what should be done with Kadence Theme settings, what should be built with Kadence Blocks, and when WPCode is warranted. Do not invent installed plugin capabilities or pretend you accessed the live site. DELIVER EXACTLY 1. A task-specific implementation blueprint for “Membership tiers architecture” with exact WordPress/Kadence navigation or WPCode placement when relevant. 2. An ordered action checklist with dependencies and who owns each action. 3. Copy-ready artifacts where relevant (block hierarchy, settings matrix, sample copy, scoped CSS, PHP or vanilla JavaScript), with code fences and placement instructions. 4. Desktop/tablet/mobile acceptance tests, accessibility and security checks relevant to the task. 5. Failure cases, troubleshooting clues, rollback steps and final client-facing completion criteria. IMPLEMENTATION SAFETY Flag assumptions; favor native block controls over custom code; do not hardcode credentials or private data. For PHP/JS/CSS, provide exact location, activation scope, prerequisite checks, staging test, and undo method. If a plugin or version-specific behavior is uncertain, say what to verify first. Finish with a concise Definition of Done and a measurable business or UX outcome, without promising a result unsupported by data.
Private content permissions
Create a tested, client-ready outcome for private content permissions.
Act as a senior WordPress solution architect and Kadence Theme/Kadence Blocks/WPCode specialist. TASK: Private content permissions. PROJECT INPUTS - Website type and business goal: [SITE TYPE + GOAL] - Audience, locale and key conversion: [AUDIENCE + LOCALE + CTA] - Current stack (WordPress/PHP, Kadence Theme, Kadence Blocks, WPCode, plugins): [VERIFIED VERSIONS] - Current page, screenshot, issue or reference: [URL OR SANITIZED DETAILS] - Constraints (budget, editor skill, hosting, launch date): [CONSTRAINTS] - Existing content, brand styles and approved data: [SOURCE MATERIAL] SPECIFIC OBJECTIVE Develop a practical, results-oriented solution for private content permissions in the context of this website. Distinguish content access, payments, consent and third-party plugin responsibilities. Explain what should be done with Kadence Theme settings, what should be built with Kadence Blocks, and when WPCode is warranted. Do not invent installed plugin capabilities or pretend you accessed the live site. DELIVER EXACTLY 1. A task-specific implementation blueprint for “Private content permissions” with exact WordPress/Kadence navigation or WPCode placement when relevant. 2. An ordered action checklist with dependencies and who owns each action. 3. Copy-ready artifacts where relevant (block hierarchy, settings matrix, sample copy, scoped CSS, PHP or vanilla JavaScript), with code fences and placement instructions. 4. Desktop/tablet/mobile acceptance tests, accessibility and security checks relevant to the task. 5. Failure cases, troubleshooting clues, rollback steps and final client-facing completion criteria. IMPLEMENTATION SAFETY Flag assumptions; favor native block controls over custom code; do not hardcode credentials or private data. For PHP/JS/CSS, provide exact location, activation scope, prerequisite checks, staging test, and undo method. If a plugin or version-specific behavior is uncertain, say what to verify first. Finish with a concise Definition of Done and a measurable business or UX outcome, without promising a result unsupported by data.
Payment renewal messaging
Create a tested, client-ready outcome for payment renewal messaging.
Act as a senior WordPress solution architect and Kadence Theme/Kadence Blocks/WPCode specialist. TASK: Payment renewal messaging. PROJECT INPUTS - Website type and business goal: [SITE TYPE + GOAL] - Audience, locale and key conversion: [AUDIENCE + LOCALE + CTA] - Current stack (WordPress/PHP, Kadence Theme, Kadence Blocks, WPCode, plugins): [VERIFIED VERSIONS] - Current page, screenshot, issue or reference: [URL OR SANITIZED DETAILS] - Constraints (budget, editor skill, hosting, launch date): [CONSTRAINTS] - Existing content, brand styles and approved data: [SOURCE MATERIAL] SPECIFIC OBJECTIVE Develop a practical, results-oriented solution for payment renewal messaging in the context of this website. Distinguish content access, payments, consent and third-party plugin responsibilities. Explain what should be done with Kadence Theme settings, what should be built with Kadence Blocks, and when WPCode is warranted. Do not invent installed plugin capabilities or pretend you accessed the live site. DELIVER EXACTLY 1. A task-specific implementation blueprint for “Payment renewal messaging” with exact WordPress/Kadence navigation or WPCode placement when relevant. 2. An ordered action checklist with dependencies and who owns each action. 3. Copy-ready artifacts where relevant (block hierarchy, settings matrix, sample copy, scoped CSS, PHP or vanilla JavaScript), with code fences and placement instructions. 4. Desktop/tablet/mobile acceptance tests, accessibility and security checks relevant to the task. 5. Failure cases, troubleshooting clues, rollback steps and final client-facing completion criteria. IMPLEMENTATION SAFETY Flag assumptions; favor native block controls over custom code; do not hardcode credentials or private data. For PHP/JS/CSS, provide exact location, activation scope, prerequisite checks, staging test, and undo method. If a plugin or version-specific behavior is uncertain, say what to verify first. Finish with a concise Definition of Done and a measurable business or UX outcome, without promising a result unsupported by data.
Cancellation flow specification
Create a tested, client-ready outcome for cancellation flow specification.
Act as a senior WordPress solution architect and Kadence Theme/Kadence Blocks/WPCode specialist. TASK: Cancellation flow specification. PROJECT INPUTS - Website type and business goal: [SITE TYPE + GOAL] - Audience, locale and key conversion: [AUDIENCE + LOCALE + CTA] - Current stack (WordPress/PHP, Kadence Theme, Kadence Blocks, WPCode, plugins): [VERIFIED VERSIONS] - Current page, screenshot, issue or reference: [URL OR SANITIZED DETAILS] - Constraints (budget, editor skill, hosting, launch date): [CONSTRAINTS] - Existing content, brand styles and approved data: [SOURCE MATERIAL] SPECIFIC OBJECTIVE Develop a practical, results-oriented solution for cancellation flow specification in the context of this website. Distinguish content access, payments, consent and third-party plugin responsibilities. Explain what should be done with Kadence Theme settings, what should be built with Kadence Blocks, and when WPCode is warranted. Do not invent installed plugin capabilities or pretend you accessed the live site. DELIVER EXACTLY 1. A task-specific implementation blueprint for “Cancellation flow specification” with exact WordPress/Kadence navigation or WPCode placement when relevant. 2. An ordered action checklist with dependencies and who owns each action. 3. Copy-ready artifacts where relevant (block hierarchy, settings matrix, sample copy, scoped CSS, PHP or vanilla JavaScript), with code fences and placement instructions. 4. Desktop/tablet/mobile acceptance tests, accessibility and security checks relevant to the task. 5. Failure cases, troubleshooting clues, rollback steps and final client-facing completion criteria. IMPLEMENTATION SAFETY Flag assumptions; favor native block controls over custom code; do not hardcode credentials or private data. For PHP/JS/CSS, provide exact location, activation scope, prerequisite checks, staging test, and undo method. If a plugin or version-specific behavior is uncertain, say what to verify first. Finish with a concise Definition of Done and a measurable business or UX outcome, without promising a result unsupported by data.
Member dashboard outline
Create a tested, client-ready outcome for member dashboard outline.
Act as a senior WordPress solution architect and Kadence Theme/Kadence Blocks/WPCode specialist. TASK: Member dashboard outline. PROJECT INPUTS - Website type and business goal: [SITE TYPE + GOAL] - Audience, locale and key conversion: [AUDIENCE + LOCALE + CTA] - Current stack (WordPress/PHP, Kadence Theme, Kadence Blocks, WPCode, plugins): [VERIFIED VERSIONS] - Current page, screenshot, issue or reference: [URL OR SANITIZED DETAILS] - Constraints (budget, editor skill, hosting, launch date): [CONSTRAINTS] - Existing content, brand styles and approved data: [SOURCE MATERIAL] SPECIFIC OBJECTIVE Develop a practical, results-oriented solution for member dashboard outline in the context of this website. Distinguish content access, payments, consent and third-party plugin responsibilities. Explain what should be done with Kadence Theme settings, what should be built with Kadence Blocks, and when WPCode is warranted. Do not invent installed plugin capabilities or pretend you accessed the live site. DELIVER EXACTLY 1. A task-specific implementation blueprint for “Member dashboard outline” with exact WordPress/Kadence navigation or WPCode placement when relevant. 2. An ordered action checklist with dependencies and who owns each action. 3. Copy-ready artifacts where relevant (block hierarchy, settings matrix, sample copy, scoped CSS, PHP or vanilla JavaScript), with code fences and placement instructions. 4. Desktop/tablet/mobile acceptance tests, accessibility and security checks relevant to the task. 5. Failure cases, troubleshooting clues, rollback steps and final client-facing completion criteria. IMPLEMENTATION SAFETY Flag assumptions; favor native block controls over custom code; do not hardcode credentials or private data. For PHP/JS/CSS, provide exact location, activation scope, prerequisite checks, staging test, and undo method. If a plugin or version-specific behavior is uncertain, say what to verify first. Finish with a concise Definition of Done and a measurable business or UX outcome, without promising a result unsupported by data.
11. Forms, Leads & CRM Integrations
Lead form field minimization
Create a tested, client-ready outcome for lead form field minimization.
Act as a senior WordPress solution architect and Kadence Theme/Kadence Blocks/WPCode specialist. TASK: Lead form field minimization. PROJECT INPUTS - Website type and business goal: [SITE TYPE + GOAL] - Audience, locale and key conversion: [AUDIENCE + LOCALE + CTA] - Current stack (WordPress/PHP, Kadence Theme, Kadence Blocks, WPCode, plugins): [VERIFIED VERSIONS] - Current page, screenshot, issue or reference: [URL OR SANITIZED DETAILS] - Constraints (budget, editor skill, hosting, launch date): [CONSTRAINTS] - Existing content, brand styles and approved data: [SOURCE MATERIAL] SPECIFIC OBJECTIVE Develop a practical, results-oriented solution for lead form field minimization in the context of this website. Map data fields and consent; keep credentials and pii out of prompt and logs. Explain what should be done with Kadence Theme settings, what should be built with Kadence Blocks, and when WPCode is warranted. Do not invent installed plugin capabilities or pretend you accessed the live site. DELIVER EXACTLY 1. A task-specific implementation blueprint for “Lead form field minimization” with exact WordPress/Kadence navigation or WPCode placement when relevant. 2. An ordered action checklist with dependencies and who owns each action. 3. Copy-ready artifacts where relevant (block hierarchy, settings matrix, sample copy, scoped CSS, PHP or vanilla JavaScript), with code fences and placement instructions. 4. Desktop/tablet/mobile acceptance tests, accessibility and security checks relevant to the task. 5. Failure cases, troubleshooting clues, rollback steps and final client-facing completion criteria. IMPLEMENTATION SAFETY Flag assumptions; favor native block controls over custom code; do not hardcode credentials or private data. For PHP/JS/CSS, provide exact location, activation scope, prerequisite checks, staging test, and undo method. If a plugin or version-specific behavior is uncertain, say what to verify first. Finish with a concise Definition of Done and a measurable business or UX outcome, without promising a result unsupported by data.
Conditional form logic
Create a tested, client-ready outcome for conditional form logic.
Act as a senior WordPress solution architect and Kadence Theme/Kadence Blocks/WPCode specialist. TASK: Conditional form logic. PROJECT INPUTS - Website type and business goal: [SITE TYPE + GOAL] - Audience, locale and key conversion: [AUDIENCE + LOCALE + CTA] - Current stack (WordPress/PHP, Kadence Theme, Kadence Blocks, WPCode, plugins): [VERIFIED VERSIONS] - Current page, screenshot, issue or reference: [URL OR SANITIZED DETAILS] - Constraints (budget, editor skill, hosting, launch date): [CONSTRAINTS] - Existing content, brand styles and approved data: [SOURCE MATERIAL] SPECIFIC OBJECTIVE Develop a practical, results-oriented solution for conditional form logic in the context of this website. Map data fields and consent; keep credentials and pii out of prompt and logs. Explain what should be done with Kadence Theme settings, what should be built with Kadence Blocks, and when WPCode is warranted. Do not invent installed plugin capabilities or pretend you accessed the live site. DELIVER EXACTLY 1. A task-specific implementation blueprint for “Conditional form logic” with exact WordPress/Kadence navigation or WPCode placement when relevant. 2. An ordered action checklist with dependencies and who owns each action. 3. Copy-ready artifacts where relevant (block hierarchy, settings matrix, sample copy, scoped CSS, PHP or vanilla JavaScript), with code fences and placement instructions. 4. Desktop/tablet/mobile acceptance tests, accessibility and security checks relevant to the task. 5. Failure cases, troubleshooting clues, rollback steps and final client-facing completion criteria. IMPLEMENTATION SAFETY Flag assumptions; favor native block controls over custom code; do not hardcode credentials or private data. For PHP/JS/CSS, provide exact location, activation scope, prerequisite checks, staging test, and undo method. If a plugin or version-specific behavior is uncertain, say what to verify first. Finish with a concise Definition of Done and a measurable business or UX outcome, without promising a result unsupported by data.
Spam prevention approach
Create a tested, client-ready outcome for spam prevention approach.
Act as a senior WordPress solution architect and Kadence Theme/Kadence Blocks/WPCode specialist. TASK: Spam prevention approach. PROJECT INPUTS - Website type and business goal: [SITE TYPE + GOAL] - Audience, locale and key conversion: [AUDIENCE + LOCALE + CTA] - Current stack (WordPress/PHP, Kadence Theme, Kadence Blocks, WPCode, plugins): [VERIFIED VERSIONS] - Current page, screenshot, issue or reference: [URL OR SANITIZED DETAILS] - Constraints (budget, editor skill, hosting, launch date): [CONSTRAINTS] - Existing content, brand styles and approved data: [SOURCE MATERIAL] SPECIFIC OBJECTIVE Develop a practical, results-oriented solution for spam prevention approach in the context of this website. Map data fields and consent; keep credentials and pii out of prompt and logs. Explain what should be done with Kadence Theme settings, what should be built with Kadence Blocks, and when WPCode is warranted. Do not invent installed plugin capabilities or pretend you accessed the live site. DELIVER EXACTLY 1. A task-specific implementation blueprint for “Spam prevention approach” with exact WordPress/Kadence navigation or WPCode placement when relevant. 2. An ordered action checklist with dependencies and who owns each action. 3. Copy-ready artifacts where relevant (block hierarchy, settings matrix, sample copy, scoped CSS, PHP or vanilla JavaScript), with code fences and placement instructions. 4. Desktop/tablet/mobile acceptance tests, accessibility and security checks relevant to the task. 5. Failure cases, troubleshooting clues, rollback steps and final client-facing completion criteria. IMPLEMENTATION SAFETY Flag assumptions; favor native block controls over custom code; do not hardcode credentials or private data. For PHP/JS/CSS, provide exact location, activation scope, prerequisite checks, staging test, and undo method. If a plugin or version-specific behavior is uncertain, say what to verify first. Finish with a concise Definition of Done and a measurable business or UX outcome, without promising a result unsupported by data.
Form validation messages
Create a tested, client-ready outcome for form validation messages.
Act as a senior WordPress solution architect and Kadence Theme/Kadence Blocks/WPCode specialist. TASK: Form validation messages. PROJECT INPUTS - Website type and business goal: [SITE TYPE + GOAL] - Audience, locale and key conversion: [AUDIENCE + LOCALE + CTA] - Current stack (WordPress/PHP, Kadence Theme, Kadence Blocks, WPCode, plugins): [VERIFIED VERSIONS] - Current page, screenshot, issue or reference: [URL OR SANITIZED DETAILS] - Constraints (budget, editor skill, hosting, launch date): [CONSTRAINTS] - Existing content, brand styles and approved data: [SOURCE MATERIAL] SPECIFIC OBJECTIVE Develop a practical, results-oriented solution for form validation messages in the context of this website. Map data fields and consent; keep credentials and pii out of prompt and logs. Explain what should be done with Kadence Theme settings, what should be built with Kadence Blocks, and when WPCode is warranted. Do not invent installed plugin capabilities or pretend you accessed the live site. DELIVER EXACTLY 1. A task-specific implementation blueprint for “Form validation messages” with exact WordPress/Kadence navigation or WPCode placement when relevant. 2. An ordered action checklist with dependencies and who owns each action. 3. Copy-ready artifacts where relevant (block hierarchy, settings matrix, sample copy, scoped CSS, PHP or vanilla JavaScript), with code fences and placement instructions. 4. Desktop/tablet/mobile acceptance tests, accessibility and security checks relevant to the task. 5. Failure cases, troubleshooting clues, rollback steps and final client-facing completion criteria. IMPLEMENTATION SAFETY Flag assumptions; favor native block controls over custom code; do not hardcode credentials or private data. For PHP/JS/CSS, provide exact location, activation scope, prerequisite checks, staging test, and undo method. If a plugin or version-specific behavior is uncertain, say what to verify first. Finish with a concise Definition of Done and a measurable business or UX outcome, without promising a result unsupported by data.
Consent checkbox design
Create a tested, client-ready outcome for consent checkbox design.
Act as a senior WordPress solution architect and Kadence Theme/Kadence Blocks/WPCode specialist. TASK: Consent checkbox design. PROJECT INPUTS - Website type and business goal: [SITE TYPE + GOAL] - Audience, locale and key conversion: [AUDIENCE + LOCALE + CTA] - Current stack (WordPress/PHP, Kadence Theme, Kadence Blocks, WPCode, plugins): [VERIFIED VERSIONS] - Current page, screenshot, issue or reference: [URL OR SANITIZED DETAILS] - Constraints (budget, editor skill, hosting, launch date): [CONSTRAINTS] - Existing content, brand styles and approved data: [SOURCE MATERIAL] SPECIFIC OBJECTIVE Develop a practical, results-oriented solution for consent checkbox design in the context of this website. Map data fields and consent; keep credentials and pii out of prompt and logs. Explain what should be done with Kadence Theme settings, what should be built with Kadence Blocks, and when WPCode is warranted. Do not invent installed plugin capabilities or pretend you accessed the live site. DELIVER EXACTLY 1. A task-specific implementation blueprint for “Consent checkbox design” with exact WordPress/Kadence navigation or WPCode placement when relevant. 2. An ordered action checklist with dependencies and who owns each action. 3. Copy-ready artifacts where relevant (block hierarchy, settings matrix, sample copy, scoped CSS, PHP or vanilla JavaScript), with code fences and placement instructions. 4. Desktop/tablet/mobile acceptance tests, accessibility and security checks relevant to the task. 5. Failure cases, troubleshooting clues, rollback steps and final client-facing completion criteria. IMPLEMENTATION SAFETY Flag assumptions; favor native block controls over custom code; do not hardcode credentials or private data. For PHP/JS/CSS, provide exact location, activation scope, prerequisite checks, staging test, and undo method. If a plugin or version-specific behavior is uncertain, say what to verify first. Finish with a concise Definition of Done and a measurable business or UX outcome, without promising a result unsupported by data.
Email notification routing
Create a tested, client-ready outcome for email notification routing.
Act as a senior WordPress solution architect and Kadence Theme/Kadence Blocks/WPCode specialist. TASK: Email notification routing. PROJECT INPUTS - Website type and business goal: [SITE TYPE + GOAL] - Audience, locale and key conversion: [AUDIENCE + LOCALE + CTA] - Current stack (WordPress/PHP, Kadence Theme, Kadence Blocks, WPCode, plugins): [VERIFIED VERSIONS] - Current page, screenshot, issue or reference: [URL OR SANITIZED DETAILS] - Constraints (budget, editor skill, hosting, launch date): [CONSTRAINTS] - Existing content, brand styles and approved data: [SOURCE MATERIAL] SPECIFIC OBJECTIVE Develop a practical, results-oriented solution for email notification routing in the context of this website. Map data fields and consent; keep credentials and pii out of prompt and logs. Explain what should be done with Kadence Theme settings, what should be built with Kadence Blocks, and when WPCode is warranted. Do not invent installed plugin capabilities or pretend you accessed the live site. DELIVER EXACTLY 1. A task-specific implementation blueprint for “Email notification routing” with exact WordPress/Kadence navigation or WPCode placement when relevant. 2. An ordered action checklist with dependencies and who owns each action. 3. Copy-ready artifacts where relevant (block hierarchy, settings matrix, sample copy, scoped CSS, PHP or vanilla JavaScript), with code fences and placement instructions. 4. Desktop/tablet/mobile acceptance tests, accessibility and security checks relevant to the task. 5. Failure cases, troubleshooting clues, rollback steps and final client-facing completion criteria. IMPLEMENTATION SAFETY Flag assumptions; favor native block controls over custom code; do not hardcode credentials or private data. For PHP/JS/CSS, provide exact location, activation scope, prerequisite checks, staging test, and undo method. If a plugin or version-specific behavior is uncertain, say what to verify first. Finish with a concise Definition of Done and a measurable business or UX outcome, without promising a result unsupported by data.
CRM field mapping
Create a tested, client-ready outcome for crm field mapping.
Act as a senior WordPress solution architect and Kadence Theme/Kadence Blocks/WPCode specialist. TASK: CRM field mapping. PROJECT INPUTS - Website type and business goal: [SITE TYPE + GOAL] - Audience, locale and key conversion: [AUDIENCE + LOCALE + CTA] - Current stack (WordPress/PHP, Kadence Theme, Kadence Blocks, WPCode, plugins): [VERIFIED VERSIONS] - Current page, screenshot, issue or reference: [URL OR SANITIZED DETAILS] - Constraints (budget, editor skill, hosting, launch date): [CONSTRAINTS] - Existing content, brand styles and approved data: [SOURCE MATERIAL] SPECIFIC OBJECTIVE Develop a practical, results-oriented solution for crm field mapping in the context of this website. Map data fields and consent; keep credentials and pii out of prompt and logs. Explain what should be done with Kadence Theme settings, what should be built with Kadence Blocks, and when WPCode is warranted. Do not invent installed plugin capabilities or pretend you accessed the live site. DELIVER EXACTLY 1. A task-specific implementation blueprint for “CRM field mapping” with exact WordPress/Kadence navigation or WPCode placement when relevant. 2. An ordered action checklist with dependencies and who owns each action. 3. Copy-ready artifacts where relevant (block hierarchy, settings matrix, sample copy, scoped CSS, PHP or vanilla JavaScript), with code fences and placement instructions. 4. Desktop/tablet/mobile acceptance tests, accessibility and security checks relevant to the task. 5. Failure cases, troubleshooting clues, rollback steps and final client-facing completion criteria. IMPLEMENTATION SAFETY Flag assumptions; favor native block controls over custom code; do not hardcode credentials or private data. For PHP/JS/CSS, provide exact location, activation scope, prerequisite checks, staging test, and undo method. If a plugin or version-specific behavior is uncertain, say what to verify first. Finish with a concise Definition of Done and a measurable business or UX outcome, without promising a result unsupported by data.
Webhook payload specification
Create a tested, client-ready outcome for webhook payload specification.
Act as a senior WordPress solution architect and Kadence Theme/Kadence Blocks/WPCode specialist. TASK: Webhook payload specification. PROJECT INPUTS - Website type and business goal: [SITE TYPE + GOAL] - Audience, locale and key conversion: [AUDIENCE + LOCALE + CTA] - Current stack (WordPress/PHP, Kadence Theme, Kadence Blocks, WPCode, plugins): [VERIFIED VERSIONS] - Current page, screenshot, issue or reference: [URL OR SANITIZED DETAILS] - Constraints (budget, editor skill, hosting, launch date): [CONSTRAINTS] - Existing content, brand styles and approved data: [SOURCE MATERIAL] SPECIFIC OBJECTIVE Develop a practical, results-oriented solution for webhook payload specification in the context of this website. Map data fields and consent; keep credentials and pii out of prompt and logs. Explain what should be done with Kadence Theme settings, what should be built with Kadence Blocks, and when WPCode is warranted. Do not invent installed plugin capabilities or pretend you accessed the live site. DELIVER EXACTLY 1. A task-specific implementation blueprint for “Webhook payload specification” with exact WordPress/Kadence navigation or WPCode placement when relevant. 2. An ordered action checklist with dependencies and who owns each action. 3. Copy-ready artifacts where relevant (block hierarchy, settings matrix, sample copy, scoped CSS, PHP or vanilla JavaScript), with code fences and placement instructions. 4. Desktop/tablet/mobile acceptance tests, accessibility and security checks relevant to the task. 5. Failure cases, troubleshooting clues, rollback steps and final client-facing completion criteria. IMPLEMENTATION SAFETY Flag assumptions; favor native block controls over custom code; do not hardcode credentials or private data. For PHP/JS/CSS, provide exact location, activation scope, prerequisite checks, staging test, and undo method. If a plugin or version-specific behavior is uncertain, say what to verify first. Finish with a concise Definition of Done and a measurable business or UX outcome, without promising a result unsupported by data.
Lead source attribution
Create a tested, client-ready outcome for lead source attribution.
Act as a senior WordPress solution architect and Kadence Theme/Kadence Blocks/WPCode specialist. TASK: Lead source attribution. PROJECT INPUTS - Website type and business goal: [SITE TYPE + GOAL] - Audience, locale and key conversion: [AUDIENCE + LOCALE + CTA] - Current stack (WordPress/PHP, Kadence Theme, Kadence Blocks, WPCode, plugins): [VERIFIED VERSIONS] - Current page, screenshot, issue or reference: [URL OR SANITIZED DETAILS] - Constraints (budget, editor skill, hosting, launch date): [CONSTRAINTS] - Existing content, brand styles and approved data: [SOURCE MATERIAL] SPECIFIC OBJECTIVE Develop a practical, results-oriented solution for lead source attribution in the context of this website. Map data fields and consent; keep credentials and pii out of prompt and logs. Explain what should be done with Kadence Theme settings, what should be built with Kadence Blocks, and when WPCode is warranted. Do not invent installed plugin capabilities or pretend you accessed the live site. DELIVER EXACTLY 1. A task-specific implementation blueprint for “Lead source attribution” with exact WordPress/Kadence navigation or WPCode placement when relevant. 2. An ordered action checklist with dependencies and who owns each action. 3. Copy-ready artifacts where relevant (block hierarchy, settings matrix, sample copy, scoped CSS, PHP or vanilla JavaScript), with code fences and placement instructions. 4. Desktop/tablet/mobile acceptance tests, accessibility and security checks relevant to the task. 5. Failure cases, troubleshooting clues, rollback steps and final client-facing completion criteria. IMPLEMENTATION SAFETY Flag assumptions; favor native block controls over custom code; do not hardcode credentials or private data. For PHP/JS/CSS, provide exact location, activation scope, prerequisite checks, staging test, and undo method. If a plugin or version-specific behavior is uncertain, say what to verify first. Finish with a concise Definition of Done and a measurable business or UX outcome, without promising a result unsupported by data.
Submission failure recovery
Create a tested, client-ready outcome for submission failure recovery.
Act as a senior WordPress solution architect and Kadence Theme/Kadence Blocks/WPCode specialist. TASK: Submission failure recovery. PROJECT INPUTS - Website type and business goal: [SITE TYPE + GOAL] - Audience, locale and key conversion: [AUDIENCE + LOCALE + CTA] - Current stack (WordPress/PHP, Kadence Theme, Kadence Blocks, WPCode, plugins): [VERIFIED VERSIONS] - Current page, screenshot, issue or reference: [URL OR SANITIZED DETAILS] - Constraints (budget, editor skill, hosting, launch date): [CONSTRAINTS] - Existing content, brand styles and approved data: [SOURCE MATERIAL] SPECIFIC OBJECTIVE Develop a practical, results-oriented solution for submission failure recovery in the context of this website. Map data fields and consent; keep credentials and pii out of prompt and logs. Explain what should be done with Kadence Theme settings, what should be built with Kadence Blocks, and when WPCode is warranted. Do not invent installed plugin capabilities or pretend you accessed the live site. DELIVER EXACTLY 1. A task-specific implementation blueprint for “Submission failure recovery” with exact WordPress/Kadence navigation or WPCode placement when relevant. 2. An ordered action checklist with dependencies and who owns each action. 3. Copy-ready artifacts where relevant (block hierarchy, settings matrix, sample copy, scoped CSS, PHP or vanilla JavaScript), with code fences and placement instructions. 4. Desktop/tablet/mobile acceptance tests, accessibility and security checks relevant to the task. 5. Failure cases, troubleshooting clues, rollback steps and final client-facing completion criteria. IMPLEMENTATION SAFETY Flag assumptions; favor native block controls over custom code; do not hardcode credentials or private data. For PHP/JS/CSS, provide exact location, activation scope, prerequisite checks, staging test, and undo method. If a plugin or version-specific behavior is uncertain, say what to verify first. Finish with a concise Definition of Done and a measurable business or UX outcome, without promising a result unsupported by data.
12. WPCode Snippet Architecture
Snippet requirement spec
Create a tested, client-ready outcome for snippet requirement spec.
Act as a senior WordPress solution architect and Kadence Theme/Kadence Blocks/WPCode specialist. TASK: Snippet requirement spec. PROJECT INPUTS - Website type and business goal: [SITE TYPE + GOAL] - Audience, locale and key conversion: [AUDIENCE + LOCALE + CTA] - Current stack (WordPress/PHP, Kadence Theme, Kadence Blocks, WPCode, plugins): [VERIFIED VERSIONS] - Current page, screenshot, issue or reference: [URL OR SANITIZED DETAILS] - Constraints (budget, editor skill, hosting, launch date): [CONSTRAINTS] - Existing content, brand styles and approved data: [SOURCE MATERIAL] SPECIFIC OBJECTIVE Develop a practical, results-oriented solution for snippet requirement spec in the context of this website. First decide whether kadence native settings, a reputable plugin, or wpcode is appropriate; avoid redundant snippets. Explain what should be done with Kadence Theme settings, what should be built with Kadence Blocks, and when WPCode is warranted. Do not invent installed plugin capabilities or pretend you accessed the live site. DELIVER EXACTLY 1. A task-specific implementation blueprint for “Snippet requirement spec” with exact WordPress/Kadence navigation or WPCode placement when relevant. 2. An ordered action checklist with dependencies and who owns each action. 3. Copy-ready artifacts where relevant (block hierarchy, settings matrix, sample copy, scoped CSS, PHP or vanilla JavaScript), with code fences and placement instructions. 4. Desktop/tablet/mobile acceptance tests, accessibility and security checks relevant to the task. 5. Failure cases, troubleshooting clues, rollback steps and final client-facing completion criteria. IMPLEMENTATION SAFETY Flag assumptions; favor native block controls over custom code; do not hardcode credentials or private data. For PHP/JS/CSS, provide exact location, activation scope, prerequisite checks, staging test, and undo method. If a plugin or version-specific behavior is uncertain, say what to verify first. Finish with a concise Definition of Done and a measurable business or UX outcome, without promising a result unsupported by data.
PHP versus JavaScript decision
Create a tested, client-ready outcome for php versus javascript decision.
Act as a senior WordPress solution architect and Kadence Theme/Kadence Blocks/WPCode specialist. TASK: PHP versus JavaScript decision. PROJECT INPUTS - Website type and business goal: [SITE TYPE + GOAL] - Audience, locale and key conversion: [AUDIENCE + LOCALE + CTA] - Current stack (WordPress/PHP, Kadence Theme, Kadence Blocks, WPCode, plugins): [VERIFIED VERSIONS] - Current page, screenshot, issue or reference: [URL OR SANITIZED DETAILS] - Constraints (budget, editor skill, hosting, launch date): [CONSTRAINTS] - Existing content, brand styles and approved data: [SOURCE MATERIAL] SPECIFIC OBJECTIVE Develop a practical, results-oriented solution for php versus javascript decision in the context of this website. First decide whether kadence native settings, a reputable plugin, or wpcode is appropriate; avoid redundant snippets. Explain what should be done with Kadence Theme settings, what should be built with Kadence Blocks, and when WPCode is warranted. Do not invent installed plugin capabilities or pretend you accessed the live site. DELIVER EXACTLY 1. A task-specific implementation blueprint for “PHP versus JavaScript decision” with exact WordPress/Kadence navigation or WPCode placement when relevant. 2. An ordered action checklist with dependencies and who owns each action. 3. Copy-ready artifacts where relevant (block hierarchy, settings matrix, sample copy, scoped CSS, PHP or vanilla JavaScript), with code fences and placement instructions. 4. Desktop/tablet/mobile acceptance tests, accessibility and security checks relevant to the task. 5. Failure cases, troubleshooting clues, rollback steps and final client-facing completion criteria. IMPLEMENTATION SAFETY Flag assumptions; favor native block controls over custom code; do not hardcode credentials or private data. For PHP/JS/CSS, provide exact location, activation scope, prerequisite checks, staging test, and undo method. If a plugin or version-specific behavior is uncertain, say what to verify first. Finish with a concise Definition of Done and a measurable business or UX outcome, without promising a result unsupported by data.
Sitewide versus conditional loading
Create a tested, client-ready outcome for sitewide versus conditional loading.
Act as a senior WordPress solution architect and Kadence Theme/Kadence Blocks/WPCode specialist. TASK: Sitewide versus conditional loading. PROJECT INPUTS - Website type and business goal: [SITE TYPE + GOAL] - Audience, locale and key conversion: [AUDIENCE + LOCALE + CTA] - Current stack (WordPress/PHP, Kadence Theme, Kadence Blocks, WPCode, plugins): [VERIFIED VERSIONS] - Current page, screenshot, issue or reference: [URL OR SANITIZED DETAILS] - Constraints (budget, editor skill, hosting, launch date): [CONSTRAINTS] - Existing content, brand styles and approved data: [SOURCE MATERIAL] SPECIFIC OBJECTIVE Develop a practical, results-oriented solution for sitewide versus conditional loading in the context of this website. First decide whether kadence native settings, a reputable plugin, or wpcode is appropriate; avoid redundant snippets. Explain what should be done with Kadence Theme settings, what should be built with Kadence Blocks, and when WPCode is warranted. Do not invent installed plugin capabilities or pretend you accessed the live site. DELIVER EXACTLY 1. A task-specific implementation blueprint for “Sitewide versus conditional loading” with exact WordPress/Kadence navigation or WPCode placement when relevant. 2. An ordered action checklist with dependencies and who owns each action. 3. Copy-ready artifacts where relevant (block hierarchy, settings matrix, sample copy, scoped CSS, PHP or vanilla JavaScript), with code fences and placement instructions. 4. Desktop/tablet/mobile acceptance tests, accessibility and security checks relevant to the task. 5. Failure cases, troubleshooting clues, rollback steps and final client-facing completion criteria. IMPLEMENTATION SAFETY Flag assumptions; favor native block controls over custom code; do not hardcode credentials or private data. For PHP/JS/CSS, provide exact location, activation scope, prerequisite checks, staging test, and undo method. If a plugin or version-specific behavior is uncertain, say what to verify first. Finish with a concise Definition of Done and a measurable business or UX outcome, without promising a result unsupported by data.
Frontend CSS snippet
Create a tested, client-ready outcome for frontend css snippet.
Act as a senior WordPress solution architect and Kadence Theme/Kadence Blocks/WPCode specialist. TASK: Frontend CSS snippet. PROJECT INPUTS - Website type and business goal: [SITE TYPE + GOAL] - Audience, locale and key conversion: [AUDIENCE + LOCALE + CTA] - Current stack (WordPress/PHP, Kadence Theme, Kadence Blocks, WPCode, plugins): [VERIFIED VERSIONS] - Current page, screenshot, issue or reference: [URL OR SANITIZED DETAILS] - Constraints (budget, editor skill, hosting, launch date): [CONSTRAINTS] - Existing content, brand styles and approved data: [SOURCE MATERIAL] SPECIFIC OBJECTIVE Develop a practical, results-oriented solution for frontend css snippet in the context of this website. First decide whether kadence native settings, a reputable plugin, or wpcode is appropriate; avoid redundant snippets. Explain what should be done with Kadence Theme settings, what should be built with Kadence Blocks, and when WPCode is warranted. Do not invent installed plugin capabilities or pretend you accessed the live site. DELIVER EXACTLY 1. A task-specific implementation blueprint for “Frontend CSS snippet” with exact WordPress/Kadence navigation or WPCode placement when relevant. 2. An ordered action checklist with dependencies and who owns each action. 3. Copy-ready artifacts where relevant (block hierarchy, settings matrix, sample copy, scoped CSS, PHP or vanilla JavaScript), with code fences and placement instructions. 4. Desktop/tablet/mobile acceptance tests, accessibility and security checks relevant to the task. 5. Failure cases, troubleshooting clues, rollback steps and final client-facing completion criteria. IMPLEMENTATION SAFETY Flag assumptions; favor native block controls over custom code; do not hardcode credentials or private data. For PHP/JS/CSS, provide exact location, activation scope, prerequisite checks, staging test, and undo method. If a plugin or version-specific behavior is uncertain, say what to verify first. Finish with a concise Definition of Done and a measurable business or UX outcome, without promising a result unsupported by data.
Header footer insertion plan
Create a tested, client-ready outcome for header footer insertion plan.
Act as a senior WordPress solution architect and Kadence Theme/Kadence Blocks/WPCode specialist. TASK: Header footer insertion plan. PROJECT INPUTS - Website type and business goal: [SITE TYPE + GOAL] - Audience, locale and key conversion: [AUDIENCE + LOCALE + CTA] - Current stack (WordPress/PHP, Kadence Theme, Kadence Blocks, WPCode, plugins): [VERIFIED VERSIONS] - Current page, screenshot, issue or reference: [URL OR SANITIZED DETAILS] - Constraints (budget, editor skill, hosting, launch date): [CONSTRAINTS] - Existing content, brand styles and approved data: [SOURCE MATERIAL] SPECIFIC OBJECTIVE Develop a practical, results-oriented solution for header footer insertion plan in the context of this website. First decide whether kadence native settings, a reputable plugin, or wpcode is appropriate; avoid redundant snippets. Explain what should be done with Kadence Theme settings, what should be built with Kadence Blocks, and when WPCode is warranted. Do not invent installed plugin capabilities or pretend you accessed the live site. DELIVER EXACTLY 1. A task-specific implementation blueprint for “Header footer insertion plan” with exact WordPress/Kadence navigation or WPCode placement when relevant. 2. An ordered action checklist with dependencies and who owns each action. 3. Copy-ready artifacts where relevant (block hierarchy, settings matrix, sample copy, scoped CSS, PHP or vanilla JavaScript), with code fences and placement instructions. 4. Desktop/tablet/mobile acceptance tests, accessibility and security checks relevant to the task. 5. Failure cases, troubleshooting clues, rollback steps and final client-facing completion criteria. IMPLEMENTATION SAFETY Flag assumptions; favor native block controls over custom code; do not hardcode credentials or private data. For PHP/JS/CSS, provide exact location, activation scope, prerequisite checks, staging test, and undo method. If a plugin or version-specific behavior is uncertain, say what to verify first. Finish with a concise Definition of Done and a measurable business or UX outcome, without promising a result unsupported by data.
Shortcode creation design
Create a tested, client-ready outcome for shortcode creation design.
Act as a senior WordPress solution architect and Kadence Theme/Kadence Blocks/WPCode specialist. TASK: Shortcode creation design. PROJECT INPUTS - Website type and business goal: [SITE TYPE + GOAL] - Audience, locale and key conversion: [AUDIENCE + LOCALE + CTA] - Current stack (WordPress/PHP, Kadence Theme, Kadence Blocks, WPCode, plugins): [VERIFIED VERSIONS] - Current page, screenshot, issue or reference: [URL OR SANITIZED DETAILS] - Constraints (budget, editor skill, hosting, launch date): [CONSTRAINTS] - Existing content, brand styles and approved data: [SOURCE MATERIAL] SPECIFIC OBJECTIVE Develop a practical, results-oriented solution for shortcode creation design in the context of this website. First decide whether kadence native settings, a reputable plugin, or wpcode is appropriate; avoid redundant snippets. Explain what should be done with Kadence Theme settings, what should be built with Kadence Blocks, and when WPCode is warranted. Do not invent installed plugin capabilities or pretend you accessed the live site. DELIVER EXACTLY 1. A task-specific implementation blueprint for “Shortcode creation design” with exact WordPress/Kadence navigation or WPCode placement when relevant. 2. An ordered action checklist with dependencies and who owns each action. 3. Copy-ready artifacts where relevant (block hierarchy, settings matrix, sample copy, scoped CSS, PHP or vanilla JavaScript), with code fences and placement instructions. 4. Desktop/tablet/mobile acceptance tests, accessibility and security checks relevant to the task. 5. Failure cases, troubleshooting clues, rollback steps and final client-facing completion criteria. IMPLEMENTATION SAFETY Flag assumptions; favor native block controls over custom code; do not hardcode credentials or private data. For PHP/JS/CSS, provide exact location, activation scope, prerequisite checks, staging test, and undo method. If a plugin or version-specific behavior is uncertain, say what to verify first. Finish with a concise Definition of Done and a measurable business or UX outcome, without promising a result unsupported by data.
PHP action hook snippet
Create a tested, client-ready outcome for php action hook snippet.
Act as a senior WordPress solution architect and Kadence Theme/Kadence Blocks/WPCode specialist. TASK: PHP action hook snippet. PROJECT INPUTS - Website type and business goal: [SITE TYPE + GOAL] - Audience, locale and key conversion: [AUDIENCE + LOCALE + CTA] - Current stack (WordPress/PHP, Kadence Theme, Kadence Blocks, WPCode, plugins): [VERIFIED VERSIONS] - Current page, screenshot, issue or reference: [URL OR SANITIZED DETAILS] - Constraints (budget, editor skill, hosting, launch date): [CONSTRAINTS] - Existing content, brand styles and approved data: [SOURCE MATERIAL] SPECIFIC OBJECTIVE Develop a practical, results-oriented solution for php action hook snippet in the context of this website. First decide whether kadence native settings, a reputable plugin, or wpcode is appropriate; avoid redundant snippets. Explain what should be done with Kadence Theme settings, what should be built with Kadence Blocks, and when WPCode is warranted. Do not invent installed plugin capabilities or pretend you accessed the live site. DELIVER EXACTLY 1. A task-specific implementation blueprint for “PHP action hook snippet” with exact WordPress/Kadence navigation or WPCode placement when relevant. 2. An ordered action checklist with dependencies and who owns each action. 3. Copy-ready artifacts where relevant (block hierarchy, settings matrix, sample copy, scoped CSS, PHP or vanilla JavaScript), with code fences and placement instructions. 4. Desktop/tablet/mobile acceptance tests, accessibility and security checks relevant to the task. 5. Failure cases, troubleshooting clues, rollback steps and final client-facing completion criteria. IMPLEMENTATION SAFETY Flag assumptions; favor native block controls over custom code; do not hardcode credentials or private data. For PHP/JS/CSS, provide exact location, activation scope, prerequisite checks, staging test, and undo method. If a plugin or version-specific behavior is uncertain, say what to verify first. Finish with a concise Definition of Done and a measurable business or UX outcome, without promising a result unsupported by data.
PHP filter hook snippet
Create a tested, client-ready outcome for php filter hook snippet.
Act as a senior WordPress solution architect and Kadence Theme/Kadence Blocks/WPCode specialist. TASK: PHP filter hook snippet. PROJECT INPUTS - Website type and business goal: [SITE TYPE + GOAL] - Audience, locale and key conversion: [AUDIENCE + LOCALE + CTA] - Current stack (WordPress/PHP, Kadence Theme, Kadence Blocks, WPCode, plugins): [VERIFIED VERSIONS] - Current page, screenshot, issue or reference: [URL OR SANITIZED DETAILS] - Constraints (budget, editor skill, hosting, launch date): [CONSTRAINTS] - Existing content, brand styles and approved data: [SOURCE MATERIAL] SPECIFIC OBJECTIVE Develop a practical, results-oriented solution for php filter hook snippet in the context of this website. First decide whether kadence native settings, a reputable plugin, or wpcode is appropriate; avoid redundant snippets. Explain what should be done with Kadence Theme settings, what should be built with Kadence Blocks, and when WPCode is warranted. Do not invent installed plugin capabilities or pretend you accessed the live site. DELIVER EXACTLY 1. A task-specific implementation blueprint for “PHP filter hook snippet” with exact WordPress/Kadence navigation or WPCode placement when relevant. 2. An ordered action checklist with dependencies and who owns each action. 3. Copy-ready artifacts where relevant (block hierarchy, settings matrix, sample copy, scoped CSS, PHP or vanilla JavaScript), with code fences and placement instructions. 4. Desktop/tablet/mobile acceptance tests, accessibility and security checks relevant to the task. 5. Failure cases, troubleshooting clues, rollback steps and final client-facing completion criteria. IMPLEMENTATION SAFETY Flag assumptions; favor native block controls over custom code; do not hardcode credentials or private data. For PHP/JS/CSS, provide exact location, activation scope, prerequisite checks, staging test, and undo method. If a plugin or version-specific behavior is uncertain, say what to verify first. Finish with a concise Definition of Done and a measurable business or UX outcome, without promising a result unsupported by data.
Snippet naming and documentation
Create a tested, client-ready outcome for snippet naming and documentation.
Act as a senior WordPress solution architect and Kadence Theme/Kadence Blocks/WPCode specialist. TASK: Snippet naming and documentation. PROJECT INPUTS - Website type and business goal: [SITE TYPE + GOAL] - Audience, locale and key conversion: [AUDIENCE + LOCALE + CTA] - Current stack (WordPress/PHP, Kadence Theme, Kadence Blocks, WPCode, plugins): [VERIFIED VERSIONS] - Current page, screenshot, issue or reference: [URL OR SANITIZED DETAILS] - Constraints (budget, editor skill, hosting, launch date): [CONSTRAINTS] - Existing content, brand styles and approved data: [SOURCE MATERIAL] SPECIFIC OBJECTIVE Develop a practical, results-oriented solution for snippet naming and documentation in the context of this website. First decide whether kadence native settings, a reputable plugin, or wpcode is appropriate; avoid redundant snippets. Explain what should be done with Kadence Theme settings, what should be built with Kadence Blocks, and when WPCode is warranted. Do not invent installed plugin capabilities or pretend you accessed the live site. DELIVER EXACTLY 1. A task-specific implementation blueprint for “Snippet naming and documentation” with exact WordPress/Kadence navigation or WPCode placement when relevant. 2. An ordered action checklist with dependencies and who owns each action. 3. Copy-ready artifacts where relevant (block hierarchy, settings matrix, sample copy, scoped CSS, PHP or vanilla JavaScript), with code fences and placement instructions. 4. Desktop/tablet/mobile acceptance tests, accessibility and security checks relevant to the task. 5. Failure cases, troubleshooting clues, rollback steps and final client-facing completion criteria. IMPLEMENTATION SAFETY Flag assumptions; favor native block controls over custom code; do not hardcode credentials or private data. For PHP/JS/CSS, provide exact location, activation scope, prerequisite checks, staging test, and undo method. If a plugin or version-specific behavior is uncertain, say what to verify first. Finish with a concise Definition of Done and a measurable business or UX outcome, without promising a result unsupported by data.
Snippet rollback protocol
Create a tested, client-ready outcome for snippet rollback protocol.
Act as a senior WordPress solution architect and Kadence Theme/Kadence Blocks/WPCode specialist. TASK: Snippet rollback protocol. PROJECT INPUTS - Website type and business goal: [SITE TYPE + GOAL] - Audience, locale and key conversion: [AUDIENCE + LOCALE + CTA] - Current stack (WordPress/PHP, Kadence Theme, Kadence Blocks, WPCode, plugins): [VERIFIED VERSIONS] - Current page, screenshot, issue or reference: [URL OR SANITIZED DETAILS] - Constraints (budget, editor skill, hosting, launch date): [CONSTRAINTS] - Existing content, brand styles and approved data: [SOURCE MATERIAL] SPECIFIC OBJECTIVE Develop a practical, results-oriented solution for snippet rollback protocol in the context of this website. First decide whether kadence native settings, a reputable plugin, or wpcode is appropriate; avoid redundant snippets. Explain what should be done with Kadence Theme settings, what should be built with Kadence Blocks, and when WPCode is warranted. Do not invent installed plugin capabilities or pretend you accessed the live site. DELIVER EXACTLY 1. A task-specific implementation blueprint for “Snippet rollback protocol” with exact WordPress/Kadence navigation or WPCode placement when relevant. 2. An ordered action checklist with dependencies and who owns each action. 3. Copy-ready artifacts where relevant (block hierarchy, settings matrix, sample copy, scoped CSS, PHP or vanilla JavaScript), with code fences and placement instructions. 4. Desktop/tablet/mobile acceptance tests, accessibility and security checks relevant to the task. 5. Failure cases, troubleshooting clues, rollback steps and final client-facing completion criteria. IMPLEMENTATION SAFETY Flag assumptions; favor native block controls over custom code; do not hardcode credentials or private data. For PHP/JS/CSS, provide exact location, activation scope, prerequisite checks, staging test, and undo method. If a plugin or version-specific behavior is uncertain, say what to verify first. Finish with a concise Definition of Done and a measurable business or UX outcome, without promising a result unsupported by data.
13. Safe PHP Customizations
Custom post type registration
Create a tested, client-ready outcome for custom post type registration.
Act as a senior WordPress solution architect and Kadence Theme/Kadence Blocks/WPCode specialist. TASK: Custom post type registration. PROJECT INPUTS - Website type and business goal: [SITE TYPE + GOAL] - Audience, locale and key conversion: [AUDIENCE + LOCALE + CTA] - Current stack (WordPress/PHP, Kadence Theme, Kadence Blocks, WPCode, plugins): [VERIFIED VERSIONS] - Current page, screenshot, issue or reference: [URL OR SANITIZED DETAILS] - Constraints (budget, editor skill, hosting, launch date): [CONSTRAINTS] - Existing content, brand styles and approved data: [SOURCE MATERIAL] SPECIFIC OBJECTIVE Develop a practical, results-oriented solution for custom post type registration in the context of this website. Use namespaced functions, escaping, sanitization, capability and nonce checks where applicable; no production-ready claim without testing. Explain what should be done with Kadence Theme settings, what should be built with Kadence Blocks, and when WPCode is warranted. Do not invent installed plugin capabilities or pretend you accessed the live site. DELIVER EXACTLY 1. A task-specific implementation blueprint for “Custom post type registration” with exact WordPress/Kadence navigation or WPCode placement when relevant. 2. An ordered action checklist with dependencies and who owns each action. 3. Copy-ready artifacts where relevant (block hierarchy, settings matrix, sample copy, scoped CSS, PHP or vanilla JavaScript), with code fences and placement instructions. 4. Desktop/tablet/mobile acceptance tests, accessibility and security checks relevant to the task. 5. Failure cases, troubleshooting clues, rollback steps and final client-facing completion criteria. IMPLEMENTATION SAFETY Flag assumptions; favor native block controls over custom code; do not hardcode credentials or private data. For PHP/JS/CSS, provide exact location, activation scope, prerequisite checks, staging test, and undo method. If a plugin or version-specific behavior is uncertain, say what to verify first. Finish with a concise Definition of Done and a measurable business or UX outcome, without promising a result unsupported by data.
Taxonomy registration
Create a tested, client-ready outcome for taxonomy registration.
Act as a senior WordPress solution architect and Kadence Theme/Kadence Blocks/WPCode specialist. TASK: Taxonomy registration. PROJECT INPUTS - Website type and business goal: [SITE TYPE + GOAL] - Audience, locale and key conversion: [AUDIENCE + LOCALE + CTA] - Current stack (WordPress/PHP, Kadence Theme, Kadence Blocks, WPCode, plugins): [VERIFIED VERSIONS] - Current page, screenshot, issue or reference: [URL OR SANITIZED DETAILS] - Constraints (budget, editor skill, hosting, launch date): [CONSTRAINTS] - Existing content, brand styles and approved data: [SOURCE MATERIAL] SPECIFIC OBJECTIVE Develop a practical, results-oriented solution for taxonomy registration in the context of this website. Use namespaced functions, escaping, sanitization, capability and nonce checks where applicable; no production-ready claim without testing. Explain what should be done with Kadence Theme settings, what should be built with Kadence Blocks, and when WPCode is warranted. Do not invent installed plugin capabilities or pretend you accessed the live site. DELIVER EXACTLY 1. A task-specific implementation blueprint for “Taxonomy registration” with exact WordPress/Kadence navigation or WPCode placement when relevant. 2. An ordered action checklist with dependencies and who owns each action. 3. Copy-ready artifacts where relevant (block hierarchy, settings matrix, sample copy, scoped CSS, PHP or vanilla JavaScript), with code fences and placement instructions. 4. Desktop/tablet/mobile acceptance tests, accessibility and security checks relevant to the task. 5. Failure cases, troubleshooting clues, rollback steps and final client-facing completion criteria. IMPLEMENTATION SAFETY Flag assumptions; favor native block controls over custom code; do not hardcode credentials or private data. For PHP/JS/CSS, provide exact location, activation scope, prerequisite checks, staging test, and undo method. If a plugin or version-specific behavior is uncertain, say what to verify first. Finish with a concise Definition of Done and a measurable business or UX outcome, without promising a result unsupported by data.
Custom shortcode rendering
Create a tested, client-ready outcome for custom shortcode rendering.
Act as a senior WordPress solution architect and Kadence Theme/Kadence Blocks/WPCode specialist. TASK: Custom shortcode rendering. PROJECT INPUTS - Website type and business goal: [SITE TYPE + GOAL] - Audience, locale and key conversion: [AUDIENCE + LOCALE + CTA] - Current stack (WordPress/PHP, Kadence Theme, Kadence Blocks, WPCode, plugins): [VERIFIED VERSIONS] - Current page, screenshot, issue or reference: [URL OR SANITIZED DETAILS] - Constraints (budget, editor skill, hosting, launch date): [CONSTRAINTS] - Existing content, brand styles and approved data: [SOURCE MATERIAL] SPECIFIC OBJECTIVE Develop a practical, results-oriented solution for custom shortcode rendering in the context of this website. Use namespaced functions, escaping, sanitization, capability and nonce checks where applicable; no production-ready claim without testing. Explain what should be done with Kadence Theme settings, what should be built with Kadence Blocks, and when WPCode is warranted. Do not invent installed plugin capabilities or pretend you accessed the live site. DELIVER EXACTLY 1. A task-specific implementation blueprint for “Custom shortcode rendering” with exact WordPress/Kadence navigation or WPCode placement when relevant. 2. An ordered action checklist with dependencies and who owns each action. 3. Copy-ready artifacts where relevant (block hierarchy, settings matrix, sample copy, scoped CSS, PHP or vanilla JavaScript), with code fences and placement instructions. 4. Desktop/tablet/mobile acceptance tests, accessibility and security checks relevant to the task. 5. Failure cases, troubleshooting clues, rollback steps and final client-facing completion criteria. IMPLEMENTATION SAFETY Flag assumptions; favor native block controls over custom code; do not hardcode credentials or private data. For PHP/JS/CSS, provide exact location, activation scope, prerequisite checks, staging test, and undo method. If a plugin or version-specific behavior is uncertain, say what to verify first. Finish with a concise Definition of Done and a measurable business or UX outcome, without promising a result unsupported by data.
Admin dashboard notice
Create a tested, client-ready outcome for admin dashboard notice.
Act as a senior WordPress solution architect and Kadence Theme/Kadence Blocks/WPCode specialist. TASK: Admin dashboard notice. PROJECT INPUTS - Website type and business goal: [SITE TYPE + GOAL] - Audience, locale and key conversion: [AUDIENCE + LOCALE + CTA] - Current stack (WordPress/PHP, Kadence Theme, Kadence Blocks, WPCode, plugins): [VERIFIED VERSIONS] - Current page, screenshot, issue or reference: [URL OR SANITIZED DETAILS] - Constraints (budget, editor skill, hosting, launch date): [CONSTRAINTS] - Existing content, brand styles and approved data: [SOURCE MATERIAL] SPECIFIC OBJECTIVE Develop a practical, results-oriented solution for admin dashboard notice in the context of this website. Use namespaced functions, escaping, sanitization, capability and nonce checks where applicable; no production-ready claim without testing. Explain what should be done with Kadence Theme settings, what should be built with Kadence Blocks, and when WPCode is warranted. Do not invent installed plugin capabilities or pretend you accessed the live site. DELIVER EXACTLY 1. A task-specific implementation blueprint for “Admin dashboard notice” with exact WordPress/Kadence navigation or WPCode placement when relevant. 2. An ordered action checklist with dependencies and who owns each action. 3. Copy-ready artifacts where relevant (block hierarchy, settings matrix, sample copy, scoped CSS, PHP or vanilla JavaScript), with code fences and placement instructions. 4. Desktop/tablet/mobile acceptance tests, accessibility and security checks relevant to the task. 5. Failure cases, troubleshooting clues, rollback steps and final client-facing completion criteria. IMPLEMENTATION SAFETY Flag assumptions; favor native block controls over custom code; do not hardcode credentials or private data. For PHP/JS/CSS, provide exact location, activation scope, prerequisite checks, staging test, and undo method. If a plugin or version-specific behavior is uncertain, say what to verify first. Finish with a concise Definition of Done and a measurable business or UX outcome, without promising a result unsupported by data.
Login redirect rules
Create a tested, client-ready outcome for login redirect rules.
Act as a senior WordPress solution architect and Kadence Theme/Kadence Blocks/WPCode specialist. TASK: Login redirect rules. PROJECT INPUTS - Website type and business goal: [SITE TYPE + GOAL] - Audience, locale and key conversion: [AUDIENCE + LOCALE + CTA] - Current stack (WordPress/PHP, Kadence Theme, Kadence Blocks, WPCode, plugins): [VERIFIED VERSIONS] - Current page, screenshot, issue or reference: [URL OR SANITIZED DETAILS] - Constraints (budget, editor skill, hosting, launch date): [CONSTRAINTS] - Existing content, brand styles and approved data: [SOURCE MATERIAL] SPECIFIC OBJECTIVE Develop a practical, results-oriented solution for login redirect rules in the context of this website. Use namespaced functions, escaping, sanitization, capability and nonce checks where applicable; no production-ready claim without testing. Explain what should be done with Kadence Theme settings, what should be built with Kadence Blocks, and when WPCode is warranted. Do not invent installed plugin capabilities or pretend you accessed the live site. DELIVER EXACTLY 1. A task-specific implementation blueprint for “Login redirect rules” with exact WordPress/Kadence navigation or WPCode placement when relevant. 2. An ordered action checklist with dependencies and who owns each action. 3. Copy-ready artifacts where relevant (block hierarchy, settings matrix, sample copy, scoped CSS, PHP or vanilla JavaScript), with code fences and placement instructions. 4. Desktop/tablet/mobile acceptance tests, accessibility and security checks relevant to the task. 5. Failure cases, troubleshooting clues, rollback steps and final client-facing completion criteria. IMPLEMENTATION SAFETY Flag assumptions; favor native block controls over custom code; do not hardcode credentials or private data. For PHP/JS/CSS, provide exact location, activation scope, prerequisite checks, staging test, and undo method. If a plugin or version-specific behavior is uncertain, say what to verify first. Finish with a concise Definition of Done and a measurable business or UX outcome, without promising a result unsupported by data.
Custom excerpt logic
Create a tested, client-ready outcome for custom excerpt logic.
Act as a senior WordPress solution architect and Kadence Theme/Kadence Blocks/WPCode specialist. TASK: Custom excerpt logic. PROJECT INPUTS - Website type and business goal: [SITE TYPE + GOAL] - Audience, locale and key conversion: [AUDIENCE + LOCALE + CTA] - Current stack (WordPress/PHP, Kadence Theme, Kadence Blocks, WPCode, plugins): [VERIFIED VERSIONS] - Current page, screenshot, issue or reference: [URL OR SANITIZED DETAILS] - Constraints (budget, editor skill, hosting, launch date): [CONSTRAINTS] - Existing content, brand styles and approved data: [SOURCE MATERIAL] SPECIFIC OBJECTIVE Develop a practical, results-oriented solution for custom excerpt logic in the context of this website. Use namespaced functions, escaping, sanitization, capability and nonce checks where applicable; no production-ready claim without testing. Explain what should be done with Kadence Theme settings, what should be built with Kadence Blocks, and when WPCode is warranted. Do not invent installed plugin capabilities or pretend you accessed the live site. DELIVER EXACTLY 1. A task-specific implementation blueprint for “Custom excerpt logic” with exact WordPress/Kadence navigation or WPCode placement when relevant. 2. An ordered action checklist with dependencies and who owns each action. 3. Copy-ready artifacts where relevant (block hierarchy, settings matrix, sample copy, scoped CSS, PHP or vanilla JavaScript), with code fences and placement instructions. 4. Desktop/tablet/mobile acceptance tests, accessibility and security checks relevant to the task. 5. Failure cases, troubleshooting clues, rollback steps and final client-facing completion criteria. IMPLEMENTATION SAFETY Flag assumptions; favor native block controls over custom code; do not hardcode credentials or private data. For PHP/JS/CSS, provide exact location, activation scope, prerequisite checks, staging test, and undo method. If a plugin or version-specific behavior is uncertain, say what to verify first. Finish with a concise Definition of Done and a measurable business or UX outcome, without promising a result unsupported by data.
Body class adjustment
Create a tested, client-ready outcome for body class adjustment.
Act as a senior WordPress solution architect and Kadence Theme/Kadence Blocks/WPCode specialist. TASK: Body class adjustment. PROJECT INPUTS - Website type and business goal: [SITE TYPE + GOAL] - Audience, locale and key conversion: [AUDIENCE + LOCALE + CTA] - Current stack (WordPress/PHP, Kadence Theme, Kadence Blocks, WPCode, plugins): [VERIFIED VERSIONS] - Current page, screenshot, issue or reference: [URL OR SANITIZED DETAILS] - Constraints (budget, editor skill, hosting, launch date): [CONSTRAINTS] - Existing content, brand styles and approved data: [SOURCE MATERIAL] SPECIFIC OBJECTIVE Develop a practical, results-oriented solution for body class adjustment in the context of this website. Use namespaced functions, escaping, sanitization, capability and nonce checks where applicable; no production-ready claim without testing. Explain what should be done with Kadence Theme settings, what should be built with Kadence Blocks, and when WPCode is warranted. Do not invent installed plugin capabilities or pretend you accessed the live site. DELIVER EXACTLY 1. A task-specific implementation blueprint for “Body class adjustment” with exact WordPress/Kadence navigation or WPCode placement when relevant. 2. An ordered action checklist with dependencies and who owns each action. 3. Copy-ready artifacts where relevant (block hierarchy, settings matrix, sample copy, scoped CSS, PHP or vanilla JavaScript), with code fences and placement instructions. 4. Desktop/tablet/mobile acceptance tests, accessibility and security checks relevant to the task. 5. Failure cases, troubleshooting clues, rollback steps and final client-facing completion criteria. IMPLEMENTATION SAFETY Flag assumptions; favor native block controls over custom code; do not hardcode credentials or private data. For PHP/JS/CSS, provide exact location, activation scope, prerequisite checks, staging test, and undo method. If a plugin or version-specific behavior is uncertain, say what to verify first. Finish with a concise Definition of Done and a measurable business or UX outcome, without promising a result unsupported by data.
WooCommerce hook customization
Create a tested, client-ready outcome for woocommerce hook customization.
Act as a senior WordPress solution architect and Kadence Theme/Kadence Blocks/WPCode specialist. TASK: WooCommerce hook customization. PROJECT INPUTS - Website type and business goal: [SITE TYPE + GOAL] - Audience, locale and key conversion: [AUDIENCE + LOCALE + CTA] - Current stack (WordPress/PHP, Kadence Theme, Kadence Blocks, WPCode, plugins): [VERIFIED VERSIONS] - Current page, screenshot, issue or reference: [URL OR SANITIZED DETAILS] - Constraints (budget, editor skill, hosting, launch date): [CONSTRAINTS] - Existing content, brand styles and approved data: [SOURCE MATERIAL] SPECIFIC OBJECTIVE Develop a practical, results-oriented solution for woocommerce hook customization in the context of this website. Use namespaced functions, escaping, sanitization, capability and nonce checks where applicable; no production-ready claim without testing. Explain what should be done with Kadence Theme settings, what should be built with Kadence Blocks, and when WPCode is warranted. Do not invent installed plugin capabilities or pretend you accessed the live site. DELIVER EXACTLY 1. A task-specific implementation blueprint for “WooCommerce hook customization” with exact WordPress/Kadence navigation or WPCode placement when relevant. 2. An ordered action checklist with dependencies and who owns each action. 3. Copy-ready artifacts where relevant (block hierarchy, settings matrix, sample copy, scoped CSS, PHP or vanilla JavaScript), with code fences and placement instructions. 4. Desktop/tablet/mobile acceptance tests, accessibility and security checks relevant to the task. 5. Failure cases, troubleshooting clues, rollback steps and final client-facing completion criteria. IMPLEMENTATION SAFETY Flag assumptions; favor native block controls over custom code; do not hardcode credentials or private data. For PHP/JS/CSS, provide exact location, activation scope, prerequisite checks, staging test, and undo method. If a plugin or version-specific behavior is uncertain, say what to verify first. Finish with a concise Definition of Done and a measurable business or UX outcome, without promising a result unsupported by data.
Capability check pattern
Create a tested, client-ready outcome for capability check pattern.
Act as a senior WordPress solution architect and Kadence Theme/Kadence Blocks/WPCode specialist. TASK: Capability check pattern. PROJECT INPUTS - Website type and business goal: [SITE TYPE + GOAL] - Audience, locale and key conversion: [AUDIENCE + LOCALE + CTA] - Current stack (WordPress/PHP, Kadence Theme, Kadence Blocks, WPCode, plugins): [VERIFIED VERSIONS] - Current page, screenshot, issue or reference: [URL OR SANITIZED DETAILS] - Constraints (budget, editor skill, hosting, launch date): [CONSTRAINTS] - Existing content, brand styles and approved data: [SOURCE MATERIAL] SPECIFIC OBJECTIVE Develop a practical, results-oriented solution for capability check pattern in the context of this website. Use namespaced functions, escaping, sanitization, capability and nonce checks where applicable; no production-ready claim without testing. Explain what should be done with Kadence Theme settings, what should be built with Kadence Blocks, and when WPCode is warranted. Do not invent installed plugin capabilities or pretend you accessed the live site. DELIVER EXACTLY 1. A task-specific implementation blueprint for “Capability check pattern” with exact WordPress/Kadence navigation or WPCode placement when relevant. 2. An ordered action checklist with dependencies and who owns each action. 3. Copy-ready artifacts where relevant (block hierarchy, settings matrix, sample copy, scoped CSS, PHP or vanilla JavaScript), with code fences and placement instructions. 4. Desktop/tablet/mobile acceptance tests, accessibility and security checks relevant to the task. 5. Failure cases, troubleshooting clues, rollback steps and final client-facing completion criteria. IMPLEMENTATION SAFETY Flag assumptions; favor native block controls over custom code; do not hardcode credentials or private data. For PHP/JS/CSS, provide exact location, activation scope, prerequisite checks, staging test, and undo method. If a plugin or version-specific behavior is uncertain, say what to verify first. Finish with a concise Definition of Done and a measurable business or UX outcome, without promising a result unsupported by data.
Nonce and sanitization review
Create a tested, client-ready outcome for nonce and sanitization review.
Act as a senior WordPress solution architect and Kadence Theme/Kadence Blocks/WPCode specialist. TASK: Nonce and sanitization review. PROJECT INPUTS - Website type and business goal: [SITE TYPE + GOAL] - Audience, locale and key conversion: [AUDIENCE + LOCALE + CTA] - Current stack (WordPress/PHP, Kadence Theme, Kadence Blocks, WPCode, plugins): [VERIFIED VERSIONS] - Current page, screenshot, issue or reference: [URL OR SANITIZED DETAILS] - Constraints (budget, editor skill, hosting, launch date): [CONSTRAINTS] - Existing content, brand styles and approved data: [SOURCE MATERIAL] SPECIFIC OBJECTIVE Develop a practical, results-oriented solution for nonce and sanitization review in the context of this website. Use namespaced functions, escaping, sanitization, capability and nonce checks where applicable; no production-ready claim without testing. Explain what should be done with Kadence Theme settings, what should be built with Kadence Blocks, and when WPCode is warranted. Do not invent installed plugin capabilities or pretend you accessed the live site. DELIVER EXACTLY 1. A task-specific implementation blueprint for “Nonce and sanitization review” with exact WordPress/Kadence navigation or WPCode placement when relevant. 2. An ordered action checklist with dependencies and who owns each action. 3. Copy-ready artifacts where relevant (block hierarchy, settings matrix, sample copy, scoped CSS, PHP or vanilla JavaScript), with code fences and placement instructions. 4. Desktop/tablet/mobile acceptance tests, accessibility and security checks relevant to the task. 5. Failure cases, troubleshooting clues, rollback steps and final client-facing completion criteria. IMPLEMENTATION SAFETY Flag assumptions; favor native block controls over custom code; do not hardcode credentials or private data. For PHP/JS/CSS, provide exact location, activation scope, prerequisite checks, staging test, and undo method. If a plugin or version-specific behavior is uncertain, say what to verify first. Finish with a concise Definition of Done and a measurable business or UX outcome, without promising a result unsupported by data.
14. CSS & Responsive Refinements
Scoped CSS selector design
Create a tested, client-ready outcome for scoped css selector design.
Act as a senior WordPress solution architect and Kadence Theme/Kadence Blocks/WPCode specialist. TASK: Scoped CSS selector design. PROJECT INPUTS - Website type and business goal: [SITE TYPE + GOAL] - Audience, locale and key conversion: [AUDIENCE + LOCALE + CTA] - Current stack (WordPress/PHP, Kadence Theme, Kadence Blocks, WPCode, plugins): [VERIFIED VERSIONS] - Current page, screenshot, issue or reference: [URL OR SANITIZED DETAILS] - Constraints (budget, editor skill, hosting, launch date): [CONSTRAINTS] - Existing content, brand styles and approved data: [SOURCE MATERIAL] SPECIFIC OBJECTIVE Develop a practical, results-oriented solution for scoped css selector design in the context of this website. Scope selectors under a unique parent class; avoid !important unless justified and test 320px to wide screens. Explain what should be done with Kadence Theme settings, what should be built with Kadence Blocks, and when WPCode is warranted. Do not invent installed plugin capabilities or pretend you accessed the live site. DELIVER EXACTLY 1. A task-specific implementation blueprint for “Scoped CSS selector design” with exact WordPress/Kadence navigation or WPCode placement when relevant. 2. An ordered action checklist with dependencies and who owns each action. 3. Copy-ready artifacts where relevant (block hierarchy, settings matrix, sample copy, scoped CSS, PHP or vanilla JavaScript), with code fences and placement instructions. 4. Desktop/tablet/mobile acceptance tests, accessibility and security checks relevant to the task. 5. Failure cases, troubleshooting clues, rollback steps and final client-facing completion criteria. IMPLEMENTATION SAFETY Flag assumptions; favor native block controls over custom code; do not hardcode credentials or private data. For PHP/JS/CSS, provide exact location, activation scope, prerequisite checks, staging test, and undo method. If a plugin or version-specific behavior is uncertain, say what to verify first. Finish with a concise Definition of Done and a measurable business or UX outcome, without promising a result unsupported by data.
Responsive breakpoint review
Create a tested, client-ready outcome for responsive breakpoint review.
Act as a senior WordPress solution architect and Kadence Theme/Kadence Blocks/WPCode specialist. TASK: Responsive breakpoint review. PROJECT INPUTS - Website type and business goal: [SITE TYPE + GOAL] - Audience, locale and key conversion: [AUDIENCE + LOCALE + CTA] - Current stack (WordPress/PHP, Kadence Theme, Kadence Blocks, WPCode, plugins): [VERIFIED VERSIONS] - Current page, screenshot, issue or reference: [URL OR SANITIZED DETAILS] - Constraints (budget, editor skill, hosting, launch date): [CONSTRAINTS] - Existing content, brand styles and approved data: [SOURCE MATERIAL] SPECIFIC OBJECTIVE Develop a practical, results-oriented solution for responsive breakpoint review in the context of this website. Scope selectors under a unique parent class; avoid !important unless justified and test 320px to wide screens. Explain what should be done with Kadence Theme settings, what should be built with Kadence Blocks, and when WPCode is warranted. Do not invent installed plugin capabilities or pretend you accessed the live site. DELIVER EXACTLY 1. A task-specific implementation blueprint for “Responsive breakpoint review” with exact WordPress/Kadence navigation or WPCode placement when relevant. 2. An ordered action checklist with dependencies and who owns each action. 3. Copy-ready artifacts where relevant (block hierarchy, settings matrix, sample copy, scoped CSS, PHP or vanilla JavaScript), with code fences and placement instructions. 4. Desktop/tablet/mobile acceptance tests, accessibility and security checks relevant to the task. 5. Failure cases, troubleshooting clues, rollback steps and final client-facing completion criteria. IMPLEMENTATION SAFETY Flag assumptions; favor native block controls over custom code; do not hardcode credentials or private data. For PHP/JS/CSS, provide exact location, activation scope, prerequisite checks, staging test, and undo method. If a plugin or version-specific behavior is uncertain, say what to verify first. Finish with a concise Definition of Done and a measurable business or UX outcome, without promising a result unsupported by data.
Fluid type and spacing
Create a tested, client-ready outcome for fluid type and spacing.
Act as a senior WordPress solution architect and Kadence Theme/Kadence Blocks/WPCode specialist. TASK: Fluid type and spacing. PROJECT INPUTS - Website type and business goal: [SITE TYPE + GOAL] - Audience, locale and key conversion: [AUDIENCE + LOCALE + CTA] - Current stack (WordPress/PHP, Kadence Theme, Kadence Blocks, WPCode, plugins): [VERIFIED VERSIONS] - Current page, screenshot, issue or reference: [URL OR SANITIZED DETAILS] - Constraints (budget, editor skill, hosting, launch date): [CONSTRAINTS] - Existing content, brand styles and approved data: [SOURCE MATERIAL] SPECIFIC OBJECTIVE Develop a practical, results-oriented solution for fluid type and spacing in the context of this website. Scope selectors under a unique parent class; avoid !important unless justified and test 320px to wide screens. Explain what should be done with Kadence Theme settings, what should be built with Kadence Blocks, and when WPCode is warranted. Do not invent installed plugin capabilities or pretend you accessed the live site. DELIVER EXACTLY 1. A task-specific implementation blueprint for “Fluid type and spacing” with exact WordPress/Kadence navigation or WPCode placement when relevant. 2. An ordered action checklist with dependencies and who owns each action. 3. Copy-ready artifacts where relevant (block hierarchy, settings matrix, sample copy, scoped CSS, PHP or vanilla JavaScript), with code fences and placement instructions. 4. Desktop/tablet/mobile acceptance tests, accessibility and security checks relevant to the task. 5. Failure cases, troubleshooting clues, rollback steps and final client-facing completion criteria. IMPLEMENTATION SAFETY Flag assumptions; favor native block controls over custom code; do not hardcode credentials or private data. For PHP/JS/CSS, provide exact location, activation scope, prerequisite checks, staging test, and undo method. If a plugin or version-specific behavior is uncertain, say what to verify first. Finish with a concise Definition of Done and a measurable business or UX outcome, without promising a result unsupported by data.
Header mobile overflow fix
Create a tested, client-ready outcome for header mobile overflow fix.
Act as a senior WordPress solution architect and Kadence Theme/Kadence Blocks/WPCode specialist. TASK: Header mobile overflow fix. PROJECT INPUTS - Website type and business goal: [SITE TYPE + GOAL] - Audience, locale and key conversion: [AUDIENCE + LOCALE + CTA] - Current stack (WordPress/PHP, Kadence Theme, Kadence Blocks, WPCode, plugins): [VERIFIED VERSIONS] - Current page, screenshot, issue or reference: [URL OR SANITIZED DETAILS] - Constraints (budget, editor skill, hosting, launch date): [CONSTRAINTS] - Existing content, brand styles and approved data: [SOURCE MATERIAL] SPECIFIC OBJECTIVE Develop a practical, results-oriented solution for header mobile overflow fix in the context of this website. Scope selectors under a unique parent class; avoid !important unless justified and test 320px to wide screens. Explain what should be done with Kadence Theme settings, what should be built with Kadence Blocks, and when WPCode is warranted. Do not invent installed plugin capabilities or pretend you accessed the live site. DELIVER EXACTLY 1. A task-specific implementation blueprint for “Header mobile overflow fix” with exact WordPress/Kadence navigation or WPCode placement when relevant. 2. An ordered action checklist with dependencies and who owns each action. 3. Copy-ready artifacts where relevant (block hierarchy, settings matrix, sample copy, scoped CSS, PHP or vanilla JavaScript), with code fences and placement instructions. 4. Desktop/tablet/mobile acceptance tests, accessibility and security checks relevant to the task. 5. Failure cases, troubleshooting clues, rollback steps and final client-facing completion criteria. IMPLEMENTATION SAFETY Flag assumptions; favor native block controls over custom code; do not hardcode credentials or private data. For PHP/JS/CSS, provide exact location, activation scope, prerequisite checks, staging test, and undo method. If a plugin or version-specific behavior is uncertain, say what to verify first. Finish with a concise Definition of Done and a measurable business or UX outcome, without promising a result unsupported by data.
Grid alignment repair
Create a tested, client-ready outcome for grid alignment repair.
Act as a senior WordPress solution architect and Kadence Theme/Kadence Blocks/WPCode specialist. TASK: Grid alignment repair. PROJECT INPUTS - Website type and business goal: [SITE TYPE + GOAL] - Audience, locale and key conversion: [AUDIENCE + LOCALE + CTA] - Current stack (WordPress/PHP, Kadence Theme, Kadence Blocks, WPCode, plugins): [VERIFIED VERSIONS] - Current page, screenshot, issue or reference: [URL OR SANITIZED DETAILS] - Constraints (budget, editor skill, hosting, launch date): [CONSTRAINTS] - Existing content, brand styles and approved data: [SOURCE MATERIAL] SPECIFIC OBJECTIVE Develop a practical, results-oriented solution for grid alignment repair in the context of this website. Scope selectors under a unique parent class; avoid !important unless justified and test 320px to wide screens. Explain what should be done with Kadence Theme settings, what should be built with Kadence Blocks, and when WPCode is warranted. Do not invent installed plugin capabilities or pretend you accessed the live site. DELIVER EXACTLY 1. A task-specific implementation blueprint for “Grid alignment repair” with exact WordPress/Kadence navigation or WPCode placement when relevant. 2. An ordered action checklist with dependencies and who owns each action. 3. Copy-ready artifacts where relevant (block hierarchy, settings matrix, sample copy, scoped CSS, PHP or vanilla JavaScript), with code fences and placement instructions. 4. Desktop/tablet/mobile acceptance tests, accessibility and security checks relevant to the task. 5. Failure cases, troubleshooting clues, rollback steps and final client-facing completion criteria. IMPLEMENTATION SAFETY Flag assumptions; favor native block controls over custom code; do not hardcode credentials or private data. For PHP/JS/CSS, provide exact location, activation scope, prerequisite checks, staging test, and undo method. If a plugin or version-specific behavior is uncertain, say what to verify first. Finish with a concise Definition of Done and a measurable business or UX outcome, without promising a result unsupported by data.
Button state styling
Create a tested, client-ready outcome for button state styling.
Act as a senior WordPress solution architect and Kadence Theme/Kadence Blocks/WPCode specialist. TASK: Button state styling. PROJECT INPUTS - Website type and business goal: [SITE TYPE + GOAL] - Audience, locale and key conversion: [AUDIENCE + LOCALE + CTA] - Current stack (WordPress/PHP, Kadence Theme, Kadence Blocks, WPCode, plugins): [VERIFIED VERSIONS] - Current page, screenshot, issue or reference: [URL OR SANITIZED DETAILS] - Constraints (budget, editor skill, hosting, launch date): [CONSTRAINTS] - Existing content, brand styles and approved data: [SOURCE MATERIAL] SPECIFIC OBJECTIVE Develop a practical, results-oriented solution for button state styling in the context of this website. Scope selectors under a unique parent class; avoid !important unless justified and test 320px to wide screens. Explain what should be done with Kadence Theme settings, what should be built with Kadence Blocks, and when WPCode is warranted. Do not invent installed plugin capabilities or pretend you accessed the live site. DELIVER EXACTLY 1. A task-specific implementation blueprint for “Button state styling” with exact WordPress/Kadence navigation or WPCode placement when relevant. 2. An ordered action checklist with dependencies and who owns each action. 3. Copy-ready artifacts where relevant (block hierarchy, settings matrix, sample copy, scoped CSS, PHP or vanilla JavaScript), with code fences and placement instructions. 4. Desktop/tablet/mobile acceptance tests, accessibility and security checks relevant to the task. 5. Failure cases, troubleshooting clues, rollback steps and final client-facing completion criteria. IMPLEMENTATION SAFETY Flag assumptions; favor native block controls over custom code; do not hardcode credentials or private data. For PHP/JS/CSS, provide exact location, activation scope, prerequisite checks, staging test, and undo method. If a plugin or version-specific behavior is uncertain, say what to verify first. Finish with a concise Definition of Done and a measurable business or UX outcome, without promising a result unsupported by data.
Dark section contrast
Create a tested, client-ready outcome for dark section contrast.
Act as a senior WordPress solution architect and Kadence Theme/Kadence Blocks/WPCode specialist. TASK: Dark section contrast. PROJECT INPUTS - Website type and business goal: [SITE TYPE + GOAL] - Audience, locale and key conversion: [AUDIENCE + LOCALE + CTA] - Current stack (WordPress/PHP, Kadence Theme, Kadence Blocks, WPCode, plugins): [VERIFIED VERSIONS] - Current page, screenshot, issue or reference: [URL OR SANITIZED DETAILS] - Constraints (budget, editor skill, hosting, launch date): [CONSTRAINTS] - Existing content, brand styles and approved data: [SOURCE MATERIAL] SPECIFIC OBJECTIVE Develop a practical, results-oriented solution for dark section contrast in the context of this website. Scope selectors under a unique parent class; avoid !important unless justified and test 320px to wide screens. Explain what should be done with Kadence Theme settings, what should be built with Kadence Blocks, and when WPCode is warranted. Do not invent installed plugin capabilities or pretend you accessed the live site. DELIVER EXACTLY 1. A task-specific implementation blueprint for “Dark section contrast” with exact WordPress/Kadence navigation or WPCode placement when relevant. 2. An ordered action checklist with dependencies and who owns each action. 3. Copy-ready artifacts where relevant (block hierarchy, settings matrix, sample copy, scoped CSS, PHP or vanilla JavaScript), with code fences and placement instructions. 4. Desktop/tablet/mobile acceptance tests, accessibility and security checks relevant to the task. 5. Failure cases, troubleshooting clues, rollback steps and final client-facing completion criteria. IMPLEMENTATION SAFETY Flag assumptions; favor native block controls over custom code; do not hardcode credentials or private data. For PHP/JS/CSS, provide exact location, activation scope, prerequisite checks, staging test, and undo method. If a plugin or version-specific behavior is uncertain, say what to verify first. Finish with a concise Definition of Done and a measurable business or UX outcome, without promising a result unsupported by data.
Sticky element collision fix
Create a tested, client-ready outcome for sticky element collision fix.
Act as a senior WordPress solution architect and Kadence Theme/Kadence Blocks/WPCode specialist. TASK: Sticky element collision fix. PROJECT INPUTS - Website type and business goal: [SITE TYPE + GOAL] - Audience, locale and key conversion: [AUDIENCE + LOCALE + CTA] - Current stack (WordPress/PHP, Kadence Theme, Kadence Blocks, WPCode, plugins): [VERIFIED VERSIONS] - Current page, screenshot, issue or reference: [URL OR SANITIZED DETAILS] - Constraints (budget, editor skill, hosting, launch date): [CONSTRAINTS] - Existing content, brand styles and approved data: [SOURCE MATERIAL] SPECIFIC OBJECTIVE Develop a practical, results-oriented solution for sticky element collision fix in the context of this website. Scope selectors under a unique parent class; avoid !important unless justified and test 320px to wide screens. Explain what should be done with Kadence Theme settings, what should be built with Kadence Blocks, and when WPCode is warranted. Do not invent installed plugin capabilities or pretend you accessed the live site. DELIVER EXACTLY 1. A task-specific implementation blueprint for “Sticky element collision fix” with exact WordPress/Kadence navigation or WPCode placement when relevant. 2. An ordered action checklist with dependencies and who owns each action. 3. Copy-ready artifacts where relevant (block hierarchy, settings matrix, sample copy, scoped CSS, PHP or vanilla JavaScript), with code fences and placement instructions. 4. Desktop/tablet/mobile acceptance tests, accessibility and security checks relevant to the task. 5. Failure cases, troubleshooting clues, rollback steps and final client-facing completion criteria. IMPLEMENTATION SAFETY Flag assumptions; favor native block controls over custom code; do not hardcode credentials or private data. For PHP/JS/CSS, provide exact location, activation scope, prerequisite checks, staging test, and undo method. If a plugin or version-specific behavior is uncertain, say what to verify first. Finish with a concise Definition of Done and a measurable business or UX outcome, without promising a result unsupported by data.
Long-word overflow protection
Create a tested, client-ready outcome for long-word overflow protection.
Act as a senior WordPress solution architect and Kadence Theme/Kadence Blocks/WPCode specialist. TASK: Long-word overflow protection. PROJECT INPUTS - Website type and business goal: [SITE TYPE + GOAL] - Audience, locale and key conversion: [AUDIENCE + LOCALE + CTA] - Current stack (WordPress/PHP, Kadence Theme, Kadence Blocks, WPCode, plugins): [VERIFIED VERSIONS] - Current page, screenshot, issue or reference: [URL OR SANITIZED DETAILS] - Constraints (budget, editor skill, hosting, launch date): [CONSTRAINTS] - Existing content, brand styles and approved data: [SOURCE MATERIAL] SPECIFIC OBJECTIVE Develop a practical, results-oriented solution for long-word overflow protection in the context of this website. Scope selectors under a unique parent class; avoid !important unless justified and test 320px to wide screens. Explain what should be done with Kadence Theme settings, what should be built with Kadence Blocks, and when WPCode is warranted. Do not invent installed plugin capabilities or pretend you accessed the live site. DELIVER EXACTLY 1. A task-specific implementation blueprint for “Long-word overflow protection” with exact WordPress/Kadence navigation or WPCode placement when relevant. 2. An ordered action checklist with dependencies and who owns each action. 3. Copy-ready artifacts where relevant (block hierarchy, settings matrix, sample copy, scoped CSS, PHP or vanilla JavaScript), with code fences and placement instructions. 4. Desktop/tablet/mobile acceptance tests, accessibility and security checks relevant to the task. 5. Failure cases, troubleshooting clues, rollback steps and final client-facing completion criteria. IMPLEMENTATION SAFETY Flag assumptions; favor native block controls over custom code; do not hardcode credentials or private data. For PHP/JS/CSS, provide exact location, activation scope, prerequisite checks, staging test, and undo method. If a plugin or version-specific behavior is uncertain, say what to verify first. Finish with a concise Definition of Done and a measurable business or UX outcome, without promising a result unsupported by data.
Print stylesheet plan
Create a tested, client-ready outcome for print stylesheet plan.
Act as a senior WordPress solution architect and Kadence Theme/Kadence Blocks/WPCode specialist. TASK: Print stylesheet plan. PROJECT INPUTS - Website type and business goal: [SITE TYPE + GOAL] - Audience, locale and key conversion: [AUDIENCE + LOCALE + CTA] - Current stack (WordPress/PHP, Kadence Theme, Kadence Blocks, WPCode, plugins): [VERIFIED VERSIONS] - Current page, screenshot, issue or reference: [URL OR SANITIZED DETAILS] - Constraints (budget, editor skill, hosting, launch date): [CONSTRAINTS] - Existing content, brand styles and approved data: [SOURCE MATERIAL] SPECIFIC OBJECTIVE Develop a practical, results-oriented solution for print stylesheet plan in the context of this website. Scope selectors under a unique parent class; avoid !important unless justified and test 320px to wide screens. Explain what should be done with Kadence Theme settings, what should be built with Kadence Blocks, and when WPCode is warranted. Do not invent installed plugin capabilities or pretend you accessed the live site. DELIVER EXACTLY 1. A task-specific implementation blueprint for “Print stylesheet plan” with exact WordPress/Kadence navigation or WPCode placement when relevant. 2. An ordered action checklist with dependencies and who owns each action. 3. Copy-ready artifacts where relevant (block hierarchy, settings matrix, sample copy, scoped CSS, PHP or vanilla JavaScript), with code fences and placement instructions. 4. Desktop/tablet/mobile acceptance tests, accessibility and security checks relevant to the task. 5. Failure cases, troubleshooting clues, rollback steps and final client-facing completion criteria. IMPLEMENTATION SAFETY Flag assumptions; favor native block controls over custom code; do not hardcode credentials or private data. For PHP/JS/CSS, provide exact location, activation scope, prerequisite checks, staging test, and undo method. If a plugin or version-specific behavior is uncertain, say what to verify first. Finish with a concise Definition of Done and a measurable business or UX outcome, without promising a result unsupported by data.
15. JavaScript & Interactive UX
Vanilla JS accordion
Create a tested, client-ready outcome for vanilla js accordion.
Act as a senior WordPress solution architect and Kadence Theme/Kadence Blocks/WPCode specialist. TASK: Vanilla JS accordion. PROJECT INPUTS - Website type and business goal: [SITE TYPE + GOAL] - Audience, locale and key conversion: [AUDIENCE + LOCALE + CTA] - Current stack (WordPress/PHP, Kadence Theme, Kadence Blocks, WPCode, plugins): [VERIFIED VERSIONS] - Current page, screenshot, issue or reference: [URL OR SANITIZED DETAILS] - Constraints (budget, editor skill, hosting, launch date): [CONSTRAINTS] - Existing content, brand styles and approved data: [SOURCE MATERIAL] SPECIFIC OBJECTIVE Develop a practical, results-oriented solution for vanilla js accordion in the context of this website. Use progressive enhancement, accessible event handling and an explicit no-javascript fallback. Explain what should be done with Kadence Theme settings, what should be built with Kadence Blocks, and when WPCode is warranted. Do not invent installed plugin capabilities or pretend you accessed the live site. DELIVER EXACTLY 1. A task-specific implementation blueprint for “Vanilla JS accordion” with exact WordPress/Kadence navigation or WPCode placement when relevant. 2. An ordered action checklist with dependencies and who owns each action. 3. Copy-ready artifacts where relevant (block hierarchy, settings matrix, sample copy, scoped CSS, PHP or vanilla JavaScript), with code fences and placement instructions. 4. Desktop/tablet/mobile acceptance tests, accessibility and security checks relevant to the task. 5. Failure cases, troubleshooting clues, rollback steps and final client-facing completion criteria. IMPLEMENTATION SAFETY Flag assumptions; favor native block controls over custom code; do not hardcode credentials or private data. For PHP/JS/CSS, provide exact location, activation scope, prerequisite checks, staging test, and undo method. If a plugin or version-specific behavior is uncertain, say what to verify first. Finish with a concise Definition of Done and a measurable business or UX outcome, without promising a result unsupported by data.
Searchable FAQ interface
Create a tested, client-ready outcome for searchable faq interface.
Act as a senior WordPress solution architect and Kadence Theme/Kadence Blocks/WPCode specialist. TASK: Searchable FAQ interface. PROJECT INPUTS - Website type and business goal: [SITE TYPE + GOAL] - Audience, locale and key conversion: [AUDIENCE + LOCALE + CTA] - Current stack (WordPress/PHP, Kadence Theme, Kadence Blocks, WPCode, plugins): [VERIFIED VERSIONS] - Current page, screenshot, issue or reference: [URL OR SANITIZED DETAILS] - Constraints (budget, editor skill, hosting, launch date): [CONSTRAINTS] - Existing content, brand styles and approved data: [SOURCE MATERIAL] SPECIFIC OBJECTIVE Develop a practical, results-oriented solution for searchable faq interface in the context of this website. Use progressive enhancement, accessible event handling and an explicit no-javascript fallback. Explain what should be done with Kadence Theme settings, what should be built with Kadence Blocks, and when WPCode is warranted. Do not invent installed plugin capabilities or pretend you accessed the live site. DELIVER EXACTLY 1. A task-specific implementation blueprint for “Searchable FAQ interface” with exact WordPress/Kadence navigation or WPCode placement when relevant. 2. An ordered action checklist with dependencies and who owns each action. 3. Copy-ready artifacts where relevant (block hierarchy, settings matrix, sample copy, scoped CSS, PHP or vanilla JavaScript), with code fences and placement instructions. 4. Desktop/tablet/mobile acceptance tests, accessibility and security checks relevant to the task. 5. Failure cases, troubleshooting clues, rollback steps and final client-facing completion criteria. IMPLEMENTATION SAFETY Flag assumptions; favor native block controls over custom code; do not hardcode credentials or private data. For PHP/JS/CSS, provide exact location, activation scope, prerequisite checks, staging test, and undo method. If a plugin or version-specific behavior is uncertain, say what to verify first. Finish with a concise Definition of Done and a measurable business or UX outcome, without promising a result unsupported by data.
Client-side category filter
Create a tested, client-ready outcome for client-side category filter.
Act as a senior WordPress solution architect and Kadence Theme/Kadence Blocks/WPCode specialist. TASK: Client-side category filter. PROJECT INPUTS - Website type and business goal: [SITE TYPE + GOAL] - Audience, locale and key conversion: [AUDIENCE + LOCALE + CTA] - Current stack (WordPress/PHP, Kadence Theme, Kadence Blocks, WPCode, plugins): [VERIFIED VERSIONS] - Current page, screenshot, issue or reference: [URL OR SANITIZED DETAILS] - Constraints (budget, editor skill, hosting, launch date): [CONSTRAINTS] - Existing content, brand styles and approved data: [SOURCE MATERIAL] SPECIFIC OBJECTIVE Develop a practical, results-oriented solution for client-side category filter in the context of this website. Use progressive enhancement, accessible event handling and an explicit no-javascript fallback. Explain what should be done with Kadence Theme settings, what should be built with Kadence Blocks, and when WPCode is warranted. Do not invent installed plugin capabilities or pretend you accessed the live site. DELIVER EXACTLY 1. A task-specific implementation blueprint for “Client-side category filter” with exact WordPress/Kadence navigation or WPCode placement when relevant. 2. An ordered action checklist with dependencies and who owns each action. 3. Copy-ready artifacts where relevant (block hierarchy, settings matrix, sample copy, scoped CSS, PHP or vanilla JavaScript), with code fences and placement instructions. 4. Desktop/tablet/mobile acceptance tests, accessibility and security checks relevant to the task. 5. Failure cases, troubleshooting clues, rollback steps and final client-facing completion criteria. IMPLEMENTATION SAFETY Flag assumptions; favor native block controls over custom code; do not hardcode credentials or private data. For PHP/JS/CSS, provide exact location, activation scope, prerequisite checks, staging test, and undo method. If a plugin or version-specific behavior is uncertain, say what to verify first. Finish with a concise Definition of Done and a measurable business or UX outcome, without promising a result unsupported by data.
Copy-to-clipboard fallback
Create a tested, client-ready outcome for copy-to-clipboard fallback.
Act as a senior WordPress solution architect and Kadence Theme/Kadence Blocks/WPCode specialist. TASK: Copy-to-clipboard fallback. PROJECT INPUTS - Website type and business goal: [SITE TYPE + GOAL] - Audience, locale and key conversion: [AUDIENCE + LOCALE + CTA] - Current stack (WordPress/PHP, Kadence Theme, Kadence Blocks, WPCode, plugins): [VERIFIED VERSIONS] - Current page, screenshot, issue or reference: [URL OR SANITIZED DETAILS] - Constraints (budget, editor skill, hosting, launch date): [CONSTRAINTS] - Existing content, brand styles and approved data: [SOURCE MATERIAL] SPECIFIC OBJECTIVE Develop a practical, results-oriented solution for copy-to-clipboard fallback in the context of this website. Use progressive enhancement, accessible event handling and an explicit no-javascript fallback. Explain what should be done with Kadence Theme settings, what should be built with Kadence Blocks, and when WPCode is warranted. Do not invent installed plugin capabilities or pretend you accessed the live site. DELIVER EXACTLY 1. A task-specific implementation blueprint for “Copy-to-clipboard fallback” with exact WordPress/Kadence navigation or WPCode placement when relevant. 2. An ordered action checklist with dependencies and who owns each action. 3. Copy-ready artifacts where relevant (block hierarchy, settings matrix, sample copy, scoped CSS, PHP or vanilla JavaScript), with code fences and placement instructions. 4. Desktop/tablet/mobile acceptance tests, accessibility and security checks relevant to the task. 5. Failure cases, troubleshooting clues, rollback steps and final client-facing completion criteria. IMPLEMENTATION SAFETY Flag assumptions; favor native block controls over custom code; do not hardcode credentials or private data. For PHP/JS/CSS, provide exact location, activation scope, prerequisite checks, staging test, and undo method. If a plugin or version-specific behavior is uncertain, say what to verify first. Finish with a concise Definition of Done and a measurable business or UX outcome, without promising a result unsupported by data.
Accessible modal interaction
Create a tested, client-ready outcome for accessible modal interaction.
Act as a senior WordPress solution architect and Kadence Theme/Kadence Blocks/WPCode specialist. TASK: Accessible modal interaction. PROJECT INPUTS - Website type and business goal: [SITE TYPE + GOAL] - Audience, locale and key conversion: [AUDIENCE + LOCALE + CTA] - Current stack (WordPress/PHP, Kadence Theme, Kadence Blocks, WPCode, plugins): [VERIFIED VERSIONS] - Current page, screenshot, issue or reference: [URL OR SANITIZED DETAILS] - Constraints (budget, editor skill, hosting, launch date): [CONSTRAINTS] - Existing content, brand styles and approved data: [SOURCE MATERIAL] SPECIFIC OBJECTIVE Develop a practical, results-oriented solution for accessible modal interaction in the context of this website. Use progressive enhancement, accessible event handling and an explicit no-javascript fallback. Explain what should be done with Kadence Theme settings, what should be built with Kadence Blocks, and when WPCode is warranted. Do not invent installed plugin capabilities or pretend you accessed the live site. DELIVER EXACTLY 1. A task-specific implementation blueprint for “Accessible modal interaction” with exact WordPress/Kadence navigation or WPCode placement when relevant. 2. An ordered action checklist with dependencies and who owns each action. 3. Copy-ready artifacts where relevant (block hierarchy, settings matrix, sample copy, scoped CSS, PHP or vanilla JavaScript), with code fences and placement instructions. 4. Desktop/tablet/mobile acceptance tests, accessibility and security checks relevant to the task. 5. Failure cases, troubleshooting clues, rollback steps and final client-facing completion criteria. IMPLEMENTATION SAFETY Flag assumptions; favor native block controls over custom code; do not hardcode credentials or private data. For PHP/JS/CSS, provide exact location, activation scope, prerequisite checks, staging test, and undo method. If a plugin or version-specific behavior is uncertain, say what to verify first. Finish with a concise Definition of Done and a measurable business or UX outcome, without promising a result unsupported by data.
Form progress indicator
Create a tested, client-ready outcome for form progress indicator.
Act as a senior WordPress solution architect and Kadence Theme/Kadence Blocks/WPCode specialist. TASK: Form progress indicator. PROJECT INPUTS - Website type and business goal: [SITE TYPE + GOAL] - Audience, locale and key conversion: [AUDIENCE + LOCALE + CTA] - Current stack (WordPress/PHP, Kadence Theme, Kadence Blocks, WPCode, plugins): [VERIFIED VERSIONS] - Current page, screenshot, issue or reference: [URL OR SANITIZED DETAILS] - Constraints (budget, editor skill, hosting, launch date): [CONSTRAINTS] - Existing content, brand styles and approved data: [SOURCE MATERIAL] SPECIFIC OBJECTIVE Develop a practical, results-oriented solution for form progress indicator in the context of this website. Use progressive enhancement, accessible event handling and an explicit no-javascript fallback. Explain what should be done with Kadence Theme settings, what should be built with Kadence Blocks, and when WPCode is warranted. Do not invent installed plugin capabilities or pretend you accessed the live site. DELIVER EXACTLY 1. A task-specific implementation blueprint for “Form progress indicator” with exact WordPress/Kadence navigation or WPCode placement when relevant. 2. An ordered action checklist with dependencies and who owns each action. 3. Copy-ready artifacts where relevant (block hierarchy, settings matrix, sample copy, scoped CSS, PHP or vanilla JavaScript), with code fences and placement instructions. 4. Desktop/tablet/mobile acceptance tests, accessibility and security checks relevant to the task. 5. Failure cases, troubleshooting clues, rollback steps and final client-facing completion criteria. IMPLEMENTATION SAFETY Flag assumptions; favor native block controls over custom code; do not hardcode credentials or private data. For PHP/JS/CSS, provide exact location, activation scope, prerequisite checks, staging test, and undo method. If a plugin or version-specific behavior is uncertain, say what to verify first. Finish with a concise Definition of Done and a measurable business or UX outcome, without promising a result unsupported by data.
Sticky CTA behavior
Create a tested, client-ready outcome for sticky cta behavior.
Act as a senior WordPress solution architect and Kadence Theme/Kadence Blocks/WPCode specialist. TASK: Sticky CTA behavior. PROJECT INPUTS - Website type and business goal: [SITE TYPE + GOAL] - Audience, locale and key conversion: [AUDIENCE + LOCALE + CTA] - Current stack (WordPress/PHP, Kadence Theme, Kadence Blocks, WPCode, plugins): [VERIFIED VERSIONS] - Current page, screenshot, issue or reference: [URL OR SANITIZED DETAILS] - Constraints (budget, editor skill, hosting, launch date): [CONSTRAINTS] - Existing content, brand styles and approved data: [SOURCE MATERIAL] SPECIFIC OBJECTIVE Develop a practical, results-oriented solution for sticky cta behavior in the context of this website. Use progressive enhancement, accessible event handling and an explicit no-javascript fallback. Explain what should be done with Kadence Theme settings, what should be built with Kadence Blocks, and when WPCode is warranted. Do not invent installed plugin capabilities or pretend you accessed the live site. DELIVER EXACTLY 1. A task-specific implementation blueprint for “Sticky CTA behavior” with exact WordPress/Kadence navigation or WPCode placement when relevant. 2. An ordered action checklist with dependencies and who owns each action. 3. Copy-ready artifacts where relevant (block hierarchy, settings matrix, sample copy, scoped CSS, PHP or vanilla JavaScript), with code fences and placement instructions. 4. Desktop/tablet/mobile acceptance tests, accessibility and security checks relevant to the task. 5. Failure cases, troubleshooting clues, rollback steps and final client-facing completion criteria. IMPLEMENTATION SAFETY Flag assumptions; favor native block controls over custom code; do not hardcode credentials or private data. For PHP/JS/CSS, provide exact location, activation scope, prerequisite checks, staging test, and undo method. If a plugin or version-specific behavior is uncertain, say what to verify first. Finish with a concise Definition of Done and a measurable business or UX outcome, without promising a result unsupported by data.
Table sorting utility
Create a tested, client-ready outcome for table sorting utility.
Act as a senior WordPress solution architect and Kadence Theme/Kadence Blocks/WPCode specialist. TASK: Table sorting utility. PROJECT INPUTS - Website type and business goal: [SITE TYPE + GOAL] - Audience, locale and key conversion: [AUDIENCE + LOCALE + CTA] - Current stack (WordPress/PHP, Kadence Theme, Kadence Blocks, WPCode, plugins): [VERIFIED VERSIONS] - Current page, screenshot, issue or reference: [URL OR SANITIZED DETAILS] - Constraints (budget, editor skill, hosting, launch date): [CONSTRAINTS] - Existing content, brand styles and approved data: [SOURCE MATERIAL] SPECIFIC OBJECTIVE Develop a practical, results-oriented solution for table sorting utility in the context of this website. Use progressive enhancement, accessible event handling and an explicit no-javascript fallback. Explain what should be done with Kadence Theme settings, what should be built with Kadence Blocks, and when WPCode is warranted. Do not invent installed plugin capabilities or pretend you accessed the live site. DELIVER EXACTLY 1. A task-specific implementation blueprint for “Table sorting utility” with exact WordPress/Kadence navigation or WPCode placement when relevant. 2. An ordered action checklist with dependencies and who owns each action. 3. Copy-ready artifacts where relevant (block hierarchy, settings matrix, sample copy, scoped CSS, PHP or vanilla JavaScript), with code fences and placement instructions. 4. Desktop/tablet/mobile acceptance tests, accessibility and security checks relevant to the task. 5. Failure cases, troubleshooting clues, rollback steps and final client-facing completion criteria. IMPLEMENTATION SAFETY Flag assumptions; favor native block controls over custom code; do not hardcode credentials or private data. For PHP/JS/CSS, provide exact location, activation scope, prerequisite checks, staging test, and undo method. If a plugin or version-specific behavior is uncertain, say what to verify first. Finish with a concise Definition of Done and a measurable business or UX outcome, without promising a result unsupported by data.
Event delegation strategy
Create a tested, client-ready outcome for event delegation strategy.
Act as a senior WordPress solution architect and Kadence Theme/Kadence Blocks/WPCode specialist. TASK: Event delegation strategy. PROJECT INPUTS - Website type and business goal: [SITE TYPE + GOAL] - Audience, locale and key conversion: [AUDIENCE + LOCALE + CTA] - Current stack (WordPress/PHP, Kadence Theme, Kadence Blocks, WPCode, plugins): [VERIFIED VERSIONS] - Current page, screenshot, issue or reference: [URL OR SANITIZED DETAILS] - Constraints (budget, editor skill, hosting, launch date): [CONSTRAINTS] - Existing content, brand styles and approved data: [SOURCE MATERIAL] SPECIFIC OBJECTIVE Develop a practical, results-oriented solution for event delegation strategy in the context of this website. Use progressive enhancement, accessible event handling and an explicit no-javascript fallback. Explain what should be done with Kadence Theme settings, what should be built with Kadence Blocks, and when WPCode is warranted. Do not invent installed plugin capabilities or pretend you accessed the live site. DELIVER EXACTLY 1. A task-specific implementation blueprint for “Event delegation strategy” with exact WordPress/Kadence navigation or WPCode placement when relevant. 2. An ordered action checklist with dependencies and who owns each action. 3. Copy-ready artifacts where relevant (block hierarchy, settings matrix, sample copy, scoped CSS, PHP or vanilla JavaScript), with code fences and placement instructions. 4. Desktop/tablet/mobile acceptance tests, accessibility and security checks relevant to the task. 5. Failure cases, troubleshooting clues, rollback steps and final client-facing completion criteria. IMPLEMENTATION SAFETY Flag assumptions; favor native block controls over custom code; do not hardcode credentials or private data. For PHP/JS/CSS, provide exact location, activation scope, prerequisite checks, staging test, and undo method. If a plugin or version-specific behavior is uncertain, say what to verify first. Finish with a concise Definition of Done and a measurable business or UX outcome, without promising a result unsupported by data.
Reduced motion handling
Create a tested, client-ready outcome for reduced motion handling.
Act as a senior WordPress solution architect and Kadence Theme/Kadence Blocks/WPCode specialist. TASK: Reduced motion handling. PROJECT INPUTS - Website type and business goal: [SITE TYPE + GOAL] - Audience, locale and key conversion: [AUDIENCE + LOCALE + CTA] - Current stack (WordPress/PHP, Kadence Theme, Kadence Blocks, WPCode, plugins): [VERIFIED VERSIONS] - Current page, screenshot, issue or reference: [URL OR SANITIZED DETAILS] - Constraints (budget, editor skill, hosting, launch date): [CONSTRAINTS] - Existing content, brand styles and approved data: [SOURCE MATERIAL] SPECIFIC OBJECTIVE Develop a practical, results-oriented solution for reduced motion handling in the context of this website. Use progressive enhancement, accessible event handling and an explicit no-javascript fallback. Explain what should be done with Kadence Theme settings, what should be built with Kadence Blocks, and when WPCode is warranted. Do not invent installed plugin capabilities or pretend you accessed the live site. DELIVER EXACTLY 1. A task-specific implementation blueprint for “Reduced motion handling” with exact WordPress/Kadence navigation or WPCode placement when relevant. 2. An ordered action checklist with dependencies and who owns each action. 3. Copy-ready artifacts where relevant (block hierarchy, settings matrix, sample copy, scoped CSS, PHP or vanilla JavaScript), with code fences and placement instructions. 4. Desktop/tablet/mobile acceptance tests, accessibility and security checks relevant to the task. 5. Failure cases, troubleshooting clues, rollback steps and final client-facing completion criteria. IMPLEMENTATION SAFETY Flag assumptions; favor native block controls over custom code; do not hardcode credentials or private data. For PHP/JS/CSS, provide exact location, activation scope, prerequisite checks, staging test, and undo method. If a plugin or version-specific behavior is uncertain, say what to verify first. Finish with a concise Definition of Done and a measurable business or UX outcome, without promising a result unsupported by data.
16. Dynamic Data & Advanced Templates
Custom field schema planning
Create a tested, client-ready outcome for custom field schema planning.
Act as a senior WordPress solution architect and Kadence Theme/Kadence Blocks/WPCode specialist. TASK: Custom field schema planning. PROJECT INPUTS - Website type and business goal: [SITE TYPE + GOAL] - Audience, locale and key conversion: [AUDIENCE + LOCALE + CTA] - Current stack (WordPress/PHP, Kadence Theme, Kadence Blocks, WPCode, plugins): [VERIFIED VERSIONS] - Current page, screenshot, issue or reference: [URL OR SANITIZED DETAILS] - Constraints (budget, editor skill, hosting, launch date): [CONSTRAINTS] - Existing content, brand styles and approved data: [SOURCE MATERIAL] SPECIFIC OBJECTIVE Develop a practical, results-oriented solution for custom field schema planning in the context of this website. Define post types, fields, queries and ownership before building; avoid duplicate source-of-truth fields. Explain what should be done with Kadence Theme settings, what should be built with Kadence Blocks, and when WPCode is warranted. Do not invent installed plugin capabilities or pretend you accessed the live site. DELIVER EXACTLY 1. A task-specific implementation blueprint for “Custom field schema planning” with exact WordPress/Kadence navigation or WPCode placement when relevant. 2. An ordered action checklist with dependencies and who owns each action. 3. Copy-ready artifacts where relevant (block hierarchy, settings matrix, sample copy, scoped CSS, PHP or vanilla JavaScript), with code fences and placement instructions. 4. Desktop/tablet/mobile acceptance tests, accessibility and security checks relevant to the task. 5. Failure cases, troubleshooting clues, rollback steps and final client-facing completion criteria. IMPLEMENTATION SAFETY Flag assumptions; favor native block controls over custom code; do not hardcode credentials or private data. For PHP/JS/CSS, provide exact location, activation scope, prerequisite checks, staging test, and undo method. If a plugin or version-specific behavior is uncertain, say what to verify first. Finish with a concise Definition of Done and a measurable business or UX outcome, without promising a result unsupported by data.
CPT archive template
Create a tested, client-ready outcome for cpt archive template.
Act as a senior WordPress solution architect and Kadence Theme/Kadence Blocks/WPCode specialist. TASK: CPT archive template. PROJECT INPUTS - Website type and business goal: [SITE TYPE + GOAL] - Audience, locale and key conversion: [AUDIENCE + LOCALE + CTA] - Current stack (WordPress/PHP, Kadence Theme, Kadence Blocks, WPCode, plugins): [VERIFIED VERSIONS] - Current page, screenshot, issue or reference: [URL OR SANITIZED DETAILS] - Constraints (budget, editor skill, hosting, launch date): [CONSTRAINTS] - Existing content, brand styles and approved data: [SOURCE MATERIAL] SPECIFIC OBJECTIVE Develop a practical, results-oriented solution for cpt archive template in the context of this website. Define post types, fields, queries and ownership before building; avoid duplicate source-of-truth fields. Explain what should be done with Kadence Theme settings, what should be built with Kadence Blocks, and when WPCode is warranted. Do not invent installed plugin capabilities or pretend you accessed the live site. DELIVER EXACTLY 1. A task-specific implementation blueprint for “CPT archive template” with exact WordPress/Kadence navigation or WPCode placement when relevant. 2. An ordered action checklist with dependencies and who owns each action. 3. Copy-ready artifacts where relevant (block hierarchy, settings matrix, sample copy, scoped CSS, PHP or vanilla JavaScript), with code fences and placement instructions. 4. Desktop/tablet/mobile acceptance tests, accessibility and security checks relevant to the task. 5. Failure cases, troubleshooting clues, rollback steps and final client-facing completion criteria. IMPLEMENTATION SAFETY Flag assumptions; favor native block controls over custom code; do not hardcode credentials or private data. For PHP/JS/CSS, provide exact location, activation scope, prerequisite checks, staging test, and undo method. If a plugin or version-specific behavior is uncertain, say what to verify first. Finish with a concise Definition of Done and a measurable business or UX outcome, without promising a result unsupported by data.
Dynamic single item template
Create a tested, client-ready outcome for dynamic single item template.
Act as a senior WordPress solution architect and Kadence Theme/Kadence Blocks/WPCode specialist. TASK: Dynamic single item template. PROJECT INPUTS - Website type and business goal: [SITE TYPE + GOAL] - Audience, locale and key conversion: [AUDIENCE + LOCALE + CTA] - Current stack (WordPress/PHP, Kadence Theme, Kadence Blocks, WPCode, plugins): [VERIFIED VERSIONS] - Current page, screenshot, issue or reference: [URL OR SANITIZED DETAILS] - Constraints (budget, editor skill, hosting, launch date): [CONSTRAINTS] - Existing content, brand styles and approved data: [SOURCE MATERIAL] SPECIFIC OBJECTIVE Develop a practical, results-oriented solution for dynamic single item template in the context of this website. Define post types, fields, queries and ownership before building; avoid duplicate source-of-truth fields. Explain what should be done with Kadence Theme settings, what should be built with Kadence Blocks, and when WPCode is warranted. Do not invent installed plugin capabilities or pretend you accessed the live site. DELIVER EXACTLY 1. A task-specific implementation blueprint for “Dynamic single item template” with exact WordPress/Kadence navigation or WPCode placement when relevant. 2. An ordered action checklist with dependencies and who owns each action. 3. Copy-ready artifacts where relevant (block hierarchy, settings matrix, sample copy, scoped CSS, PHP or vanilla JavaScript), with code fences and placement instructions. 4. Desktop/tablet/mobile acceptance tests, accessibility and security checks relevant to the task. 5. Failure cases, troubleshooting clues, rollback steps and final client-facing completion criteria. IMPLEMENTATION SAFETY Flag assumptions; favor native block controls over custom code; do not hardcode credentials or private data. For PHP/JS/CSS, provide exact location, activation scope, prerequisite checks, staging test, and undo method. If a plugin or version-specific behavior is uncertain, say what to verify first. Finish with a concise Definition of Done and a measurable business or UX outcome, without promising a result unsupported by data.
Related content query spec
Create a tested, client-ready outcome for related content query spec.
Act as a senior WordPress solution architect and Kadence Theme/Kadence Blocks/WPCode specialist. TASK: Related content query spec. PROJECT INPUTS - Website type and business goal: [SITE TYPE + GOAL] - Audience, locale and key conversion: [AUDIENCE + LOCALE + CTA] - Current stack (WordPress/PHP, Kadence Theme, Kadence Blocks, WPCode, plugins): [VERIFIED VERSIONS] - Current page, screenshot, issue or reference: [URL OR SANITIZED DETAILS] - Constraints (budget, editor skill, hosting, launch date): [CONSTRAINTS] - Existing content, brand styles and approved data: [SOURCE MATERIAL] SPECIFIC OBJECTIVE Develop a practical, results-oriented solution for related content query spec in the context of this website. Define post types, fields, queries and ownership before building; avoid duplicate source-of-truth fields. Explain what should be done with Kadence Theme settings, what should be built with Kadence Blocks, and when WPCode is warranted. Do not invent installed plugin capabilities or pretend you accessed the live site. DELIVER EXACTLY 1. A task-specific implementation blueprint for “Related content query spec” with exact WordPress/Kadence navigation or WPCode placement when relevant. 2. An ordered action checklist with dependencies and who owns each action. 3. Copy-ready artifacts where relevant (block hierarchy, settings matrix, sample copy, scoped CSS, PHP or vanilla JavaScript), with code fences and placement instructions. 4. Desktop/tablet/mobile acceptance tests, accessibility and security checks relevant to the task. 5. Failure cases, troubleshooting clues, rollback steps and final client-facing completion criteria. IMPLEMENTATION SAFETY Flag assumptions; favor native block controls over custom code; do not hardcode credentials or private data. For PHP/JS/CSS, provide exact location, activation scope, prerequisite checks, staging test, and undo method. If a plugin or version-specific behavior is uncertain, say what to verify first. Finish with a concise Definition of Done and a measurable business or UX outcome, without promising a result unsupported by data.
Directory listing UX
Create a tested, client-ready outcome for directory listing ux.
Act as a senior WordPress solution architect and Kadence Theme/Kadence Blocks/WPCode specialist. TASK: Directory listing UX. PROJECT INPUTS - Website type and business goal: [SITE TYPE + GOAL] - Audience, locale and key conversion: [AUDIENCE + LOCALE + CTA] - Current stack (WordPress/PHP, Kadence Theme, Kadence Blocks, WPCode, plugins): [VERIFIED VERSIONS] - Current page, screenshot, issue or reference: [URL OR SANITIZED DETAILS] - Constraints (budget, editor skill, hosting, launch date): [CONSTRAINTS] - Existing content, brand styles and approved data: [SOURCE MATERIAL] SPECIFIC OBJECTIVE Develop a practical, results-oriented solution for directory listing ux in the context of this website. Define post types, fields, queries and ownership before building; avoid duplicate source-of-truth fields. Explain what should be done with Kadence Theme settings, what should be built with Kadence Blocks, and when WPCode is warranted. Do not invent installed plugin capabilities or pretend you accessed the live site. DELIVER EXACTLY 1. A task-specific implementation blueprint for “Directory listing UX” with exact WordPress/Kadence navigation or WPCode placement when relevant. 2. An ordered action checklist with dependencies and who owns each action. 3. Copy-ready artifacts where relevant (block hierarchy, settings matrix, sample copy, scoped CSS, PHP or vanilla JavaScript), with code fences and placement instructions. 4. Desktop/tablet/mobile acceptance tests, accessibility and security checks relevant to the task. 5. Failure cases, troubleshooting clues, rollback steps and final client-facing completion criteria. IMPLEMENTATION SAFETY Flag assumptions; favor native block controls over custom code; do not hardcode credentials or private data. For PHP/JS/CSS, provide exact location, activation scope, prerequisite checks, staging test, and undo method. If a plugin or version-specific behavior is uncertain, say what to verify first. Finish with a concise Definition of Done and a measurable business or UX outcome, without promising a result unsupported by data.
Faceted filter feasibility
Create a tested, client-ready outcome for faceted filter feasibility.
Act as a senior WordPress solution architect and Kadence Theme/Kadence Blocks/WPCode specialist. TASK: Faceted filter feasibility. PROJECT INPUTS - Website type and business goal: [SITE TYPE + GOAL] - Audience, locale and key conversion: [AUDIENCE + LOCALE + CTA] - Current stack (WordPress/PHP, Kadence Theme, Kadence Blocks, WPCode, plugins): [VERIFIED VERSIONS] - Current page, screenshot, issue or reference: [URL OR SANITIZED DETAILS] - Constraints (budget, editor skill, hosting, launch date): [CONSTRAINTS] - Existing content, brand styles and approved data: [SOURCE MATERIAL] SPECIFIC OBJECTIVE Develop a practical, results-oriented solution for faceted filter feasibility in the context of this website. Define post types, fields, queries and ownership before building; avoid duplicate source-of-truth fields. Explain what should be done with Kadence Theme settings, what should be built with Kadence Blocks, and when WPCode is warranted. Do not invent installed plugin capabilities or pretend you accessed the live site. DELIVER EXACTLY 1. A task-specific implementation blueprint for “Faceted filter feasibility” with exact WordPress/Kadence navigation or WPCode placement when relevant. 2. An ordered action checklist with dependencies and who owns each action. 3. Copy-ready artifacts where relevant (block hierarchy, settings matrix, sample copy, scoped CSS, PHP or vanilla JavaScript), with code fences and placement instructions. 4. Desktop/tablet/mobile acceptance tests, accessibility and security checks relevant to the task. 5. Failure cases, troubleshooting clues, rollback steps and final client-facing completion criteria. IMPLEMENTATION SAFETY Flag assumptions; favor native block controls over custom code; do not hardcode credentials or private data. For PHP/JS/CSS, provide exact location, activation scope, prerequisite checks, staging test, and undo method. If a plugin or version-specific behavior is uncertain, say what to verify first. Finish with a concise Definition of Done and a measurable business or UX outcome, without promising a result unsupported by data.
Profile directory structure
Create a tested, client-ready outcome for profile directory structure.
Act as a senior WordPress solution architect and Kadence Theme/Kadence Blocks/WPCode specialist. TASK: Profile directory structure. PROJECT INPUTS - Website type and business goal: [SITE TYPE + GOAL] - Audience, locale and key conversion: [AUDIENCE + LOCALE + CTA] - Current stack (WordPress/PHP, Kadence Theme, Kadence Blocks, WPCode, plugins): [VERIFIED VERSIONS] - Current page, screenshot, issue or reference: [URL OR SANITIZED DETAILS] - Constraints (budget, editor skill, hosting, launch date): [CONSTRAINTS] - Existing content, brand styles and approved data: [SOURCE MATERIAL] SPECIFIC OBJECTIVE Develop a practical, results-oriented solution for profile directory structure in the context of this website. Define post types, fields, queries and ownership before building; avoid duplicate source-of-truth fields. Explain what should be done with Kadence Theme settings, what should be built with Kadence Blocks, and when WPCode is warranted. Do not invent installed plugin capabilities or pretend you accessed the live site. DELIVER EXACTLY 1. A task-specific implementation blueprint for “Profile directory structure” with exact WordPress/Kadence navigation or WPCode placement when relevant. 2. An ordered action checklist with dependencies and who owns each action. 3. Copy-ready artifacts where relevant (block hierarchy, settings matrix, sample copy, scoped CSS, PHP or vanilla JavaScript), with code fences and placement instructions. 4. Desktop/tablet/mobile acceptance tests, accessibility and security checks relevant to the task. 5. Failure cases, troubleshooting clues, rollback steps and final client-facing completion criteria. IMPLEMENTATION SAFETY Flag assumptions; favor native block controls over custom code; do not hardcode credentials or private data. For PHP/JS/CSS, provide exact location, activation scope, prerequisite checks, staging test, and undo method. If a plugin or version-specific behavior is uncertain, say what to verify first. Finish with a concise Definition of Done and a measurable business or UX outcome, without promising a result unsupported by data.
Property listing blueprint
Create a tested, client-ready outcome for property listing blueprint.
Act as a senior WordPress solution architect and Kadence Theme/Kadence Blocks/WPCode specialist. TASK: Property listing blueprint. PROJECT INPUTS - Website type and business goal: [SITE TYPE + GOAL] - Audience, locale and key conversion: [AUDIENCE + LOCALE + CTA] - Current stack (WordPress/PHP, Kadence Theme, Kadence Blocks, WPCode, plugins): [VERIFIED VERSIONS] - Current page, screenshot, issue or reference: [URL OR SANITIZED DETAILS] - Constraints (budget, editor skill, hosting, launch date): [CONSTRAINTS] - Existing content, brand styles and approved data: [SOURCE MATERIAL] SPECIFIC OBJECTIVE Develop a practical, results-oriented solution for property listing blueprint in the context of this website. Define post types, fields, queries and ownership before building; avoid duplicate source-of-truth fields. Explain what should be done with Kadence Theme settings, what should be built with Kadence Blocks, and when WPCode is warranted. Do not invent installed plugin capabilities or pretend you accessed the live site. DELIVER EXACTLY 1. A task-specific implementation blueprint for “Property listing blueprint” with exact WordPress/Kadence navigation or WPCode placement when relevant. 2. An ordered action checklist with dependencies and who owns each action. 3. Copy-ready artifacts where relevant (block hierarchy, settings matrix, sample copy, scoped CSS, PHP or vanilla JavaScript), with code fences and placement instructions. 4. Desktop/tablet/mobile acceptance tests, accessibility and security checks relevant to the task. 5. Failure cases, troubleshooting clues, rollback steps and final client-facing completion criteria. IMPLEMENTATION SAFETY Flag assumptions; favor native block controls over custom code; do not hardcode credentials or private data. For PHP/JS/CSS, provide exact location, activation scope, prerequisite checks, staging test, and undo method. If a plugin or version-specific behavior is uncertain, say what to verify first. Finish with a concise Definition of Done and a measurable business or UX outcome, without promising a result unsupported by data.
Job board information design
Create a tested, client-ready outcome for job board information design.
Act as a senior WordPress solution architect and Kadence Theme/Kadence Blocks/WPCode specialist. TASK: Job board information design. PROJECT INPUTS - Website type and business goal: [SITE TYPE + GOAL] - Audience, locale and key conversion: [AUDIENCE + LOCALE + CTA] - Current stack (WordPress/PHP, Kadence Theme, Kadence Blocks, WPCode, plugins): [VERIFIED VERSIONS] - Current page, screenshot, issue or reference: [URL OR SANITIZED DETAILS] - Constraints (budget, editor skill, hosting, launch date): [CONSTRAINTS] - Existing content, brand styles and approved data: [SOURCE MATERIAL] SPECIFIC OBJECTIVE Develop a practical, results-oriented solution for job board information design in the context of this website. Define post types, fields, queries and ownership before building; avoid duplicate source-of-truth fields. Explain what should be done with Kadence Theme settings, what should be built with Kadence Blocks, and when WPCode is warranted. Do not invent installed plugin capabilities or pretend you accessed the live site. DELIVER EXACTLY 1. A task-specific implementation blueprint for “Job board information design” with exact WordPress/Kadence navigation or WPCode placement when relevant. 2. An ordered action checklist with dependencies and who owns each action. 3. Copy-ready artifacts where relevant (block hierarchy, settings matrix, sample copy, scoped CSS, PHP or vanilla JavaScript), with code fences and placement instructions. 4. Desktop/tablet/mobile acceptance tests, accessibility and security checks relevant to the task. 5. Failure cases, troubleshooting clues, rollback steps and final client-facing completion criteria. IMPLEMENTATION SAFETY Flag assumptions; favor native block controls over custom code; do not hardcode credentials or private data. For PHP/JS/CSS, provide exact location, activation scope, prerequisite checks, staging test, and undo method. If a plugin or version-specific behavior is uncertain, say what to verify first. Finish with a concise Definition of Done and a measurable business or UX outcome, without promising a result unsupported by data.
Data migration field map
Create a tested, client-ready outcome for data migration field map.
Act as a senior WordPress solution architect and Kadence Theme/Kadence Blocks/WPCode specialist. TASK: Data migration field map. PROJECT INPUTS - Website type and business goal: [SITE TYPE + GOAL] - Audience, locale and key conversion: [AUDIENCE + LOCALE + CTA] - Current stack (WordPress/PHP, Kadence Theme, Kadence Blocks, WPCode, plugins): [VERIFIED VERSIONS] - Current page, screenshot, issue or reference: [URL OR SANITIZED DETAILS] - Constraints (budget, editor skill, hosting, launch date): [CONSTRAINTS] - Existing content, brand styles and approved data: [SOURCE MATERIAL] SPECIFIC OBJECTIVE Develop a practical, results-oriented solution for data migration field map in the context of this website. Define post types, fields, queries and ownership before building; avoid duplicate source-of-truth fields. Explain what should be done with Kadence Theme settings, what should be built with Kadence Blocks, and when WPCode is warranted. Do not invent installed plugin capabilities or pretend you accessed the live site. DELIVER EXACTLY 1. A task-specific implementation blueprint for “Data migration field map” with exact WordPress/Kadence navigation or WPCode placement when relevant. 2. An ordered action checklist with dependencies and who owns each action. 3. Copy-ready artifacts where relevant (block hierarchy, settings matrix, sample copy, scoped CSS, PHP or vanilla JavaScript), with code fences and placement instructions. 4. Desktop/tablet/mobile acceptance tests, accessibility and security checks relevant to the task. 5. Failure cases, troubleshooting clues, rollback steps and final client-facing completion criteria. IMPLEMENTATION SAFETY Flag assumptions; favor native block controls over custom code; do not hardcode credentials or private data. For PHP/JS/CSS, provide exact location, activation scope, prerequisite checks, staging test, and undo method. If a plugin or version-specific behavior is uncertain, say what to verify first. Finish with a concise Definition of Done and a measurable business or UX outcome, without promising a result unsupported by data.
17. API, Webhook & External Services
REST API endpoint assessment
Create a tested, client-ready outcome for rest api endpoint assessment.
Act as a senior WordPress solution architect and Kadence Theme/Kadence Blocks/WPCode specialist. TASK: REST API endpoint assessment. PROJECT INPUTS - Website type and business goal: [SITE TYPE + GOAL] - Audience, locale and key conversion: [AUDIENCE + LOCALE + CTA] - Current stack (WordPress/PHP, Kadence Theme, Kadence Blocks, WPCode, plugins): [VERIFIED VERSIONS] - Current page, screenshot, issue or reference: [URL OR SANITIZED DETAILS] - Constraints (budget, editor skill, hosting, launch date): [CONSTRAINTS] - Existing content, brand styles and approved data: [SOURCE MATERIAL] SPECIFIC OBJECTIVE Develop a practical, results-oriented solution for rest api endpoint assessment in the context of this website. Never expose api keys or tokens in client javascript; define auth, error and retry handling. Explain what should be done with Kadence Theme settings, what should be built with Kadence Blocks, and when WPCode is warranted. Do not invent installed plugin capabilities or pretend you accessed the live site. DELIVER EXACTLY 1. A task-specific implementation blueprint for “REST API endpoint assessment” with exact WordPress/Kadence navigation or WPCode placement when relevant. 2. An ordered action checklist with dependencies and who owns each action. 3. Copy-ready artifacts where relevant (block hierarchy, settings matrix, sample copy, scoped CSS, PHP or vanilla JavaScript), with code fences and placement instructions. 4. Desktop/tablet/mobile acceptance tests, accessibility and security checks relevant to the task. 5. Failure cases, troubleshooting clues, rollback steps and final client-facing completion criteria. IMPLEMENTATION SAFETY Flag assumptions; favor native block controls over custom code; do not hardcode credentials or private data. For PHP/JS/CSS, provide exact location, activation scope, prerequisite checks, staging test, and undo method. If a plugin or version-specific behavior is uncertain, say what to verify first. Finish with a concise Definition of Done and a measurable business or UX outcome, without promising a result unsupported by data.
Third-party API integration plan
Create a tested, client-ready outcome for third-party api integration plan.
Act as a senior WordPress solution architect and Kadence Theme/Kadence Blocks/WPCode specialist. TASK: Third-party API integration plan. PROJECT INPUTS - Website type and business goal: [SITE TYPE + GOAL] - Audience, locale and key conversion: [AUDIENCE + LOCALE + CTA] - Current stack (WordPress/PHP, Kadence Theme, Kadence Blocks, WPCode, plugins): [VERIFIED VERSIONS] - Current page, screenshot, issue or reference: [URL OR SANITIZED DETAILS] - Constraints (budget, editor skill, hosting, launch date): [CONSTRAINTS] - Existing content, brand styles and approved data: [SOURCE MATERIAL] SPECIFIC OBJECTIVE Develop a practical, results-oriented solution for third-party api integration plan in the context of this website. Never expose api keys or tokens in client javascript; define auth, error and retry handling. Explain what should be done with Kadence Theme settings, what should be built with Kadence Blocks, and when WPCode is warranted. Do not invent installed plugin capabilities or pretend you accessed the live site. DELIVER EXACTLY 1. A task-specific implementation blueprint for “Third-party API integration plan” with exact WordPress/Kadence navigation or WPCode placement when relevant. 2. An ordered action checklist with dependencies and who owns each action. 3. Copy-ready artifacts where relevant (block hierarchy, settings matrix, sample copy, scoped CSS, PHP or vanilla JavaScript), with code fences and placement instructions. 4. Desktop/tablet/mobile acceptance tests, accessibility and security checks relevant to the task. 5. Failure cases, troubleshooting clues, rollback steps and final client-facing completion criteria. IMPLEMENTATION SAFETY Flag assumptions; favor native block controls over custom code; do not hardcode credentials or private data. For PHP/JS/CSS, provide exact location, activation scope, prerequisite checks, staging test, and undo method. If a plugin or version-specific behavior is uncertain, say what to verify first. Finish with a concise Definition of Done and a measurable business or UX outcome, without promising a result unsupported by data.
API authentication safety
Create a tested, client-ready outcome for api authentication safety.
Act as a senior WordPress solution architect and Kadence Theme/Kadence Blocks/WPCode specialist. TASK: API authentication safety. PROJECT INPUTS - Website type and business goal: [SITE TYPE + GOAL] - Audience, locale and key conversion: [AUDIENCE + LOCALE + CTA] - Current stack (WordPress/PHP, Kadence Theme, Kadence Blocks, WPCode, plugins): [VERIFIED VERSIONS] - Current page, screenshot, issue or reference: [URL OR SANITIZED DETAILS] - Constraints (budget, editor skill, hosting, launch date): [CONSTRAINTS] - Existing content, brand styles and approved data: [SOURCE MATERIAL] SPECIFIC OBJECTIVE Develop a practical, results-oriented solution for api authentication safety in the context of this website. Never expose api keys or tokens in client javascript; define auth, error and retry handling. Explain what should be done with Kadence Theme settings, what should be built with Kadence Blocks, and when WPCode is warranted. Do not invent installed plugin capabilities or pretend you accessed the live site. DELIVER EXACTLY 1. A task-specific implementation blueprint for “API authentication safety” with exact WordPress/Kadence navigation or WPCode placement when relevant. 2. An ordered action checklist with dependencies and who owns each action. 3. Copy-ready artifacts where relevant (block hierarchy, settings matrix, sample copy, scoped CSS, PHP or vanilla JavaScript), with code fences and placement instructions. 4. Desktop/tablet/mobile acceptance tests, accessibility and security checks relevant to the task. 5. Failure cases, troubleshooting clues, rollback steps and final client-facing completion criteria. IMPLEMENTATION SAFETY Flag assumptions; favor native block controls over custom code; do not hardcode credentials or private data. For PHP/JS/CSS, provide exact location, activation scope, prerequisite checks, staging test, and undo method. If a plugin or version-specific behavior is uncertain, say what to verify first. Finish with a concise Definition of Done and a measurable business or UX outcome, without promising a result unsupported by data.
Webhook retry workflow
Create a tested, client-ready outcome for webhook retry workflow.
Act as a senior WordPress solution architect and Kadence Theme/Kadence Blocks/WPCode specialist. TASK: Webhook retry workflow. PROJECT INPUTS - Website type and business goal: [SITE TYPE + GOAL] - Audience, locale and key conversion: [AUDIENCE + LOCALE + CTA] - Current stack (WordPress/PHP, Kadence Theme, Kadence Blocks, WPCode, plugins): [VERIFIED VERSIONS] - Current page, screenshot, issue or reference: [URL OR SANITIZED DETAILS] - Constraints (budget, editor skill, hosting, launch date): [CONSTRAINTS] - Existing content, brand styles and approved data: [SOURCE MATERIAL] SPECIFIC OBJECTIVE Develop a practical, results-oriented solution for webhook retry workflow in the context of this website. Never expose api keys or tokens in client javascript; define auth, error and retry handling. Explain what should be done with Kadence Theme settings, what should be built with Kadence Blocks, and when WPCode is warranted. Do not invent installed plugin capabilities or pretend you accessed the live site. DELIVER EXACTLY 1. A task-specific implementation blueprint for “Webhook retry workflow” with exact WordPress/Kadence navigation or WPCode placement when relevant. 2. An ordered action checklist with dependencies and who owns each action. 3. Copy-ready artifacts where relevant (block hierarchy, settings matrix, sample copy, scoped CSS, PHP or vanilla JavaScript), with code fences and placement instructions. 4. Desktop/tablet/mobile acceptance tests, accessibility and security checks relevant to the task. 5. Failure cases, troubleshooting clues, rollback steps and final client-facing completion criteria. IMPLEMENTATION SAFETY Flag assumptions; favor native block controls over custom code; do not hardcode credentials or private data. For PHP/JS/CSS, provide exact location, activation scope, prerequisite checks, staging test, and undo method. If a plugin or version-specific behavior is uncertain, say what to verify first. Finish with a concise Definition of Done and a measurable business or UX outcome, without promising a result unsupported by data.
JSON response validation
Create a tested, client-ready outcome for json response validation.
Act as a senior WordPress solution architect and Kadence Theme/Kadence Blocks/WPCode specialist. TASK: JSON response validation. PROJECT INPUTS - Website type and business goal: [SITE TYPE + GOAL] - Audience, locale and key conversion: [AUDIENCE + LOCALE + CTA] - Current stack (WordPress/PHP, Kadence Theme, Kadence Blocks, WPCode, plugins): [VERIFIED VERSIONS] - Current page, screenshot, issue or reference: [URL OR SANITIZED DETAILS] - Constraints (budget, editor skill, hosting, launch date): [CONSTRAINTS] - Existing content, brand styles and approved data: [SOURCE MATERIAL] SPECIFIC OBJECTIVE Develop a practical, results-oriented solution for json response validation in the context of this website. Never expose api keys or tokens in client javascript; define auth, error and retry handling. Explain what should be done with Kadence Theme settings, what should be built with Kadence Blocks, and when WPCode is warranted. Do not invent installed plugin capabilities or pretend you accessed the live site. DELIVER EXACTLY 1. A task-specific implementation blueprint for “JSON response validation” with exact WordPress/Kadence navigation or WPCode placement when relevant. 2. An ordered action checklist with dependencies and who owns each action. 3. Copy-ready artifacts where relevant (block hierarchy, settings matrix, sample copy, scoped CSS, PHP or vanilla JavaScript), with code fences and placement instructions. 4. Desktop/tablet/mobile acceptance tests, accessibility and security checks relevant to the task. 5. Failure cases, troubleshooting clues, rollback steps and final client-facing completion criteria. IMPLEMENTATION SAFETY Flag assumptions; favor native block controls over custom code; do not hardcode credentials or private data. For PHP/JS/CSS, provide exact location, activation scope, prerequisite checks, staging test, and undo method. If a plugin or version-specific behavior is uncertain, say what to verify first. Finish with a concise Definition of Done and a measurable business or UX outcome, without promising a result unsupported by data.
Rate-limit strategy
Create a tested, client-ready outcome for rate-limit strategy.
Act as a senior WordPress solution architect and Kadence Theme/Kadence Blocks/WPCode specialist. TASK: Rate-limit strategy. PROJECT INPUTS - Website type and business goal: [SITE TYPE + GOAL] - Audience, locale and key conversion: [AUDIENCE + LOCALE + CTA] - Current stack (WordPress/PHP, Kadence Theme, Kadence Blocks, WPCode, plugins): [VERIFIED VERSIONS] - Current page, screenshot, issue or reference: [URL OR SANITIZED DETAILS] - Constraints (budget, editor skill, hosting, launch date): [CONSTRAINTS] - Existing content, brand styles and approved data: [SOURCE MATERIAL] SPECIFIC OBJECTIVE Develop a practical, results-oriented solution for rate-limit strategy in the context of this website. Never expose api keys or tokens in client javascript; define auth, error and retry handling. Explain what should be done with Kadence Theme settings, what should be built with Kadence Blocks, and when WPCode is warranted. Do not invent installed plugin capabilities or pretend you accessed the live site. DELIVER EXACTLY 1. A task-specific implementation blueprint for “Rate-limit strategy” with exact WordPress/Kadence navigation or WPCode placement when relevant. 2. An ordered action checklist with dependencies and who owns each action. 3. Copy-ready artifacts where relevant (block hierarchy, settings matrix, sample copy, scoped CSS, PHP or vanilla JavaScript), with code fences and placement instructions. 4. Desktop/tablet/mobile acceptance tests, accessibility and security checks relevant to the task. 5. Failure cases, troubleshooting clues, rollback steps and final client-facing completion criteria. IMPLEMENTATION SAFETY Flag assumptions; favor native block controls over custom code; do not hardcode credentials or private data. For PHP/JS/CSS, provide exact location, activation scope, prerequisite checks, staging test, and undo method. If a plugin or version-specific behavior is uncertain, say what to verify first. Finish with a concise Definition of Done and a measurable business or UX outcome, without promising a result unsupported by data.
External search embedding plan
Create a tested, client-ready outcome for external search embedding plan.
Act as a senior WordPress solution architect and Kadence Theme/Kadence Blocks/WPCode specialist. TASK: External search embedding plan. PROJECT INPUTS - Website type and business goal: [SITE TYPE + GOAL] - Audience, locale and key conversion: [AUDIENCE + LOCALE + CTA] - Current stack (WordPress/PHP, Kadence Theme, Kadence Blocks, WPCode, plugins): [VERIFIED VERSIONS] - Current page, screenshot, issue or reference: [URL OR SANITIZED DETAILS] - Constraints (budget, editor skill, hosting, launch date): [CONSTRAINTS] - Existing content, brand styles and approved data: [SOURCE MATERIAL] SPECIFIC OBJECTIVE Develop a practical, results-oriented solution for external search embedding plan in the context of this website. Never expose api keys or tokens in client javascript; define auth, error and retry handling. Explain what should be done with Kadence Theme settings, what should be built with Kadence Blocks, and when WPCode is warranted. Do not invent installed plugin capabilities or pretend you accessed the live site. DELIVER EXACTLY 1. A task-specific implementation blueprint for “External search embedding plan” with exact WordPress/Kadence navigation or WPCode placement when relevant. 2. An ordered action checklist with dependencies and who owns each action. 3. Copy-ready artifacts where relevant (block hierarchy, settings matrix, sample copy, scoped CSS, PHP or vanilla JavaScript), with code fences and placement instructions. 4. Desktop/tablet/mobile acceptance tests, accessibility and security checks relevant to the task. 5. Failure cases, troubleshooting clues, rollback steps and final client-facing completion criteria. IMPLEMENTATION SAFETY Flag assumptions; favor native block controls over custom code; do not hardcode credentials or private data. For PHP/JS/CSS, provide exact location, activation scope, prerequisite checks, staging test, and undo method. If a plugin or version-specific behavior is uncertain, say what to verify first. Finish with a concise Definition of Done and a measurable business or UX outcome, without promising a result unsupported by data.
Calendar integration specification
Create a tested, client-ready outcome for calendar integration specification.
Act as a senior WordPress solution architect and Kadence Theme/Kadence Blocks/WPCode specialist. TASK: Calendar integration specification. PROJECT INPUTS - Website type and business goal: [SITE TYPE + GOAL] - Audience, locale and key conversion: [AUDIENCE + LOCALE + CTA] - Current stack (WordPress/PHP, Kadence Theme, Kadence Blocks, WPCode, plugins): [VERIFIED VERSIONS] - Current page, screenshot, issue or reference: [URL OR SANITIZED DETAILS] - Constraints (budget, editor skill, hosting, launch date): [CONSTRAINTS] - Existing content, brand styles and approved data: [SOURCE MATERIAL] SPECIFIC OBJECTIVE Develop a practical, results-oriented solution for calendar integration specification in the context of this website. Never expose api keys or tokens in client javascript; define auth, error and retry handling. Explain what should be done with Kadence Theme settings, what should be built with Kadence Blocks, and when WPCode is warranted. Do not invent installed plugin capabilities or pretend you accessed the live site. DELIVER EXACTLY 1. A task-specific implementation blueprint for “Calendar integration specification” with exact WordPress/Kadence navigation or WPCode placement when relevant. 2. An ordered action checklist with dependencies and who owns each action. 3. Copy-ready artifacts where relevant (block hierarchy, settings matrix, sample copy, scoped CSS, PHP or vanilla JavaScript), with code fences and placement instructions. 4. Desktop/tablet/mobile acceptance tests, accessibility and security checks relevant to the task. 5. Failure cases, troubleshooting clues, rollback steps and final client-facing completion criteria. IMPLEMENTATION SAFETY Flag assumptions; favor native block controls over custom code; do not hardcode credentials or private data. For PHP/JS/CSS, provide exact location, activation scope, prerequisite checks, staging test, and undo method. If a plugin or version-specific behavior is uncertain, say what to verify first. Finish with a concise Definition of Done and a measurable business or UX outcome, without promising a result unsupported by data.
CRM integration failure logging
Create a tested, client-ready outcome for crm integration failure logging.
Act as a senior WordPress solution architect and Kadence Theme/Kadence Blocks/WPCode specialist. TASK: CRM integration failure logging. PROJECT INPUTS - Website type and business goal: [SITE TYPE + GOAL] - Audience, locale and key conversion: [AUDIENCE + LOCALE + CTA] - Current stack (WordPress/PHP, Kadence Theme, Kadence Blocks, WPCode, plugins): [VERIFIED VERSIONS] - Current page, screenshot, issue or reference: [URL OR SANITIZED DETAILS] - Constraints (budget, editor skill, hosting, launch date): [CONSTRAINTS] - Existing content, brand styles and approved data: [SOURCE MATERIAL] SPECIFIC OBJECTIVE Develop a practical, results-oriented solution for crm integration failure logging in the context of this website. Never expose api keys or tokens in client javascript; define auth, error and retry handling. Explain what should be done with Kadence Theme settings, what should be built with Kadence Blocks, and when WPCode is warranted. Do not invent installed plugin capabilities or pretend you accessed the live site. DELIVER EXACTLY 1. A task-specific implementation blueprint for “CRM integration failure logging” with exact WordPress/Kadence navigation or WPCode placement when relevant. 2. An ordered action checklist with dependencies and who owns each action. 3. Copy-ready artifacts where relevant (block hierarchy, settings matrix, sample copy, scoped CSS, PHP or vanilla JavaScript), with code fences and placement instructions. 4. Desktop/tablet/mobile acceptance tests, accessibility and security checks relevant to the task. 5. Failure cases, troubleshooting clues, rollback steps and final client-facing completion criteria. IMPLEMENTATION SAFETY Flag assumptions; favor native block controls over custom code; do not hardcode credentials or private data. For PHP/JS/CSS, provide exact location, activation scope, prerequisite checks, staging test, and undo method. If a plugin or version-specific behavior is uncertain, say what to verify first. Finish with a concise Definition of Done and a measurable business or UX outcome, without promising a result unsupported by data.
Secrets and environment audit
Create a tested, client-ready outcome for secrets and environment audit.
Act as a senior WordPress solution architect and Kadence Theme/Kadence Blocks/WPCode specialist. TASK: Secrets and environment audit. PROJECT INPUTS - Website type and business goal: [SITE TYPE + GOAL] - Audience, locale and key conversion: [AUDIENCE + LOCALE + CTA] - Current stack (WordPress/PHP, Kadence Theme, Kadence Blocks, WPCode, plugins): [VERIFIED VERSIONS] - Current page, screenshot, issue or reference: [URL OR SANITIZED DETAILS] - Constraints (budget, editor skill, hosting, launch date): [CONSTRAINTS] - Existing content, brand styles and approved data: [SOURCE MATERIAL] SPECIFIC OBJECTIVE Develop a practical, results-oriented solution for secrets and environment audit in the context of this website. Never expose api keys or tokens in client javascript; define auth, error and retry handling. Explain what should be done with Kadence Theme settings, what should be built with Kadence Blocks, and when WPCode is warranted. Do not invent installed plugin capabilities or pretend you accessed the live site. DELIVER EXACTLY 1. A task-specific implementation blueprint for “Secrets and environment audit” with exact WordPress/Kadence navigation or WPCode placement when relevant. 2. An ordered action checklist with dependencies and who owns each action. 3. Copy-ready artifacts where relevant (block hierarchy, settings matrix, sample copy, scoped CSS, PHP or vanilla JavaScript), with code fences and placement instructions. 4. Desktop/tablet/mobile acceptance tests, accessibility and security checks relevant to the task. 5. Failure cases, troubleshooting clues, rollback steps and final client-facing completion criteria. IMPLEMENTATION SAFETY Flag assumptions; favor native block controls over custom code; do not hardcode credentials or private data. For PHP/JS/CSS, provide exact location, activation scope, prerequisite checks, staging test, and undo method. If a plugin or version-specific behavior is uncertain, say what to verify first. Finish with a concise Definition of Done and a measurable business or UX outcome, without promising a result unsupported by data.
18. SEO, AEO & GEO Architecture
Search intent page map
Create a tested, client-ready outcome for search intent page map.
Act as a senior WordPress solution architect and Kadence Theme/Kadence Blocks/WPCode specialist. TASK: Search intent page map. PROJECT INPUTS - Website type and business goal: [SITE TYPE + GOAL] - Audience, locale and key conversion: [AUDIENCE + LOCALE + CTA] - Current stack (WordPress/PHP, Kadence Theme, Kadence Blocks, WPCode, plugins): [VERIFIED VERSIONS] - Current page, screenshot, issue or reference: [URL OR SANITIZED DETAILS] - Constraints (budget, editor skill, hosting, launch date): [CONSTRAINTS] - Existing content, brand styles and approved data: [SOURCE MATERIAL] SPECIFIC OBJECTIVE Develop a practical, results-oriented solution for search intent page map in the context of this website. Prioritize helpful, accurate content; validate schema eligibility and do not guarantee rankings or ai citations. Explain what should be done with Kadence Theme settings, what should be built with Kadence Blocks, and when WPCode is warranted. Do not invent installed plugin capabilities or pretend you accessed the live site. DELIVER EXACTLY 1. A task-specific implementation blueprint for “Search intent page map” with exact WordPress/Kadence navigation or WPCode placement when relevant. 2. An ordered action checklist with dependencies and who owns each action. 3. Copy-ready artifacts where relevant (block hierarchy, settings matrix, sample copy, scoped CSS, PHP or vanilla JavaScript), with code fences and placement instructions. 4. Desktop/tablet/mobile acceptance tests, accessibility and security checks relevant to the task. 5. Failure cases, troubleshooting clues, rollback steps and final client-facing completion criteria. IMPLEMENTATION SAFETY Flag assumptions; favor native block controls over custom code; do not hardcode credentials or private data. For PHP/JS/CSS, provide exact location, activation scope, prerequisite checks, staging test, and undo method. If a plugin or version-specific behavior is uncertain, say what to verify first. Finish with a concise Definition of Done and a measurable business or UX outcome, without promising a result unsupported by data.
Heading and entity coverage
Create a tested, client-ready outcome for heading and entity coverage.
Act as a senior WordPress solution architect and Kadence Theme/Kadence Blocks/WPCode specialist. TASK: Heading and entity coverage. PROJECT INPUTS - Website type and business goal: [SITE TYPE + GOAL] - Audience, locale and key conversion: [AUDIENCE + LOCALE + CTA] - Current stack (WordPress/PHP, Kadence Theme, Kadence Blocks, WPCode, plugins): [VERIFIED VERSIONS] - Current page, screenshot, issue or reference: [URL OR SANITIZED DETAILS] - Constraints (budget, editor skill, hosting, launch date): [CONSTRAINTS] - Existing content, brand styles and approved data: [SOURCE MATERIAL] SPECIFIC OBJECTIVE Develop a practical, results-oriented solution for heading and entity coverage in the context of this website. Prioritize helpful, accurate content; validate schema eligibility and do not guarantee rankings or ai citations. Explain what should be done with Kadence Theme settings, what should be built with Kadence Blocks, and when WPCode is warranted. Do not invent installed plugin capabilities or pretend you accessed the live site. DELIVER EXACTLY 1. A task-specific implementation blueprint for “Heading and entity coverage” with exact WordPress/Kadence navigation or WPCode placement when relevant. 2. An ordered action checklist with dependencies and who owns each action. 3. Copy-ready artifacts where relevant (block hierarchy, settings matrix, sample copy, scoped CSS, PHP or vanilla JavaScript), with code fences and placement instructions. 4. Desktop/tablet/mobile acceptance tests, accessibility and security checks relevant to the task. 5. Failure cases, troubleshooting clues, rollback steps and final client-facing completion criteria. IMPLEMENTATION SAFETY Flag assumptions; favor native block controls over custom code; do not hardcode credentials or private data. For PHP/JS/CSS, provide exact location, activation scope, prerequisite checks, staging test, and undo method. If a plugin or version-specific behavior is uncertain, say what to verify first. Finish with a concise Definition of Done and a measurable business or UX outcome, without promising a result unsupported by data.
Title and meta drafting
Create a tested, client-ready outcome for title and meta drafting.
Act as a senior WordPress solution architect and Kadence Theme/Kadence Blocks/WPCode specialist. TASK: Title and meta drafting. PROJECT INPUTS - Website type and business goal: [SITE TYPE + GOAL] - Audience, locale and key conversion: [AUDIENCE + LOCALE + CTA] - Current stack (WordPress/PHP, Kadence Theme, Kadence Blocks, WPCode, plugins): [VERIFIED VERSIONS] - Current page, screenshot, issue or reference: [URL OR SANITIZED DETAILS] - Constraints (budget, editor skill, hosting, launch date): [CONSTRAINTS] - Existing content, brand styles and approved data: [SOURCE MATERIAL] SPECIFIC OBJECTIVE Develop a practical, results-oriented solution for title and meta drafting in the context of this website. Prioritize helpful, accurate content; validate schema eligibility and do not guarantee rankings or ai citations. Explain what should be done with Kadence Theme settings, what should be built with Kadence Blocks, and when WPCode is warranted. Do not invent installed plugin capabilities or pretend you accessed the live site. DELIVER EXACTLY 1. A task-specific implementation blueprint for “Title and meta drafting” with exact WordPress/Kadence navigation or WPCode placement when relevant. 2. An ordered action checklist with dependencies and who owns each action. 3. Copy-ready artifacts where relevant (block hierarchy, settings matrix, sample copy, scoped CSS, PHP or vanilla JavaScript), with code fences and placement instructions. 4. Desktop/tablet/mobile acceptance tests, accessibility and security checks relevant to the task. 5. Failure cases, troubleshooting clues, rollback steps and final client-facing completion criteria. IMPLEMENTATION SAFETY Flag assumptions; favor native block controls over custom code; do not hardcode credentials or private data. For PHP/JS/CSS, provide exact location, activation scope, prerequisite checks, staging test, and undo method. If a plugin or version-specific behavior is uncertain, say what to verify first. Finish with a concise Definition of Done and a measurable business or UX outcome, without promising a result unsupported by data.
Internal link hub design
Create a tested, client-ready outcome for internal link hub design.
Act as a senior WordPress solution architect and Kadence Theme/Kadence Blocks/WPCode specialist. TASK: Internal link hub design. PROJECT INPUTS - Website type and business goal: [SITE TYPE + GOAL] - Audience, locale and key conversion: [AUDIENCE + LOCALE + CTA] - Current stack (WordPress/PHP, Kadence Theme, Kadence Blocks, WPCode, plugins): [VERIFIED VERSIONS] - Current page, screenshot, issue or reference: [URL OR SANITIZED DETAILS] - Constraints (budget, editor skill, hosting, launch date): [CONSTRAINTS] - Existing content, brand styles and approved data: [SOURCE MATERIAL] SPECIFIC OBJECTIVE Develop a practical, results-oriented solution for internal link hub design in the context of this website. Prioritize helpful, accurate content; validate schema eligibility and do not guarantee rankings or ai citations. Explain what should be done with Kadence Theme settings, what should be built with Kadence Blocks, and when WPCode is warranted. Do not invent installed plugin capabilities or pretend you accessed the live site. DELIVER EXACTLY 1. A task-specific implementation blueprint for “Internal link hub design” with exact WordPress/Kadence navigation or WPCode placement when relevant. 2. An ordered action checklist with dependencies and who owns each action. 3. Copy-ready artifacts where relevant (block hierarchy, settings matrix, sample copy, scoped CSS, PHP or vanilla JavaScript), with code fences and placement instructions. 4. Desktop/tablet/mobile acceptance tests, accessibility and security checks relevant to the task. 5. Failure cases, troubleshooting clues, rollback steps and final client-facing completion criteria. IMPLEMENTATION SAFETY Flag assumptions; favor native block controls over custom code; do not hardcode credentials or private data. For PHP/JS/CSS, provide exact location, activation scope, prerequisite checks, staging test, and undo method. If a plugin or version-specific behavior is uncertain, say what to verify first. Finish with a concise Definition of Done and a measurable business or UX outcome, without promising a result unsupported by data.
Schema eligibility audit
Create a tested, client-ready outcome for schema eligibility audit.
Act as a senior WordPress solution architect and Kadence Theme/Kadence Blocks/WPCode specialist. TASK: Schema eligibility audit. PROJECT INPUTS - Website type and business goal: [SITE TYPE + GOAL] - Audience, locale and key conversion: [AUDIENCE + LOCALE + CTA] - Current stack (WordPress/PHP, Kadence Theme, Kadence Blocks, WPCode, plugins): [VERIFIED VERSIONS] - Current page, screenshot, issue or reference: [URL OR SANITIZED DETAILS] - Constraints (budget, editor skill, hosting, launch date): [CONSTRAINTS] - Existing content, brand styles and approved data: [SOURCE MATERIAL] SPECIFIC OBJECTIVE Develop a practical, results-oriented solution for schema eligibility audit in the context of this website. Prioritize helpful, accurate content; validate schema eligibility and do not guarantee rankings or ai citations. Explain what should be done with Kadence Theme settings, what should be built with Kadence Blocks, and when WPCode is warranted. Do not invent installed plugin capabilities or pretend you accessed the live site. DELIVER EXACTLY 1. A task-specific implementation blueprint for “Schema eligibility audit” with exact WordPress/Kadence navigation or WPCode placement when relevant. 2. An ordered action checklist with dependencies and who owns each action. 3. Copy-ready artifacts where relevant (block hierarchy, settings matrix, sample copy, scoped CSS, PHP or vanilla JavaScript), with code fences and placement instructions. 4. Desktop/tablet/mobile acceptance tests, accessibility and security checks relevant to the task. 5. Failure cases, troubleshooting clues, rollback steps and final client-facing completion criteria. IMPLEMENTATION SAFETY Flag assumptions; favor native block controls over custom code; do not hardcode credentials or private data. For PHP/JS/CSS, provide exact location, activation scope, prerequisite checks, staging test, and undo method. If a plugin or version-specific behavior is uncertain, say what to verify first. Finish with a concise Definition of Done and a measurable business or UX outcome, without promising a result unsupported by data.
FAQ direct-answer design
Create a tested, client-ready outcome for faq direct-answer design.
Act as a senior WordPress solution architect and Kadence Theme/Kadence Blocks/WPCode specialist. TASK: FAQ direct-answer design. PROJECT INPUTS - Website type and business goal: [SITE TYPE + GOAL] - Audience, locale and key conversion: [AUDIENCE + LOCALE + CTA] - Current stack (WordPress/PHP, Kadence Theme, Kadence Blocks, WPCode, plugins): [VERIFIED VERSIONS] - Current page, screenshot, issue or reference: [URL OR SANITIZED DETAILS] - Constraints (budget, editor skill, hosting, launch date): [CONSTRAINTS] - Existing content, brand styles and approved data: [SOURCE MATERIAL] SPECIFIC OBJECTIVE Develop a practical, results-oriented solution for faq direct-answer design in the context of this website. Prioritize helpful, accurate content; validate schema eligibility and do not guarantee rankings or ai citations. Explain what should be done with Kadence Theme settings, what should be built with Kadence Blocks, and when WPCode is warranted. Do not invent installed plugin capabilities or pretend you accessed the live site. DELIVER EXACTLY 1. A task-specific implementation blueprint for “FAQ direct-answer design” with exact WordPress/Kadence navigation or WPCode placement when relevant. 2. An ordered action checklist with dependencies and who owns each action. 3. Copy-ready artifacts where relevant (block hierarchy, settings matrix, sample copy, scoped CSS, PHP or vanilla JavaScript), with code fences and placement instructions. 4. Desktop/tablet/mobile acceptance tests, accessibility and security checks relevant to the task. 5. Failure cases, troubleshooting clues, rollback steps and final client-facing completion criteria. IMPLEMENTATION SAFETY Flag assumptions; favor native block controls over custom code; do not hardcode credentials or private data. For PHP/JS/CSS, provide exact location, activation scope, prerequisite checks, staging test, and undo method. If a plugin or version-specific behavior is uncertain, say what to verify first. Finish with a concise Definition of Done and a measurable business or UX outcome, without promising a result unsupported by data.
Breadcrumb implementation check
Create a tested, client-ready outcome for breadcrumb implementation check.
Act as a senior WordPress solution architect and Kadence Theme/Kadence Blocks/WPCode specialist. TASK: Breadcrumb implementation check. PROJECT INPUTS - Website type and business goal: [SITE TYPE + GOAL] - Audience, locale and key conversion: [AUDIENCE + LOCALE + CTA] - Current stack (WordPress/PHP, Kadence Theme, Kadence Blocks, WPCode, plugins): [VERIFIED VERSIONS] - Current page, screenshot, issue or reference: [URL OR SANITIZED DETAILS] - Constraints (budget, editor skill, hosting, launch date): [CONSTRAINTS] - Existing content, brand styles and approved data: [SOURCE MATERIAL] SPECIFIC OBJECTIVE Develop a practical, results-oriented solution for breadcrumb implementation check in the context of this website. Prioritize helpful, accurate content; validate schema eligibility and do not guarantee rankings or ai citations. Explain what should be done with Kadence Theme settings, what should be built with Kadence Blocks, and when WPCode is warranted. Do not invent installed plugin capabilities or pretend you accessed the live site. DELIVER EXACTLY 1. A task-specific implementation blueprint for “Breadcrumb implementation check” with exact WordPress/Kadence navigation or WPCode placement when relevant. 2. An ordered action checklist with dependencies and who owns each action. 3. Copy-ready artifacts where relevant (block hierarchy, settings matrix, sample copy, scoped CSS, PHP or vanilla JavaScript), with code fences and placement instructions. 4. Desktop/tablet/mobile acceptance tests, accessibility and security checks relevant to the task. 5. Failure cases, troubleshooting clues, rollback steps and final client-facing completion criteria. IMPLEMENTATION SAFETY Flag assumptions; favor native block controls over custom code; do not hardcode credentials or private data. For PHP/JS/CSS, provide exact location, activation scope, prerequisite checks, staging test, and undo method. If a plugin or version-specific behavior is uncertain, say what to verify first. Finish with a concise Definition of Done and a measurable business or UX outcome, without promising a result unsupported by data.
Canonical and indexation audit
Create a tested, client-ready outcome for canonical and indexation audit.
Act as a senior WordPress solution architect and Kadence Theme/Kadence Blocks/WPCode specialist. TASK: Canonical and indexation audit. PROJECT INPUTS - Website type and business goal: [SITE TYPE + GOAL] - Audience, locale and key conversion: [AUDIENCE + LOCALE + CTA] - Current stack (WordPress/PHP, Kadence Theme, Kadence Blocks, WPCode, plugins): [VERIFIED VERSIONS] - Current page, screenshot, issue or reference: [URL OR SANITIZED DETAILS] - Constraints (budget, editor skill, hosting, launch date): [CONSTRAINTS] - Existing content, brand styles and approved data: [SOURCE MATERIAL] SPECIFIC OBJECTIVE Develop a practical, results-oriented solution for canonical and indexation audit in the context of this website. Prioritize helpful, accurate content; validate schema eligibility and do not guarantee rankings or ai citations. Explain what should be done with Kadence Theme settings, what should be built with Kadence Blocks, and when WPCode is warranted. Do not invent installed plugin capabilities or pretend you accessed the live site. DELIVER EXACTLY 1. A task-specific implementation blueprint for “Canonical and indexation audit” with exact WordPress/Kadence navigation or WPCode placement when relevant. 2. An ordered action checklist with dependencies and who owns each action. 3. Copy-ready artifacts where relevant (block hierarchy, settings matrix, sample copy, scoped CSS, PHP or vanilla JavaScript), with code fences and placement instructions. 4. Desktop/tablet/mobile acceptance tests, accessibility and security checks relevant to the task. 5. Failure cases, troubleshooting clues, rollback steps and final client-facing completion criteria. IMPLEMENTATION SAFETY Flag assumptions; favor native block controls over custom code; do not hardcode credentials or private data. For PHP/JS/CSS, provide exact location, activation scope, prerequisite checks, staging test, and undo method. If a plugin or version-specific behavior is uncertain, say what to verify first. Finish with a concise Definition of Done and a measurable business or UX outcome, without promising a result unsupported by data.
XML sitemap governance
Create a tested, client-ready outcome for xml sitemap governance.
Act as a senior WordPress solution architect and Kadence Theme/Kadence Blocks/WPCode specialist. TASK: XML sitemap governance. PROJECT INPUTS - Website type and business goal: [SITE TYPE + GOAL] - Audience, locale and key conversion: [AUDIENCE + LOCALE + CTA] - Current stack (WordPress/PHP, Kadence Theme, Kadence Blocks, WPCode, plugins): [VERIFIED VERSIONS] - Current page, screenshot, issue or reference: [URL OR SANITIZED DETAILS] - Constraints (budget, editor skill, hosting, launch date): [CONSTRAINTS] - Existing content, brand styles and approved data: [SOURCE MATERIAL] SPECIFIC OBJECTIVE Develop a practical, results-oriented solution for xml sitemap governance in the context of this website. Prioritize helpful, accurate content; validate schema eligibility and do not guarantee rankings or ai citations. Explain what should be done with Kadence Theme settings, what should be built with Kadence Blocks, and when WPCode is warranted. Do not invent installed plugin capabilities or pretend you accessed the live site. DELIVER EXACTLY 1. A task-specific implementation blueprint for “XML sitemap governance” with exact WordPress/Kadence navigation or WPCode placement when relevant. 2. An ordered action checklist with dependencies and who owns each action. 3. Copy-ready artifacts where relevant (block hierarchy, settings matrix, sample copy, scoped CSS, PHP or vanilla JavaScript), with code fences and placement instructions. 4. Desktop/tablet/mobile acceptance tests, accessibility and security checks relevant to the task. 5. Failure cases, troubleshooting clues, rollback steps and final client-facing completion criteria. IMPLEMENTATION SAFETY Flag assumptions; favor native block controls over custom code; do not hardcode credentials or private data. For PHP/JS/CSS, provide exact location, activation scope, prerequisite checks, staging test, and undo method. If a plugin or version-specific behavior is uncertain, say what to verify first. Finish with a concise Definition of Done and a measurable business or UX outcome, without promising a result unsupported by data.
AI-answer citation readiness
Create a tested, client-ready outcome for ai-answer citation readiness.
Act as a senior WordPress solution architect and Kadence Theme/Kadence Blocks/WPCode specialist. TASK: AI-answer citation readiness. PROJECT INPUTS - Website type and business goal: [SITE TYPE + GOAL] - Audience, locale and key conversion: [AUDIENCE + LOCALE + CTA] - Current stack (WordPress/PHP, Kadence Theme, Kadence Blocks, WPCode, plugins): [VERIFIED VERSIONS] - Current page, screenshot, issue or reference: [URL OR SANITIZED DETAILS] - Constraints (budget, editor skill, hosting, launch date): [CONSTRAINTS] - Existing content, brand styles and approved data: [SOURCE MATERIAL] SPECIFIC OBJECTIVE Develop a practical, results-oriented solution for ai-answer citation readiness in the context of this website. Prioritize helpful, accurate content; validate schema eligibility and do not guarantee rankings or ai citations. Explain what should be done with Kadence Theme settings, what should be built with Kadence Blocks, and when WPCode is warranted. Do not invent installed plugin capabilities or pretend you accessed the live site. DELIVER EXACTLY 1. A task-specific implementation blueprint for “AI-answer citation readiness” with exact WordPress/Kadence navigation or WPCode placement when relevant. 2. An ordered action checklist with dependencies and who owns each action. 3. Copy-ready artifacts where relevant (block hierarchy, settings matrix, sample copy, scoped CSS, PHP or vanilla JavaScript), with code fences and placement instructions. 4. Desktop/tablet/mobile acceptance tests, accessibility and security checks relevant to the task. 5. Failure cases, troubleshooting clues, rollback steps and final client-facing completion criteria. IMPLEMENTATION SAFETY Flag assumptions; favor native block controls over custom code; do not hardcode credentials or private data. For PHP/JS/CSS, provide exact location, activation scope, prerequisite checks, staging test, and undo method. If a plugin or version-specific behavior is uncertain, say what to verify first. Finish with a concise Definition of Done and a measurable business or UX outcome, without promising a result unsupported by data.
19. Core Web Vitals & Performance
Performance baseline report
Create a tested, client-ready outcome for performance baseline report.
Act as a senior WordPress solution architect and Kadence Theme/Kadence Blocks/WPCode specialist. TASK: Performance baseline report. PROJECT INPUTS - Website type and business goal: [SITE TYPE + GOAL] - Audience, locale and key conversion: [AUDIENCE + LOCALE + CTA] - Current stack (WordPress/PHP, Kadence Theme, Kadence Blocks, WPCode, plugins): [VERIFIED VERSIONS] - Current page, screenshot, issue or reference: [URL OR SANITIZED DETAILS] - Constraints (budget, editor skill, hosting, launch date): [CONSTRAINTS] - Existing content, brand styles and approved data: [SOURCE MATERIAL] SPECIFIC OBJECTIVE Develop a practical, results-oriented solution for performance baseline report in the context of this website. Require baseline metrics and measured post-change checks; avoid blanket plugin disabling. Explain what should be done with Kadence Theme settings, what should be built with Kadence Blocks, and when WPCode is warranted. Do not invent installed plugin capabilities or pretend you accessed the live site. DELIVER EXACTLY 1. A task-specific implementation blueprint for “Performance baseline report” with exact WordPress/Kadence navigation or WPCode placement when relevant. 2. An ordered action checklist with dependencies and who owns each action. 3. Copy-ready artifacts where relevant (block hierarchy, settings matrix, sample copy, scoped CSS, PHP or vanilla JavaScript), with code fences and placement instructions. 4. Desktop/tablet/mobile acceptance tests, accessibility and security checks relevant to the task. 5. Failure cases, troubleshooting clues, rollback steps and final client-facing completion criteria. IMPLEMENTATION SAFETY Flag assumptions; favor native block controls over custom code; do not hardcode credentials or private data. For PHP/JS/CSS, provide exact location, activation scope, prerequisite checks, staging test, and undo method. If a plugin or version-specific behavior is uncertain, say what to verify first. Finish with a concise Definition of Done and a measurable business or UX outcome, without promising a result unsupported by data.
LCP image optimization
Create a tested, client-ready outcome for lcp image optimization.
Act as a senior WordPress solution architect and Kadence Theme/Kadence Blocks/WPCode specialist. TASK: LCP image optimization. PROJECT INPUTS - Website type and business goal: [SITE TYPE + GOAL] - Audience, locale and key conversion: [AUDIENCE + LOCALE + CTA] - Current stack (WordPress/PHP, Kadence Theme, Kadence Blocks, WPCode, plugins): [VERIFIED VERSIONS] - Current page, screenshot, issue or reference: [URL OR SANITIZED DETAILS] - Constraints (budget, editor skill, hosting, launch date): [CONSTRAINTS] - Existing content, brand styles and approved data: [SOURCE MATERIAL] SPECIFIC OBJECTIVE Develop a practical, results-oriented solution for lcp image optimization in the context of this website. Require baseline metrics and measured post-change checks; avoid blanket plugin disabling. Explain what should be done with Kadence Theme settings, what should be built with Kadence Blocks, and when WPCode is warranted. Do not invent installed plugin capabilities or pretend you accessed the live site. DELIVER EXACTLY 1. A task-specific implementation blueprint for “LCP image optimization” with exact WordPress/Kadence navigation or WPCode placement when relevant. 2. An ordered action checklist with dependencies and who owns each action. 3. Copy-ready artifacts where relevant (block hierarchy, settings matrix, sample copy, scoped CSS, PHP or vanilla JavaScript), with code fences and placement instructions. 4. Desktop/tablet/mobile acceptance tests, accessibility and security checks relevant to the task. 5. Failure cases, troubleshooting clues, rollback steps and final client-facing completion criteria. IMPLEMENTATION SAFETY Flag assumptions; favor native block controls over custom code; do not hardcode credentials or private data. For PHP/JS/CSS, provide exact location, activation scope, prerequisite checks, staging test, and undo method. If a plugin or version-specific behavior is uncertain, say what to verify first. Finish with a concise Definition of Done and a measurable business or UX outcome, without promising a result unsupported by data.
CLS layout stability fix
Create a tested, client-ready outcome for cls layout stability fix.
Act as a senior WordPress solution architect and Kadence Theme/Kadence Blocks/WPCode specialist. TASK: CLS layout stability fix. PROJECT INPUTS - Website type and business goal: [SITE TYPE + GOAL] - Audience, locale and key conversion: [AUDIENCE + LOCALE + CTA] - Current stack (WordPress/PHP, Kadence Theme, Kadence Blocks, WPCode, plugins): [VERIFIED VERSIONS] - Current page, screenshot, issue or reference: [URL OR SANITIZED DETAILS] - Constraints (budget, editor skill, hosting, launch date): [CONSTRAINTS] - Existing content, brand styles and approved data: [SOURCE MATERIAL] SPECIFIC OBJECTIVE Develop a practical, results-oriented solution for cls layout stability fix in the context of this website. Require baseline metrics and measured post-change checks; avoid blanket plugin disabling. Explain what should be done with Kadence Theme settings, what should be built with Kadence Blocks, and when WPCode is warranted. Do not invent installed plugin capabilities or pretend you accessed the live site. DELIVER EXACTLY 1. A task-specific implementation blueprint for “CLS layout stability fix” with exact WordPress/Kadence navigation or WPCode placement when relevant. 2. An ordered action checklist with dependencies and who owns each action. 3. Copy-ready artifacts where relevant (block hierarchy, settings matrix, sample copy, scoped CSS, PHP or vanilla JavaScript), with code fences and placement instructions. 4. Desktop/tablet/mobile acceptance tests, accessibility and security checks relevant to the task. 5. Failure cases, troubleshooting clues, rollback steps and final client-facing completion criteria. IMPLEMENTATION SAFETY Flag assumptions; favor native block controls over custom code; do not hardcode credentials or private data. For PHP/JS/CSS, provide exact location, activation scope, prerequisite checks, staging test, and undo method. If a plugin or version-specific behavior is uncertain, say what to verify first. Finish with a concise Definition of Done and a measurable business or UX outcome, without promising a result unsupported by data.
INP interaction audit
Create a tested, client-ready outcome for inp interaction audit.
Act as a senior WordPress solution architect and Kadence Theme/Kadence Blocks/WPCode specialist. TASK: INP interaction audit. PROJECT INPUTS - Website type and business goal: [SITE TYPE + GOAL] - Audience, locale and key conversion: [AUDIENCE + LOCALE + CTA] - Current stack (WordPress/PHP, Kadence Theme, Kadence Blocks, WPCode, plugins): [VERIFIED VERSIONS] - Current page, screenshot, issue or reference: [URL OR SANITIZED DETAILS] - Constraints (budget, editor skill, hosting, launch date): [CONSTRAINTS] - Existing content, brand styles and approved data: [SOURCE MATERIAL] SPECIFIC OBJECTIVE Develop a practical, results-oriented solution for inp interaction audit in the context of this website. Require baseline metrics and measured post-change checks; avoid blanket plugin disabling. Explain what should be done with Kadence Theme settings, what should be built with Kadence Blocks, and when WPCode is warranted. Do not invent installed plugin capabilities or pretend you accessed the live site. DELIVER EXACTLY 1. A task-specific implementation blueprint for “INP interaction audit” with exact WordPress/Kadence navigation or WPCode placement when relevant. 2. An ordered action checklist with dependencies and who owns each action. 3. Copy-ready artifacts where relevant (block hierarchy, settings matrix, sample copy, scoped CSS, PHP or vanilla JavaScript), with code fences and placement instructions. 4. Desktop/tablet/mobile acceptance tests, accessibility and security checks relevant to the task. 5. Failure cases, troubleshooting clues, rollback steps and final client-facing completion criteria. IMPLEMENTATION SAFETY Flag assumptions; favor native block controls over custom code; do not hardcode credentials or private data. For PHP/JS/CSS, provide exact location, activation scope, prerequisite checks, staging test, and undo method. If a plugin or version-specific behavior is uncertain, say what to verify first. Finish with a concise Definition of Done and a measurable business or UX outcome, without promising a result unsupported by data.
Font loading strategy
Create a tested, client-ready outcome for font loading strategy.
Act as a senior WordPress solution architect and Kadence Theme/Kadence Blocks/WPCode specialist. TASK: Font loading strategy. PROJECT INPUTS - Website type and business goal: [SITE TYPE + GOAL] - Audience, locale and key conversion: [AUDIENCE + LOCALE + CTA] - Current stack (WordPress/PHP, Kadence Theme, Kadence Blocks, WPCode, plugins): [VERIFIED VERSIONS] - Current page, screenshot, issue or reference: [URL OR SANITIZED DETAILS] - Constraints (budget, editor skill, hosting, launch date): [CONSTRAINTS] - Existing content, brand styles and approved data: [SOURCE MATERIAL] SPECIFIC OBJECTIVE Develop a practical, results-oriented solution for font loading strategy in the context of this website. Require baseline metrics and measured post-change checks; avoid blanket plugin disabling. Explain what should be done with Kadence Theme settings, what should be built with Kadence Blocks, and when WPCode is warranted. Do not invent installed plugin capabilities or pretend you accessed the live site. DELIVER EXACTLY 1. A task-specific implementation blueprint for “Font loading strategy” with exact WordPress/Kadence navigation or WPCode placement when relevant. 2. An ordered action checklist with dependencies and who owns each action. 3. Copy-ready artifacts where relevant (block hierarchy, settings matrix, sample copy, scoped CSS, PHP or vanilla JavaScript), with code fences and placement instructions. 4. Desktop/tablet/mobile acceptance tests, accessibility and security checks relevant to the task. 5. Failure cases, troubleshooting clues, rollback steps and final client-facing completion criteria. IMPLEMENTATION SAFETY Flag assumptions; favor native block controls over custom code; do not hardcode credentials or private data. For PHP/JS/CSS, provide exact location, activation scope, prerequisite checks, staging test, and undo method. If a plugin or version-specific behavior is uncertain, say what to verify first. Finish with a concise Definition of Done and a measurable business or UX outcome, without promising a result unsupported by data.
Kadence asset optimization
Create a tested, client-ready outcome for kadence asset optimization.
Act as a senior WordPress solution architect and Kadence Theme/Kadence Blocks/WPCode specialist. TASK: Kadence asset optimization. PROJECT INPUTS - Website type and business goal: [SITE TYPE + GOAL] - Audience, locale and key conversion: [AUDIENCE + LOCALE + CTA] - Current stack (WordPress/PHP, Kadence Theme, Kadence Blocks, WPCode, plugins): [VERIFIED VERSIONS] - Current page, screenshot, issue or reference: [URL OR SANITIZED DETAILS] - Constraints (budget, editor skill, hosting, launch date): [CONSTRAINTS] - Existing content, brand styles and approved data: [SOURCE MATERIAL] SPECIFIC OBJECTIVE Develop a practical, results-oriented solution for kadence asset optimization in the context of this website. Require baseline metrics and measured post-change checks; avoid blanket plugin disabling. Explain what should be done with Kadence Theme settings, what should be built with Kadence Blocks, and when WPCode is warranted. Do not invent installed plugin capabilities or pretend you accessed the live site. DELIVER EXACTLY 1. A task-specific implementation blueprint for “Kadence asset optimization” with exact WordPress/Kadence navigation or WPCode placement when relevant. 2. An ordered action checklist with dependencies and who owns each action. 3. Copy-ready artifacts where relevant (block hierarchy, settings matrix, sample copy, scoped CSS, PHP or vanilla JavaScript), with code fences and placement instructions. 4. Desktop/tablet/mobile acceptance tests, accessibility and security checks relevant to the task. 5. Failure cases, troubleshooting clues, rollback steps and final client-facing completion criteria. IMPLEMENTATION SAFETY Flag assumptions; favor native block controls over custom code; do not hardcode credentials or private data. For PHP/JS/CSS, provide exact location, activation scope, prerequisite checks, staging test, and undo method. If a plugin or version-specific behavior is uncertain, say what to verify first. Finish with a concise Definition of Done and a measurable business or UX outcome, without promising a result unsupported by data.
Plugin bloat investigation
Create a tested, client-ready outcome for plugin bloat investigation.
Act as a senior WordPress solution architect and Kadence Theme/Kadence Blocks/WPCode specialist. TASK: Plugin bloat investigation. PROJECT INPUTS - Website type and business goal: [SITE TYPE + GOAL] - Audience, locale and key conversion: [AUDIENCE + LOCALE + CTA] - Current stack (WordPress/PHP, Kadence Theme, Kadence Blocks, WPCode, plugins): [VERIFIED VERSIONS] - Current page, screenshot, issue or reference: [URL OR SANITIZED DETAILS] - Constraints (budget, editor skill, hosting, launch date): [CONSTRAINTS] - Existing content, brand styles and approved data: [SOURCE MATERIAL] SPECIFIC OBJECTIVE Develop a practical, results-oriented solution for plugin bloat investigation in the context of this website. Require baseline metrics and measured post-change checks; avoid blanket plugin disabling. Explain what should be done with Kadence Theme settings, what should be built with Kadence Blocks, and when WPCode is warranted. Do not invent installed plugin capabilities or pretend you accessed the live site. DELIVER EXACTLY 1. A task-specific implementation blueprint for “Plugin bloat investigation” with exact WordPress/Kadence navigation or WPCode placement when relevant. 2. An ordered action checklist with dependencies and who owns each action. 3. Copy-ready artifacts where relevant (block hierarchy, settings matrix, sample copy, scoped CSS, PHP or vanilla JavaScript), with code fences and placement instructions. 4. Desktop/tablet/mobile acceptance tests, accessibility and security checks relevant to the task. 5. Failure cases, troubleshooting clues, rollback steps and final client-facing completion criteria. IMPLEMENTATION SAFETY Flag assumptions; favor native block controls over custom code; do not hardcode credentials or private data. For PHP/JS/CSS, provide exact location, activation scope, prerequisite checks, staging test, and undo method. If a plugin or version-specific behavior is uncertain, say what to verify first. Finish with a concise Definition of Done and a measurable business or UX outcome, without promising a result unsupported by data.
Caching compatibility check
Create a tested, client-ready outcome for caching compatibility check.
Act as a senior WordPress solution architect and Kadence Theme/Kadence Blocks/WPCode specialist. TASK: Caching compatibility check. PROJECT INPUTS - Website type and business goal: [SITE TYPE + GOAL] - Audience, locale and key conversion: [AUDIENCE + LOCALE + CTA] - Current stack (WordPress/PHP, Kadence Theme, Kadence Blocks, WPCode, plugins): [VERIFIED VERSIONS] - Current page, screenshot, issue or reference: [URL OR SANITIZED DETAILS] - Constraints (budget, editor skill, hosting, launch date): [CONSTRAINTS] - Existing content, brand styles and approved data: [SOURCE MATERIAL] SPECIFIC OBJECTIVE Develop a practical, results-oriented solution for caching compatibility check in the context of this website. Require baseline metrics and measured post-change checks; avoid blanket plugin disabling. Explain what should be done with Kadence Theme settings, what should be built with Kadence Blocks, and when WPCode is warranted. Do not invent installed plugin capabilities or pretend you accessed the live site. DELIVER EXACTLY 1. A task-specific implementation blueprint for “Caching compatibility check” with exact WordPress/Kadence navigation or WPCode placement when relevant. 2. An ordered action checklist with dependencies and who owns each action. 3. Copy-ready artifacts where relevant (block hierarchy, settings matrix, sample copy, scoped CSS, PHP or vanilla JavaScript), with code fences and placement instructions. 4. Desktop/tablet/mobile acceptance tests, accessibility and security checks relevant to the task. 5. Failure cases, troubleshooting clues, rollback steps and final client-facing completion criteria. IMPLEMENTATION SAFETY Flag assumptions; favor native block controls over custom code; do not hardcode credentials or private data. For PHP/JS/CSS, provide exact location, activation scope, prerequisite checks, staging test, and undo method. If a plugin or version-specific behavior is uncertain, say what to verify first. Finish with a concise Definition of Done and a measurable business or UX outcome, without promising a result unsupported by data.
Image delivery pipeline
Create a tested, client-ready outcome for image delivery pipeline.
Act as a senior WordPress solution architect and Kadence Theme/Kadence Blocks/WPCode specialist. TASK: Image delivery pipeline. PROJECT INPUTS - Website type and business goal: [SITE TYPE + GOAL] - Audience, locale and key conversion: [AUDIENCE + LOCALE + CTA] - Current stack (WordPress/PHP, Kadence Theme, Kadence Blocks, WPCode, plugins): [VERIFIED VERSIONS] - Current page, screenshot, issue or reference: [URL OR SANITIZED DETAILS] - Constraints (budget, editor skill, hosting, launch date): [CONSTRAINTS] - Existing content, brand styles and approved data: [SOURCE MATERIAL] SPECIFIC OBJECTIVE Develop a practical, results-oriented solution for image delivery pipeline in the context of this website. Require baseline metrics and measured post-change checks; avoid blanket plugin disabling. Explain what should be done with Kadence Theme settings, what should be built with Kadence Blocks, and when WPCode is warranted. Do not invent installed plugin capabilities or pretend you accessed the live site. DELIVER EXACTLY 1. A task-specific implementation blueprint for “Image delivery pipeline” with exact WordPress/Kadence navigation or WPCode placement when relevant. 2. An ordered action checklist with dependencies and who owns each action. 3. Copy-ready artifacts where relevant (block hierarchy, settings matrix, sample copy, scoped CSS, PHP or vanilla JavaScript), with code fences and placement instructions. 4. Desktop/tablet/mobile acceptance tests, accessibility and security checks relevant to the task. 5. Failure cases, troubleshooting clues, rollback steps and final client-facing completion criteria. IMPLEMENTATION SAFETY Flag assumptions; favor native block controls over custom code; do not hardcode credentials or private data. For PHP/JS/CSS, provide exact location, activation scope, prerequisite checks, staging test, and undo method. If a plugin or version-specific behavior is uncertain, say what to verify first. Finish with a concise Definition of Done and a measurable business or UX outcome, without promising a result unsupported by data.
Before-after speed verification
Create a tested, client-ready outcome for before-after speed verification.
Act as a senior WordPress solution architect and Kadence Theme/Kadence Blocks/WPCode specialist. TASK: Before-after speed verification. PROJECT INPUTS - Website type and business goal: [SITE TYPE + GOAL] - Audience, locale and key conversion: [AUDIENCE + LOCALE + CTA] - Current stack (WordPress/PHP, Kadence Theme, Kadence Blocks, WPCode, plugins): [VERIFIED VERSIONS] - Current page, screenshot, issue or reference: [URL OR SANITIZED DETAILS] - Constraints (budget, editor skill, hosting, launch date): [CONSTRAINTS] - Existing content, brand styles and approved data: [SOURCE MATERIAL] SPECIFIC OBJECTIVE Develop a practical, results-oriented solution for before-after speed verification in the context of this website. Require baseline metrics and measured post-change checks; avoid blanket plugin disabling. Explain what should be done with Kadence Theme settings, what should be built with Kadence Blocks, and when WPCode is warranted. Do not invent installed plugin capabilities or pretend you accessed the live site. DELIVER EXACTLY 1. A task-specific implementation blueprint for “Before-after speed verification” with exact WordPress/Kadence navigation or WPCode placement when relevant. 2. An ordered action checklist with dependencies and who owns each action. 3. Copy-ready artifacts where relevant (block hierarchy, settings matrix, sample copy, scoped CSS, PHP or vanilla JavaScript), with code fences and placement instructions. 4. Desktop/tablet/mobile acceptance tests, accessibility and security checks relevant to the task. 5. Failure cases, troubleshooting clues, rollback steps and final client-facing completion criteria. IMPLEMENTATION SAFETY Flag assumptions; favor native block controls over custom code; do not hardcode credentials or private data. For PHP/JS/CSS, provide exact location, activation scope, prerequisite checks, staging test, and undo method. If a plugin or version-specific behavior is uncertain, say what to verify first. Finish with a concise Definition of Done and a measurable business or UX outcome, without promising a result unsupported by data.
20. Accessibility & Inclusive UX
WCAG audit checklist
Create a tested, client-ready outcome for wcag audit checklist.
Act as a senior WordPress solution architect and Kadence Theme/Kadence Blocks/WPCode specialist. TASK: WCAG audit checklist. PROJECT INPUTS - Website type and business goal: [SITE TYPE + GOAL] - Audience, locale and key conversion: [AUDIENCE + LOCALE + CTA] - Current stack (WordPress/PHP, Kadence Theme, Kadence Blocks, WPCode, plugins): [VERIFIED VERSIONS] - Current page, screenshot, issue or reference: [URL OR SANITIZED DETAILS] - Constraints (budget, editor skill, hosting, launch date): [CONSTRAINTS] - Existing content, brand styles and approved data: [SOURCE MATERIAL] SPECIFIC OBJECTIVE Develop a practical, results-oriented solution for wcag audit checklist in the context of this website. Include keyboard, screen reader, reduced-motion and zoom checks as applicable. Explain what should be done with Kadence Theme settings, what should be built with Kadence Blocks, and when WPCode is warranted. Do not invent installed plugin capabilities or pretend you accessed the live site. DELIVER EXACTLY 1. A task-specific implementation blueprint for “WCAG audit checklist” with exact WordPress/Kadence navigation or WPCode placement when relevant. 2. An ordered action checklist with dependencies and who owns each action. 3. Copy-ready artifacts where relevant (block hierarchy, settings matrix, sample copy, scoped CSS, PHP or vanilla JavaScript), with code fences and placement instructions. 4. Desktop/tablet/mobile acceptance tests, accessibility and security checks relevant to the task. 5. Failure cases, troubleshooting clues, rollback steps and final client-facing completion criteria. IMPLEMENTATION SAFETY Flag assumptions; favor native block controls over custom code; do not hardcode credentials or private data. For PHP/JS/CSS, provide exact location, activation scope, prerequisite checks, staging test, and undo method. If a plugin or version-specific behavior is uncertain, say what to verify first. Finish with a concise Definition of Done and a measurable business or UX outcome, without promising a result unsupported by data.
Keyboard navigation test
Create a tested, client-ready outcome for keyboard navigation test.
Act as a senior WordPress solution architect and Kadence Theme/Kadence Blocks/WPCode specialist. TASK: Keyboard navigation test. PROJECT INPUTS - Website type and business goal: [SITE TYPE + GOAL] - Audience, locale and key conversion: [AUDIENCE + LOCALE + CTA] - Current stack (WordPress/PHP, Kadence Theme, Kadence Blocks, WPCode, plugins): [VERIFIED VERSIONS] - Current page, screenshot, issue or reference: [URL OR SANITIZED DETAILS] - Constraints (budget, editor skill, hosting, launch date): [CONSTRAINTS] - Existing content, brand styles and approved data: [SOURCE MATERIAL] SPECIFIC OBJECTIVE Develop a practical, results-oriented solution for keyboard navigation test in the context of this website. Include keyboard, screen reader, reduced-motion and zoom checks as applicable. Explain what should be done with Kadence Theme settings, what should be built with Kadence Blocks, and when WPCode is warranted. Do not invent installed plugin capabilities or pretend you accessed the live site. DELIVER EXACTLY 1. A task-specific implementation blueprint for “Keyboard navigation test” with exact WordPress/Kadence navigation or WPCode placement when relevant. 2. An ordered action checklist with dependencies and who owns each action. 3. Copy-ready artifacts where relevant (block hierarchy, settings matrix, sample copy, scoped CSS, PHP or vanilla JavaScript), with code fences and placement instructions. 4. Desktop/tablet/mobile acceptance tests, accessibility and security checks relevant to the task. 5. Failure cases, troubleshooting clues, rollback steps and final client-facing completion criteria. IMPLEMENTATION SAFETY Flag assumptions; favor native block controls over custom code; do not hardcode credentials or private data. For PHP/JS/CSS, provide exact location, activation scope, prerequisite checks, staging test, and undo method. If a plugin or version-specific behavior is uncertain, say what to verify first. Finish with a concise Definition of Done and a measurable business or UX outcome, without promising a result unsupported by data.
Visible focus treatment
Create a tested, client-ready outcome for visible focus treatment.
Act as a senior WordPress solution architect and Kadence Theme/Kadence Blocks/WPCode specialist. TASK: Visible focus treatment. PROJECT INPUTS - Website type and business goal: [SITE TYPE + GOAL] - Audience, locale and key conversion: [AUDIENCE + LOCALE + CTA] - Current stack (WordPress/PHP, Kadence Theme, Kadence Blocks, WPCode, plugins): [VERIFIED VERSIONS] - Current page, screenshot, issue or reference: [URL OR SANITIZED DETAILS] - Constraints (budget, editor skill, hosting, launch date): [CONSTRAINTS] - Existing content, brand styles and approved data: [SOURCE MATERIAL] SPECIFIC OBJECTIVE Develop a practical, results-oriented solution for visible focus treatment in the context of this website. Include keyboard, screen reader, reduced-motion and zoom checks as applicable. Explain what should be done with Kadence Theme settings, what should be built with Kadence Blocks, and when WPCode is warranted. Do not invent installed plugin capabilities or pretend you accessed the live site. DELIVER EXACTLY 1. A task-specific implementation blueprint for “Visible focus treatment” with exact WordPress/Kadence navigation or WPCode placement when relevant. 2. An ordered action checklist with dependencies and who owns each action. 3. Copy-ready artifacts where relevant (block hierarchy, settings matrix, sample copy, scoped CSS, PHP or vanilla JavaScript), with code fences and placement instructions. 4. Desktop/tablet/mobile acceptance tests, accessibility and security checks relevant to the task. 5. Failure cases, troubleshooting clues, rollback steps and final client-facing completion criteria. IMPLEMENTATION SAFETY Flag assumptions; favor native block controls over custom code; do not hardcode credentials or private data. For PHP/JS/CSS, provide exact location, activation scope, prerequisite checks, staging test, and undo method. If a plugin or version-specific behavior is uncertain, say what to verify first. Finish with a concise Definition of Done and a measurable business or UX outcome, without promising a result unsupported by data.
Form label and error audit
Create a tested, client-ready outcome for form label and error audit.
Act as a senior WordPress solution architect and Kadence Theme/Kadence Blocks/WPCode specialist. TASK: Form label and error audit. PROJECT INPUTS - Website type and business goal: [SITE TYPE + GOAL] - Audience, locale and key conversion: [AUDIENCE + LOCALE + CTA] - Current stack (WordPress/PHP, Kadence Theme, Kadence Blocks, WPCode, plugins): [VERIFIED VERSIONS] - Current page, screenshot, issue or reference: [URL OR SANITIZED DETAILS] - Constraints (budget, editor skill, hosting, launch date): [CONSTRAINTS] - Existing content, brand styles and approved data: [SOURCE MATERIAL] SPECIFIC OBJECTIVE Develop a practical, results-oriented solution for form label and error audit in the context of this website. Include keyboard, screen reader, reduced-motion and zoom checks as applicable. Explain what should be done with Kadence Theme settings, what should be built with Kadence Blocks, and when WPCode is warranted. Do not invent installed plugin capabilities or pretend you accessed the live site. DELIVER EXACTLY 1. A task-specific implementation blueprint for “Form label and error audit” with exact WordPress/Kadence navigation or WPCode placement when relevant. 2. An ordered action checklist with dependencies and who owns each action. 3. Copy-ready artifacts where relevant (block hierarchy, settings matrix, sample copy, scoped CSS, PHP or vanilla JavaScript), with code fences and placement instructions. 4. Desktop/tablet/mobile acceptance tests, accessibility and security checks relevant to the task. 5. Failure cases, troubleshooting clues, rollback steps and final client-facing completion criteria. IMPLEMENTATION SAFETY Flag assumptions; favor native block controls over custom code; do not hardcode credentials or private data. For PHP/JS/CSS, provide exact location, activation scope, prerequisite checks, staging test, and undo method. If a plugin or version-specific behavior is uncertain, say what to verify first. Finish with a concise Definition of Done and a measurable business or UX outcome, without promising a result unsupported by data.
Color contrast remediation
Create a tested, client-ready outcome for color contrast remediation.
Act as a senior WordPress solution architect and Kadence Theme/Kadence Blocks/WPCode specialist. TASK: Color contrast remediation. PROJECT INPUTS - Website type and business goal: [SITE TYPE + GOAL] - Audience, locale and key conversion: [AUDIENCE + LOCALE + CTA] - Current stack (WordPress/PHP, Kadence Theme, Kadence Blocks, WPCode, plugins): [VERIFIED VERSIONS] - Current page, screenshot, issue or reference: [URL OR SANITIZED DETAILS] - Constraints (budget, editor skill, hosting, launch date): [CONSTRAINTS] - Existing content, brand styles and approved data: [SOURCE MATERIAL] SPECIFIC OBJECTIVE Develop a practical, results-oriented solution for color contrast remediation in the context of this website. Include keyboard, screen reader, reduced-motion and zoom checks as applicable. Explain what should be done with Kadence Theme settings, what should be built with Kadence Blocks, and when WPCode is warranted. Do not invent installed plugin capabilities or pretend you accessed the live site. DELIVER EXACTLY 1. A task-specific implementation blueprint for “Color contrast remediation” with exact WordPress/Kadence navigation or WPCode placement when relevant. 2. An ordered action checklist with dependencies and who owns each action. 3. Copy-ready artifacts where relevant (block hierarchy, settings matrix, sample copy, scoped CSS, PHP or vanilla JavaScript), with code fences and placement instructions. 4. Desktop/tablet/mobile acceptance tests, accessibility and security checks relevant to the task. 5. Failure cases, troubleshooting clues, rollback steps and final client-facing completion criteria. IMPLEMENTATION SAFETY Flag assumptions; favor native block controls over custom code; do not hardcode credentials or private data. For PHP/JS/CSS, provide exact location, activation scope, prerequisite checks, staging test, and undo method. If a plugin or version-specific behavior is uncertain, say what to verify first. Finish with a concise Definition of Done and a measurable business or UX outcome, without promising a result unsupported by data.
Screen reader heading audit
Create a tested, client-ready outcome for screen reader heading audit.
Act as a senior WordPress solution architect and Kadence Theme/Kadence Blocks/WPCode specialist. TASK: Screen reader heading audit. PROJECT INPUTS - Website type and business goal: [SITE TYPE + GOAL] - Audience, locale and key conversion: [AUDIENCE + LOCALE + CTA] - Current stack (WordPress/PHP, Kadence Theme, Kadence Blocks, WPCode, plugins): [VERIFIED VERSIONS] - Current page, screenshot, issue or reference: [URL OR SANITIZED DETAILS] - Constraints (budget, editor skill, hosting, launch date): [CONSTRAINTS] - Existing content, brand styles and approved data: [SOURCE MATERIAL] SPECIFIC OBJECTIVE Develop a practical, results-oriented solution for screen reader heading audit in the context of this website. Include keyboard, screen reader, reduced-motion and zoom checks as applicable. Explain what should be done with Kadence Theme settings, what should be built with Kadence Blocks, and when WPCode is warranted. Do not invent installed plugin capabilities or pretend you accessed the live site. DELIVER EXACTLY 1. A task-specific implementation blueprint for “Screen reader heading audit” with exact WordPress/Kadence navigation or WPCode placement when relevant. 2. An ordered action checklist with dependencies and who owns each action. 3. Copy-ready artifacts where relevant (block hierarchy, settings matrix, sample copy, scoped CSS, PHP or vanilla JavaScript), with code fences and placement instructions. 4. Desktop/tablet/mobile acceptance tests, accessibility and security checks relevant to the task. 5. Failure cases, troubleshooting clues, rollback steps and final client-facing completion criteria. IMPLEMENTATION SAFETY Flag assumptions; favor native block controls over custom code; do not hardcode credentials or private data. For PHP/JS/CSS, provide exact location, activation scope, prerequisite checks, staging test, and undo method. If a plugin or version-specific behavior is uncertain, say what to verify first. Finish with a concise Definition of Done and a measurable business or UX outcome, without promising a result unsupported by data.
Alt text writing guide
Create a tested, client-ready outcome for alt text writing guide.
Act as a senior WordPress solution architect and Kadence Theme/Kadence Blocks/WPCode specialist. TASK: Alt text writing guide. PROJECT INPUTS - Website type and business goal: [SITE TYPE + GOAL] - Audience, locale and key conversion: [AUDIENCE + LOCALE + CTA] - Current stack (WordPress/PHP, Kadence Theme, Kadence Blocks, WPCode, plugins): [VERIFIED VERSIONS] - Current page, screenshot, issue or reference: [URL OR SANITIZED DETAILS] - Constraints (budget, editor skill, hosting, launch date): [CONSTRAINTS] - Existing content, brand styles and approved data: [SOURCE MATERIAL] SPECIFIC OBJECTIVE Develop a practical, results-oriented solution for alt text writing guide in the context of this website. Include keyboard, screen reader, reduced-motion and zoom checks as applicable. Explain what should be done with Kadence Theme settings, what should be built with Kadence Blocks, and when WPCode is warranted. Do not invent installed plugin capabilities or pretend you accessed the live site. DELIVER EXACTLY 1. A task-specific implementation blueprint for “Alt text writing guide” with exact WordPress/Kadence navigation or WPCode placement when relevant. 2. An ordered action checklist with dependencies and who owns each action. 3. Copy-ready artifacts where relevant (block hierarchy, settings matrix, sample copy, scoped CSS, PHP or vanilla JavaScript), with code fences and placement instructions. 4. Desktop/tablet/mobile acceptance tests, accessibility and security checks relevant to the task. 5. Failure cases, troubleshooting clues, rollback steps and final client-facing completion criteria. IMPLEMENTATION SAFETY Flag assumptions; favor native block controls over custom code; do not hardcode credentials or private data. For PHP/JS/CSS, provide exact location, activation scope, prerequisite checks, staging test, and undo method. If a plugin or version-specific behavior is uncertain, say what to verify first. Finish with a concise Definition of Done and a measurable business or UX outcome, without promising a result unsupported by data.
Accessible menu review
Create a tested, client-ready outcome for accessible menu review.
Act as a senior WordPress solution architect and Kadence Theme/Kadence Blocks/WPCode specialist. TASK: Accessible menu review. PROJECT INPUTS - Website type and business goal: [SITE TYPE + GOAL] - Audience, locale and key conversion: [AUDIENCE + LOCALE + CTA] - Current stack (WordPress/PHP, Kadence Theme, Kadence Blocks, WPCode, plugins): [VERIFIED VERSIONS] - Current page, screenshot, issue or reference: [URL OR SANITIZED DETAILS] - Constraints (budget, editor skill, hosting, launch date): [CONSTRAINTS] - Existing content, brand styles and approved data: [SOURCE MATERIAL] SPECIFIC OBJECTIVE Develop a practical, results-oriented solution for accessible menu review in the context of this website. Include keyboard, screen reader, reduced-motion and zoom checks as applicable. Explain what should be done with Kadence Theme settings, what should be built with Kadence Blocks, and when WPCode is warranted. Do not invent installed plugin capabilities or pretend you accessed the live site. DELIVER EXACTLY 1. A task-specific implementation blueprint for “Accessible menu review” with exact WordPress/Kadence navigation or WPCode placement when relevant. 2. An ordered action checklist with dependencies and who owns each action. 3. Copy-ready artifacts where relevant (block hierarchy, settings matrix, sample copy, scoped CSS, PHP or vanilla JavaScript), with code fences and placement instructions. 4. Desktop/tablet/mobile acceptance tests, accessibility and security checks relevant to the task. 5. Failure cases, troubleshooting clues, rollback steps and final client-facing completion criteria. IMPLEMENTATION SAFETY Flag assumptions; favor native block controls over custom code; do not hardcode credentials or private data. For PHP/JS/CSS, provide exact location, activation scope, prerequisite checks, staging test, and undo method. If a plugin or version-specific behavior is uncertain, say what to verify first. Finish with a concise Definition of Done and a measurable business or UX outcome, without promising a result unsupported by data.
Motion and animation fallback
Create a tested, client-ready outcome for motion and animation fallback.
Act as a senior WordPress solution architect and Kadence Theme/Kadence Blocks/WPCode specialist. TASK: Motion and animation fallback. PROJECT INPUTS - Website type and business goal: [SITE TYPE + GOAL] - Audience, locale and key conversion: [AUDIENCE + LOCALE + CTA] - Current stack (WordPress/PHP, Kadence Theme, Kadence Blocks, WPCode, plugins): [VERIFIED VERSIONS] - Current page, screenshot, issue or reference: [URL OR SANITIZED DETAILS] - Constraints (budget, editor skill, hosting, launch date): [CONSTRAINTS] - Existing content, brand styles and approved data: [SOURCE MATERIAL] SPECIFIC OBJECTIVE Develop a practical, results-oriented solution for motion and animation fallback in the context of this website. Include keyboard, screen reader, reduced-motion and zoom checks as applicable. Explain what should be done with Kadence Theme settings, what should be built with Kadence Blocks, and when WPCode is warranted. Do not invent installed plugin capabilities or pretend you accessed the live site. DELIVER EXACTLY 1. A task-specific implementation blueprint for “Motion and animation fallback” with exact WordPress/Kadence navigation or WPCode placement when relevant. 2. An ordered action checklist with dependencies and who owns each action. 3. Copy-ready artifacts where relevant (block hierarchy, settings matrix, sample copy, scoped CSS, PHP or vanilla JavaScript), with code fences and placement instructions. 4. Desktop/tablet/mobile acceptance tests, accessibility and security checks relevant to the task. 5. Failure cases, troubleshooting clues, rollback steps and final client-facing completion criteria. IMPLEMENTATION SAFETY Flag assumptions; favor native block controls over custom code; do not hardcode credentials or private data. For PHP/JS/CSS, provide exact location, activation scope, prerequisite checks, staging test, and undo method. If a plugin or version-specific behavior is uncertain, say what to verify first. Finish with a concise Definition of Done and a measurable business or UX outcome, without promising a result unsupported by data.
Mobile zoom and reflow audit
Create a tested, client-ready outcome for mobile zoom and reflow audit.
Act as a senior WordPress solution architect and Kadence Theme/Kadence Blocks/WPCode specialist. TASK: Mobile zoom and reflow audit. PROJECT INPUTS - Website type and business goal: [SITE TYPE + GOAL] - Audience, locale and key conversion: [AUDIENCE + LOCALE + CTA] - Current stack (WordPress/PHP, Kadence Theme, Kadence Blocks, WPCode, plugins): [VERIFIED VERSIONS] - Current page, screenshot, issue or reference: [URL OR SANITIZED DETAILS] - Constraints (budget, editor skill, hosting, launch date): [CONSTRAINTS] - Existing content, brand styles and approved data: [SOURCE MATERIAL] SPECIFIC OBJECTIVE Develop a practical, results-oriented solution for mobile zoom and reflow audit in the context of this website. Include keyboard, screen reader, reduced-motion and zoom checks as applicable. Explain what should be done with Kadence Theme settings, what should be built with Kadence Blocks, and when WPCode is warranted. Do not invent installed plugin capabilities or pretend you accessed the live site. DELIVER EXACTLY 1. A task-specific implementation blueprint for “Mobile zoom and reflow audit” with exact WordPress/Kadence navigation or WPCode placement when relevant. 2. An ordered action checklist with dependencies and who owns each action. 3. Copy-ready artifacts where relevant (block hierarchy, settings matrix, sample copy, scoped CSS, PHP or vanilla JavaScript), with code fences and placement instructions. 4. Desktop/tablet/mobile acceptance tests, accessibility and security checks relevant to the task. 5. Failure cases, troubleshooting clues, rollback steps and final client-facing completion criteria. IMPLEMENTATION SAFETY Flag assumptions; favor native block controls over custom code; do not hardcode credentials or private data. For PHP/JS/CSS, provide exact location, activation scope, prerequisite checks, staging test, and undo method. If a plugin or version-specific behavior is uncertain, say what to verify first. Finish with a concise Definition of Done and a measurable business or UX outcome, without promising a result unsupported by data.
21. Security, Privacy & Compliance
Threat model for site
Create a tested, client-ready outcome for threat model for site.
Act as a senior WordPress solution architect and Kadence Theme/Kadence Blocks/WPCode specialist. TASK: Threat model for site. PROJECT INPUTS - Website type and business goal: [SITE TYPE + GOAL] - Audience, locale and key conversion: [AUDIENCE + LOCALE + CTA] - Current stack (WordPress/PHP, Kadence Theme, Kadence Blocks, WPCode, plugins): [VERIFIED VERSIONS] - Current page, screenshot, issue or reference: [URL OR SANITIZED DETAILS] - Constraints (budget, editor skill, hosting, launch date): [CONSTRAINTS] - Existing content, brand styles and approved data: [SOURCE MATERIAL] SPECIFIC OBJECTIVE Develop a practical, results-oriented solution for threat model for site in the context of this website. Avoid storing secrets, public endpoints without authorization, or legal compliance guarantees. Explain what should be done with Kadence Theme settings, what should be built with Kadence Blocks, and when WPCode is warranted. Do not invent installed plugin capabilities or pretend you accessed the live site. DELIVER EXACTLY 1. A task-specific implementation blueprint for “Threat model for site” with exact WordPress/Kadence navigation or WPCode placement when relevant. 2. An ordered action checklist with dependencies and who owns each action. 3. Copy-ready artifacts where relevant (block hierarchy, settings matrix, sample copy, scoped CSS, PHP or vanilla JavaScript), with code fences and placement instructions. 4. Desktop/tablet/mobile acceptance tests, accessibility and security checks relevant to the task. 5. Failure cases, troubleshooting clues, rollback steps and final client-facing completion criteria. IMPLEMENTATION SAFETY Flag assumptions; favor native block controls over custom code; do not hardcode credentials or private data. For PHP/JS/CSS, provide exact location, activation scope, prerequisite checks, staging test, and undo method. If a plugin or version-specific behavior is uncertain, say what to verify first. Finish with a concise Definition of Done and a measurable business or UX outcome, without promising a result unsupported by data.
WPCode snippet security review
Create a tested, client-ready outcome for wpcode snippet security review.
Act as a senior WordPress solution architect and Kadence Theme/Kadence Blocks/WPCode specialist. TASK: WPCode snippet security review. PROJECT INPUTS - Website type and business goal: [SITE TYPE + GOAL] - Audience, locale and key conversion: [AUDIENCE + LOCALE + CTA] - Current stack (WordPress/PHP, Kadence Theme, Kadence Blocks, WPCode, plugins): [VERIFIED VERSIONS] - Current page, screenshot, issue or reference: [URL OR SANITIZED DETAILS] - Constraints (budget, editor skill, hosting, launch date): [CONSTRAINTS] - Existing content, brand styles and approved data: [SOURCE MATERIAL] SPECIFIC OBJECTIVE Develop a practical, results-oriented solution for wpcode snippet security review in the context of this website. Avoid storing secrets, public endpoints without authorization, or legal compliance guarantees. Explain what should be done with Kadence Theme settings, what should be built with Kadence Blocks, and when WPCode is warranted. Do not invent installed plugin capabilities or pretend you accessed the live site. DELIVER EXACTLY 1. A task-specific implementation blueprint for “WPCode snippet security review” with exact WordPress/Kadence navigation or WPCode placement when relevant. 2. An ordered action checklist with dependencies and who owns each action. 3. Copy-ready artifacts where relevant (block hierarchy, settings matrix, sample copy, scoped CSS, PHP or vanilla JavaScript), with code fences and placement instructions. 4. Desktop/tablet/mobile acceptance tests, accessibility and security checks relevant to the task. 5. Failure cases, troubleshooting clues, rollback steps and final client-facing completion criteria. IMPLEMENTATION SAFETY Flag assumptions; favor native block controls over custom code; do not hardcode credentials or private data. For PHP/JS/CSS, provide exact location, activation scope, prerequisite checks, staging test, and undo method. If a plugin or version-specific behavior is uncertain, say what to verify first. Finish with a concise Definition of Done and a measurable business or UX outcome, without promising a result unsupported by data.
Login hardening checklist
Create a tested, client-ready outcome for login hardening checklist.
Act as a senior WordPress solution architect and Kadence Theme/Kadence Blocks/WPCode specialist. TASK: Login hardening checklist. PROJECT INPUTS - Website type and business goal: [SITE TYPE + GOAL] - Audience, locale and key conversion: [AUDIENCE + LOCALE + CTA] - Current stack (WordPress/PHP, Kadence Theme, Kadence Blocks, WPCode, plugins): [VERIFIED VERSIONS] - Current page, screenshot, issue or reference: [URL OR SANITIZED DETAILS] - Constraints (budget, editor skill, hosting, launch date): [CONSTRAINTS] - Existing content, brand styles and approved data: [SOURCE MATERIAL] SPECIFIC OBJECTIVE Develop a practical, results-oriented solution for login hardening checklist in the context of this website. Avoid storing secrets, public endpoints without authorization, or legal compliance guarantees. Explain what should be done with Kadence Theme settings, what should be built with Kadence Blocks, and when WPCode is warranted. Do not invent installed plugin capabilities or pretend you accessed the live site. DELIVER EXACTLY 1. A task-specific implementation blueprint for “Login hardening checklist” with exact WordPress/Kadence navigation or WPCode placement when relevant. 2. An ordered action checklist with dependencies and who owns each action. 3. Copy-ready artifacts where relevant (block hierarchy, settings matrix, sample copy, scoped CSS, PHP or vanilla JavaScript), with code fences and placement instructions. 4. Desktop/tablet/mobile acceptance tests, accessibility and security checks relevant to the task. 5. Failure cases, troubleshooting clues, rollback steps and final client-facing completion criteria. IMPLEMENTATION SAFETY Flag assumptions; favor native block controls over custom code; do not hardcode credentials or private data. For PHP/JS/CSS, provide exact location, activation scope, prerequisite checks, staging test, and undo method. If a plugin or version-specific behavior is uncertain, say what to verify first. Finish with a concise Definition of Done and a measurable business or UX outcome, without promising a result unsupported by data.
Least-privilege user roles
Create a tested, client-ready outcome for least-privilege user roles.
Act as a senior WordPress solution architect and Kadence Theme/Kadence Blocks/WPCode specialist. TASK: Least-privilege user roles. PROJECT INPUTS - Website type and business goal: [SITE TYPE + GOAL] - Audience, locale and key conversion: [AUDIENCE + LOCALE + CTA] - Current stack (WordPress/PHP, Kadence Theme, Kadence Blocks, WPCode, plugins): [VERIFIED VERSIONS] - Current page, screenshot, issue or reference: [URL OR SANITIZED DETAILS] - Constraints (budget, editor skill, hosting, launch date): [CONSTRAINTS] - Existing content, brand styles and approved data: [SOURCE MATERIAL] SPECIFIC OBJECTIVE Develop a practical, results-oriented solution for least-privilege user roles in the context of this website. Avoid storing secrets, public endpoints without authorization, or legal compliance guarantees. Explain what should be done with Kadence Theme settings, what should be built with Kadence Blocks, and when WPCode is warranted. Do not invent installed plugin capabilities or pretend you accessed the live site. DELIVER EXACTLY 1. A task-specific implementation blueprint for “Least-privilege user roles” with exact WordPress/Kadence navigation or WPCode placement when relevant. 2. An ordered action checklist with dependencies and who owns each action. 3. Copy-ready artifacts where relevant (block hierarchy, settings matrix, sample copy, scoped CSS, PHP or vanilla JavaScript), with code fences and placement instructions. 4. Desktop/tablet/mobile acceptance tests, accessibility and security checks relevant to the task. 5. Failure cases, troubleshooting clues, rollback steps and final client-facing completion criteria. IMPLEMENTATION SAFETY Flag assumptions; favor native block controls over custom code; do not hardcode credentials or private data. For PHP/JS/CSS, provide exact location, activation scope, prerequisite checks, staging test, and undo method. If a plugin or version-specific behavior is uncertain, say what to verify first. Finish with a concise Definition of Done and a measurable business or UX outcome, without promising a result unsupported by data.
Plugin supply-chain audit
Create a tested, client-ready outcome for plugin supply-chain audit.
Act as a senior WordPress solution architect and Kadence Theme/Kadence Blocks/WPCode specialist. TASK: Plugin supply-chain audit. PROJECT INPUTS - Website type and business goal: [SITE TYPE + GOAL] - Audience, locale and key conversion: [AUDIENCE + LOCALE + CTA] - Current stack (WordPress/PHP, Kadence Theme, Kadence Blocks, WPCode, plugins): [VERIFIED VERSIONS] - Current page, screenshot, issue or reference: [URL OR SANITIZED DETAILS] - Constraints (budget, editor skill, hosting, launch date): [CONSTRAINTS] - Existing content, brand styles and approved data: [SOURCE MATERIAL] SPECIFIC OBJECTIVE Develop a practical, results-oriented solution for plugin supply-chain audit in the context of this website. Avoid storing secrets, public endpoints without authorization, or legal compliance guarantees. Explain what should be done with Kadence Theme settings, what should be built with Kadence Blocks, and when WPCode is warranted. Do not invent installed plugin capabilities or pretend you accessed the live site. DELIVER EXACTLY 1. A task-specific implementation blueprint for “Plugin supply-chain audit” with exact WordPress/Kadence navigation or WPCode placement when relevant. 2. An ordered action checklist with dependencies and who owns each action. 3. Copy-ready artifacts where relevant (block hierarchy, settings matrix, sample copy, scoped CSS, PHP or vanilla JavaScript), with code fences and placement instructions. 4. Desktop/tablet/mobile acceptance tests, accessibility and security checks relevant to the task. 5. Failure cases, troubleshooting clues, rollback steps and final client-facing completion criteria. IMPLEMENTATION SAFETY Flag assumptions; favor native block controls over custom code; do not hardcode credentials or private data. For PHP/JS/CSS, provide exact location, activation scope, prerequisite checks, staging test, and undo method. If a plugin or version-specific behavior is uncertain, say what to verify first. Finish with a concise Definition of Done and a measurable business or UX outcome, without promising a result unsupported by data.
Personal data inventory
Create a tested, client-ready outcome for personal data inventory.
Act as a senior WordPress solution architect and Kadence Theme/Kadence Blocks/WPCode specialist. TASK: Personal data inventory. PROJECT INPUTS - Website type and business goal: [SITE TYPE + GOAL] - Audience, locale and key conversion: [AUDIENCE + LOCALE + CTA] - Current stack (WordPress/PHP, Kadence Theme, Kadence Blocks, WPCode, plugins): [VERIFIED VERSIONS] - Current page, screenshot, issue or reference: [URL OR SANITIZED DETAILS] - Constraints (budget, editor skill, hosting, launch date): [CONSTRAINTS] - Existing content, brand styles and approved data: [SOURCE MATERIAL] SPECIFIC OBJECTIVE Develop a practical, results-oriented solution for personal data inventory in the context of this website. Avoid storing secrets, public endpoints without authorization, or legal compliance guarantees. Explain what should be done with Kadence Theme settings, what should be built with Kadence Blocks, and when WPCode is warranted. Do not invent installed plugin capabilities or pretend you accessed the live site. DELIVER EXACTLY 1. A task-specific implementation blueprint for “Personal data inventory” with exact WordPress/Kadence navigation or WPCode placement when relevant. 2. An ordered action checklist with dependencies and who owns each action. 3. Copy-ready artifacts where relevant (block hierarchy, settings matrix, sample copy, scoped CSS, PHP or vanilla JavaScript), with code fences and placement instructions. 4. Desktop/tablet/mobile acceptance tests, accessibility and security checks relevant to the task. 5. Failure cases, troubleshooting clues, rollback steps and final client-facing completion criteria. IMPLEMENTATION SAFETY Flag assumptions; favor native block controls over custom code; do not hardcode credentials or private data. For PHP/JS/CSS, provide exact location, activation scope, prerequisite checks, staging test, and undo method. If a plugin or version-specific behavior is uncertain, say what to verify first. Finish with a concise Definition of Done and a measurable business or UX outcome, without promising a result unsupported by data.
Consent and tracking map
Create a tested, client-ready outcome for consent and tracking map.
Act as a senior WordPress solution architect and Kadence Theme/Kadence Blocks/WPCode specialist. TASK: Consent and tracking map. PROJECT INPUTS - Website type and business goal: [SITE TYPE + GOAL] - Audience, locale and key conversion: [AUDIENCE + LOCALE + CTA] - Current stack (WordPress/PHP, Kadence Theme, Kadence Blocks, WPCode, plugins): [VERIFIED VERSIONS] - Current page, screenshot, issue or reference: [URL OR SANITIZED DETAILS] - Constraints (budget, editor skill, hosting, launch date): [CONSTRAINTS] - Existing content, brand styles and approved data: [SOURCE MATERIAL] SPECIFIC OBJECTIVE Develop a practical, results-oriented solution for consent and tracking map in the context of this website. Avoid storing secrets, public endpoints without authorization, or legal compliance guarantees. Explain what should be done with Kadence Theme settings, what should be built with Kadence Blocks, and when WPCode is warranted. Do not invent installed plugin capabilities or pretend you accessed the live site. DELIVER EXACTLY 1. A task-specific implementation blueprint for “Consent and tracking map” with exact WordPress/Kadence navigation or WPCode placement when relevant. 2. An ordered action checklist with dependencies and who owns each action. 3. Copy-ready artifacts where relevant (block hierarchy, settings matrix, sample copy, scoped CSS, PHP or vanilla JavaScript), with code fences and placement instructions. 4. Desktop/tablet/mobile acceptance tests, accessibility and security checks relevant to the task. 5. Failure cases, troubleshooting clues, rollback steps and final client-facing completion criteria. IMPLEMENTATION SAFETY Flag assumptions; favor native block controls over custom code; do not hardcode credentials or private data. For PHP/JS/CSS, provide exact location, activation scope, prerequisite checks, staging test, and undo method. If a plugin or version-specific behavior is uncertain, say what to verify first. Finish with a concise Definition of Done and a measurable business or UX outcome, without promising a result unsupported by data.
File upload protections
Create a tested, client-ready outcome for file upload protections.
Act as a senior WordPress solution architect and Kadence Theme/Kadence Blocks/WPCode specialist. TASK: File upload protections. PROJECT INPUTS - Website type and business goal: [SITE TYPE + GOAL] - Audience, locale and key conversion: [AUDIENCE + LOCALE + CTA] - Current stack (WordPress/PHP, Kadence Theme, Kadence Blocks, WPCode, plugins): [VERIFIED VERSIONS] - Current page, screenshot, issue or reference: [URL OR SANITIZED DETAILS] - Constraints (budget, editor skill, hosting, launch date): [CONSTRAINTS] - Existing content, brand styles and approved data: [SOURCE MATERIAL] SPECIFIC OBJECTIVE Develop a practical, results-oriented solution for file upload protections in the context of this website. Avoid storing secrets, public endpoints without authorization, or legal compliance guarantees. Explain what should be done with Kadence Theme settings, what should be built with Kadence Blocks, and when WPCode is warranted. Do not invent installed plugin capabilities or pretend you accessed the live site. DELIVER EXACTLY 1. A task-specific implementation blueprint for “File upload protections” with exact WordPress/Kadence navigation or WPCode placement when relevant. 2. An ordered action checklist with dependencies and who owns each action. 3. Copy-ready artifacts where relevant (block hierarchy, settings matrix, sample copy, scoped CSS, PHP or vanilla JavaScript), with code fences and placement instructions. 4. Desktop/tablet/mobile acceptance tests, accessibility and security checks relevant to the task. 5. Failure cases, troubleshooting clues, rollback steps and final client-facing completion criteria. IMPLEMENTATION SAFETY Flag assumptions; favor native block controls over custom code; do not hardcode credentials or private data. For PHP/JS/CSS, provide exact location, activation scope, prerequisite checks, staging test, and undo method. If a plugin or version-specific behavior is uncertain, say what to verify first. Finish with a concise Definition of Done and a measurable business or UX outcome, without promising a result unsupported by data.
Incident response runbook
Create a tested, client-ready outcome for incident response runbook.
Act as a senior WordPress solution architect and Kadence Theme/Kadence Blocks/WPCode specialist. TASK: Incident response runbook. PROJECT INPUTS - Website type and business goal: [SITE TYPE + GOAL] - Audience, locale and key conversion: [AUDIENCE + LOCALE + CTA] - Current stack (WordPress/PHP, Kadence Theme, Kadence Blocks, WPCode, plugins): [VERIFIED VERSIONS] - Current page, screenshot, issue or reference: [URL OR SANITIZED DETAILS] - Constraints (budget, editor skill, hosting, launch date): [CONSTRAINTS] - Existing content, brand styles and approved data: [SOURCE MATERIAL] SPECIFIC OBJECTIVE Develop a practical, results-oriented solution for incident response runbook in the context of this website. Avoid storing secrets, public endpoints without authorization, or legal compliance guarantees. Explain what should be done with Kadence Theme settings, what should be built with Kadence Blocks, and when WPCode is warranted. Do not invent installed plugin capabilities or pretend you accessed the live site. DELIVER EXACTLY 1. A task-specific implementation blueprint for “Incident response runbook” with exact WordPress/Kadence navigation or WPCode placement when relevant. 2. An ordered action checklist with dependencies and who owns each action. 3. Copy-ready artifacts where relevant (block hierarchy, settings matrix, sample copy, scoped CSS, PHP or vanilla JavaScript), with code fences and placement instructions. 4. Desktop/tablet/mobile acceptance tests, accessibility and security checks relevant to the task. 5. Failure cases, troubleshooting clues, rollback steps and final client-facing completion criteria. IMPLEMENTATION SAFETY Flag assumptions; favor native block controls over custom code; do not hardcode credentials or private data. For PHP/JS/CSS, provide exact location, activation scope, prerequisite checks, staging test, and undo method. If a plugin or version-specific behavior is uncertain, say what to verify first. Finish with a concise Definition of Done and a measurable business or UX outcome, without promising a result unsupported by data.
Security maintenance schedule
Create a tested, client-ready outcome for security maintenance schedule.
Act as a senior WordPress solution architect and Kadence Theme/Kadence Blocks/WPCode specialist. TASK: Security maintenance schedule. PROJECT INPUTS - Website type and business goal: [SITE TYPE + GOAL] - Audience, locale and key conversion: [AUDIENCE + LOCALE + CTA] - Current stack (WordPress/PHP, Kadence Theme, Kadence Blocks, WPCode, plugins): [VERIFIED VERSIONS] - Current page, screenshot, issue or reference: [URL OR SANITIZED DETAILS] - Constraints (budget, editor skill, hosting, launch date): [CONSTRAINTS] - Existing content, brand styles and approved data: [SOURCE MATERIAL] SPECIFIC OBJECTIVE Develop a practical, results-oriented solution for security maintenance schedule in the context of this website. Avoid storing secrets, public endpoints without authorization, or legal compliance guarantees. Explain what should be done with Kadence Theme settings, what should be built with Kadence Blocks, and when WPCode is warranted. Do not invent installed plugin capabilities or pretend you accessed the live site. DELIVER EXACTLY 1. A task-specific implementation blueprint for “Security maintenance schedule” with exact WordPress/Kadence navigation or WPCode placement when relevant. 2. An ordered action checklist with dependencies and who owns each action. 3. Copy-ready artifacts where relevant (block hierarchy, settings matrix, sample copy, scoped CSS, PHP or vanilla JavaScript), with code fences and placement instructions. 4. Desktop/tablet/mobile acceptance tests, accessibility and security checks relevant to the task. 5. Failure cases, troubleshooting clues, rollback steps and final client-facing completion criteria. IMPLEMENTATION SAFETY Flag assumptions; favor native block controls over custom code; do not hardcode credentials or private data. For PHP/JS/CSS, provide exact location, activation scope, prerequisite checks, staging test, and undo method. If a plugin or version-specific behavior is uncertain, say what to verify first. Finish with a concise Definition of Done and a measurable business or UX outcome, without promising a result unsupported by data.
22. Testing, Debugging & Reliability
Reproducible bug report
Create a tested, client-ready outcome for reproducible bug report.
Act as a senior WordPress solution architect and Kadence Theme/Kadence Blocks/WPCode specialist. TASK: Reproducible bug report. PROJECT INPUTS - Website type and business goal: [SITE TYPE + GOAL] - Audience, locale and key conversion: [AUDIENCE + LOCALE + CTA] - Current stack (WordPress/PHP, Kadence Theme, Kadence Blocks, WPCode, plugins): [VERIFIED VERSIONS] - Current page, screenshot, issue or reference: [URL OR SANITIZED DETAILS] - Constraints (budget, editor skill, hosting, launch date): [CONSTRAINTS] - Existing content, brand styles and approved data: [SOURCE MATERIAL] SPECIFIC OBJECTIVE Develop a practical, results-oriented solution for reproducible bug report in the context of this website. Request minimal reproduction evidence, isolate changes and document actual versus expected outcomes. Explain what should be done with Kadence Theme settings, what should be built with Kadence Blocks, and when WPCode is warranted. Do not invent installed plugin capabilities or pretend you accessed the live site. DELIVER EXACTLY 1. A task-specific implementation blueprint for “Reproducible bug report” with exact WordPress/Kadence navigation or WPCode placement when relevant. 2. An ordered action checklist with dependencies and who owns each action. 3. Copy-ready artifacts where relevant (block hierarchy, settings matrix, sample copy, scoped CSS, PHP or vanilla JavaScript), with code fences and placement instructions. 4. Desktop/tablet/mobile acceptance tests, accessibility and security checks relevant to the task. 5. Failure cases, troubleshooting clues, rollback steps and final client-facing completion criteria. IMPLEMENTATION SAFETY Flag assumptions; favor native block controls over custom code; do not hardcode credentials or private data. For PHP/JS/CSS, provide exact location, activation scope, prerequisite checks, staging test, and undo method. If a plugin or version-specific behavior is uncertain, say what to verify first. Finish with a concise Definition of Done and a measurable business or UX outcome, without promising a result unsupported by data.
Plugin conflict isolation
Create a tested, client-ready outcome for plugin conflict isolation.
Act as a senior WordPress solution architect and Kadence Theme/Kadence Blocks/WPCode specialist. TASK: Plugin conflict isolation. PROJECT INPUTS - Website type and business goal: [SITE TYPE + GOAL] - Audience, locale and key conversion: [AUDIENCE + LOCALE + CTA] - Current stack (WordPress/PHP, Kadence Theme, Kadence Blocks, WPCode, plugins): [VERIFIED VERSIONS] - Current page, screenshot, issue or reference: [URL OR SANITIZED DETAILS] - Constraints (budget, editor skill, hosting, launch date): [CONSTRAINTS] - Existing content, brand styles and approved data: [SOURCE MATERIAL] SPECIFIC OBJECTIVE Develop a practical, results-oriented solution for plugin conflict isolation in the context of this website. Request minimal reproduction evidence, isolate changes and document actual versus expected outcomes. Explain what should be done with Kadence Theme settings, what should be built with Kadence Blocks, and when WPCode is warranted. Do not invent installed plugin capabilities or pretend you accessed the live site. DELIVER EXACTLY 1. A task-specific implementation blueprint for “Plugin conflict isolation” with exact WordPress/Kadence navigation or WPCode placement when relevant. 2. An ordered action checklist with dependencies and who owns each action. 3. Copy-ready artifacts where relevant (block hierarchy, settings matrix, sample copy, scoped CSS, PHP or vanilla JavaScript), with code fences and placement instructions. 4. Desktop/tablet/mobile acceptance tests, accessibility and security checks relevant to the task. 5. Failure cases, troubleshooting clues, rollback steps and final client-facing completion criteria. IMPLEMENTATION SAFETY Flag assumptions; favor native block controls over custom code; do not hardcode credentials or private data. For PHP/JS/CSS, provide exact location, activation scope, prerequisite checks, staging test, and undo method. If a plugin or version-specific behavior is uncertain, say what to verify first. Finish with a concise Definition of Done and a measurable business or UX outcome, without promising a result unsupported by data.
Theme and block regression test
Create a tested, client-ready outcome for theme and block regression test.
Act as a senior WordPress solution architect and Kadence Theme/Kadence Blocks/WPCode specialist. TASK: Theme and block regression test. PROJECT INPUTS - Website type and business goal: [SITE TYPE + GOAL] - Audience, locale and key conversion: [AUDIENCE + LOCALE + CTA] - Current stack (WordPress/PHP, Kadence Theme, Kadence Blocks, WPCode, plugins): [VERIFIED VERSIONS] - Current page, screenshot, issue or reference: [URL OR SANITIZED DETAILS] - Constraints (budget, editor skill, hosting, launch date): [CONSTRAINTS] - Existing content, brand styles and approved data: [SOURCE MATERIAL] SPECIFIC OBJECTIVE Develop a practical, results-oriented solution for theme and block regression test in the context of this website. Request minimal reproduction evidence, isolate changes and document actual versus expected outcomes. Explain what should be done with Kadence Theme settings, what should be built with Kadence Blocks, and when WPCode is warranted. Do not invent installed plugin capabilities or pretend you accessed the live site. DELIVER EXACTLY 1. A task-specific implementation blueprint for “Theme and block regression test” with exact WordPress/Kadence navigation or WPCode placement when relevant. 2. An ordered action checklist with dependencies and who owns each action. 3. Copy-ready artifacts where relevant (block hierarchy, settings matrix, sample copy, scoped CSS, PHP or vanilla JavaScript), with code fences and placement instructions. 4. Desktop/tablet/mobile acceptance tests, accessibility and security checks relevant to the task. 5. Failure cases, troubleshooting clues, rollback steps and final client-facing completion criteria. IMPLEMENTATION SAFETY Flag assumptions; favor native block controls over custom code; do not hardcode credentials or private data. For PHP/JS/CSS, provide exact location, activation scope, prerequisite checks, staging test, and undo method. If a plugin or version-specific behavior is uncertain, say what to verify first. Finish with a concise Definition of Done and a measurable business or UX outcome, without promising a result unsupported by data.
PHP error log triage
Create a tested, client-ready outcome for php error log triage.
Act as a senior WordPress solution architect and Kadence Theme/Kadence Blocks/WPCode specialist. TASK: PHP error log triage. PROJECT INPUTS - Website type and business goal: [SITE TYPE + GOAL] - Audience, locale and key conversion: [AUDIENCE + LOCALE + CTA] - Current stack (WordPress/PHP, Kadence Theme, Kadence Blocks, WPCode, plugins): [VERIFIED VERSIONS] - Current page, screenshot, issue or reference: [URL OR SANITIZED DETAILS] - Constraints (budget, editor skill, hosting, launch date): [CONSTRAINTS] - Existing content, brand styles and approved data: [SOURCE MATERIAL] SPECIFIC OBJECTIVE Develop a practical, results-oriented solution for php error log triage in the context of this website. Request minimal reproduction evidence, isolate changes and document actual versus expected outcomes. Explain what should be done with Kadence Theme settings, what should be built with Kadence Blocks, and when WPCode is warranted. Do not invent installed plugin capabilities or pretend you accessed the live site. DELIVER EXACTLY 1. A task-specific implementation blueprint for “PHP error log triage” with exact WordPress/Kadence navigation or WPCode placement when relevant. 2. An ordered action checklist with dependencies and who owns each action. 3. Copy-ready artifacts where relevant (block hierarchy, settings matrix, sample copy, scoped CSS, PHP or vanilla JavaScript), with code fences and placement instructions. 4. Desktop/tablet/mobile acceptance tests, accessibility and security checks relevant to the task. 5. Failure cases, troubleshooting clues, rollback steps and final client-facing completion criteria. IMPLEMENTATION SAFETY Flag assumptions; favor native block controls over custom code; do not hardcode credentials or private data. For PHP/JS/CSS, provide exact location, activation scope, prerequisite checks, staging test, and undo method. If a plugin or version-specific behavior is uncertain, say what to verify first. Finish with a concise Definition of Done and a measurable business or UX outcome, without promising a result unsupported by data.
Browser console triage
Create a tested, client-ready outcome for browser console triage.
Act as a senior WordPress solution architect and Kadence Theme/Kadence Blocks/WPCode specialist. TASK: Browser console triage. PROJECT INPUTS - Website type and business goal: [SITE TYPE + GOAL] - Audience, locale and key conversion: [AUDIENCE + LOCALE + CTA] - Current stack (WordPress/PHP, Kadence Theme, Kadence Blocks, WPCode, plugins): [VERIFIED VERSIONS] - Current page, screenshot, issue or reference: [URL OR SANITIZED DETAILS] - Constraints (budget, editor skill, hosting, launch date): [CONSTRAINTS] - Existing content, brand styles and approved data: [SOURCE MATERIAL] SPECIFIC OBJECTIVE Develop a practical, results-oriented solution for browser console triage in the context of this website. Request minimal reproduction evidence, isolate changes and document actual versus expected outcomes. Explain what should be done with Kadence Theme settings, what should be built with Kadence Blocks, and when WPCode is warranted. Do not invent installed plugin capabilities or pretend you accessed the live site. DELIVER EXACTLY 1. A task-specific implementation blueprint for “Browser console triage” with exact WordPress/Kadence navigation or WPCode placement when relevant. 2. An ordered action checklist with dependencies and who owns each action. 3. Copy-ready artifacts where relevant (block hierarchy, settings matrix, sample copy, scoped CSS, PHP or vanilla JavaScript), with code fences and placement instructions. 4. Desktop/tablet/mobile acceptance tests, accessibility and security checks relevant to the task. 5. Failure cases, troubleshooting clues, rollback steps and final client-facing completion criteria. IMPLEMENTATION SAFETY Flag assumptions; favor native block controls over custom code; do not hardcode credentials or private data. For PHP/JS/CSS, provide exact location, activation scope, prerequisite checks, staging test, and undo method. If a plugin or version-specific behavior is uncertain, say what to verify first. Finish with a concise Definition of Done and a measurable business or UX outcome, without promising a result unsupported by data.
Responsive device matrix
Create a tested, client-ready outcome for responsive device matrix.
Act as a senior WordPress solution architect and Kadence Theme/Kadence Blocks/WPCode specialist. TASK: Responsive device matrix. PROJECT INPUTS - Website type and business goal: [SITE TYPE + GOAL] - Audience, locale and key conversion: [AUDIENCE + LOCALE + CTA] - Current stack (WordPress/PHP, Kadence Theme, Kadence Blocks, WPCode, plugins): [VERIFIED VERSIONS] - Current page, screenshot, issue or reference: [URL OR SANITIZED DETAILS] - Constraints (budget, editor skill, hosting, launch date): [CONSTRAINTS] - Existing content, brand styles and approved data: [SOURCE MATERIAL] SPECIFIC OBJECTIVE Develop a practical, results-oriented solution for responsive device matrix in the context of this website. Request minimal reproduction evidence, isolate changes and document actual versus expected outcomes. Explain what should be done with Kadence Theme settings, what should be built with Kadence Blocks, and when WPCode is warranted. Do not invent installed plugin capabilities or pretend you accessed the live site. DELIVER EXACTLY 1. A task-specific implementation blueprint for “Responsive device matrix” with exact WordPress/Kadence navigation or WPCode placement when relevant. 2. An ordered action checklist with dependencies and who owns each action. 3. Copy-ready artifacts where relevant (block hierarchy, settings matrix, sample copy, scoped CSS, PHP or vanilla JavaScript), with code fences and placement instructions. 4. Desktop/tablet/mobile acceptance tests, accessibility and security checks relevant to the task. 5. Failure cases, troubleshooting clues, rollback steps and final client-facing completion criteria. IMPLEMENTATION SAFETY Flag assumptions; favor native block controls over custom code; do not hardcode credentials or private data. For PHP/JS/CSS, provide exact location, activation scope, prerequisite checks, staging test, and undo method. If a plugin or version-specific behavior is uncertain, say what to verify first. Finish with a concise Definition of Done and a measurable business or UX outcome, without promising a result unsupported by data.
Form delivery end-to-end test
Create a tested, client-ready outcome for form delivery end-to-end test.
Act as a senior WordPress solution architect and Kadence Theme/Kadence Blocks/WPCode specialist. TASK: Form delivery end-to-end test. PROJECT INPUTS - Website type and business goal: [SITE TYPE + GOAL] - Audience, locale and key conversion: [AUDIENCE + LOCALE + CTA] - Current stack (WordPress/PHP, Kadence Theme, Kadence Blocks, WPCode, plugins): [VERIFIED VERSIONS] - Current page, screenshot, issue or reference: [URL OR SANITIZED DETAILS] - Constraints (budget, editor skill, hosting, launch date): [CONSTRAINTS] - Existing content, brand styles and approved data: [SOURCE MATERIAL] SPECIFIC OBJECTIVE Develop a practical, results-oriented solution for form delivery end-to-end test in the context of this website. Request minimal reproduction evidence, isolate changes and document actual versus expected outcomes. Explain what should be done with Kadence Theme settings, what should be built with Kadence Blocks, and when WPCode is warranted. Do not invent installed plugin capabilities or pretend you accessed the live site. DELIVER EXACTLY 1. A task-specific implementation blueprint for “Form delivery end-to-end test” with exact WordPress/Kadence navigation or WPCode placement when relevant. 2. An ordered action checklist with dependencies and who owns each action. 3. Copy-ready artifacts where relevant (block hierarchy, settings matrix, sample copy, scoped CSS, PHP or vanilla JavaScript), with code fences and placement instructions. 4. Desktop/tablet/mobile acceptance tests, accessibility and security checks relevant to the task. 5. Failure cases, troubleshooting clues, rollback steps and final client-facing completion criteria. IMPLEMENTATION SAFETY Flag assumptions; favor native block controls over custom code; do not hardcode credentials or private data. For PHP/JS/CSS, provide exact location, activation scope, prerequisite checks, staging test, and undo method. If a plugin or version-specific behavior is uncertain, say what to verify first. Finish with a concise Definition of Done and a measurable business or UX outcome, without promising a result unsupported by data.
WooCommerce purchase test
Create a tested, client-ready outcome for woocommerce purchase test.
Act as a senior WordPress solution architect and Kadence Theme/Kadence Blocks/WPCode specialist. TASK: WooCommerce purchase test. PROJECT INPUTS - Website type and business goal: [SITE TYPE + GOAL] - Audience, locale and key conversion: [AUDIENCE + LOCALE + CTA] - Current stack (WordPress/PHP, Kadence Theme, Kadence Blocks, WPCode, plugins): [VERIFIED VERSIONS] - Current page, screenshot, issue or reference: [URL OR SANITIZED DETAILS] - Constraints (budget, editor skill, hosting, launch date): [CONSTRAINTS] - Existing content, brand styles and approved data: [SOURCE MATERIAL] SPECIFIC OBJECTIVE Develop a practical, results-oriented solution for woocommerce purchase test in the context of this website. Request minimal reproduction evidence, isolate changes and document actual versus expected outcomes. Explain what should be done with Kadence Theme settings, what should be built with Kadence Blocks, and when WPCode is warranted. Do not invent installed plugin capabilities or pretend you accessed the live site. DELIVER EXACTLY 1. A task-specific implementation blueprint for “WooCommerce purchase test” with exact WordPress/Kadence navigation or WPCode placement when relevant. 2. An ordered action checklist with dependencies and who owns each action. 3. Copy-ready artifacts where relevant (block hierarchy, settings matrix, sample copy, scoped CSS, PHP or vanilla JavaScript), with code fences and placement instructions. 4. Desktop/tablet/mobile acceptance tests, accessibility and security checks relevant to the task. 5. Failure cases, troubleshooting clues, rollback steps and final client-facing completion criteria. IMPLEMENTATION SAFETY Flag assumptions; favor native block controls over custom code; do not hardcode credentials or private data. For PHP/JS/CSS, provide exact location, activation scope, prerequisite checks, staging test, and undo method. If a plugin or version-specific behavior is uncertain, say what to verify first. Finish with a concise Definition of Done and a measurable business or UX outcome, without promising a result unsupported by data.
Rollback rehearsal
Create a tested, client-ready outcome for rollback rehearsal.
Act as a senior WordPress solution architect and Kadence Theme/Kadence Blocks/WPCode specialist. TASK: Rollback rehearsal. PROJECT INPUTS - Website type and business goal: [SITE TYPE + GOAL] - Audience, locale and key conversion: [AUDIENCE + LOCALE + CTA] - Current stack (WordPress/PHP, Kadence Theme, Kadence Blocks, WPCode, plugins): [VERIFIED VERSIONS] - Current page, screenshot, issue or reference: [URL OR SANITIZED DETAILS] - Constraints (budget, editor skill, hosting, launch date): [CONSTRAINTS] - Existing content, brand styles and approved data: [SOURCE MATERIAL] SPECIFIC OBJECTIVE Develop a practical, results-oriented solution for rollback rehearsal in the context of this website. Request minimal reproduction evidence, isolate changes and document actual versus expected outcomes. Explain what should be done with Kadence Theme settings, what should be built with Kadence Blocks, and when WPCode is warranted. Do not invent installed plugin capabilities or pretend you accessed the live site. DELIVER EXACTLY 1. A task-specific implementation blueprint for “Rollback rehearsal” with exact WordPress/Kadence navigation or WPCode placement when relevant. 2. An ordered action checklist with dependencies and who owns each action. 3. Copy-ready artifacts where relevant (block hierarchy, settings matrix, sample copy, scoped CSS, PHP or vanilla JavaScript), with code fences and placement instructions. 4. Desktop/tablet/mobile acceptance tests, accessibility and security checks relevant to the task. 5. Failure cases, troubleshooting clues, rollback steps and final client-facing completion criteria. IMPLEMENTATION SAFETY Flag assumptions; favor native block controls over custom code; do not hardcode credentials or private data. For PHP/JS/CSS, provide exact location, activation scope, prerequisite checks, staging test, and undo method. If a plugin or version-specific behavior is uncertain, say what to verify first. Finish with a concise Definition of Done and a measurable business or UX outcome, without promising a result unsupported by data.
Post-update smoke test
Create a tested, client-ready outcome for post-update smoke test.
Act as a senior WordPress solution architect and Kadence Theme/Kadence Blocks/WPCode specialist. TASK: Post-update smoke test. PROJECT INPUTS - Website type and business goal: [SITE TYPE + GOAL] - Audience, locale and key conversion: [AUDIENCE + LOCALE + CTA] - Current stack (WordPress/PHP, Kadence Theme, Kadence Blocks, WPCode, plugins): [VERIFIED VERSIONS] - Current page, screenshot, issue or reference: [URL OR SANITIZED DETAILS] - Constraints (budget, editor skill, hosting, launch date): [CONSTRAINTS] - Existing content, brand styles and approved data: [SOURCE MATERIAL] SPECIFIC OBJECTIVE Develop a practical, results-oriented solution for post-update smoke test in the context of this website. Request minimal reproduction evidence, isolate changes and document actual versus expected outcomes. Explain what should be done with Kadence Theme settings, what should be built with Kadence Blocks, and when WPCode is warranted. Do not invent installed plugin capabilities or pretend you accessed the live site. DELIVER EXACTLY 1. A task-specific implementation blueprint for “Post-update smoke test” with exact WordPress/Kadence navigation or WPCode placement when relevant. 2. An ordered action checklist with dependencies and who owns each action. 3. Copy-ready artifacts where relevant (block hierarchy, settings matrix, sample copy, scoped CSS, PHP or vanilla JavaScript), with code fences and placement instructions. 4. Desktop/tablet/mobile acceptance tests, accessibility and security checks relevant to the task. 5. Failure cases, troubleshooting clues, rollback steps and final client-facing completion criteria. IMPLEMENTATION SAFETY Flag assumptions; favor native block controls over custom code; do not hardcode credentials or private data. For PHP/JS/CSS, provide exact location, activation scope, prerequisite checks, staging test, and undo method. If a plugin or version-specific behavior is uncertain, say what to verify first. Finish with a concise Definition of Done and a measurable business or UX outcome, without promising a result unsupported by data.
23. Migration, Launch & Maintenance
Prelaunch release checklist
Create a tested, client-ready outcome for prelaunch release checklist.
Act as a senior WordPress solution architect and Kadence Theme/Kadence Blocks/WPCode specialist. TASK: Prelaunch release checklist. PROJECT INPUTS - Website type and business goal: [SITE TYPE + GOAL] - Audience, locale and key conversion: [AUDIENCE + LOCALE + CTA] - Current stack (WordPress/PHP, Kadence Theme, Kadence Blocks, WPCode, plugins): [VERIFIED VERSIONS] - Current page, screenshot, issue or reference: [URL OR SANITIZED DETAILS] - Constraints (budget, editor skill, hosting, launch date): [CONSTRAINTS] - Existing content, brand styles and approved data: [SOURCE MATERIAL] SPECIFIC OBJECTIVE Develop a practical, results-oriented solution for prelaunch release checklist in the context of this website. Include release owner, backups, rollback, redirects and verification. Explain what should be done with Kadence Theme settings, what should be built with Kadence Blocks, and when WPCode is warranted. Do not invent installed plugin capabilities or pretend you accessed the live site. DELIVER EXACTLY 1. A task-specific implementation blueprint for “Prelaunch release checklist” with exact WordPress/Kadence navigation or WPCode placement when relevant. 2. An ordered action checklist with dependencies and who owns each action. 3. Copy-ready artifacts where relevant (block hierarchy, settings matrix, sample copy, scoped CSS, PHP or vanilla JavaScript), with code fences and placement instructions. 4. Desktop/tablet/mobile acceptance tests, accessibility and security checks relevant to the task. 5. Failure cases, troubleshooting clues, rollback steps and final client-facing completion criteria. IMPLEMENTATION SAFETY Flag assumptions; favor native block controls over custom code; do not hardcode credentials or private data. For PHP/JS/CSS, provide exact location, activation scope, prerequisite checks, staging test, and undo method. If a plugin or version-specific behavior is uncertain, say what to verify first. Finish with a concise Definition of Done and a measurable business or UX outcome, without promising a result unsupported by data.
URL redirect mapping
Create a tested, client-ready outcome for url redirect mapping.
Act as a senior WordPress solution architect and Kadence Theme/Kadence Blocks/WPCode specialist. TASK: URL redirect mapping. PROJECT INPUTS - Website type and business goal: [SITE TYPE + GOAL] - Audience, locale and key conversion: [AUDIENCE + LOCALE + CTA] - Current stack (WordPress/PHP, Kadence Theme, Kadence Blocks, WPCode, plugins): [VERIFIED VERSIONS] - Current page, screenshot, issue or reference: [URL OR SANITIZED DETAILS] - Constraints (budget, editor skill, hosting, launch date): [CONSTRAINTS] - Existing content, brand styles and approved data: [SOURCE MATERIAL] SPECIFIC OBJECTIVE Develop a practical, results-oriented solution for url redirect mapping in the context of this website. Include release owner, backups, rollback, redirects and verification. Explain what should be done with Kadence Theme settings, what should be built with Kadence Blocks, and when WPCode is warranted. Do not invent installed plugin capabilities or pretend you accessed the live site. DELIVER EXACTLY 1. A task-specific implementation blueprint for “URL redirect mapping” with exact WordPress/Kadence navigation or WPCode placement when relevant. 2. An ordered action checklist with dependencies and who owns each action. 3. Copy-ready artifacts where relevant (block hierarchy, settings matrix, sample copy, scoped CSS, PHP or vanilla JavaScript), with code fences and placement instructions. 4. Desktop/tablet/mobile acceptance tests, accessibility and security checks relevant to the task. 5. Failure cases, troubleshooting clues, rollback steps and final client-facing completion criteria. IMPLEMENTATION SAFETY Flag assumptions; favor native block controls over custom code; do not hardcode credentials or private data. For PHP/JS/CSS, provide exact location, activation scope, prerequisite checks, staging test, and undo method. If a plugin or version-specific behavior is uncertain, say what to verify first. Finish with a concise Definition of Done and a measurable business or UX outcome, without promising a result unsupported by data.
Staging-to-live plan
Create a tested, client-ready outcome for staging-to-live plan.
Act as a senior WordPress solution architect and Kadence Theme/Kadence Blocks/WPCode specialist. TASK: Staging-to-live plan. PROJECT INPUTS - Website type and business goal: [SITE TYPE + GOAL] - Audience, locale and key conversion: [AUDIENCE + LOCALE + CTA] - Current stack (WordPress/PHP, Kadence Theme, Kadence Blocks, WPCode, plugins): [VERIFIED VERSIONS] - Current page, screenshot, issue or reference: [URL OR SANITIZED DETAILS] - Constraints (budget, editor skill, hosting, launch date): [CONSTRAINTS] - Existing content, brand styles and approved data: [SOURCE MATERIAL] SPECIFIC OBJECTIVE Develop a practical, results-oriented solution for staging-to-live plan in the context of this website. Include release owner, backups, rollback, redirects and verification. Explain what should be done with Kadence Theme settings, what should be built with Kadence Blocks, and when WPCode is warranted. Do not invent installed plugin capabilities or pretend you accessed the live site. DELIVER EXACTLY 1. A task-specific implementation blueprint for “Staging-to-live plan” with exact WordPress/Kadence navigation or WPCode placement when relevant. 2. An ordered action checklist with dependencies and who owns each action. 3. Copy-ready artifacts where relevant (block hierarchy, settings matrix, sample copy, scoped CSS, PHP or vanilla JavaScript), with code fences and placement instructions. 4. Desktop/tablet/mobile acceptance tests, accessibility and security checks relevant to the task. 5. Failure cases, troubleshooting clues, rollback steps and final client-facing completion criteria. IMPLEMENTATION SAFETY Flag assumptions; favor native block controls over custom code; do not hardcode credentials or private data. For PHP/JS/CSS, provide exact location, activation scope, prerequisite checks, staging test, and undo method. If a plugin or version-specific behavior is uncertain, say what to verify first. Finish with a concise Definition of Done and a measurable business or UX outcome, without promising a result unsupported by data.
Media link verification
Create a tested, client-ready outcome for media link verification.
Act as a senior WordPress solution architect and Kadence Theme/Kadence Blocks/WPCode specialist. TASK: Media link verification. PROJECT INPUTS - Website type and business goal: [SITE TYPE + GOAL] - Audience, locale and key conversion: [AUDIENCE + LOCALE + CTA] - Current stack (WordPress/PHP, Kadence Theme, Kadence Blocks, WPCode, plugins): [VERIFIED VERSIONS] - Current page, screenshot, issue or reference: [URL OR SANITIZED DETAILS] - Constraints (budget, editor skill, hosting, launch date): [CONSTRAINTS] - Existing content, brand styles and approved data: [SOURCE MATERIAL] SPECIFIC OBJECTIVE Develop a practical, results-oriented solution for media link verification in the context of this website. Include release owner, backups, rollback, redirects and verification. Explain what should be done with Kadence Theme settings, what should be built with Kadence Blocks, and when WPCode is warranted. Do not invent installed plugin capabilities or pretend you accessed the live site. DELIVER EXACTLY 1. A task-specific implementation blueprint for “Media link verification” with exact WordPress/Kadence navigation or WPCode placement when relevant. 2. An ordered action checklist with dependencies and who owns each action. 3. Copy-ready artifacts where relevant (block hierarchy, settings matrix, sample copy, scoped CSS, PHP or vanilla JavaScript), with code fences and placement instructions. 4. Desktop/tablet/mobile acceptance tests, accessibility and security checks relevant to the task. 5. Failure cases, troubleshooting clues, rollback steps and final client-facing completion criteria. IMPLEMENTATION SAFETY Flag assumptions; favor native block controls over custom code; do not hardcode credentials or private data. For PHP/JS/CSS, provide exact location, activation scope, prerequisite checks, staging test, and undo method. If a plugin or version-specific behavior is uncertain, say what to verify first. Finish with a concise Definition of Done and a measurable business or UX outcome, without promising a result unsupported by data.
Analytics launch validation
Create a tested, client-ready outcome for analytics launch validation.
Act as a senior WordPress solution architect and Kadence Theme/Kadence Blocks/WPCode specialist. TASK: Analytics launch validation. PROJECT INPUTS - Website type and business goal: [SITE TYPE + GOAL] - Audience, locale and key conversion: [AUDIENCE + LOCALE + CTA] - Current stack (WordPress/PHP, Kadence Theme, Kadence Blocks, WPCode, plugins): [VERIFIED VERSIONS] - Current page, screenshot, issue or reference: [URL OR SANITIZED DETAILS] - Constraints (budget, editor skill, hosting, launch date): [CONSTRAINTS] - Existing content, brand styles and approved data: [SOURCE MATERIAL] SPECIFIC OBJECTIVE Develop a practical, results-oriented solution for analytics launch validation in the context of this website. Include release owner, backups, rollback, redirects and verification. Explain what should be done with Kadence Theme settings, what should be built with Kadence Blocks, and when WPCode is warranted. Do not invent installed plugin capabilities or pretend you accessed the live site. DELIVER EXACTLY 1. A task-specific implementation blueprint for “Analytics launch validation” with exact WordPress/Kadence navigation or WPCode placement when relevant. 2. An ordered action checklist with dependencies and who owns each action. 3. Copy-ready artifacts where relevant (block hierarchy, settings matrix, sample copy, scoped CSS, PHP or vanilla JavaScript), with code fences and placement instructions. 4. Desktop/tablet/mobile acceptance tests, accessibility and security checks relevant to the task. 5. Failure cases, troubleshooting clues, rollback steps and final client-facing completion criteria. IMPLEMENTATION SAFETY Flag assumptions; favor native block controls over custom code; do not hardcode credentials or private data. For PHP/JS/CSS, provide exact location, activation scope, prerequisite checks, staging test, and undo method. If a plugin or version-specific behavior is uncertain, say what to verify first. Finish with a concise Definition of Done and a measurable business or UX outcome, without promising a result unsupported by data.
Search Console setup review
Create a tested, client-ready outcome for search console setup review.
Act as a senior WordPress solution architect and Kadence Theme/Kadence Blocks/WPCode specialist. TASK: Search Console setup review. PROJECT INPUTS - Website type and business goal: [SITE TYPE + GOAL] - Audience, locale and key conversion: [AUDIENCE + LOCALE + CTA] - Current stack (WordPress/PHP, Kadence Theme, Kadence Blocks, WPCode, plugins): [VERIFIED VERSIONS] - Current page, screenshot, issue or reference: [URL OR SANITIZED DETAILS] - Constraints (budget, editor skill, hosting, launch date): [CONSTRAINTS] - Existing content, brand styles and approved data: [SOURCE MATERIAL] SPECIFIC OBJECTIVE Develop a practical, results-oriented solution for search console setup review in the context of this website. Include release owner, backups, rollback, redirects and verification. Explain what should be done with Kadence Theme settings, what should be built with Kadence Blocks, and when WPCode is warranted. Do not invent installed plugin capabilities or pretend you accessed the live site. DELIVER EXACTLY 1. A task-specific implementation blueprint for “Search Console setup review” with exact WordPress/Kadence navigation or WPCode placement when relevant. 2. An ordered action checklist with dependencies and who owns each action. 3. Copy-ready artifacts where relevant (block hierarchy, settings matrix, sample copy, scoped CSS, PHP or vanilla JavaScript), with code fences and placement instructions. 4. Desktop/tablet/mobile acceptance tests, accessibility and security checks relevant to the task. 5. Failure cases, troubleshooting clues, rollback steps and final client-facing completion criteria. IMPLEMENTATION SAFETY Flag assumptions; favor native block controls over custom code; do not hardcode credentials or private data. For PHP/JS/CSS, provide exact location, activation scope, prerequisite checks, staging test, and undo method. If a plugin or version-specific behavior is uncertain, say what to verify first. Finish with a concise Definition of Done and a measurable business or UX outcome, without promising a result unsupported by data.
Client training agenda
Create a tested, client-ready outcome for client training agenda.
Act as a senior WordPress solution architect and Kadence Theme/Kadence Blocks/WPCode specialist. TASK: Client training agenda. PROJECT INPUTS - Website type and business goal: [SITE TYPE + GOAL] - Audience, locale and key conversion: [AUDIENCE + LOCALE + CTA] - Current stack (WordPress/PHP, Kadence Theme, Kadence Blocks, WPCode, plugins): [VERIFIED VERSIONS] - Current page, screenshot, issue or reference: [URL OR SANITIZED DETAILS] - Constraints (budget, editor skill, hosting, launch date): [CONSTRAINTS] - Existing content, brand styles and approved data: [SOURCE MATERIAL] SPECIFIC OBJECTIVE Develop a practical, results-oriented solution for client training agenda in the context of this website. Include release owner, backups, rollback, redirects and verification. Explain what should be done with Kadence Theme settings, what should be built with Kadence Blocks, and when WPCode is warranted. Do not invent installed plugin capabilities or pretend you accessed the live site. DELIVER EXACTLY 1. A task-specific implementation blueprint for “Client training agenda” with exact WordPress/Kadence navigation or WPCode placement when relevant. 2. An ordered action checklist with dependencies and who owns each action. 3. Copy-ready artifacts where relevant (block hierarchy, settings matrix, sample copy, scoped CSS, PHP or vanilla JavaScript), with code fences and placement instructions. 4. Desktop/tablet/mobile acceptance tests, accessibility and security checks relevant to the task. 5. Failure cases, troubleshooting clues, rollback steps and final client-facing completion criteria. IMPLEMENTATION SAFETY Flag assumptions; favor native block controls over custom code; do not hardcode credentials or private data. For PHP/JS/CSS, provide exact location, activation scope, prerequisite checks, staging test, and undo method. If a plugin or version-specific behavior is uncertain, say what to verify first. Finish with a concise Definition of Done and a measurable business or UX outcome, without promising a result unsupported by data.
Monthly maintenance SOP
Create a tested, client-ready outcome for monthly maintenance sop.
Act as a senior WordPress solution architect and Kadence Theme/Kadence Blocks/WPCode specialist. TASK: Monthly maintenance SOP. PROJECT INPUTS - Website type and business goal: [SITE TYPE + GOAL] - Audience, locale and key conversion: [AUDIENCE + LOCALE + CTA] - Current stack (WordPress/PHP, Kadence Theme, Kadence Blocks, WPCode, plugins): [VERIFIED VERSIONS] - Current page, screenshot, issue or reference: [URL OR SANITIZED DETAILS] - Constraints (budget, editor skill, hosting, launch date): [CONSTRAINTS] - Existing content, brand styles and approved data: [SOURCE MATERIAL] SPECIFIC OBJECTIVE Develop a practical, results-oriented solution for monthly maintenance sop in the context of this website. Include release owner, backups, rollback, redirects and verification. Explain what should be done with Kadence Theme settings, what should be built with Kadence Blocks, and when WPCode is warranted. Do not invent installed plugin capabilities or pretend you accessed the live site. DELIVER EXACTLY 1. A task-specific implementation blueprint for “Monthly maintenance SOP” with exact WordPress/Kadence navigation or WPCode placement when relevant. 2. An ordered action checklist with dependencies and who owns each action. 3. Copy-ready artifacts where relevant (block hierarchy, settings matrix, sample copy, scoped CSS, PHP or vanilla JavaScript), with code fences and placement instructions. 4. Desktop/tablet/mobile acceptance tests, accessibility and security checks relevant to the task. 5. Failure cases, troubleshooting clues, rollback steps and final client-facing completion criteria. IMPLEMENTATION SAFETY Flag assumptions; favor native block controls over custom code; do not hardcode credentials or private data. For PHP/JS/CSS, provide exact location, activation scope, prerequisite checks, staging test, and undo method. If a plugin or version-specific behavior is uncertain, say what to verify first. Finish with a concise Definition of Done and a measurable business or UX outcome, without promising a result unsupported by data.
Disaster recovery drill
Create a tested, client-ready outcome for disaster recovery drill.
Act as a senior WordPress solution architect and Kadence Theme/Kadence Blocks/WPCode specialist. TASK: Disaster recovery drill. PROJECT INPUTS - Website type and business goal: [SITE TYPE + GOAL] - Audience, locale and key conversion: [AUDIENCE + LOCALE + CTA] - Current stack (WordPress/PHP, Kadence Theme, Kadence Blocks, WPCode, plugins): [VERIFIED VERSIONS] - Current page, screenshot, issue or reference: [URL OR SANITIZED DETAILS] - Constraints (budget, editor skill, hosting, launch date): [CONSTRAINTS] - Existing content, brand styles and approved data: [SOURCE MATERIAL] SPECIFIC OBJECTIVE Develop a practical, results-oriented solution for disaster recovery drill in the context of this website. Include release owner, backups, rollback, redirects and verification. Explain what should be done with Kadence Theme settings, what should be built with Kadence Blocks, and when WPCode is warranted. Do not invent installed plugin capabilities or pretend you accessed the live site. DELIVER EXACTLY 1. A task-specific implementation blueprint for “Disaster recovery drill” with exact WordPress/Kadence navigation or WPCode placement when relevant. 2. An ordered action checklist with dependencies and who owns each action. 3. Copy-ready artifacts where relevant (block hierarchy, settings matrix, sample copy, scoped CSS, PHP or vanilla JavaScript), with code fences and placement instructions. 4. Desktop/tablet/mobile acceptance tests, accessibility and security checks relevant to the task. 5. Failure cases, troubleshooting clues, rollback steps and final client-facing completion criteria. IMPLEMENTATION SAFETY Flag assumptions; favor native block controls over custom code; do not hardcode credentials or private data. For PHP/JS/CSS, provide exact location, activation scope, prerequisite checks, staging test, and undo method. If a plugin or version-specific behavior is uncertain, say what to verify first. Finish with a concise Definition of Done and a measurable business or UX outcome, without promising a result unsupported by data.
Decommission old environment
Create a tested, client-ready outcome for decommission old environment.
Act as a senior WordPress solution architect and Kadence Theme/Kadence Blocks/WPCode specialist. TASK: Decommission old environment. PROJECT INPUTS - Website type and business goal: [SITE TYPE + GOAL] - Audience, locale and key conversion: [AUDIENCE + LOCALE + CTA] - Current stack (WordPress/PHP, Kadence Theme, Kadence Blocks, WPCode, plugins): [VERIFIED VERSIONS] - Current page, screenshot, issue or reference: [URL OR SANITIZED DETAILS] - Constraints (budget, editor skill, hosting, launch date): [CONSTRAINTS] - Existing content, brand styles and approved data: [SOURCE MATERIAL] SPECIFIC OBJECTIVE Develop a practical, results-oriented solution for decommission old environment in the context of this website. Include release owner, backups, rollback, redirects and verification. Explain what should be done with Kadence Theme settings, what should be built with Kadence Blocks, and when WPCode is warranted. Do not invent installed plugin capabilities or pretend you accessed the live site. DELIVER EXACTLY 1. A task-specific implementation blueprint for “Decommission old environment” with exact WordPress/Kadence navigation or WPCode placement when relevant. 2. An ordered action checklist with dependencies and who owns each action. 3. Copy-ready artifacts where relevant (block hierarchy, settings matrix, sample copy, scoped CSS, PHP or vanilla JavaScript), with code fences and placement instructions. 4. Desktop/tablet/mobile acceptance tests, accessibility and security checks relevant to the task. 5. Failure cases, troubleshooting clues, rollback steps and final client-facing completion criteria. IMPLEMENTATION SAFETY Flag assumptions; favor native block controls over custom code; do not hardcode credentials or private data. For PHP/JS/CSS, provide exact location, activation scope, prerequisite checks, staging test, and undo method. If a plugin or version-specific behavior is uncertain, say what to verify first. Finish with a concise Definition of Done and a measurable business or UX outcome, without promising a result unsupported by data.
24. Industry Website Blueprints
Restaurant information architecture
Create a tested, client-ready outcome for restaurant information architecture.
Act as a senior WordPress solution architect and Kadence Theme/Kadence Blocks/WPCode specialist. TASK: Restaurant information architecture. PROJECT INPUTS - Website type and business goal: [SITE TYPE + GOAL] - Audience, locale and key conversion: [AUDIENCE + LOCALE + CTA] - Current stack (WordPress/PHP, Kadence Theme, Kadence Blocks, WPCode, plugins): [VERIFIED VERSIONS] - Current page, screenshot, issue or reference: [URL OR SANITIZED DETAILS] - Constraints (budget, editor skill, hosting, launch date): [CONSTRAINTS] - Existing content, brand styles and approved data: [SOURCE MATERIAL] SPECIFIC OBJECTIVE Develop a practical, results-oriented solution for restaurant information architecture in the context of this website. Account for sector-specific restrictions without inventing integrations or regulatory status. Explain what should be done with Kadence Theme settings, what should be built with Kadence Blocks, and when WPCode is warranted. Do not invent installed plugin capabilities or pretend you accessed the live site. DELIVER EXACTLY 1. A task-specific implementation blueprint for “Restaurant information architecture” with exact WordPress/Kadence navigation or WPCode placement when relevant. 2. An ordered action checklist with dependencies and who owns each action. 3. Copy-ready artifacts where relevant (block hierarchy, settings matrix, sample copy, scoped CSS, PHP or vanilla JavaScript), with code fences and placement instructions. 4. Desktop/tablet/mobile acceptance tests, accessibility and security checks relevant to the task. 5. Failure cases, troubleshooting clues, rollback steps and final client-facing completion criteria. IMPLEMENTATION SAFETY Flag assumptions; favor native block controls over custom code; do not hardcode credentials or private data. For PHP/JS/CSS, provide exact location, activation scope, prerequisite checks, staging test, and undo method. If a plugin or version-specific behavior is uncertain, say what to verify first. Finish with a concise Definition of Done and a measurable business or UX outcome, without promising a result unsupported by data.
Real estate lead website
Create a tested, client-ready outcome for real estate lead website.
Act as a senior WordPress solution architect and Kadence Theme/Kadence Blocks/WPCode specialist. TASK: Real estate lead website. PROJECT INPUTS - Website type and business goal: [SITE TYPE + GOAL] - Audience, locale and key conversion: [AUDIENCE + LOCALE + CTA] - Current stack (WordPress/PHP, Kadence Theme, Kadence Blocks, WPCode, plugins): [VERIFIED VERSIONS] - Current page, screenshot, issue or reference: [URL OR SANITIZED DETAILS] - Constraints (budget, editor skill, hosting, launch date): [CONSTRAINTS] - Existing content, brand styles and approved data: [SOURCE MATERIAL] SPECIFIC OBJECTIVE Develop a practical, results-oriented solution for real estate lead website in the context of this website. Account for sector-specific restrictions without inventing integrations or regulatory status. Explain what should be done with Kadence Theme settings, what should be built with Kadence Blocks, and when WPCode is warranted. Do not invent installed plugin capabilities or pretend you accessed the live site. DELIVER EXACTLY 1. A task-specific implementation blueprint for “Real estate lead website” with exact WordPress/Kadence navigation or WPCode placement when relevant. 2. An ordered action checklist with dependencies and who owns each action. 3. Copy-ready artifacts where relevant (block hierarchy, settings matrix, sample copy, scoped CSS, PHP or vanilla JavaScript), with code fences and placement instructions. 4. Desktop/tablet/mobile acceptance tests, accessibility and security checks relevant to the task. 5. Failure cases, troubleshooting clues, rollback steps and final client-facing completion criteria. IMPLEMENTATION SAFETY Flag assumptions; favor native block controls over custom code; do not hardcode credentials or private data. For PHP/JS/CSS, provide exact location, activation scope, prerequisite checks, staging test, and undo method. If a plugin or version-specific behavior is uncertain, say what to verify first. Finish with a concise Definition of Done and a measurable business or UX outcome, without promising a result unsupported by data.
Construction contractor website
Create a tested, client-ready outcome for construction contractor website.
Act as a senior WordPress solution architect and Kadence Theme/Kadence Blocks/WPCode specialist. TASK: Construction contractor website. PROJECT INPUTS - Website type and business goal: [SITE TYPE + GOAL] - Audience, locale and key conversion: [AUDIENCE + LOCALE + CTA] - Current stack (WordPress/PHP, Kadence Theme, Kadence Blocks, WPCode, plugins): [VERIFIED VERSIONS] - Current page, screenshot, issue or reference: [URL OR SANITIZED DETAILS] - Constraints (budget, editor skill, hosting, launch date): [CONSTRAINTS] - Existing content, brand styles and approved data: [SOURCE MATERIAL] SPECIFIC OBJECTIVE Develop a practical, results-oriented solution for construction contractor website in the context of this website. Account for sector-specific restrictions without inventing integrations or regulatory status. Explain what should be done with Kadence Theme settings, what should be built with Kadence Blocks, and when WPCode is warranted. Do not invent installed plugin capabilities or pretend you accessed the live site. DELIVER EXACTLY 1. A task-specific implementation blueprint for “Construction contractor website” with exact WordPress/Kadence navigation or WPCode placement when relevant. 2. An ordered action checklist with dependencies and who owns each action. 3. Copy-ready artifacts where relevant (block hierarchy, settings matrix, sample copy, scoped CSS, PHP or vanilla JavaScript), with code fences and placement instructions. 4. Desktop/tablet/mobile acceptance tests, accessibility and security checks relevant to the task. 5. Failure cases, troubleshooting clues, rollback steps and final client-facing completion criteria. IMPLEMENTATION SAFETY Flag assumptions; favor native block controls over custom code; do not hardcode credentials or private data. For PHP/JS/CSS, provide exact location, activation scope, prerequisite checks, staging test, and undo method. If a plugin or version-specific behavior is uncertain, say what to verify first. Finish with a concise Definition of Done and a measurable business or UX outcome, without promising a result unsupported by data.
Nonprofit donation website
Create a tested, client-ready outcome for nonprofit donation website.
Act as a senior WordPress solution architect and Kadence Theme/Kadence Blocks/WPCode specialist. TASK: Nonprofit donation website. PROJECT INPUTS - Website type and business goal: [SITE TYPE + GOAL] - Audience, locale and key conversion: [AUDIENCE + LOCALE + CTA] - Current stack (WordPress/PHP, Kadence Theme, Kadence Blocks, WPCode, plugins): [VERIFIED VERSIONS] - Current page, screenshot, issue or reference: [URL OR SANITIZED DETAILS] - Constraints (budget, editor skill, hosting, launch date): [CONSTRAINTS] - Existing content, brand styles and approved data: [SOURCE MATERIAL] SPECIFIC OBJECTIVE Develop a practical, results-oriented solution for nonprofit donation website in the context of this website. Account for sector-specific restrictions without inventing integrations or regulatory status. Explain what should be done with Kadence Theme settings, what should be built with Kadence Blocks, and when WPCode is warranted. Do not invent installed plugin capabilities or pretend you accessed the live site. DELIVER EXACTLY 1. A task-specific implementation blueprint for “Nonprofit donation website” with exact WordPress/Kadence navigation or WPCode placement when relevant. 2. An ordered action checklist with dependencies and who owns each action. 3. Copy-ready artifacts where relevant (block hierarchy, settings matrix, sample copy, scoped CSS, PHP or vanilla JavaScript), with code fences and placement instructions. 4. Desktop/tablet/mobile acceptance tests, accessibility and security checks relevant to the task. 5. Failure cases, troubleshooting clues, rollback steps and final client-facing completion criteria. IMPLEMENTATION SAFETY Flag assumptions; favor native block controls over custom code; do not hardcode credentials or private data. For PHP/JS/CSS, provide exact location, activation scope, prerequisite checks, staging test, and undo method. If a plugin or version-specific behavior is uncertain, say what to verify first. Finish with a concise Definition of Done and a measurable business or UX outcome, without promising a result unsupported by data.
School and training website
Create a tested, client-ready outcome for school and training website.
Act as a senior WordPress solution architect and Kadence Theme/Kadence Blocks/WPCode specialist. TASK: School and training website. PROJECT INPUTS - Website type and business goal: [SITE TYPE + GOAL] - Audience, locale and key conversion: [AUDIENCE + LOCALE + CTA] - Current stack (WordPress/PHP, Kadence Theme, Kadence Blocks, WPCode, plugins): [VERIFIED VERSIONS] - Current page, screenshot, issue or reference: [URL OR SANITIZED DETAILS] - Constraints (budget, editor skill, hosting, launch date): [CONSTRAINTS] - Existing content, brand styles and approved data: [SOURCE MATERIAL] SPECIFIC OBJECTIVE Develop a practical, results-oriented solution for school and training website in the context of this website. Account for sector-specific restrictions without inventing integrations or regulatory status. Explain what should be done with Kadence Theme settings, what should be built with Kadence Blocks, and when WPCode is warranted. Do not invent installed plugin capabilities or pretend you accessed the live site. DELIVER EXACTLY 1. A task-specific implementation blueprint for “School and training website” with exact WordPress/Kadence navigation or WPCode placement when relevant. 2. An ordered action checklist with dependencies and who owns each action. 3. Copy-ready artifacts where relevant (block hierarchy, settings matrix, sample copy, scoped CSS, PHP or vanilla JavaScript), with code fences and placement instructions. 4. Desktop/tablet/mobile acceptance tests, accessibility and security checks relevant to the task. 5. Failure cases, troubleshooting clues, rollback steps and final client-facing completion criteria. IMPLEMENTATION SAFETY Flag assumptions; favor native block controls over custom code; do not hardcode credentials or private data. For PHP/JS/CSS, provide exact location, activation scope, prerequisite checks, staging test, and undo method. If a plugin or version-specific behavior is uncertain, say what to verify first. Finish with a concise Definition of Done and a measurable business or UX outcome, without promising a result unsupported by data.
Fitness studio website
Create a tested, client-ready outcome for fitness studio website.
Act as a senior WordPress solution architect and Kadence Theme/Kadence Blocks/WPCode specialist. TASK: Fitness studio website. PROJECT INPUTS - Website type and business goal: [SITE TYPE + GOAL] - Audience, locale and key conversion: [AUDIENCE + LOCALE + CTA] - Current stack (WordPress/PHP, Kadence Theme, Kadence Blocks, WPCode, plugins): [VERIFIED VERSIONS] - Current page, screenshot, issue or reference: [URL OR SANITIZED DETAILS] - Constraints (budget, editor skill, hosting, launch date): [CONSTRAINTS] - Existing content, brand styles and approved data: [SOURCE MATERIAL] SPECIFIC OBJECTIVE Develop a practical, results-oriented solution for fitness studio website in the context of this website. Account for sector-specific restrictions without inventing integrations or regulatory status. Explain what should be done with Kadence Theme settings, what should be built with Kadence Blocks, and when WPCode is warranted. Do not invent installed plugin capabilities or pretend you accessed the live site. DELIVER EXACTLY 1. A task-specific implementation blueprint for “Fitness studio website” with exact WordPress/Kadence navigation or WPCode placement when relevant. 2. An ordered action checklist with dependencies and who owns each action. 3. Copy-ready artifacts where relevant (block hierarchy, settings matrix, sample copy, scoped CSS, PHP or vanilla JavaScript), with code fences and placement instructions. 4. Desktop/tablet/mobile acceptance tests, accessibility and security checks relevant to the task. 5. Failure cases, troubleshooting clues, rollback steps and final client-facing completion criteria. IMPLEMENTATION SAFETY Flag assumptions; favor native block controls over custom code; do not hardcode credentials or private data. For PHP/JS/CSS, provide exact location, activation scope, prerequisite checks, staging test, and undo method. If a plugin or version-specific behavior is uncertain, say what to verify first. Finish with a concise Definition of Done and a measurable business or UX outcome, without promising a result unsupported by data.
Travel agency website
Create a tested, client-ready outcome for travel agency website.
Act as a senior WordPress solution architect and Kadence Theme/Kadence Blocks/WPCode specialist. TASK: Travel agency website. PROJECT INPUTS - Website type and business goal: [SITE TYPE + GOAL] - Audience, locale and key conversion: [AUDIENCE + LOCALE + CTA] - Current stack (WordPress/PHP, Kadence Theme, Kadence Blocks, WPCode, plugins): [VERIFIED VERSIONS] - Current page, screenshot, issue or reference: [URL OR SANITIZED DETAILS] - Constraints (budget, editor skill, hosting, launch date): [CONSTRAINTS] - Existing content, brand styles and approved data: [SOURCE MATERIAL] SPECIFIC OBJECTIVE Develop a practical, results-oriented solution for travel agency website in the context of this website. Account for sector-specific restrictions without inventing integrations or regulatory status. Explain what should be done with Kadence Theme settings, what should be built with Kadence Blocks, and when WPCode is warranted. Do not invent installed plugin capabilities or pretend you accessed the live site. DELIVER EXACTLY 1. A task-specific implementation blueprint for “Travel agency website” with exact WordPress/Kadence navigation or WPCode placement when relevant. 2. An ordered action checklist with dependencies and who owns each action. 3. Copy-ready artifacts where relevant (block hierarchy, settings matrix, sample copy, scoped CSS, PHP or vanilla JavaScript), with code fences and placement instructions. 4. Desktop/tablet/mobile acceptance tests, accessibility and security checks relevant to the task. 5. Failure cases, troubleshooting clues, rollback steps and final client-facing completion criteria. IMPLEMENTATION SAFETY Flag assumptions; favor native block controls over custom code; do not hardcode credentials or private data. For PHP/JS/CSS, provide exact location, activation scope, prerequisite checks, staging test, and undo method. If a plugin or version-specific behavior is uncertain, say what to verify first. Finish with a concise Definition of Done and a measurable business or UX outcome, without promising a result unsupported by data.
SaaS marketing website
Create a tested, client-ready outcome for saas marketing website.
Act as a senior WordPress solution architect and Kadence Theme/Kadence Blocks/WPCode specialist. TASK: SaaS marketing website. PROJECT INPUTS - Website type and business goal: [SITE TYPE + GOAL] - Audience, locale and key conversion: [AUDIENCE + LOCALE + CTA] - Current stack (WordPress/PHP, Kadence Theme, Kadence Blocks, WPCode, plugins): [VERIFIED VERSIONS] - Current page, screenshot, issue or reference: [URL OR SANITIZED DETAILS] - Constraints (budget, editor skill, hosting, launch date): [CONSTRAINTS] - Existing content, brand styles and approved data: [SOURCE MATERIAL] SPECIFIC OBJECTIVE Develop a practical, results-oriented solution for saas marketing website in the context of this website. Account for sector-specific restrictions without inventing integrations or regulatory status. Explain what should be done with Kadence Theme settings, what should be built with Kadence Blocks, and when WPCode is warranted. Do not invent installed plugin capabilities or pretend you accessed the live site. DELIVER EXACTLY 1. A task-specific implementation blueprint for “SaaS marketing website” with exact WordPress/Kadence navigation or WPCode placement when relevant. 2. An ordered action checklist with dependencies and who owns each action. 3. Copy-ready artifacts where relevant (block hierarchy, settings matrix, sample copy, scoped CSS, PHP or vanilla JavaScript), with code fences and placement instructions. 4. Desktop/tablet/mobile acceptance tests, accessibility and security checks relevant to the task. 5. Failure cases, troubleshooting clues, rollback steps and final client-facing completion criteria. IMPLEMENTATION SAFETY Flag assumptions; favor native block controls over custom code; do not hardcode credentials or private data. For PHP/JS/CSS, provide exact location, activation scope, prerequisite checks, staging test, and undo method. If a plugin or version-specific behavior is uncertain, say what to verify first. Finish with a concise Definition of Done and a measurable business or UX outcome, without promising a result unsupported by data.
Marketplace MVP website
Create a tested, client-ready outcome for marketplace mvp website.
Act as a senior WordPress solution architect and Kadence Theme/Kadence Blocks/WPCode specialist. TASK: Marketplace MVP website. PROJECT INPUTS - Website type and business goal: [SITE TYPE + GOAL] - Audience, locale and key conversion: [AUDIENCE + LOCALE + CTA] - Current stack (WordPress/PHP, Kadence Theme, Kadence Blocks, WPCode, plugins): [VERIFIED VERSIONS] - Current page, screenshot, issue or reference: [URL OR SANITIZED DETAILS] - Constraints (budget, editor skill, hosting, launch date): [CONSTRAINTS] - Existing content, brand styles and approved data: [SOURCE MATERIAL] SPECIFIC OBJECTIVE Develop a practical, results-oriented solution for marketplace mvp website in the context of this website. Account for sector-specific restrictions without inventing integrations or regulatory status. Explain what should be done with Kadence Theme settings, what should be built with Kadence Blocks, and when WPCode is warranted. Do not invent installed plugin capabilities or pretend you accessed the live site. DELIVER EXACTLY 1. A task-specific implementation blueprint for “Marketplace MVP website” with exact WordPress/Kadence navigation or WPCode placement when relevant. 2. An ordered action checklist with dependencies and who owns each action. 3. Copy-ready artifacts where relevant (block hierarchy, settings matrix, sample copy, scoped CSS, PHP or vanilla JavaScript), with code fences and placement instructions. 4. Desktop/tablet/mobile acceptance tests, accessibility and security checks relevant to the task. 5. Failure cases, troubleshooting clues, rollback steps and final client-facing completion criteria. IMPLEMENTATION SAFETY Flag assumptions; favor native block controls over custom code; do not hardcode credentials or private data. For PHP/JS/CSS, provide exact location, activation scope, prerequisite checks, staging test, and undo method. If a plugin or version-specific behavior is uncertain, say what to verify first. Finish with a concise Definition of Done and a measurable business or UX outcome, without promising a result unsupported by data.
Healthcare practice website
Create a tested, client-ready outcome for healthcare practice website.
Act as a senior WordPress solution architect and Kadence Theme/Kadence Blocks/WPCode specialist. TASK: Healthcare practice website. PROJECT INPUTS - Website type and business goal: [SITE TYPE + GOAL] - Audience, locale and key conversion: [AUDIENCE + LOCALE + CTA] - Current stack (WordPress/PHP, Kadence Theme, Kadence Blocks, WPCode, plugins): [VERIFIED VERSIONS] - Current page, screenshot, issue or reference: [URL OR SANITIZED DETAILS] - Constraints (budget, editor skill, hosting, launch date): [CONSTRAINTS] - Existing content, brand styles and approved data: [SOURCE MATERIAL] SPECIFIC OBJECTIVE Develop a practical, results-oriented solution for healthcare practice website in the context of this website. Account for sector-specific restrictions without inventing integrations or regulatory status. Explain what should be done with Kadence Theme settings, what should be built with Kadence Blocks, and when WPCode is warranted. Do not invent installed plugin capabilities or pretend you accessed the live site. DELIVER EXACTLY 1. A task-specific implementation blueprint for “Healthcare practice website” with exact WordPress/Kadence navigation or WPCode placement when relevant. 2. An ordered action checklist with dependencies and who owns each action. 3. Copy-ready artifacts where relevant (block hierarchy, settings matrix, sample copy, scoped CSS, PHP or vanilla JavaScript), with code fences and placement instructions. 4. Desktop/tablet/mobile acceptance tests, accessibility and security checks relevant to the task. 5. Failure cases, troubleshooting clues, rollback steps and final client-facing completion criteria. IMPLEMENTATION SAFETY Flag assumptions; favor native block controls over custom code; do not hardcode credentials or private data. For PHP/JS/CSS, provide exact location, activation scope, prerequisite checks, staging test, and undo method. If a plugin or version-specific behavior is uncertain, say what to verify first. Finish with a concise Definition of Done and a measurable business or UX outcome, without promising a result unsupported by data.
25. AI-Assisted Development Workflow
Screenshot-to-block decomposition
Create a tested, client-ready outcome for screenshot-to-block decomposition.
Act as a senior WordPress solution architect and Kadence Theme/Kadence Blocks/WPCode specialist. TASK: Screenshot-to-block decomposition. PROJECT INPUTS - Website type and business goal: [SITE TYPE + GOAL] - Audience, locale and key conversion: [AUDIENCE + LOCALE + CTA] - Current stack (WordPress/PHP, Kadence Theme, Kadence Blocks, WPCode, plugins): [VERIFIED VERSIONS] - Current page, screenshot, issue or reference: [URL OR SANITIZED DETAILS] - Constraints (budget, editor skill, hosting, launch date): [CONSTRAINTS] - Existing content, brand styles and approved data: [SOURCE MATERIAL] SPECIFIC OBJECTIVE Develop a practical, results-oriented solution for screenshot-to-block decomposition in the context of this website. Treat generated code as untrusted until inspected, staged and tested. Explain what should be done with Kadence Theme settings, what should be built with Kadence Blocks, and when WPCode is warranted. Do not invent installed plugin capabilities or pretend you accessed the live site. DELIVER EXACTLY 1. A task-specific implementation blueprint for “Screenshot-to-block decomposition” with exact WordPress/Kadence navigation or WPCode placement when relevant. 2. An ordered action checklist with dependencies and who owns each action. 3. Copy-ready artifacts where relevant (block hierarchy, settings matrix, sample copy, scoped CSS, PHP or vanilla JavaScript), with code fences and placement instructions. 4. Desktop/tablet/mobile acceptance tests, accessibility and security checks relevant to the task. 5. Failure cases, troubleshooting clues, rollback steps and final client-facing completion criteria. IMPLEMENTATION SAFETY Flag assumptions; favor native block controls over custom code; do not hardcode credentials or private data. For PHP/JS/CSS, provide exact location, activation scope, prerequisite checks, staging test, and undo method. If a plugin or version-specific behavior is uncertain, say what to verify first. Finish with a concise Definition of Done and a measurable business or UX outcome, without promising a result unsupported by data.
Design brief to Kadence pattern
Create a tested, client-ready outcome for design brief to kadence pattern.
Act as a senior WordPress solution architect and Kadence Theme/Kadence Blocks/WPCode specialist. TASK: Design brief to Kadence pattern. PROJECT INPUTS - Website type and business goal: [SITE TYPE + GOAL] - Audience, locale and key conversion: [AUDIENCE + LOCALE + CTA] - Current stack (WordPress/PHP, Kadence Theme, Kadence Blocks, WPCode, plugins): [VERIFIED VERSIONS] - Current page, screenshot, issue or reference: [URL OR SANITIZED DETAILS] - Constraints (budget, editor skill, hosting, launch date): [CONSTRAINTS] - Existing content, brand styles and approved data: [SOURCE MATERIAL] SPECIFIC OBJECTIVE Develop a practical, results-oriented solution for design brief to kadence pattern in the context of this website. Treat generated code as untrusted until inspected, staged and tested. Explain what should be done with Kadence Theme settings, what should be built with Kadence Blocks, and when WPCode is warranted. Do not invent installed plugin capabilities or pretend you accessed the live site. DELIVER EXACTLY 1. A task-specific implementation blueprint for “Design brief to Kadence pattern” with exact WordPress/Kadence navigation or WPCode placement when relevant. 2. An ordered action checklist with dependencies and who owns each action. 3. Copy-ready artifacts where relevant (block hierarchy, settings matrix, sample copy, scoped CSS, PHP or vanilla JavaScript), with code fences and placement instructions. 4. Desktop/tablet/mobile acceptance tests, accessibility and security checks relevant to the task. 5. Failure cases, troubleshooting clues, rollback steps and final client-facing completion criteria. IMPLEMENTATION SAFETY Flag assumptions; favor native block controls over custom code; do not hardcode credentials or private data. For PHP/JS/CSS, provide exact location, activation scope, prerequisite checks, staging test, and undo method. If a plugin or version-specific behavior is uncertain, say what to verify first. Finish with a concise Definition of Done and a measurable business or UX outcome, without promising a result unsupported by data.
AI-generated code review
Create a tested, client-ready outcome for ai-generated code review.
Act as a senior WordPress solution architect and Kadence Theme/Kadence Blocks/WPCode specialist. TASK: AI-generated code review. PROJECT INPUTS - Website type and business goal: [SITE TYPE + GOAL] - Audience, locale and key conversion: [AUDIENCE + LOCALE + CTA] - Current stack (WordPress/PHP, Kadence Theme, Kadence Blocks, WPCode, plugins): [VERIFIED VERSIONS] - Current page, screenshot, issue or reference: [URL OR SANITIZED DETAILS] - Constraints (budget, editor skill, hosting, launch date): [CONSTRAINTS] - Existing content, brand styles and approved data: [SOURCE MATERIAL] SPECIFIC OBJECTIVE Develop a practical, results-oriented solution for ai-generated code review in the context of this website. Treat generated code as untrusted until inspected, staged and tested. Explain what should be done with Kadence Theme settings, what should be built with Kadence Blocks, and when WPCode is warranted. Do not invent installed plugin capabilities or pretend you accessed the live site. DELIVER EXACTLY 1. A task-specific implementation blueprint for “AI-generated code review” with exact WordPress/Kadence navigation or WPCode placement when relevant. 2. An ordered action checklist with dependencies and who owns each action. 3. Copy-ready artifacts where relevant (block hierarchy, settings matrix, sample copy, scoped CSS, PHP or vanilla JavaScript), with code fences and placement instructions. 4. Desktop/tablet/mobile acceptance tests, accessibility and security checks relevant to the task. 5. Failure cases, troubleshooting clues, rollback steps and final client-facing completion criteria. IMPLEMENTATION SAFETY Flag assumptions; favor native block controls over custom code; do not hardcode credentials or private data. For PHP/JS/CSS, provide exact location, activation scope, prerequisite checks, staging test, and undo method. If a plugin or version-specific behavior is uncertain, say what to verify first. Finish with a concise Definition of Done and a measurable business or UX outcome, without promising a result unsupported by data.
Prompt-to-WPCode specification
Create a tested, client-ready outcome for prompt-to-wpcode specification.
Act as a senior WordPress solution architect and Kadence Theme/Kadence Blocks/WPCode specialist. TASK: Prompt-to-WPCode specification. PROJECT INPUTS - Website type and business goal: [SITE TYPE + GOAL] - Audience, locale and key conversion: [AUDIENCE + LOCALE + CTA] - Current stack (WordPress/PHP, Kadence Theme, Kadence Blocks, WPCode, plugins): [VERIFIED VERSIONS] - Current page, screenshot, issue or reference: [URL OR SANITIZED DETAILS] - Constraints (budget, editor skill, hosting, launch date): [CONSTRAINTS] - Existing content, brand styles and approved data: [SOURCE MATERIAL] SPECIFIC OBJECTIVE Develop a practical, results-oriented solution for prompt-to-wpcode specification in the context of this website. Treat generated code as untrusted until inspected, staged and tested. Explain what should be done with Kadence Theme settings, what should be built with Kadence Blocks, and when WPCode is warranted. Do not invent installed plugin capabilities or pretend you accessed the live site. DELIVER EXACTLY 1. A task-specific implementation blueprint for “Prompt-to-WPCode specification” with exact WordPress/Kadence navigation or WPCode placement when relevant. 2. An ordered action checklist with dependencies and who owns each action. 3. Copy-ready artifacts where relevant (block hierarchy, settings matrix, sample copy, scoped CSS, PHP or vanilla JavaScript), with code fences and placement instructions. 4. Desktop/tablet/mobile acceptance tests, accessibility and security checks relevant to the task. 5. Failure cases, troubleshooting clues, rollback steps and final client-facing completion criteria. IMPLEMENTATION SAFETY Flag assumptions; favor native block controls over custom code; do not hardcode credentials or private data. For PHP/JS/CSS, provide exact location, activation scope, prerequisite checks, staging test, and undo method. If a plugin or version-specific behavior is uncertain, say what to verify first. Finish with a concise Definition of Done and a measurable business or UX outcome, without promising a result unsupported by data.
AI debugging evidence packet
Create a tested, client-ready outcome for ai debugging evidence packet.
Act as a senior WordPress solution architect and Kadence Theme/Kadence Blocks/WPCode specialist. TASK: AI debugging evidence packet. PROJECT INPUTS - Website type and business goal: [SITE TYPE + GOAL] - Audience, locale and key conversion: [AUDIENCE + LOCALE + CTA] - Current stack (WordPress/PHP, Kadence Theme, Kadence Blocks, WPCode, plugins): [VERIFIED VERSIONS] - Current page, screenshot, issue or reference: [URL OR SANITIZED DETAILS] - Constraints (budget, editor skill, hosting, launch date): [CONSTRAINTS] - Existing content, brand styles and approved data: [SOURCE MATERIAL] SPECIFIC OBJECTIVE Develop a practical, results-oriented solution for ai debugging evidence packet in the context of this website. Treat generated code as untrusted until inspected, staged and tested. Explain what should be done with Kadence Theme settings, what should be built with Kadence Blocks, and when WPCode is warranted. Do not invent installed plugin capabilities or pretend you accessed the live site. DELIVER EXACTLY 1. A task-specific implementation blueprint for “AI debugging evidence packet” with exact WordPress/Kadence navigation or WPCode placement when relevant. 2. An ordered action checklist with dependencies and who owns each action. 3. Copy-ready artifacts where relevant (block hierarchy, settings matrix, sample copy, scoped CSS, PHP or vanilla JavaScript), with code fences and placement instructions. 4. Desktop/tablet/mobile acceptance tests, accessibility and security checks relevant to the task. 5. Failure cases, troubleshooting clues, rollback steps and final client-facing completion criteria. IMPLEMENTATION SAFETY Flag assumptions; favor native block controls over custom code; do not hardcode credentials or private data. For PHP/JS/CSS, provide exact location, activation scope, prerequisite checks, staging test, and undo method. If a plugin or version-specific behavior is uncertain, say what to verify first. Finish with a concise Definition of Done and a measurable business or UX outcome, without promising a result unsupported by data.
Reusable client prompt template
Create a tested, client-ready outcome for reusable client prompt template.
Act as a senior WordPress solution architect and Kadence Theme/Kadence Blocks/WPCode specialist. TASK: Reusable client prompt template. PROJECT INPUTS - Website type and business goal: [SITE TYPE + GOAL] - Audience, locale and key conversion: [AUDIENCE + LOCALE + CTA] - Current stack (WordPress/PHP, Kadence Theme, Kadence Blocks, WPCode, plugins): [VERIFIED VERSIONS] - Current page, screenshot, issue or reference: [URL OR SANITIZED DETAILS] - Constraints (budget, editor skill, hosting, launch date): [CONSTRAINTS] - Existing content, brand styles and approved data: [SOURCE MATERIAL] SPECIFIC OBJECTIVE Develop a practical, results-oriented solution for reusable client prompt template in the context of this website. Treat generated code as untrusted until inspected, staged and tested. Explain what should be done with Kadence Theme settings, what should be built with Kadence Blocks, and when WPCode is warranted. Do not invent installed plugin capabilities or pretend you accessed the live site. DELIVER EXACTLY 1. A task-specific implementation blueprint for “Reusable client prompt template” with exact WordPress/Kadence navigation or WPCode placement when relevant. 2. An ordered action checklist with dependencies and who owns each action. 3. Copy-ready artifacts where relevant (block hierarchy, settings matrix, sample copy, scoped CSS, PHP or vanilla JavaScript), with code fences and placement instructions. 4. Desktop/tablet/mobile acceptance tests, accessibility and security checks relevant to the task. 5. Failure cases, troubleshooting clues, rollback steps and final client-facing completion criteria. IMPLEMENTATION SAFETY Flag assumptions; favor native block controls over custom code; do not hardcode credentials or private data. For PHP/JS/CSS, provide exact location, activation scope, prerequisite checks, staging test, and undo method. If a plugin or version-specific behavior is uncertain, say what to verify first. Finish with a concise Definition of Done and a measurable business or UX outcome, without promising a result unsupported by data.
Human approval gate design
Create a tested, client-ready outcome for human approval gate design.
Act as a senior WordPress solution architect and Kadence Theme/Kadence Blocks/WPCode specialist. TASK: Human approval gate design. PROJECT INPUTS - Website type and business goal: [SITE TYPE + GOAL] - Audience, locale and key conversion: [AUDIENCE + LOCALE + CTA] - Current stack (WordPress/PHP, Kadence Theme, Kadence Blocks, WPCode, plugins): [VERIFIED VERSIONS] - Current page, screenshot, issue or reference: [URL OR SANITIZED DETAILS] - Constraints (budget, editor skill, hosting, launch date): [CONSTRAINTS] - Existing content, brand styles and approved data: [SOURCE MATERIAL] SPECIFIC OBJECTIVE Develop a practical, results-oriented solution for human approval gate design in the context of this website. Treat generated code as untrusted until inspected, staged and tested. Explain what should be done with Kadence Theme settings, what should be built with Kadence Blocks, and when WPCode is warranted. Do not invent installed plugin capabilities or pretend you accessed the live site. DELIVER EXACTLY 1. A task-specific implementation blueprint for “Human approval gate design” with exact WordPress/Kadence navigation or WPCode placement when relevant. 2. An ordered action checklist with dependencies and who owns each action. 3. Copy-ready artifacts where relevant (block hierarchy, settings matrix, sample copy, scoped CSS, PHP or vanilla JavaScript), with code fences and placement instructions. 4. Desktop/tablet/mobile acceptance tests, accessibility and security checks relevant to the task. 5. Failure cases, troubleshooting clues, rollback steps and final client-facing completion criteria. IMPLEMENTATION SAFETY Flag assumptions; favor native block controls over custom code; do not hardcode credentials or private data. For PHP/JS/CSS, provide exact location, activation scope, prerequisite checks, staging test, and undo method. If a plugin or version-specific behavior is uncertain, say what to verify first. Finish with a concise Definition of Done and a measurable business or UX outcome, without promising a result unsupported by data.
Change log automation plan
Create a tested, client-ready outcome for change log automation plan.
Act as a senior WordPress solution architect and Kadence Theme/Kadence Blocks/WPCode specialist. TASK: Change log automation plan. PROJECT INPUTS - Website type and business goal: [SITE TYPE + GOAL] - Audience, locale and key conversion: [AUDIENCE + LOCALE + CTA] - Current stack (WordPress/PHP, Kadence Theme, Kadence Blocks, WPCode, plugins): [VERIFIED VERSIONS] - Current page, screenshot, issue or reference: [URL OR SANITIZED DETAILS] - Constraints (budget, editor skill, hosting, launch date): [CONSTRAINTS] - Existing content, brand styles and approved data: [SOURCE MATERIAL] SPECIFIC OBJECTIVE Develop a practical, results-oriented solution for change log automation plan in the context of this website. Treat generated code as untrusted until inspected, staged and tested. Explain what should be done with Kadence Theme settings, what should be built with Kadence Blocks, and when WPCode is warranted. Do not invent installed plugin capabilities or pretend you accessed the live site. DELIVER EXACTLY 1. A task-specific implementation blueprint for “Change log automation plan” with exact WordPress/Kadence navigation or WPCode placement when relevant. 2. An ordered action checklist with dependencies and who owns each action. 3. Copy-ready artifacts where relevant (block hierarchy, settings matrix, sample copy, scoped CSS, PHP or vanilla JavaScript), with code fences and placement instructions. 4. Desktop/tablet/mobile acceptance tests, accessibility and security checks relevant to the task. 5. Failure cases, troubleshooting clues, rollback steps and final client-facing completion criteria. IMPLEMENTATION SAFETY Flag assumptions; favor native block controls over custom code; do not hardcode credentials or private data. For PHP/JS/CSS, provide exact location, activation scope, prerequisite checks, staging test, and undo method. If a plugin or version-specific behavior is uncertain, say what to verify first. Finish with a concise Definition of Done and a measurable business or UX outcome, without promising a result unsupported by data.
Documentation generator
Create a tested, client-ready outcome for documentation generator.
Act as a senior WordPress solution architect and Kadence Theme/Kadence Blocks/WPCode specialist. TASK: Documentation generator. PROJECT INPUTS - Website type and business goal: [SITE TYPE + GOAL] - Audience, locale and key conversion: [AUDIENCE + LOCALE + CTA] - Current stack (WordPress/PHP, Kadence Theme, Kadence Blocks, WPCode, plugins): [VERIFIED VERSIONS] - Current page, screenshot, issue or reference: [URL OR SANITIZED DETAILS] - Constraints (budget, editor skill, hosting, launch date): [CONSTRAINTS] - Existing content, brand styles and approved data: [SOURCE MATERIAL] SPECIFIC OBJECTIVE Develop a practical, results-oriented solution for documentation generator in the context of this website. Treat generated code as untrusted until inspected, staged and tested. Explain what should be done with Kadence Theme settings, what should be built with Kadence Blocks, and when WPCode is warranted. Do not invent installed plugin capabilities or pretend you accessed the live site. DELIVER EXACTLY 1. A task-specific implementation blueprint for “Documentation generator” with exact WordPress/Kadence navigation or WPCode placement when relevant. 2. An ordered action checklist with dependencies and who owns each action. 3. Copy-ready artifacts where relevant (block hierarchy, settings matrix, sample copy, scoped CSS, PHP or vanilla JavaScript), with code fences and placement instructions. 4. Desktop/tablet/mobile acceptance tests, accessibility and security checks relevant to the task. 5. Failure cases, troubleshooting clues, rollback steps and final client-facing completion criteria. IMPLEMENTATION SAFETY Flag assumptions; favor native block controls over custom code; do not hardcode credentials or private data. For PHP/JS/CSS, provide exact location, activation scope, prerequisite checks, staging test, and undo method. If a plugin or version-specific behavior is uncertain, say what to verify first. Finish with a concise Definition of Done and a measurable business or UX outcome, without promising a result unsupported by data.
AI output hallucination audit
Create a tested, client-ready outcome for ai output hallucination audit.
Act as a senior WordPress solution architect and Kadence Theme/Kadence Blocks/WPCode specialist. TASK: AI output hallucination audit. PROJECT INPUTS - Website type and business goal: [SITE TYPE + GOAL] - Audience, locale and key conversion: [AUDIENCE + LOCALE + CTA] - Current stack (WordPress/PHP, Kadence Theme, Kadence Blocks, WPCode, plugins): [VERIFIED VERSIONS] - Current page, screenshot, issue or reference: [URL OR SANITIZED DETAILS] - Constraints (budget, editor skill, hosting, launch date): [CONSTRAINTS] - Existing content, brand styles and approved data: [SOURCE MATERIAL] SPECIFIC OBJECTIVE Develop a practical, results-oriented solution for ai output hallucination audit in the context of this website. Treat generated code as untrusted until inspected, staged and tested. Explain what should be done with Kadence Theme settings, what should be built with Kadence Blocks, and when WPCode is warranted. Do not invent installed plugin capabilities or pretend you accessed the live site. DELIVER EXACTLY 1. A task-specific implementation blueprint for “AI output hallucination audit” with exact WordPress/Kadence navigation or WPCode placement when relevant. 2. An ordered action checklist with dependencies and who owns each action. 3. Copy-ready artifacts where relevant (block hierarchy, settings matrix, sample copy, scoped CSS, PHP or vanilla JavaScript), with code fences and placement instructions. 4. Desktop/tablet/mobile acceptance tests, accessibility and security checks relevant to the task. 5. Failure cases, troubleshooting clues, rollback steps and final client-facing completion criteria. IMPLEMENTATION SAFETY Flag assumptions; favor native block controls over custom code; do not hardcode credentials or private data. For PHP/JS/CSS, provide exact location, activation scope, prerequisite checks, staging test, and undo method. If a plugin or version-specific behavior is uncertain, say what to verify first. Finish with a concise Definition of Done and a measurable business or UX outcome, without promising a result unsupported by data.
26. Client Delivery, Portfolio & Remote Career
Fixed-scope proposal draft
Create a tested, client-ready outcome for fixed-scope proposal draft.
Act as a senior WordPress solution architect and Kadence Theme/Kadence Blocks/WPCode specialist. TASK: Fixed-scope proposal draft. PROJECT INPUTS - Website type and business goal: [SITE TYPE + GOAL] - Audience, locale and key conversion: [AUDIENCE + LOCALE + CTA] - Current stack (WordPress/PHP, Kadence Theme, Kadence Blocks, WPCode, plugins): [VERIFIED VERSIONS] - Current page, screenshot, issue or reference: [URL OR SANITIZED DETAILS] - Constraints (budget, editor skill, hosting, launch date): [CONSTRAINTS] - Existing content, brand styles and approved data: [SOURCE MATERIAL] SPECIFIC OBJECTIVE Develop a practical, results-oriented solution for fixed-scope proposal draft in the context of this website. Separate demo project outcomes from verified client results and prohibit fabricated metrics. Explain what should be done with Kadence Theme settings, what should be built with Kadence Blocks, and when WPCode is warranted. Do not invent installed plugin capabilities or pretend you accessed the live site. DELIVER EXACTLY 1. A task-specific implementation blueprint for “Fixed-scope proposal draft” with exact WordPress/Kadence navigation or WPCode placement when relevant. 2. An ordered action checklist with dependencies and who owns each action. 3. Copy-ready artifacts where relevant (block hierarchy, settings matrix, sample copy, scoped CSS, PHP or vanilla JavaScript), with code fences and placement instructions. 4. Desktop/tablet/mobile acceptance tests, accessibility and security checks relevant to the task. 5. Failure cases, troubleshooting clues, rollback steps and final client-facing completion criteria. IMPLEMENTATION SAFETY Flag assumptions; favor native block controls over custom code; do not hardcode credentials or private data. For PHP/JS/CSS, provide exact location, activation scope, prerequisite checks, staging test, and undo method. If a plugin or version-specific behavior is uncertain, say what to verify first. Finish with a concise Definition of Done and a measurable business or UX outcome, without promising a result unsupported by data.
Discovery workshop agenda
Create a tested, client-ready outcome for discovery workshop agenda.
Act as a senior WordPress solution architect and Kadence Theme/Kadence Blocks/WPCode specialist. TASK: Discovery workshop agenda. PROJECT INPUTS - Website type and business goal: [SITE TYPE + GOAL] - Audience, locale and key conversion: [AUDIENCE + LOCALE + CTA] - Current stack (WordPress/PHP, Kadence Theme, Kadence Blocks, WPCode, plugins): [VERIFIED VERSIONS] - Current page, screenshot, issue or reference: [URL OR SANITIZED DETAILS] - Constraints (budget, editor skill, hosting, launch date): [CONSTRAINTS] - Existing content, brand styles and approved data: [SOURCE MATERIAL] SPECIFIC OBJECTIVE Develop a practical, results-oriented solution for discovery workshop agenda in the context of this website. Separate demo project outcomes from verified client results and prohibit fabricated metrics. Explain what should be done with Kadence Theme settings, what should be built with Kadence Blocks, and when WPCode is warranted. Do not invent installed plugin capabilities or pretend you accessed the live site. DELIVER EXACTLY 1. A task-specific implementation blueprint for “Discovery workshop agenda” with exact WordPress/Kadence navigation or WPCode placement when relevant. 2. An ordered action checklist with dependencies and who owns each action. 3. Copy-ready artifacts where relevant (block hierarchy, settings matrix, sample copy, scoped CSS, PHP or vanilla JavaScript), with code fences and placement instructions. 4. Desktop/tablet/mobile acceptance tests, accessibility and security checks relevant to the task. 5. Failure cases, troubleshooting clues, rollback steps and final client-facing completion criteria. IMPLEMENTATION SAFETY Flag assumptions; favor native block controls over custom code; do not hardcode credentials or private data. For PHP/JS/CSS, provide exact location, activation scope, prerequisite checks, staging test, and undo method. If a plugin or version-specific behavior is uncertain, say what to verify first. Finish with a concise Definition of Done and a measurable business or UX outcome, without promising a result unsupported by data.
Estimate and milestone plan
Create a tested, client-ready outcome for estimate and milestone plan.
Act as a senior WordPress solution architect and Kadence Theme/Kadence Blocks/WPCode specialist. TASK: Estimate and milestone plan. PROJECT INPUTS - Website type and business goal: [SITE TYPE + GOAL] - Audience, locale and key conversion: [AUDIENCE + LOCALE + CTA] - Current stack (WordPress/PHP, Kadence Theme, Kadence Blocks, WPCode, plugins): [VERIFIED VERSIONS] - Current page, screenshot, issue or reference: [URL OR SANITIZED DETAILS] - Constraints (budget, editor skill, hosting, launch date): [CONSTRAINTS] - Existing content, brand styles and approved data: [SOURCE MATERIAL] SPECIFIC OBJECTIVE Develop a practical, results-oriented solution for estimate and milestone plan in the context of this website. Separate demo project outcomes from verified client results and prohibit fabricated metrics. Explain what should be done with Kadence Theme settings, what should be built with Kadence Blocks, and when WPCode is warranted. Do not invent installed plugin capabilities or pretend you accessed the live site. DELIVER EXACTLY 1. A task-specific implementation blueprint for “Estimate and milestone plan” with exact WordPress/Kadence navigation or WPCode placement when relevant. 2. An ordered action checklist with dependencies and who owns each action. 3. Copy-ready artifacts where relevant (block hierarchy, settings matrix, sample copy, scoped CSS, PHP or vanilla JavaScript), with code fences and placement instructions. 4. Desktop/tablet/mobile acceptance tests, accessibility and security checks relevant to the task. 5. Failure cases, troubleshooting clues, rollback steps and final client-facing completion criteria. IMPLEMENTATION SAFETY Flag assumptions; favor native block controls over custom code; do not hardcode credentials or private data. For PHP/JS/CSS, provide exact location, activation scope, prerequisite checks, staging test, and undo method. If a plugin or version-specific behavior is uncertain, say what to verify first. Finish with a concise Definition of Done and a measurable business or UX outcome, without promising a result unsupported by data.
Acceptance testing script
Create a tested, client-ready outcome for acceptance testing script.
Act as a senior WordPress solution architect and Kadence Theme/Kadence Blocks/WPCode specialist. TASK: Acceptance testing script. PROJECT INPUTS - Website type and business goal: [SITE TYPE + GOAL] - Audience, locale and key conversion: [AUDIENCE + LOCALE + CTA] - Current stack (WordPress/PHP, Kadence Theme, Kadence Blocks, WPCode, plugins): [VERIFIED VERSIONS] - Current page, screenshot, issue or reference: [URL OR SANITIZED DETAILS] - Constraints (budget, editor skill, hosting, launch date): [CONSTRAINTS] - Existing content, brand styles and approved data: [SOURCE MATERIAL] SPECIFIC OBJECTIVE Develop a practical, results-oriented solution for acceptance testing script in the context of this website. Separate demo project outcomes from verified client results and prohibit fabricated metrics. Explain what should be done with Kadence Theme settings, what should be built with Kadence Blocks, and when WPCode is warranted. Do not invent installed plugin capabilities or pretend you accessed the live site. DELIVER EXACTLY 1. A task-specific implementation blueprint for “Acceptance testing script” with exact WordPress/Kadence navigation or WPCode placement when relevant. 2. An ordered action checklist with dependencies and who owns each action. 3. Copy-ready artifacts where relevant (block hierarchy, settings matrix, sample copy, scoped CSS, PHP or vanilla JavaScript), with code fences and placement instructions. 4. Desktop/tablet/mobile acceptance tests, accessibility and security checks relevant to the task. 5. Failure cases, troubleshooting clues, rollback steps and final client-facing completion criteria. IMPLEMENTATION SAFETY Flag assumptions; favor native block controls over custom code; do not hardcode credentials or private data. For PHP/JS/CSS, provide exact location, activation scope, prerequisite checks, staging test, and undo method. If a plugin or version-specific behavior is uncertain, say what to verify first. Finish with a concise Definition of Done and a measurable business or UX outcome, without promising a result unsupported by data.
Client handoff documentation
Create a tested, client-ready outcome for client handoff documentation.
Act as a senior WordPress solution architect and Kadence Theme/Kadence Blocks/WPCode specialist. TASK: Client handoff documentation. PROJECT INPUTS - Website type and business goal: [SITE TYPE + GOAL] - Audience, locale and key conversion: [AUDIENCE + LOCALE + CTA] - Current stack (WordPress/PHP, Kadence Theme, Kadence Blocks, WPCode, plugins): [VERIFIED VERSIONS] - Current page, screenshot, issue or reference: [URL OR SANITIZED DETAILS] - Constraints (budget, editor skill, hosting, launch date): [CONSTRAINTS] - Existing content, brand styles and approved data: [SOURCE MATERIAL] SPECIFIC OBJECTIVE Develop a practical, results-oriented solution for client handoff documentation in the context of this website. Separate demo project outcomes from verified client results and prohibit fabricated metrics. Explain what should be done with Kadence Theme settings, what should be built with Kadence Blocks, and when WPCode is warranted. Do not invent installed plugin capabilities or pretend you accessed the live site. DELIVER EXACTLY 1. A task-specific implementation blueprint for “Client handoff documentation” with exact WordPress/Kadence navigation or WPCode placement when relevant. 2. An ordered action checklist with dependencies and who owns each action. 3. Copy-ready artifacts where relevant (block hierarchy, settings matrix, sample copy, scoped CSS, PHP or vanilla JavaScript), with code fences and placement instructions. 4. Desktop/tablet/mobile acceptance tests, accessibility and security checks relevant to the task. 5. Failure cases, troubleshooting clues, rollback steps and final client-facing completion criteria. IMPLEMENTATION SAFETY Flag assumptions; favor native block controls over custom code; do not hardcode credentials or private data. For PHP/JS/CSS, provide exact location, activation scope, prerequisite checks, staging test, and undo method. If a plugin or version-specific behavior is uncertain, say what to verify first. Finish with a concise Definition of Done and a measurable business or UX outcome, without promising a result unsupported by data.
Maintenance offer design
Create a tested, client-ready outcome for maintenance offer design.
Act as a senior WordPress solution architect and Kadence Theme/Kadence Blocks/WPCode specialist. TASK: Maintenance offer design. PROJECT INPUTS - Website type and business goal: [SITE TYPE + GOAL] - Audience, locale and key conversion: [AUDIENCE + LOCALE + CTA] - Current stack (WordPress/PHP, Kadence Theme, Kadence Blocks, WPCode, plugins): [VERIFIED VERSIONS] - Current page, screenshot, issue or reference: [URL OR SANITIZED DETAILS] - Constraints (budget, editor skill, hosting, launch date): [CONSTRAINTS] - Existing content, brand styles and approved data: [SOURCE MATERIAL] SPECIFIC OBJECTIVE Develop a practical, results-oriented solution for maintenance offer design in the context of this website. Separate demo project outcomes from verified client results and prohibit fabricated metrics. Explain what should be done with Kadence Theme settings, what should be built with Kadence Blocks, and when WPCode is warranted. Do not invent installed plugin capabilities or pretend you accessed the live site. DELIVER EXACTLY 1. A task-specific implementation blueprint for “Maintenance offer design” with exact WordPress/Kadence navigation or WPCode placement when relevant. 2. An ordered action checklist with dependencies and who owns each action. 3. Copy-ready artifacts where relevant (block hierarchy, settings matrix, sample copy, scoped CSS, PHP or vanilla JavaScript), with code fences and placement instructions. 4. Desktop/tablet/mobile acceptance tests, accessibility and security checks relevant to the task. 5. Failure cases, troubleshooting clues, rollback steps and final client-facing completion criteria. IMPLEMENTATION SAFETY Flag assumptions; favor native block controls over custom code; do not hardcode credentials or private data. For PHP/JS/CSS, provide exact location, activation scope, prerequisite checks, staging test, and undo method. If a plugin or version-specific behavior is uncertain, say what to verify first. Finish with a concise Definition of Done and a measurable business or UX outcome, without promising a result unsupported by data.
Case study narrative
Create a tested, client-ready outcome for case study narrative.
Act as a senior WordPress solution architect and Kadence Theme/Kadence Blocks/WPCode specialist. TASK: Case study narrative. PROJECT INPUTS - Website type and business goal: [SITE TYPE + GOAL] - Audience, locale and key conversion: [AUDIENCE + LOCALE + CTA] - Current stack (WordPress/PHP, Kadence Theme, Kadence Blocks, WPCode, plugins): [VERIFIED VERSIONS] - Current page, screenshot, issue or reference: [URL OR SANITIZED DETAILS] - Constraints (budget, editor skill, hosting, launch date): [CONSTRAINTS] - Existing content, brand styles and approved data: [SOURCE MATERIAL] SPECIFIC OBJECTIVE Develop a practical, results-oriented solution for case study narrative in the context of this website. Separate demo project outcomes from verified client results and prohibit fabricated metrics. Explain what should be done with Kadence Theme settings, what should be built with Kadence Blocks, and when WPCode is warranted. Do not invent installed plugin capabilities or pretend you accessed the live site. DELIVER EXACTLY 1. A task-specific implementation blueprint for “Case study narrative” with exact WordPress/Kadence navigation or WPCode placement when relevant. 2. An ordered action checklist with dependencies and who owns each action. 3. Copy-ready artifacts where relevant (block hierarchy, settings matrix, sample copy, scoped CSS, PHP or vanilla JavaScript), with code fences and placement instructions. 4. Desktop/tablet/mobile acceptance tests, accessibility and security checks relevant to the task. 5. Failure cases, troubleshooting clues, rollback steps and final client-facing completion criteria. IMPLEMENTATION SAFETY Flag assumptions; favor native block controls over custom code; do not hardcode credentials or private data. For PHP/JS/CSS, provide exact location, activation scope, prerequisite checks, staging test, and undo method. If a plugin or version-specific behavior is uncertain, say what to verify first. Finish with a concise Definition of Done and a measurable business or UX outcome, without promising a result unsupported by data.
Before-after portfolio exhibit
Create a tested, client-ready outcome for before-after portfolio exhibit.
Act as a senior WordPress solution architect and Kadence Theme/Kadence Blocks/WPCode specialist. TASK: Before-after portfolio exhibit. PROJECT INPUTS - Website type and business goal: [SITE TYPE + GOAL] - Audience, locale and key conversion: [AUDIENCE + LOCALE + CTA] - Current stack (WordPress/PHP, Kadence Theme, Kadence Blocks, WPCode, plugins): [VERIFIED VERSIONS] - Current page, screenshot, issue or reference: [URL OR SANITIZED DETAILS] - Constraints (budget, editor skill, hosting, launch date): [CONSTRAINTS] - Existing content, brand styles and approved data: [SOURCE MATERIAL] SPECIFIC OBJECTIVE Develop a practical, results-oriented solution for before-after portfolio exhibit in the context of this website. Separate demo project outcomes from verified client results and prohibit fabricated metrics. Explain what should be done with Kadence Theme settings, what should be built with Kadence Blocks, and when WPCode is warranted. Do not invent installed plugin capabilities or pretend you accessed the live site. DELIVER EXACTLY 1. A task-specific implementation blueprint for “Before-after portfolio exhibit” with exact WordPress/Kadence navigation or WPCode placement when relevant. 2. An ordered action checklist with dependencies and who owns each action. 3. Copy-ready artifacts where relevant (block hierarchy, settings matrix, sample copy, scoped CSS, PHP or vanilla JavaScript), with code fences and placement instructions. 4. Desktop/tablet/mobile acceptance tests, accessibility and security checks relevant to the task. 5. Failure cases, troubleshooting clues, rollback steps and final client-facing completion criteria. IMPLEMENTATION SAFETY Flag assumptions; favor native block controls over custom code; do not hardcode credentials or private data. For PHP/JS/CSS, provide exact location, activation scope, prerequisite checks, staging test, and undo method. If a plugin or version-specific behavior is uncertain, say what to verify first. Finish with a concise Definition of Done and a measurable business or UX outcome, without promising a result unsupported by data.
Remote interview project walkthrough
Create a tested, client-ready outcome for remote interview project walkthrough.
Act as a senior WordPress solution architect and Kadence Theme/Kadence Blocks/WPCode specialist. TASK: Remote interview project walkthrough. PROJECT INPUTS - Website type and business goal: [SITE TYPE + GOAL] - Audience, locale and key conversion: [AUDIENCE + LOCALE + CTA] - Current stack (WordPress/PHP, Kadence Theme, Kadence Blocks, WPCode, plugins): [VERIFIED VERSIONS] - Current page, screenshot, issue or reference: [URL OR SANITIZED DETAILS] - Constraints (budget, editor skill, hosting, launch date): [CONSTRAINTS] - Existing content, brand styles and approved data: [SOURCE MATERIAL] SPECIFIC OBJECTIVE Develop a practical, results-oriented solution for remote interview project walkthrough in the context of this website. Separate demo project outcomes from verified client results and prohibit fabricated metrics. Explain what should be done with Kadence Theme settings, what should be built with Kadence Blocks, and when WPCode is warranted. Do not invent installed plugin capabilities or pretend you accessed the live site. DELIVER EXACTLY 1. A task-specific implementation blueprint for “Remote interview project walkthrough” with exact WordPress/Kadence navigation or WPCode placement when relevant. 2. An ordered action checklist with dependencies and who owns each action. 3. Copy-ready artifacts where relevant (block hierarchy, settings matrix, sample copy, scoped CSS, PHP or vanilla JavaScript), with code fences and placement instructions. 4. Desktop/tablet/mobile acceptance tests, accessibility and security checks relevant to the task. 5. Failure cases, troubleshooting clues, rollback steps and final client-facing completion criteria. IMPLEMENTATION SAFETY Flag assumptions; favor native block controls over custom code; do not hardcode credentials or private data. For PHP/JS/CSS, provide exact location, activation scope, prerequisite checks, staging test, and undo method. If a plugin or version-specific behavior is uncertain, say what to verify first. Finish with a concise Definition of Done and a measurable business or UX outcome, without promising a result unsupported by data.
Technical skills evidence matrix
Create a tested, client-ready outcome for technical skills evidence matrix.
Act as a senior WordPress solution architect and Kadence Theme/Kadence Blocks/WPCode specialist. TASK: Technical skills evidence matrix. PROJECT INPUTS - Website type and business goal: [SITE TYPE + GOAL] - Audience, locale and key conversion: [AUDIENCE + LOCALE + CTA] - Current stack (WordPress/PHP, Kadence Theme, Kadence Blocks, WPCode, plugins): [VERIFIED VERSIONS] - Current page, screenshot, issue or reference: [URL OR SANITIZED DETAILS] - Constraints (budget, editor skill, hosting, launch date): [CONSTRAINTS] - Existing content, brand styles and approved data: [SOURCE MATERIAL] SPECIFIC OBJECTIVE Develop a practical, results-oriented solution for technical skills evidence matrix in the context of this website. Separate demo project outcomes from verified client results and prohibit fabricated metrics. Explain what should be done with Kadence Theme settings, what should be built with Kadence Blocks, and when WPCode is warranted. Do not invent installed plugin capabilities or pretend you accessed the live site. DELIVER EXACTLY 1. A task-specific implementation blueprint for “Technical skills evidence matrix” with exact WordPress/Kadence navigation or WPCode placement when relevant. 2. An ordered action checklist with dependencies and who owns each action. 3. Copy-ready artifacts where relevant (block hierarchy, settings matrix, sample copy, scoped CSS, PHP or vanilla JavaScript), with code fences and placement instructions. 4. Desktop/tablet/mobile acceptance tests, accessibility and security checks relevant to the task. 5. Failure cases, troubleshooting clues, rollback steps and final client-facing completion criteria. IMPLEMENTATION SAFETY Flag assumptions; favor native block controls over custom code; do not hardcode credentials or private data. For PHP/JS/CSS, provide exact location, activation scope, prerequisite checks, staging test, and undo method. If a plugin or version-specific behavior is uncertain, say what to verify first. Finish with a concise Definition of Done and a measurable business or UX outcome, without promising a result unsupported by data.
End-to-end sample workflow
Example: Build a local contractor site with a homepage, five service pages, a contact form and performance targets. Start with KWP-001, KWP-031 and KWP-051; then use KWP-111 for form mapping, KWP-121 to decide whether WPCode is needed, KWP-171 for SEO structure, KWP-181 for speed, KWP-201 for security, KWP-211 for QA and KWP-231 for launch. Keep a decision log and obtain client approval before production deployment.
Portfolio proof for remote WordPress jobs
Show your site brief, Kadence global design tokens, page screenshots at three widths, native block choices, annotated WPCode snippet (if necessary), accessibility checks, baseline/post-build performance observations, redacted bug tickets and handoff documentation. Identify practice projects honestly, never as paid client work unless verified.
Frequently asked questions
Are KWP IDs executable WordPress shortcodes?
No. They identify prompts in this library. Only a separately implemented and registered shortcode runs in WordPress.
Does every customization require WPCode?
No. Prefer Kadence Theme and Kadence Blocks native settings. WPCode is useful for scoped custom PHP, CSS, JavaScript and insertions when a clear requirement justifies it.
Why would search or copy not work after pasting into WordPress?
Some WordPress roles, security filters and optimization plugins strip, delay or block inline JavaScript. Use the included separate JavaScript file via an appropriate script-management setup, and avoid duplicate initialization. Test on the live page.
Does this guarantee SEO rankings or website performance?
No. It supplies a repeatable implementation and verification process; outcomes depend on content, hosting, data, configuration and testing.