cue-ai 0.3.0

package/resources/skills/skills/medusa/higgsfield-to-medusa-products/scripts/run-pipeline.sh

@@ -0,0 +1,154 @@
+#!/usr/bin/env bash
+# run-pipeline.sh — generate product images via Higgsfield, host on S3, patch
+# Medusa products. See ../SKILL.md for the full contract.
+#
+# Usage:
+#   run-pipeline.sh <shop> [<manifest.json>]
+#
+# Env overrides:
+#   DRY_RUN=1       — generate + upload only, skip Medusa patch
+#   SKIP_OPTIMIZE=1 — keep PNGs, do not convert to JPEG
+#   RUN_ID=<str>    — override per-run cache subdir (default: timestamp)
+
+set -euo pipefail
+
+SHOP="${1:-}"
+MANIFEST="${2:-$HOME/.config/medusa-image-pipeline/$SHOP.manifest.json}"
+[[ -z "$SHOP" || ! -f "$MANIFEST" ]] && {
+  cat <<EOF >&2
+usage: $0 <shop> [<manifest.json>]
+  manifest defaults to ~/.config/medusa-image-pipeline/<shop>.manifest.json
+  see assets/manifest.example.json for schema
+EOF
+  exit 2
+}
+
+SCRIPT_DIR="$(cd "$(dirname "${BASH_SOURCE[0]}")" && pwd)"
+# shellcheck source=load-env.sh
+SHOP="$SHOP" source "$SCRIPT_DIR/load-env.sh"
+
+RUN_ID="${RUN_ID:-$(date +%Y%m%d-%H%M%S)}"
+CACHE_DIR="$HOME/.cache/medusa-image-pipeline/$SHOP/$RUN_ID"
+mkdir -p "$CACHE_DIR"
+
+AUTH_HEADER="Authorization: Basic $(printf '%s:' "$MEDUSA_SECRET_KEY" | base64 -w0)"
+
+# --- Bootstrap checks ---
+for cmd in jq curl aws higgsfield; do
+  command -v "$cmd" >/dev/null 2>&1 || { echo "missing: $cmd" >&2; exit 3; }
+done
+
+# --- Auth probe ---
+echo "==> Auth probe $MEDUSA_BACKEND_URL"
+code=$(curl -sL --max-time 10 -o /dev/null -w "%{http_code}" \
+  -H "$AUTH_HEADER" "$MEDUSA_BACKEND_URL/admin/products?limit=1")
+[[ "$code" != "200" ]] && { echo "    auth failed HTTP $code" >&2; exit 4; }
+echo "    ok (200)"
+
+# --- Per-product loop ---
+ENTRY_COUNT=$(jq 'length' "$MANIFEST")
+echo "==> Manifest has $ENTRY_COUNT product(s)"
+
+for i in $(seq 0 $((ENTRY_COUNT - 1))); do
+  ENTRY=$(jq -c ".[$i]" "$MANIFEST")
+  SLUG=$(echo "$ENTRY" | jq -r '.slug')
+  PID=$(echo "$ENTRY" | jq -r '.product_id // empty')
+  SHOTS_LEN=$(echo "$ENTRY" | jq '.shots | length')
+
+  echo ""
+  echo "==> [$((i+1))/$ENTRY_COUNT] $SLUG"
+
+  # Resolve product_id from slug if absent
+  if [[ -z "$PID" ]]; then
+    PID=$(curl -sL --max-time 10 -H "$AUTH_HEADER" \
+      "$MEDUSA_BACKEND_URL/admin/products?handle=$SLUG&limit=1" \
+      | jq -r '.products[0].id // empty')
+    [[ -z "$PID" ]] && { echo "    err  no product with handle=$SLUG"; continue; }
+    echo "    resolved id=$PID"
+  fi
+
+  # Generate + download + upload each shot
+  PUBLIC_URLS=()
+  FAILED=0
+  for j in $(seq 0 $((SHOTS_LEN - 1))); do
+    SHOT=$(echo "$ENTRY" | jq -c ".shots[$j]")
+    VARIANT=$(echo "$SHOT" | jq -r '.variant')
+    EXISTING_URL=$(echo "$SHOT" | jq -r '.url // empty')
+
+    if [[ -n "$EXISTING_URL" ]]; then
+      # Manifest provided a URL directly — keep it (no Higgsfield call).
+      PUBLIC_URLS+=("$EXISTING_URL")
+      echo "    keep $VARIANT $EXISTING_URL"
+      continue
+    fi
+
+    MODE=$(echo "$SHOT" | jq -r '.mode')
+    PROMPT=$(echo "$SHOT" | jq -r '.prompt')
+    ASPECT=$(echo "$SHOT" | jq -r '.aspect_ratio // "1:1"')
+    REF_IMAGE=$(echo "$SHOT" | jq -r '.image // empty')
+
+    echo "    gen  $VARIANT mode=$MODE aspect=$ASPECT"
+    HF_ARGS=(product-photoshoot create
+      --mode "$MODE"
+      --prompt "$PROMPT"
+      --count 1
+      --aspect_ratio "$ASPECT"
+      --resolution 2k
+      --output json)
+    [[ -n "$REF_IMAGE" ]] && HF_ARGS+=(--image "$REF_IMAGE")
+
+    HF_RES=$(higgsfield "${HF_ARGS[@]}" 2>&1) || {
+      echo "    err  higgsfield failed: $(echo "$HF_RES" | tail -1)"; FAILED=1; break; }
+    HF_URL=$(echo "$HF_RES" | jq -r '.[0].url // .images[0].url // empty')
+    [[ -z "$HF_URL" ]] && { echo "    err  no url in higgsfield response"; FAILED=1; break; }
+
+    PNG="$CACHE_DIR/$SLUG-$VARIANT.png"
+    curl -fsSL --max-time 60 -o "$PNG" "$HF_URL" || { echo "    err  download failed"; FAILED=1; break; }
+
+    # Optimize → jpg if magick available and not skipped
+    EXT="png"
+    UPLOAD_FILE="$PNG"
+    if [[ -z "${SKIP_OPTIMIZE:-}" ]] && command -v magick >/dev/null 2>&1; then
+      JPG="$CACHE_DIR/$SLUG-$VARIANT.jpg"
+      magick "$PNG" -quality 86 -strip "$JPG" >/dev/null 2>&1 && { EXT="jpg"; UPLOAD_FILE="$JPG"; }
+    fi
+
+    KEY="${S3_PREFIX}${SLUG}-${VARIANT}.${EXT}"
+    aws s3 cp "$UPLOAD_FILE" "s3://${S3_BUCKET}/${KEY}" \
+      --region "$S3_REGION" \
+      --content-type "image/${EXT/jpg/jpeg}" \
+      --cache-control "public, max-age=31536000, immutable" \
+      >/dev/null
+
+    PUB_URL="${S3_PUBLIC_BASE}/$(basename "$KEY")"
+    PUB_CODE=$(curl -sI -o /dev/null -w "%{http_code}" "$PUB_URL")
+    [[ "$PUB_CODE" != "200" ]] && { echo "    err  s3 public check $PUB_CODE for $PUB_URL"; FAILED=1; break; }
+
+    PUBLIC_URLS+=("$PUB_URL")
+    echo "    up   $VARIANT $PUB_URL"
+  done
+
+  (( FAILED == 1 )) && { echo "    skip $SLUG (generation/upload failed)"; continue; }
+
+  # Patch product
+  if [[ -n "${DRY_RUN:-}" ]]; then
+    echo "    dry  would PATCH $PID with ${#PUBLIC_URLS[@]} images"
+    continue
+  fi
+
+  THUMB="${PUBLIC_URLS[0]}"
+  IMAGES_JSON=$(printf '%s\n' "${PUBLIC_URLS[@]}" | jq -R . | jq -s 'map({url: .})')
+  BODY=$(jq -n --arg t "$THUMB" --argjson imgs "$IMAGES_JSON" '{thumbnail:$t, images:$imgs}')
+  STATUS=$(curl -sL --max-time 20 -o "$CACHE_DIR/$SLUG-patch.json" -w "%{http_code}" \
+    -X POST "$MEDUSA_BACKEND_URL/admin/products/$PID" \
+    -H "$AUTH_HEADER" -H "Content-Type: application/json" -d "$BODY")
+  if [[ "$STATUS" == "200" ]]; then
+    echo "    ok   $SLUG ($PID) — ${#PUBLIC_URLS[@]} images"
+  else
+    echo "    err  $SLUG ($PID) HTTP $STATUS"
+    head -c 400 "$CACHE_DIR/$SLUG-patch.json" >&2; echo >&2
+  fi
+done
+
+echo ""
+echo "==> Done. Cache: $CACHE_DIR"

package/resources/skills/skills/medusa/marva-blog-author/SKILL.md

@@ -0,0 +1,358 @@
+---
+name: marva-blog-author
+description: >-
+  Use when user says "write a MARVA blog post", "marvahome blog", "publish MARVA blog", "generate Hungarian blog for marvahome", "MARVA Home cikk", or asks to draft, author, push, or publish an SEO blog post for marvahome.com. End-to-end: Hungarian SEO+GEO authoring → marva-blog MCP push → Higgsfield thumbnail.
+---
+
+# MARVA Home Blog Author
+
+End-to-end runbook for authoring and publishing SEO + GEO-optimized Hungarian blog posts for **MARVA Home** (`https://marvahome.com`). The post is drafted directly into the `BlogPost` schema consumed by the `marva-blog` MCP, paired with a thumbnail generated by the `Higgsfield` MCP, pushed as draft, reviewed by the user, then published.
+
+## About MARVA Home (anchor context — read first)
+
+- Professional shared community space in **Győr, Hungary** (Győr-Moson-Sopron county, Northwest Hungary).
+- Therapy / coaching / consulting rooms rentable by the hour or day. No long-term commitment.
+- Audience: pszichológusok, terapeuták, coachok, mediátorok, csoportvezetők, tréningvezetők.
+- Brand voice: **calm, professional, Hungarian-first, lightly poetic but practical**. No marketing fluff. No emoji.
+- Site sections to internally link to: `/szobak`, `/foglalas`, `/arak`, `/berlet-vasarlas`, `/szakmai-kozossegunk`, `/esemenyeink`, `/rolunk`, `/blog`.
+- Geo keywords: `terápiás szoba bérlés Győr`, `coaching iroda Győr`, `csoportos foglalkozás bérleti tér`, `pszichológus rendelő Győr`, `tréningterem Győr belváros`.
+- Easy reach from Budapest / Bratislava / Vienna — name this when relevance allows.
+
+## BlogPost schema (target shape)
+
+```ts
+type BlogSection = {
+  id: string;            // kebab-case, unique within post
+  title: string;         // renders as <h2>
+  paragraphs: string[];  // 2-4 sentences each
+  bullets?: string[];    // renders as <ul>
+  code?: string;         // optional, skip for non-technical posts
+};
+
+type BlogPost = {
+  slug: string;          // kebab-case, ASCII only (run slugify)
+  title: string;         // <= 60 chars, primary keyword near front
+  description: string;   // <= 160 chars, used as meta description + OG/Twitter + JSON-LD
+  thumbnail_url: string; // 16:9 landscape, >= 1600px wide
+  author_name: string;   // default "Marva Home"
+  author_role: string;   // e.g. "Szakmai közösségi tér"
+  tags: string[];        // 3-6, lowercase Hungarian
+  sections: BlogSection[];
+};
+```
+
+The first section's first paragraph **is the lead** — write it as a self-contained answer to the post's main query (snippet-quality for AI Overviews / featured snippets). JSON-LD `BlogPosting` is emitted automatically by the storefront.
+
+## Slug algorithm (match the admin exactly)
+
+Hungarian diacritics are stripped, then non-alphanumerics become hyphens. Source of truth: `slugify()` in `apps/backend/src/admin/routes/blog/page.tsx` lines 77-89.
+
+```
+lowercase
+á à â ä → a
+é è ê ë → e
+í ì î ï → i
+ó ò ô ö ő → o
+ú ù û ü ű → u
+ç → c
+ñ → n
+anything not [a-z0-9] → "-"
+strip leading/trailing "-"
+```
+
+Examples:
+- `"Terápiás szoba bérlés Győrben"` → `terapias-szoba-berles-gyorben`
+- `"Csoportos foglalkozás: 5 tipp"` → `csoportos-foglalkozas-5-tipp`
+
+## Reference tag vocabulary
+
+**Existing tags from the admin UI** (`COMMON_TAGS` in `apps/backend/src/admin/routes/blog/page.tsx` lines 57-71) — reuse these first:
+
+`design`, `nappali`, `wellbeing`, `munka`, `tervezés`, `akusztika`, `productivity`, `interior`, `fókusz`, `csapat`, `terápia`, `coaching`, `közösség`
+
+**Additional Hungarian niche tags** (use when topically right):
+
+`szobák`, `tippek`, `bérlet`
+
+Pick **3-6 tags total**, lowercase, Hungarian. Reuse existing ones when possible to consolidate the tag cloud.
+
+---
+
+## Runbook
+
+Follow these steps in order. Do not skip 1 or 7 — the user must confirm the angle before drafting and the draft before publishing.
+
+### 1. Topic intake — propose 3 angles, get user pick
+
+Given a topic seed from the user (or self-generated from current site gaps), output **three candidate angles**. For each:
+
+- **Working title** (Hungarian, <= 60 chars)
+- **Primary search intent** (`informational` / `commercial` / `navigational`)
+- **Primary keyword** (Hungarian)
+- **Secondary keywords** (3-5, Hungarian)
+- **Győr-local angle** (one sentence — district, landmark, regional context, or persona)
+
+Present the three. Recommend one. Wait for user confirmation before drafting.
+
+Example for seed "csoportos foglalkozás":
+
+> **A) Csoportos foglalkozás Győrben — terem méretezés és akusztika**
+> Intent: informational · Primary kw: "csoportos foglalkozás terem Győr" · Secondary: "csoport szoba bérlés", "tréningterem akusztika", "kör alakú ülésrend", "10 fős csoport szoba" · Local angle: a Belváros sétálótávolságában lévő, magas belmagasságú szoba 8-12 fős csoportokra.
+>
+> **B) Hogyan válassz tréningtermet Győrben? Ellenőrzőlista bérlés előtt**
+> Intent: commercial · Primary kw: "tréningterem Győr bérlés" · Secondary: "óradíjas terembérlés", "csoportos coaching tér", "rugalmas terembérlés", "tréningterem felszereltség" · Local angle: A Győr-belvárosi elhelyezkedés előnyei budapesti és bécsi résztvevőknek.
+>
+> **C) Csoportdinamika és tér: mit üzen a szoba elrendezése?**
+> Intent: informational · Primary kw: "csoportdinamika tér elrendezés" · Secondary: "kör alakú ülésrend", "facilitátor pozíció", "csoport biztonsága", "csoport szoba berendezés", "akusztikai komfort" · Local angle: Egy Győr-Belvárosi tér leírása természetes fénnyel és lágy akusztikával.
+
+### 2. SEO blueprint (for the picked angle)
+
+Output, in this order:
+
+```yaml
+slug: <kebab-case ASCII via slugify>
+title: <= 60 chars, primary kw near the front
+description: <= 160 chars, includes Győr/Győr-Moson-Sopron, ends with a soft CTA like "Foglalj időpontot." or "Nézd meg a szobákat."
+tags: [3-6 lowercase Hungarian — prefer COMMON_TAGS]
+outline:
+  - H2 #1 (lead — direct answer to primary query)
+  - H2 #2
+  - H2 #3
+  - H2 #4
+  - (optional) H2 #5-7
+```
+
+Rules:
+- 4-7 H2 sections only. **No H3** — current schema is flat.
+- The first H2's first paragraph must answer the main query in 2-3 sentences (snippet candidate).
+- Title format: `<Primary keyword> — <benefit/qualifier>` or `<Question-style hook>` (no clickbait).
+
+### 3. GEO / E-E-A-T moves (mandatory in every post)
+
+Every published post must include all of:
+
+- **At least one Győr-specific reference** — district name (Belváros, Sziget, Révfalu, Adyváros), a distance from a landmark (e.g. "öt perc sétára a Széchenyi tértől"), or a regional context (Győr-Moson-Sopron megye, M1-ről 5 perc).
+- **At least one "kinek szól" paragraph** — name the target professional persona explicitly (pszichológus, coach, mediátor, csoportvezető, tréner, párkapcsolati tanácsadó stb.).
+- **A practical takeaway list** rendered via `bullets` on one section — usable as a checklist ("ellenőrzőlista bérlés előtt", "amit hozz magaddal", "amit nálunk találsz").
+- **Author voice note**: `author_role` set to a credible label, e.g. `"Szakmai közösségi tér"`, `"MARVA Home szerkesztőség"`, `"Győri közösségi tér csapata"`. Use first-person plural ("nálunk", "úgy gondoljuk") sparingly and naturally.
+- **Internal links inside paragraphs** as plain markdown — current renderer shows them as text, future MD upgrade will pick them up. Always include `/foglalas` and `/szobak`; add one topical post link when relevant. Example: `... időpontot a [foglalási oldalon](/foglalas) tudsz választani.`
+
+### 4. Section drafting rules
+
+- Paragraphs: **2-4 sentences max**, plain language, Hungarian native phrasing.
+- No AI tells: **avoid** "Ebben a cikkben…", "Összefoglalva…", "Mint tudjuk…", "A mai világban…", "Egyre népszerűbb…".
+- No marketing fluff: no "forradalmi", "egyedülálló", "prémium élmény" without substance.
+- Each section's **first paragraph stands alone** as a snippet-quality answer to the H2 question.
+- Concrete numbers and details over adjectives ("8-12 fős kör", "3,1 m belmagasság", "12 perc sétára").
+- Bullets: short imperative or noun phrases, max ~10 words each.
+
+### 5. Schema / metadata hooks
+
+Populate a `metadata` JSON object alongside the post — used for downstream SEO tracking and AI Overview tuning:
+
+```json
+{
+  "seo_keyword": "<primary keyword>",
+  "geo_target": "Győr, HU",
+  "reading_minutes": 4,
+  "intent": "informational",
+  "internal_links": ["/foglalas", "/szobak/..."],
+  "language": "hu-HU"
+}
+```
+
+Estimate `reading_minutes` from total word count / 220.
+
+### 6. Thumbnail brief (Higgsfield MCP)
+
+Before publishing, generate **one** landscape 16:9 image using the **`Higgsfield`** MCP (tools prefixed `mcp__Higgsfield__*`).
+
+**Base prompt template** (adapt per topic):
+
+> Editorial photo of a calm, sunlit therapy / consulting room in a renovated Győr townhouse. Warm wood, soft ochre accents, soft natural daylight from a tall window, plants, neutral palette. Wide angle, 16:9, photorealistic, no text overlay, no people unless the topic requires it.
+
+Per-topic adaptations:
+
+- Group session post → append "a small circle of 8 empty chairs facing each other, warm pendant light"
+- Solo therapy post → append "two armchairs at an angle near a window, a small side table with a glass of water"
+- Coaching / consulting post → append "a small round table with two notebooks and a fountain pen, soft blurred background"
+- Memberships / pricing post → append "a wide view of a quiet hallway with several wooden doors, soft ambient light"
+
+**Output constraints**: landscape, **≥ 1600 px wide**, no on-image text, no logos.
+
+**Two upload flows** — both supported:
+
+**Flow A (preferred, durable)** — upload to the shop's S3 public bucket:
+1. Save the Higgsfield-returned image locally.
+2. Upload to S3 (mirror the pattern in the `higgsfield-to-medusa-products` skill — public-read `<prefix>blog/<slug>.jpg`).
+3. Pass the resulting `https://<bucket>/.../blog/<slug>.jpg` URL to `marva_blog_set_thumbnail`.
+
+**Flow B (interim, fast)** — pass the Higgsfield-hosted URL directly:
+1. Take the URL returned by the Higgsfield MCP.
+2. Pass it straight to `marva_blog_set_thumbnail`.
+3. Note: Higgsfield-hosted URLs may expire — Flow A is preferred for production. Use Flow B for quick drafts or when S3 is unavailable.
+
+### 7. Push flow (marva-blog MCP)
+
+Use the **`marva-blog`** MCP. Exact tool sequence (never publish before user confirms):
+
+```text
+marva_blog_validate_sections(sections)
+  → returns ok or a list of structural problems; fix and re-run until ok.
+
+marva_blog_create_draft(
+  slug,
+  title,
+  description,
+  sections,
+  tags,
+  author_name = "Marva Home",
+  author_role = "Szakmai közösségi tér"
+)
+  → creates the post in "draft" status.
+
+marva_blog_set_thumbnail(slug, thumbnail_url)
+  → attaches the 16:9 image.
+
+# Show the draft URL to the user for review:
+#   https://admin.marvahome.com/app/blog
+# Wait for explicit "publish" / "mehet" confirmation.
+
+marva_blog_publish(slug)
+  → flips status to "published" and sets published_at.
+```
+
+If the MCP exposes additional tools (`marva_blog_update`, `marva_blog_unpublish`, `marva_blog_delete`, `marva_blog_list`), use them only when the user explicitly asks for edit / rollback / inventory.
+
+### 8. Post-publish checks
+
+After publishing:
+
+1. Open `https://marvahome.com/blog/<slug>` (via `WebFetch`) and confirm 200.
+2. Extract the inline `<script type="application/ld+json">` block via `WebFetch` (ask for "dump the script[type='application/ld+json'] content") and verify:
+   - `@type: BlogPosting`
+   - `headline` matches `title`
+   - `description` matches the post description
+   - `image` matches the thumbnail URL
+   - `inLanguage: hu-HU`
+3. Report back to the user with a **3-bullet summary**:
+   - Live URL
+   - Primary keyword + intent
+   - One sentence on the Győr-local hook used
+
+---
+
+## Reference worked example (use as your pattern)
+
+A complete post Claude should be able to reproduce in shape and tone.
+
+**Metadata**
+
+```yaml
+slug: terapias-szoba-berles-gyorben-amire-figyelj
+title: "Terápiás szoba bérlés Győrben — amire figyelj"
+description: "Hogyan válassz terápiás szobát Győrben? Praktikus szempontok akusztikához, fényhez, megközelítéshez. Foglalj időpontot."
+tags: ["terápia", "szobák", "akusztika", "tippek"]
+author_name: "Marva Home"
+author_role: "Szakmai közösségi tér"
+metadata:
+  seo_keyword: "terápiás szoba bérlés Győr"
+  geo_target: "Győr, HU"
+  reading_minutes: 4
+  intent: "commercial"
+  internal_links: ["/foglalas", "/szobak", "/arak"]
+  language: "hu-HU"
+```
+
+**Sections**
+
+```json
+[
+  {
+    "id": "mi-szamit",
+    "title": "Mi számít egy terápiás szobánál Győrben?",
+    "paragraphs": [
+      "Egy terápiás szoba akkor működik jól Győrben, ha az ügyfél már a belépés pillanatában nyugalmat érez: csendes utca, természetes fény, lágy akusztika és egyértelmű mosdóhasználat. Ez a négy alap fontosabb, mint a bútorok stílusa.",
+      "A MARVA Home szobái a [Belvárosban](/szobak), sétatávolságra a Széchenyi tértől, egy felújított polgárházban kaptak helyet. A vastag falak és a textil burkolatok miatt a szomszéd helyiségből nem szűrődik át beszéd."
+    ]
+  },
+  {
+    "id": "kinek-szol",
+    "title": "Kinek ajánljuk?",
+    "paragraphs": [
+      "Pszichológusoknak, pár- és családterapeutáknak, mediátoroknak és coachoknak, akik óradíjas vagy napidíjas konstrukcióban dolgoznak, és nem szeretnének egész éves bérleti díjat fizetni egy saját rendelőért.",
+      "Különösen hasznos azoknak, akik Budapestről vagy Bécsből járnak Győrbe heti egy-két alkalomra: a vonatállomástól tíz perc séta, parkolás a környező utcákban."
+    ]
+  },
+  {
+    "id": "ellenorzolista",
+    "title": "Ellenőrzőlista bérlés előtt",
+    "paragraphs": [
+      "Mielőtt lefoglalsz egy szobát, érdemes végigmenni ezen a rövid listán. A legtöbb panasz nem a térrel, hanem a hozzá tartozó apróságokkal kapcsolatos."
+    ],
+    "bullets": [
+      "Természetes fény és sötétíthetőség",
+      "Hangszigetelés a szomszéd helyiség felé",
+      "Külön mosdó vagy diszkrét útvonal a mosdóig",
+      "Vízforraló, pohár, papír zsebkendő",
+      "Egyértelmű érkezési és távozási rend",
+      "Rugalmas időpontmódosítás 24 órán belül"
+    ]
+  },
+  {
+    "id": "foglalas",
+    "title": "Hogyan foglalhatsz időpontot?",
+    "paragraphs": [
+      "Az időpontokat a [foglalási oldalon](/foglalas) tudod kiválasztani órás vagy napos bontásban. Ha rendszeresen használnád a teret, a [bérletes konstrukció](/berlet-vasarlas) kedvezőbb óradíjat ad.",
+      "Ha bizonytalan vagy, melyik szoba illik a munkádhoz, írj nekünk egy rövid leírást a foglalkozás típusáról és a létszámról — ajánlunk egy szobát, és ha kell, körbevezetünk személyesen."
+    ]
+  }
+]
+```
+
+**Thumbnail brief**
+
+> Editorial photo of a calm, sunlit therapy room in a renovated Győr townhouse. Two armchairs at a soft angle near a tall window, a small side table with a glass of water, warm wood floor, soft ochre textile accents, plants on the windowsill, soft natural daylight, neutral palette. Wide angle, 16:9, photorealistic, no text overlay, no people.
+
+**Push sequence**
+
+```text
+marva_blog_validate_sections(<sections>)
+marva_blog_create_draft(
+  slug="terapias-szoba-berles-gyorben-amire-figyelj",
+  title="Terápiás szoba bérlés Győrben — amire figyelj",
+  description="Hogyan válassz terápiás szobát Győrben? Praktikus szempontok akusztikához, fényhez, megközelítéshez. Foglalj időpontot.",
+  sections=<above>,
+  tags=["terápia","szobák","akusztika","tippek"],
+  author_name="Marva Home",
+  author_role="Szakmai közösségi tér"
+)
+marva_blog_set_thumbnail("terapias-szoba-berles-gyorben-amire-figyelj", "<higgsfield_or_s3_url>")
+# user reviews at https://admin.marvahome.com/app/blog
+marva_blog_publish("terapias-szoba-berles-gyorben-amire-figyelj")
+```
+
+**Post-publish report (to user)**
+
+- Live: `https://marvahome.com/blog/terapias-szoba-berles-gyorben-amire-figyelj`
+- Keyword + intent: `terápiás szoba bérlés Győr` — commercial
+- Győri horgony: Belvárosi felújított polgárház, 10 perc séta a vonatállomástól
+
+---
+
+## Quick checklist (run before push)
+
+- [ ] Title <= 60 chars, primary keyword near the front
+- [ ] Description <= 160 chars, contains Győr or Győr-Moson-Sopron, ends with soft CTA
+- [ ] Slug is ASCII kebab-case via the slugify algorithm
+- [ ] 3-6 tags, lowercase Hungarian, prefer `COMMON_TAGS`
+- [ ] 4-7 H2 sections, no H3
+- [ ] First section, first paragraph is a self-contained answer
+- [ ] At least one Győr-specific reference (district / landmark / distance)
+- [ ] At least one "kinek szól" paragraph naming the persona
+- [ ] At least one `bullets` checklist
+- [ ] At least two internal links (`/foglalas`, `/szobak`)
+- [ ] No AI tells, no marketing fluff, no emoji
+- [ ] Thumbnail 16:9, >= 1600 px wide
+- [ ] `marva_blog_validate_sections` returns ok
+- [ ] User has confirmed before `marva_blog_publish`

package/resources/skills/skills/medusa/medusa-local-dev/SKILL.md

@@ -0,0 +1,100 @@
+---
+name: medusa-local-dev
+description: Use when starting any Medusa shop locally (backend + storefront), when two shops collide on port 9000 or 3000, when "EADDRINUSE :::9000" appears, or when running multiple shops side-by-side under ~/Documents/medusa-shops/ and ~/Documents/recodee/.
+---
+
+# Running multiple Medusa shops locally
+
+## Core principle
+
+Every shop has **stable, assigned ports** in `~/Documents/medusa-shops/.dev-ports.yaml`. The `medusa-dev` helper (`~/Documents/soul/bin/medusa-dev`) reads that file, starts backend + storefront with the right `PORT=` env, and refuses to start if a port is already held. No more guessing why `pnpm dev` failed — the script tells you which other shop is on the port.
+
+## Quick reference
+
+```bash
+medusa-dev list                       # who is up, who is down, on which ports
+medusa-dev start marva                # backend (9001) + storefront (3001)
+medusa-dev start lifted back          # just the backend
+medusa-dev stop  marva                # both
+medusa-dev tail  marva back           # follow the backend log
+medusa-dev cors-fix marva             # one-time: loosen STORE_CORS/AUTH_CORS to a localhost regex
+```
+
+Logs land in `~/.cache/medusa-dev/<shop>.<back|front>.log`. Pidfiles in the same dir.
+
+## Port table
+
+The registry maps shop → backend (90xx) and storefront (30xx). See `~/Documents/medusa-shops/.dev-ports.yaml` for the canonical list. Adding a shop is just an entry — no code change.
+
+| Shop | Backend | Storefront |
+|---|---|---|
+| recodee | 9000 | 3000 |
+| marva | 9001 | 3001 |
+| lifted | 9002 | 3002 |
+| teherguminet | 9003 | 3003 |
+| compastor | 9004 | 3004 |
+| munchi-v3 | 9005 | 3005 |
+| modulix | 9006 | 3006 |
+| base-template | 9008 | 3008 |
+| koronakert | 9009 | 3009 |
+| 2026/KORONAKERTv2 | 9010 | 3010 |
+| 2026/KRSITOFWEBSHOP | 9011 | 3011 |
+| 2026/MUNCHI | 9012 | 3012 |
+| 2026/WEBUv2 | 9013 | 3013 |
+
+## CORS — set it once per shop
+
+Each backend's `.env` ships with `STORE_CORS=http://localhost:3000,…` which breaks the moment that shop moves off 3000. Fix it once per shop:
+
+```bash
+medusa-dev cors-fix marva
+```
+
+This rewrites `STORE_CORS`, `AUTH_CORS`, `ADMIN_CORS` in `apps/backend/.env` to a regex Medusa understands:
+
+```
+STORE_CORS=^http://localhost:\d+$
+AUTH_CORS=^http://localhost:\d+$
+ADMIN_CORS=^http://localhost:\d+$
+```
+
+The original file is backed up to `<file>.bak.<ts>`. Production `.env` (on Coolify) is untouched.
+
+## Discovery commands
+
+```bash
+# Which ports in the 9xxx and 3xxx ranges are held — and by what process?
+ss -lntpH 'sport >= :9000 and sport < :9100'
+ss -lntpH 'sport >= :3000 and sport < :3100'
+
+# All Medusa node processes
+ps -ef | grep -E "node.*medusa|next dev" | grep -v grep
+```
+
+## Common situations
+
+| Symptom | What to do |
+|---|---|
+| `EADDRINUSE :::9000` | `medusa-dev list` → see who owns 9000 → either `medusa-dev stop <that-shop>` or start the new shop (it has its own port). |
+| Storefront shows CORS error after starting on `:3001` | Run `medusa-dev cors-fix <shop>` once. |
+| `medusa-dev start` says "Port X already in use by 'next'" | A storefront dev is running outside the helper. Find with `ss -lntpH 'sport = :PORT'`, kill it, or stop via its own process. |
+| Need a new shop | Add an entry in `.dev-ports.yaml` with the next free index. No script edits. |
+| Lost track of what's running | `medusa-dev list` shows live state by port + pidfile. |
+
+## Architecture notes
+
+- The helper checks both `pidfile alive` and `port held` independently. If a previous run died without cleanup, the port can be "busy" without a pidfile — that's a real collision and the script refuses to start.
+- Each `start` invocation backgrounds `pnpm --filter backend dev` (or `--filter storefront dev`) with `PORT=<n>`. It does **not** swap `.env`. If your `.env` hardcodes a port, the env wins — remove that line and let the env var drive it.
+- Recodee lives at `~/Documents/recodee/`, outside `medusa-shops/`. It's still in the registry; the helper resolves paths against `~/Documents/`.
+
+## When NOT to use this
+
+- Production deploys — those go through Coolify, see the `coolify` skill.
+- Building admin frontend (`medusa build`) — not a dev server; use the project's own `pnpm build`.
+- Running tests — use the shop's `pnpm test:integration:*` scripts directly.
+
+## Bootstrapping on a fresh machine
+
+1. Ensure `~/Documents/soul/bin/` is on `PATH` (add to `~/.bashrc` or `~/.zshrc`: `export PATH="$HOME/Documents/soul/bin:$PATH"`).
+2. Confirm `python3` is available (used by the helper for YAML parsing — no PyYAML dep).
+3. `medusa-dev list` — should print the table. If the registry file is missing, the script errors out with a clear message.

package/resources/skills/skills/medusa/medusa-reference/SKILL.md

@@ -0,0 +1,32 @@
+---
+name: medusa-reference
+description: >-
+  Use when user says "Medusa workflow", "Medusa subscriber", "Medusa auth", "Medusa query", or builds/modifies API routes, models, jobs, backend logic, storefront integrations.
+---
+
+# Medusa Reference
+
+Use this skill before editing Medusa-specific code.
+
+1. Identify the change scope first:
+- backend workflow / subscriber / API / auth / model / query
+- storefront integration / request flow / data mapping
+
+2. Prefer existing project patterns:
+- locate nearest similar implementation
+- reuse naming, folder placement, and error handling style
+
+3. For backend changes:
+- keep handlers/workflows narrow and explicit
+- validate payloads and avoid silent fallback behavior
+- return actionable errors that help debugging
+
+4. For storefront changes:
+- keep data fetching and transformation predictable
+- avoid hidden coupling between UI and backend response shape
+- preserve existing loading/error states
+
+5. Read references when relevant:
+- references/workflows-and-subscribers.md
+- references/api-and-auth.md
+- references/storefront-integration.md

package/resources/skills/skills/medusa/medusa-reference/references/api-and-auth.md

@@ -0,0 +1,6 @@
+# API And Auth
+
+- Keep route handlers focused: parse input, validate, delegate, format output.
+- Reuse project auth middleware and permission checks.
+- Fail closed for protected actions.
+- Avoid leaking internal errors or stack traces in API responses.

package/resources/skills/skills/medusa/medusa-reference/references/storefront-integration.md

@@ -0,0 +1,6 @@
+# Storefront Integration
+
+- Keep storefront request/response contracts aligned with backend DTOs.
+- Normalize data at the boundary and keep component props stable.
+- Preserve locale, route context, and selected entity context when editing flows.
+- Prefer incremental UI edits over broad rewrites unless requested.

package/resources/skills/skills/medusa/medusa-reference/references/workflows-and-subscribers.md

@@ -0,0 +1,6 @@
+# Workflows And Subscribers
+
+- Use deterministic step naming and narrow responsibility per step.
+- Keep event subscriber side effects idempotent when possible.
+- Prefer explicit guards over broad try/catch suppression.
+- Reuse existing event names and payload conventions from nearby modules.