Files
greeneclipseandClaude Fable 5 b595398389 Split A1 category prompts canonically; retire attributes prompting
- Category enhance prompts (Sync A1 / seed-a1 / repair) now use the same
  three role sections as the rest of the platform: Title / Description /
  Meta. The retired "--- Attributes ---" role section is removed from the
  canonical template, the legacy-split overlay, and the web prompt editor;
  Category/Attrs stay as plain product-context lines (attribute extraction
  remains pipeline-level via AppendAttributeConstraints).
- Stored prompts still carrying an attributes section are detected by
  CategoryEnhancePromptNeedsRepair and rewritten on the next Sync.
- Legacy wp_product_categories.sql splits now also seed a default Slovenian
  metaTitle rule (dumps only carried <metaDescription>), so every A1
  category gets all four prompt areas: title formula, description
  sections, meta title, meta description.
- Role-sectioned prompts no longer imply the A1 SEO-omit cohort
  (CompanyOmitsSEOMeta): sectioned prompts are the canonical prompt-editor
  output for every tenant, and the sniff silently disabled SEO meta for
  any company that saved a category prompt.
- Verified locally: repair-category-prompts -apply updated 238 A1 +
  Platform Demo categories from scripts/seed/wp_product_categories.sql
  (216 legacy splits), idempotent on re-run, zero attributes sections
  left in DB.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
2026-08-18 00:13:44 +02:00

55 lines
2.5 KiB
Go

package aiprompts
import "strings"
// Pipeline prompt roles mirror legacy Descrybe steps (categorize → title →
// description[+meta] → attributes). Categorize stays a separate Completer call
// (ProductCategorize*). category.prompt (CategoryEnhanceUserTemplate) is the
// shared enhance USER overlay, sectioned for title/description/meta/attrs so
// seed/repair and title/meta/attrs formula work (AppendFormulaConstraints) share
// one skeleton. Enhance JSON includes meta_* (legacy bundled meta); KeySEOMeta
// remains the standalone SEO path.
const (
RoleCategorize = "categorize" // pick taxonomy unique_id (processing.ProductCategorize*)
RoleTitle = "title" // JSON name / title formula
RoleDescription = "description" // JSON description / description formula
RoleMeta = "meta" // JSON meta_* in enhance + KeySEOMeta standalone
RoleAttributes = "attributes" // JSON attrs object + allowlist/formula key guidance
)
// Section markers match legacy enhance-product "--- Section ---" / "--- Meta Title ---"
// style so stored category prompts stay human-readable and machine-detectable.
// Attributes markers are retired for category prompts (attribute extraction is
// pipeline-level, not prompt-authored) but kept so repair can detect and strip
// old stored prompts that still carry the section.
const (
SectionTitleStart = "--- Title ---"
SectionTitleEnd = "--- End Title ---"
SectionDescriptionStart = "--- Description ---"
SectionDescriptionEnd = "--- End Description ---"
SectionMetaStart = "--- Meta ---"
SectionMetaEnd = "--- End Meta ---"
SectionAttributesStart = "--- Attributes ---"
SectionAttributesEnd = "--- End Attributes ---"
)
// CategoryPromptRoles lists the role ids used across categorize + enhance + SEO.
var CategoryPromptRoles = []string{
RoleCategorize,
RoleTitle,
RoleDescription,
RoleMeta,
RoleAttributes,
}
// CategoryEnhanceHasRoleSections reports whether a stored categories.prompt
// value uses the structured title/description/meta section markers from
// CategoryEnhanceUserTemplate (seed/repair canonical shape). Attributes is not
// required — category prompts no longer carry an attributes role section.
func CategoryEnhanceHasRoleSections(prompt string) bool {
lower := strings.ToLower(prompt)
return strings.Contains(lower, strings.ToLower(SectionTitleStart)) &&
strings.Contains(lower, strings.ToLower(SectionDescriptionStart)) &&
strings.Contains(lower, strings.ToLower(SectionMetaStart))
}