Objective

Add a reusable pre-publish QA guardrail for four defects that recently slipped through on a live website-content lane: comma-space drift, lowercase Related Resources labels, dead hero URLs, and medium-width readability squeeze.

What was accomplished

• Updated Skills/pre-publish-qa/SKILL.md to explicitly block:
  • stray space-before-comma punctuation in visible copy or matching schema text
  • dead, blank, or non-rendering hero and featured-image sources
  • medium-width article pinch around 1024px to 1120px
  • lowercase labels in legacy Related Resources blocks, not just standard Related Content
• Updated Skills/sa-web-content-creation/SKILL.md so the upstream content workflow now requires:
  • a medium-width QA pass in addition to mobile
  • visibly rendering hero and featured images
  • headline-case labels in both standard and legacy related-link blocks
  • comma-space cleanup in visible copy and matching schema text
• Updated Skills/sa-template-reference/SKILL.md so the template reference itself now treats responsive QA as both mobile and medium-width and explicitly fails dead hero-image sources and lowercase legacy related-resource labels.

Verification

• Confirmed the new guardrail language is present in all three updated skills with rg.
• Verified the exact new checks appear in the canonical gate skill, not only in one upstream helper skill.
• Kept the work additive and rollback-safe. No live WordPress content, plugin, or theme code changed in this pass.

Why the session ended

The requested workflow update is complete and source-verified. No further live-system action was needed for this pass.

Suggested next steps

• If tighter enforcement is useful, a lightweight automated lint/helper can scan preview HTML for \\s,, dead hero URLs, and lowercase related-link labels before human QA.
• If process drift remains a problem, the same guardrail language can be mirrored into page-builder or deploy routines that emit approval-ready without loading pre-publish-qa directly.

Handoff

Future agents working on SA website pages or posts should rely on the updated skill stack rather than memory for these checks. If one of these defects still escapes, it likely means the agent skipped the canonical load order instead of a rule being missing.

Files touched

• Skills/pre-publish-qa/SKILL.md
• Skills/sa-web-content-creation/SKILL.md