Prompt Library

A copy-paste scenario prompt that turns a rough outline into a structured, publish-ready WordPress post. Includes a built-in self-check before it hands back a draft.

Turns a technical task into a numbered tutorial that verifies the reader is still on track after every major step and flags destructive actions before, not after, they happen.

Drafts a landing-page hero (headline, subhead, CTA) that answers the visitor's first question in under 5 seconds, matched to what the page actually delivers so the click doesn't bounce.

A scenario-based on-page SEO audit that diagnoses whether a stuck post has a structural intent mismatch or just a content gap, then fixes only what's broken.

Builds a "common mistakes" listicle from real observed patterns, explains the reasonable-sounding logic that leads people into each one, and calls out the one "mistake" that's actually fine in specific situations.

Extracts the real insight from a messy, unedited transcript (fillers, tangents, misattributed speakers) into a structured post, not a straight clean-up of the raw text.

A step-by-step diagnostic prompt that separates algorithm-driven ranking loss from technical breakage, competitor gains, or seasonal noise before recommending any fix.

Pulls a different angle for each platform from one published post (LinkedIn, X, Instagram) instead of posting the same caption everywhere, while keeping enough back that people still have to click through.

A prompt that compares what top-ranking competitors cover against your own site to find genuine content gaps, not just topics you're missing arbitrarily.

A prompt that separates a genuinely weak title/meta from an unavoidable CTR ceiling caused by SERP features stealing clicks above the organic result.

Builds an X vs Y comparison that commits to a verdict for specific use cases instead of hedging with "it depends," while flagging price and feature claims that go stale fast.

A scenario prompt for replying publicly to a low-star review that acknowledges the real issue, states the true status plainly, and writes for the future customers reading it, not just the reviewer.

Leads with the single most newsworthy finding from original survey data, and refuses to state a sub-segment result with full confidence when that segment's sample size is too small to support it.

A scenario prompt for responding to a vulnerability disclosure with urgency and discretion, before a public patch exists.

A prompt for planning an H1-H3 outline for a new landing page that serves both scanning readers and search intent, not just keyword placement.

A scenario prompt for talking a frustrated customer down from a chargeback by fixing the actual grievance, not by arguing the dispute.

Splits a broad topic into a pillar overview plus linked cluster articles, built to avoid both an unreadable mega-post and keyword cannibalization against posts that already exist.

A site-down triage scenario that reasons through load-order bugs, gives an immediate mitigation separate from the permanent fix, and flags whether the bug pattern will recur elsewhere.

A scenario-based content brief prompt that gives a freelancer everything needed to hit search intent on the first draft, including what NOT to cover.

A scenario prompt for the follow-up email after an outage is resolved, once you know the real scope and can commit to a real number.

A CSV export scenario reasoning through which memory limit is actually in effect, query batching, and the hidden $wpdb query log that quietly eats memory in debug mode.

Matches each tool in a roundup to a specific reader use case instead of an undifferentiated ranked list, and flags any tool whose ownership or quality has recently changed since older praise may be stale.

A scenario prompt for calming an angry customer over a delayed order without over-promising a new delivery date you can't guarantee.

A scenario prompt that writes benefits-first product copy calibrated to the exact price tier, and pre-empts the one objection that actually loses the sale.

A register_rest_route scenario that reasons through the gap between is_user_logged_in and real capability checks, plus param validation and rate-limit judgment calls.

Reshapes a published post into a scannable newsletter email with its own hook and CTA, instead of just copy-pasting the article into an email.

A scenario-based prompt for organizing existing posts into a hub-and-spoke topic cluster, including how to handle posts that don't cleanly belong anywhere.

A scenario prompt for planning a Black Friday landing page and discount structure that protects margin on already-discounted items and avoids fake urgency.

Translates a security advisory (CVE, affected versions, technical mechanism) into plain language for non-technical site owners without softening the severity or losing any exact technical facts.

A scenario prompt for reaching out when a customer starts the cancellation flow, addressing their stated reason directly instead of a generic save offer.

A triage prompt for a checkout stuck on Processing Payment right after a Stripe gateway plugin update, covering the webhook and API key traps that cause silent order failures.

A prompt for drafting genuinely differentiated location page copy at scale, built to avoid the template-swap pattern Google treats as doorway pages.

A triage prompt for customers receiving 2-3 copies of the same order confirmation, walking through the SMTP, webhook, and status-flapping causes rather than just disabling the email.

A real 8-second query scenario on a 50k-row postmeta join, reasoning through indexes, meta_query alternatives, and when to graduate to a custom lookup table.

Defines WordPress jargon in plain language a true beginner would use, and adds explicit "not to be confused with" callouts for the term pairs beginners most often mix up, which a plain A-Z glossary usually buries.

A prompt for drafting FAQPage schema that mirrors real visible questions on a service page, structured to survive Google's stricter FAQ rich result eligibility rules.

A scenario prompt for announcing a breaking change in a major release, with the migration path stated up front, not buried below the fold.

A full register_block_type walkthrough that covers block.json, edit/save components, server-side rendering, and the escaping judgment call most tutorials skip.

A scenario prompt for declining a refund that's past your policy window without sounding robotic, while still offering a real alternative.

A 3-email scenario prompt for recovering an abandoned $220 cart, escalating from a reminder to a real reason to come back, without training shoppers to always wait for a discount.

Works backward from key commerce dates to a 6-week content calendar, sequencing publish deadlines around SEO lead time and design turnaround instead of spacing posts evenly by week.

A prompt that inspects a page's actual content before prescribing FAQ, Product, or Review schema, since applying the wrong schema type risks a manual spam action.

A contact-request form scenario reasoning through nonce lifetime for logged-out visitors, combining nonces with capability checks, and safe redirect handling.

A reusable macro for the "invalid license key" ticket, covering the handful of real causes before assuming the key itself is wrong.

A diagnostic prompt for a product whose stock count won't go down after sales, walking through the settings, order-status, and race-condition causes in the order a support engineer should check them.

A scenario prompt that untangles a real Google Docs paste-in, with mismatched headings, broken tables, and inherited styles, into clean block markup without touching a single word.

Section-by-section audit process for updating a ranking-but-stale pillar post, built to preserve what still works and flag cosmetic "fake freshness" versus a genuine update.

A scenario prompt for a status page update that's honest about scope and next steps without speculating on a cause you haven't confirmed.

A triage scenario for a broken AJAX handler, reasoning through nonce mismatches, missing hook prefixes, and security-plugin interference before touching application code.

A prompt that works through Google's actual indexing decision tree (crawlability, quality, canonicalization) instead of jumping straight to "request indexing again."

A scenario prompt that builds an end-of-page CTA banner from a Group, Heading, Paragraph, and Buttons block, using theme palette colors so it survives a theme switch.

A diagnostic prompt for wrong tax amounts across US and Canadian orders, covering origin-vs-destination rules, tax class misassignment, and mixed digital/physical carts.

A duplicate-order-confirmation-email scenario reasoning through revision saves, double-loaded plugin files, and recursive save_post calls before blaming a race condition.

Validates that a topic genuinely needs a multi-part series, maps what later parts assume readers already learned, and plans for a reader landing on part 3 first via search.

A scenario prompt for a 3-email onboarding sequence that gets a new premium license holder to their first real result, not just a features tour.

A prompt for drafting FAQ answers phrased the way people actually speak to a voice assistant, structured to be extractable as a single spoken answer.

A scenario-driven prompt for mapping old URLs to new ones during a replatform or restructure, including how to handle orphaned and merged pages instead of leaving them 404.

A scenario prompt that builds a full-width hero for a product launch page from Cover, Heading, Paragraph, and Buttons blocks, with no custom HTML and no plugin blocks.

A scenario prompt for writing cart-page upsell and cross-sell copy for a $58 cart that nudges toward free shipping honestly, and only recommends items that actually match what's already in the cart.

A triage scenario for the frustrating case where the site is blank, WP_DEBUG is off, and the host's error log has nothing useful in it.

Groups the same handful of paraphrased support questions into one canonical help doc, ordered by how often and how badly they block the customer, not just alphabetically.

A reusable macro for diagnosing whether another plugin or theme is the real cause of a bug reported against yours, with a safe path for live sites.

A scenario prompt for an image that's illustrating a specific point, not just decoration. The alt text has to carry that meaning for a screen reader user, with SEO second.

A scenario prompt that structures a mid-content email signup section with core blocks, addressing the gap that core WordPress has no working signup form of its own and needs a plugin's embed handled carefully.

A prompt that separates genuine ranking-relevant CWV problems from noise in PageSpeed reports, and prioritizes fixes by realistic dev effort.

A scenario prompt for writing a leggings size guide built around body measurements and fit notes instead of just S/M/L labels, aimed at cutting size-related returns.

A front-end resume upload scenario covering real MIME sniffing versus extension checks, execution-proofing the uploads directory, and safe filename handling.

Busts myths people in a niche actually believe (pulled from real support tickets or forum threads), and handles the half-true ones with nuance a strict myth/fact binary would flatten.

A scenario prompt for the text layered on an Open Graph share image, distinct from the page title, tuned for how it actually gets cropped and truncated per platform.

A scenario prompt that turns eight support questions into native accordion entries with the Details/Summary block, flagging where it differs from a true single-open accordion.

A prompt for triaging a Google Search Console manual action message and building a realistic, honest reconsideration plan instead of a quick surface-level cleanup.

A scenario prompt for correcting a specific factual mistake in a public review without sounding defensive or picking a fight.

A scenario prompt that turns three client quotes into properly marked-up Quote blocks with avatars and star ratings, keeping the semantic blockquote/cite structure intact.

Drafts a guest post pitch that references the target site's actual recent content and offers concrete headline options, instead of a generic mass-pitch email editors delete on sight.

A scenario prompt for turning a raw, messy webinar transcript into a structured blog post, including how to handle a moment where a speaker misspeaks a number and corrects it later.

A prompt that validates schema implementation against Google's actual eligibility rules before assuming the markup itself is broken.

A scenario prompt for timing review requests to actual product usage rather than delivery date, and routing recent returns or complaints away from the request instead of risking a public bad review.

A custom-table migration scenario reasoning through dbDelta quirks, multisite network activation, and version-gated upgrades so activation never re-runs destructively.

An internal, non-customer-facing prompt for summarizing a ticket into something a developer can act on without re-reading the whole thread.

An event-details meta box scenario covering nonce and autosave guards on save, per-field sanitization, and avoiding the classic recursive save_post loop.

Builds an About page that leads with a client-relevant proof point instead of a generic "passionate about WordPress" line, and refuses to invent superlatives you can't back up.

Tightens a loose, real interview into a polished Q&A while keeping the subject's actual voice, and handles the question they dodged honestly instead of writing them a cleaner answer they never gave.

A scenario prompt that builds a static side-by-side before/after image layout for a renovation services page, since core Gutenberg has no built-in slider block and needs text labels that don't rely on color alone.

A scenario prompt for a tutorial video's title, description, and chapter timestamps, tuned so the description doesn't compete with the blog page it's embedded on for the same keyword.

A prompt that decides whether two competing posts should be merged, differentiated, or left alone, based on actual intent overlap rather than shared keywords alone.

A scenario prompt for a back-in-stock email for a specific shoe size, including the judgment call on holding back a mass blast when restocked quantity is too low to serve the whole waitlist.

A scenario prompt for a home renovation before/after gallery, handling which photo is which for screen readers and the honesty problem when the two shots were taken from different angles.

A scenario prompt that lays out three subscription tiers side by side using Columns and Group blocks instead of the Table block, since Table can't hold buttons or highlight a recommended plan.

A prompt that triages a list of old posts by decay pattern and traffic value to build a realistic refresh schedule instead of refreshing everything on a fixed cadence.

A scenario prompt for handling a right-to-erasure request correctly, including the parts of a customer's data you legally can't delete.

A scenario prompt for describing a 3-item skincare starter bundle that justifies the bundle price against buying each item alone, and sequences the routine instead of just listing contents.

A scenario prompt that converts a described VIP-customer workflow into an implementation-ready trigger/condition/action recipe, resolving the ambiguities the plain description leaves open.

A scenario prompt that converts a described five-email onboarding drip into a recipe with exact timing, engagement branching, and unsubscribe-mid-sequence handling.

Builds a customer case study from messy call notes, separating verbatim quotes from paraphrase and speculation, and refusing to round an uncertain number into a cleaner one.

A scenario prompt for extracting a usable bug report from a customer who can only describe the symptom, not the trigger.

A scenario prompt for captioning a multi-shot product gallery (hero, detail, lifestyle, packaging) without repeating the same sentence six times or stuffing keywords into shots that don't need them.

A scenario prompt that converts a described backup-failure-alert workflow into a recipe, covering silent failures, partial backups, and repeated-failure escalation.

A daily-digest-email scenario explaining why pseudo-cron misses schedules on quiet sites, and how to pair a real server cron trigger with an overlap-safe lock.

Filters a scattered Slack thread (banter, reactions, disagreeing angles) into an actionable brief for a writer, flagging unresolved disagreements instead of silently picking a side.

A scenario prompt that converts a described contact-form-to-CRM workflow into an implementation-ready recipe, resolving spam, routing, and ownership-assignment ambiguity.

A scenario prompt that lays out a twelve-photo portfolio gallery edge to edge, covering per-image alt text, caption structure, and the theme support required for a true full-bleed gallery.

A scenario-based prompt for triaging a Screaming Frog duplicate title export by cause (templating bug vs. genuine content overlap) before rewriting anything.

A scenario prompt for winning back customers who bought recurring-use pet food 120+ days ago and stopped, using purchase history instead of a generic discount blast.

An "SEO Priority" document panel scenario covering register_post_meta auth callbacks, useEntityProp wiring, and the classic panel-not-showing REST exposure mistake.

Finds the actual story inside a raw benchmark spreadsheet instead of narrating every row, while flagging outlier data points and sample-size limitations before they get written up as settled fact.

A scenario prompt for a line chart with a real anomaly in the data, and the judgment call of whether the alt text should flag that the spike isn't what it looks like.

A prompt that reviews a robots.txt line by line for rules that are silently wasting or restricting crawl budget on a large site.

A scenario prompt for a pre-order gadget listing that sets an honest estimated ship date and a clear policy for what happens if the date slips.

A scenario prompt that turns a described newsletter-signup-to-CRM workflow into a trigger/condition/action recipe, resolving duplicate-contact and partial-sync edge cases.

Reframes press-release bullets and executive-quote boilerplate into a benefit-led blog post, while keeping legally qualified claims like "up to X%" intact instead of quietly rounding them up.

Adapts a tri-fold brochure for the web, filling in context a salesperson used to supply face to face, and breaking dense print paragraphs into scannable structure without losing the persuasive thread.

A scenario prompt that builds four alternating image-and-text feature blocks for a SaaS product page using the Media & Text block, with attention to reading order for keyboard and screen reader users.

A scenario prompt for turning a vague "nothing works" ticket into a properly tagged, prioritized ticket before anyone tries to fix anything.

A prompt for rewriting a batch of thin, templated ecommerce category descriptions into differentiated copy without inflating word count for its own sake.

A scenario prompt for structuring a points-based loyalty program for a beauty store, including the redemption-then-return gaming loophole most merchants forget to close.

Writes a single style-guide entry (rule, rationale, before/after examples, and the edge cases the general rule doesn't cover cleanly) ready to drop into an existing team doc.

A scenario prompt that converts a described order-to-label workflow into a trigger/condition/action recipe, handling multi-package orders and address-validation failures.

A store-manager role scenario covering add_role timing, map_meta_cap for post ownership edge cases, and safely rolling out capability changes to existing installs.

A scenario prompt that lays out a free-versus-paid plan comparison side by side with Columns blocks, handling mobile stacking order and non-color-dependent status icons.

A scenario prompt for a single blog post with three different image types (banner, screenshot, icon), walking through which get empty alt attributes and which need real descriptions, plus the icon that looks decorative but isn't.

A scenario prompt that diagnoses a real 41/100 PageSpeed report against a specific shared-hosting, page-builder stack, ranking fixes by what's actually feasible, not just what the report lists first.

A scenario-based prompt for writing category page copy that ranks without becoming a wall of keyword-stuffed text above a product grid nobody reads.

A scenario prompt for writing a return policy for an apparel store that covers the exceptions merchants usually forget, final sale items, customer-paid return shipping, and delivery-date windows.

A scenario for turning a function that echoes a banner straight into theme files into a proper hook-driven template tag, without breaking sites that call the old function directly.

Localizes a US-written post for another market by checking cultural assumptions (seasons, currency, idioms, region-specific stats) baked into the original, not just swapping spelling conventions.

A scenario prompt for a 4-second cart page caused by synchronous live shipping-rate calls and uncached cart fragments, separating fixes safe to cache from the ones that would break session state if cached wrong.

A scenario prompt for converting a pattern you keep answering in tickets into a self-serve FAQ, written in the actual language customers use.

A scenario prompt that converts a described ticket-escalation workflow into a recipe, resolving priority-detection, on-call rotation, and duplicate-escalation edge cases.

A prompt for generating natural-sounding anchor text variety for a link campaign, avoiding the over-optimized exact-match pattern that trips spam filters.

A scenario for a bulk CSV user-import command that handles batching, idempotent re-runs, and progress reporting the way a real ops script needs to.

A scenario prompt that untangles Elementor-style div soup, with its plugin-specific classes and inline widths, into clean nested Group and Columns block markup that survives the plugin's removal.

A scenario prompt for saying no to a feature request honestly, without a vague "we'll consider it" that just defers the disappointment.

A scenario prompt that converts a described low-stock-to-Slack workflow into an exact trigger/threshold/action recipe, covering flash-sale spikes and multi-warehouse stock.

A scenario prompt for naming and organizing hundreds of legacy images during a media library import, including the one case where renaming a file can quietly cost you existing search traffic.

A scenario prompt for working through a 47-plugin site using real Query Monitor timings, flagging overlapping tools and sitewide asset loaders, while catching the plugin that quietly powers something another plugin depends on.

A scenario prompt for writing international shipping policy copy that sets duty, customs, and delivery-time expectations clearly enough to prevent disputes over who pays what.

A prompt for cross-referencing a crawl export against a sitemap to find truly orphaned pages, then deciding case by case whether to link them or retire them.

A hero-CTA pattern and a preset core/group variation scenario, covering theme.json pattern categories and avoiding duplicate registration between plugin and theme.

A scenario prompt for a 14-person About page team grid shot across several photoshoots and years, with a consistent caption format plus handling for a departed employee's leftover photo.

A scenario prompt for prioritizing a 3,200-image media library for next-gen format conversion, weighing plugin-based conversion against server-level rules, and handling the fallback and transparency edge cases.

A scenario prompt that converts a described inactive-user re-engagement workflow into a recipe, resolving inactivity-definition, escalation, and win-back-offer edge cases.

A scenario prompt that migrates a 2019 post full of shortcodes and inline alignment styles into clean block markup, preserving every image caption and gallery instead of letting them collapse into a Classic block.

A scenario prompt for writing plain-language billing terms for a monthly coffee subscription, covering renewal cutoffs, failed payment retries, and mid-cycle plan changes.

A scenario prompt that turns a described publish-to-social workflow into a recipe covering scheduled posts, image fallbacks, and per-platform caption limits.

A scenario prompt for correcting a mix-up with a similarly named plugin, without making the customer feel foolish about it.

A real-incident scenario, with a confirmed backdoor, rogue admin accounts, and a core file warning, triaged and sequenced the way an incident responder would, containment before cleanup.

An exported user list riddled with stale contractor accounts, forgotten service logins, and a leftover migration account, sorted into keep, downgrade, remove, and investigate, with a re-mapping to least privilege that doesn't break automation.

A weight-tiered flat rate shipping method scenario that covers WC_Shipping_Method structure, rate caching invalidation, and Store API compatibility for block checkout.

A scenario prompt for an infographic with too much data to describe in one alt attribute, covering the WCAG-correct pattern of a short alt plus a linked full data equivalent.

A scenario prompt for tracking down a 1.8s TTFB on a managed host where page caching looks fine but the origin response is still slow, separating what wp-admin can fix from what needs a hosting support ticket.

A scenario prompt that lays out an eight-person About page team grid with photos, titles, and social links, handling mobile wrapping and icon-only link accessibility.

A scenario prompt for a home decor brand's wholesale page that gates pricing behind an application instead of showing it publicly, so retail customers never see it undermining full price.

A scenario prompt that converts a described post-delivery review-request workflow into a recipe, resolving delivery-confirmation and multi-item-order ambiguity.

A scaling-specific diagnosis for a store where archive and category pages have steadily degraded with catalog size, even with caching already active.

A scenario prompt for a GTM container with 12 tags plus a chat widget blocking the main thread for 900ms, weighing deferral against the marketing and analytics costs of delaying each script.

A management-dashboard export showing which of 22 client sites are running abandoned plugins, EOL PHP, or versions years out of date, prioritized by real exposure rather than by how long the list is.

A discount-calculation function scenario comparing full WP_UnitTestCase against a mocked, WordPress-independent test, with edge cases a non-tester would skip.

A scenario prompt for planning attributes, SKU naming, and stock structure for a 60-variation t-shirt line, including how to add a new color later without breaking past order records.

A small nonprofit with no formal security team needing a real security.txt-style disclosure page, drafted with scope, response-time commitments, and safe-harbor language instead of a vague "contact us about security" line.

A scenario prompt for a post using three images under three different license terms, covering what each license actually requires versus what's just polite, and the derivative-work catch in share-alike licenses.

A scenario prompt for moving a WooCommerce site with geo-targeted pricing from origin-only serving onto a CDN, sequencing DNS, cache-control rules, and purge strategy without breaking dynamic pages.

A scenario prompt that converts a described membership-expiry-reminder workflow into a recipe covering multi-touch timing, renewal-in-progress, and failed-payment overlap.

A scenario prompt that designs a consistent end-of-post author bio and registers it as a synced pattern, so five writers get identical structure with only the details swapped.

A pasted chunk of access log lines hammering wp-login.php, read the way a responder reads logs, telling credential stuffing apart from targeted brute force and checking whether any attempt actually got through.

A scenario prompt for triaging a PageSpeed report into an image optimization plan, including the trap of third-party shortcode images that bulk optimizer plugins never touch.

A scenario prompt for turning a 900MB database with 250k revision rows and stale transients into a safe, ordered cleanup plan, distinguishing what a plugin can handle from what needs direct SQL access.

A marketing coordinator with WordPress admin, SFTP, hosting-panel, and shared-vault access let go on bad terms, turned into a same-day rotation checklist that doesn't miss the integrations nobody remembers exist.

A scenario prompt that converts a described birthday-discount workflow into a recipe, resolving timezone, missing-data, and coupon-abuse edge cases.

A scenario prompt that rebuilds a product one-pager PDF as an ordered sequence of Gutenberg sections, since PDF text position doesn't map cleanly to reading order or heading hierarchy.

A pre-incident scenario for closing the door after a credential monitoring alert, before any actual compromise, with the highest-risk part being a stale account nobody's watching.

A scenario prompt for documenting srcset and sizes attributes for a developer handoff, including the case where mobile actually needs a different crop, not just a smaller version of the same image.

A scenario prompt for confirming whether a hosting provider's "Redis enabled" claim is actually functioning, checking the drop-in file, wp-config constants, and real hit ratio rather than trusting a dashboard toggle.

A WooCommerce-specific migration scenario that reasons through webhook endpoints, serialized data, and email deliverability risks a generic "migrate a WordPress site" checklist would miss.

A deployment checklist scenario for pushing staging changes live without overwriting fresh orders, comments, or form submissions that arrived on production during the build.

A scenario prompt for a gated lead-magnet PDF, covering the file's internal metadata as well as the media library description, since PDFs get indexed and previewed separately from the page hosting them.

Google Search Console showing pharma-spam titles indexed under category pages that don't exist anywhere in wp-admin, traced through cloaking-by-user-agent to the likely injection point and cleaned up without tipping off whoever planted it.

A scenario prompt for choosing eager versus lazy loading on a homepage, including the case where an image sits below the fold on desktop but above it on mobile.

A scenario prompt for tracing a 0.28 CLS score to a page builder's default Google Fonts import, then choosing between font-display swap, self-hosting, and reserved space fixes without breaking the builder's own font settings.

A hosting provider's blacklist warning traced back through wp_mail logs to a contact form plugin sending thousands of emails to strangers overnight, stopped, root-caused, and cleared through delisting.

A search-visibility-focused HTTPS migration plan that accounts for split Search Console properties, mixed content in serialized widget data, and internal links hardcoded to http, not just "install an SSL cert."

A scenario for switching payment processors on a live subscription store where every customer's stored card is tied to the old gateway's tokens.

A scenario prompt that turns a described behavioral lead-scoring workflow into a recipe with explicit point values, decay rules, and sales-alert thresholds.

A scenario prompt for an 8-second wp-admin dashboard load on a site where the public pages are fast and fully cached, pointing at admin widgets, Heartbeat, and admin_init hooks instead of frontend fixes that won't help.

A 30-user WooCommerce site with zero 2FA today, turned into a phased rollout plan that starts with admins, covers recovery for lost devices, and includes the actual email you'd send staff.

A redesign plan for replacing an old theme that accounts for custom post types registered in its functions.php and structured data tied to old templates, not just the visual rebuild.

A scenario prompt that converts a described broken-link-scan workflow into a recipe covering false positives, redirect chains, and prioritizing which links matter.

A rebrand scenario covering redirect mapping, OAuth and webhook redirect URIs tied to the old domain, and search-property continuity, not just pointing DNS at a new name.

A scenario prompt for fixing a 4.2s LCP caused by a performance plugin lazy-loading the hero image sitewide, scoping the fix so it stops the one image that matters without turning off lazy-load everywhere else.

A scenario prompt that converts a described webhook-to-spreadsheet logging workflow into a recipe, resolving schema drift, rate limits, and duplicate-row edge cases.

A scenario prompt for tracking a WooCommerce fatal "allowed memory size exhausted" error to a related-products plugin, weighing a code fix against just raising the memory limit at the hosting level.

A scenario for moving just the WordPress database to a new dedicated MySQL instance on the same host, without touching files or domain, covering lock-safe dumps and collation mismatches.

A disclosed unauthenticated file-upload CVE in a plugin the site can't update yet, worked into a targeted WAF rule that blocks the exploit path without breaking legitimate traffic, plus the actual patch plan behind it.

A media-offload plan for moving a large image library to S3-style storage behind a CDN, covering serialized URL rewrites, orphaned file detection, and responsive srcset breakage.

A scenario prompt for a 6-second WordPress native search on a 15,000-product catalog, weighing a plugin-based search index against a hosted search service given a hosting environment that can't run Elasticsearch itself.

A brute-force wave against wp-login.php that ended in one successful login on a non-admin account, worked through to confirm the blast radius, contain it, and turn it into a hardening checklist that actually prevents a repeat.

A scenario-driven plan for converting a single install into the first site of a multisite network, covering table prefix changes, upload path shifts, and network-activation plugin fallout most guides gloss over.

Hosting support flagging a world-writable wp-config.php, 777 upload folders, and one suspicious PHP file with executable permissions, worked through to tell misconfiguration from an active backdoor and fix it without breaking the site.

A scenario for pulling one site out of a shared multisite network into a standalone WordPress install, covering the shared users table and network-licensed plugins most split guides skip.

A rebuild plan for moving pages off one page builder onto another that accounts for leftover shortcode debris, builder-specific serialized meta, and SEO meta that must survive the rebuild.

A researcher's email reporting a stored XSS with a proof of concept and a 90-day public disclosure deadline, turned into a professional acknowledgment plus an internal triage and credit plan, no legal threats, no stonewalling.

A cutover plan for moving business email providers that keeps WooCommerce order confirmation, shipping, and password-reset emails flowing through the MX and SMTP transition.

A user-migration scenario for moving accounts between two standalone WordPress installs, covering ID collisions, custom role remapping, and membership-plugin metadata tied to specific user IDs.

A content-migration plan for moving a decade-old custom PHP CMS site into WordPress, covering URL structure mismatches, incompatible password hashes, and encoding artifacts from the export.