Ty_Tech/SlabUploader
6
0
Fork 0
Code Issues 15 Pull Requests Actions Packages Projects Releases Wiki Activity

fix(call2): no metadata dump in long description

Browse Source 
Long desc is Hook + Benefits (+ brief trust close) only; forbid Full specs /
Attribute list / product-name header that re-lists DECLARED ATTRIBUTES or
DIMENSION FACT BLOCK. Defensively strip trailing Category:/Length:/Board Feet:
labeled dumps in parse.
This commit is contained in:
grokbot_ty
2026-09-26 10:52:53 -07:00
parent 7e0157e45b
commit 88278a55e8
3 changed files with 200 additions and 18 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/contracts/PROMPTS.md
+13 -7
View File
@@ -188,6 +188,11 @@ Rules that always apply:
- The product name may already appear in DECLARED ATTRIBUTES — do not invent a new title.
- Lead with usable traits (species, figure, size, edge, moisture, grade) and what the piece
suits (tabletop, bar, etc.) without ad-copy fluff.
- Specs live in taxonomy and dimension fields on the product. Do NOT restate DECLARED
ATTRIBUTES or the DIMENSION FACT BLOCK as a labeled metadata list in the description
(no Category:/Figure:/Edge:/Grade:/Moisture:/Length:/Board Feet: dump, no "Full specs"
section, no "Maple Slab" attribute-header block). You may weave 1–2 key traits into
prose or benefit bullets naturally.
SHORT DESCRIPTION (~50 words — most important on-page copy; plain text only):
1. Lead with a practical outcome for a maker (what they can build / how the stock helps),
@@ -196,20 +201,21 @@ SHORT DESCRIPTION (~50 words — most important on-page copy; plain text only):
3. Close with a trust signal or concrete reason to choose this piece.
LONG DESCRIPTION (plain text only — newlines and `- ` bullets; no HTML, no markdown markup).
Four parts, in order:
Hook + Benefits only (+ brief trust close). Do NOT add a Full specs / Attribute list /
product-name header that re-lists DECLARED ATTRIBUTES or DIMENSION FACT BLOCK:
1. Hook — one sentence on what the piece suits and its standout usable trait.
2. Benefits — 3–5 bullets; each maker-useful trait first, then the supporting spec.
3. Full specs — clean list from DECLARED ATTRIBUTES + DIMENSION FACT BLOCK (dims, species,
moisture, edge, figure, grade, etc.).
4. Trust close — return/warranty/brand; use Brand voice when present; otherwise a short
neutral close with no invented policies.
2. Benefits — 3–5 bullets; each maker-useful trait first, then the supporting detail.
Weave in at most 1–2 key traits naturally — not an exhaustive labeled catalog.
3. Trust close (optional, brief) — return/warranty/brand; use Brand voice when present;
otherwise a short neutral close with no invented policies.
Return ONE JSON object only (no prose outside JSON) with exactly these keys:
`{"short_description": "<plain text ~50 words>", "description": "<plain text long description>"}`
Runtime appends DECLARED ATTRIBUTES (title + taxonomy; not a prior short), DIMENSION FACT
BLOCK, and `Brand voice:` / `Geo:` from Settings (`SETTINGS-30`). The POST handler parses the
JSON, strips any residual HTML to plain text, and persists both fields.
JSON, strips any residual HTML to plain text, drops a labeled Category:/Length:/Board Feet:
attribute dump if the model still emits one, and persists both fields.
## 7. Prompt management