arca-marketing-video 2.26.0 → 2.27.0

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "arca-marketing-video",
-  "version": "2.26.0",
+  "version": "2.27.0",
   "repository": {
     "type": "git",
     "url": "git+https://github.com/briarbearrr/arca-marketing.git"

package/skills/_arca-marketing-assets/brand.md

@@ -19,7 +19,7 @@ Brand name:
 Arca
 
 Name usage rules:
-- Always write the brand name as "Arca" or "arca.ph".
+- Always write the brand name as "Arca" or "Arca.ph" (capital A — never "arca.ph").
 - Never write it in all caps as "ARCA" unless it appears inside a small logo mark.
 - The brand should feel premium, human, practical, and audience-first.
 
@@ -28,7 +28,7 @@ Name usage rules:
 ====================================================================
 2. WEBSITE / HANDLE
 ====================================================================
-arca.ph
+Arca.ph
 
 ====================================================================
 3. WHAT THE BRAND DOES / POSITIONING

package/skills/brand-builder/SKILL.md

@@ -27,7 +27,7 @@ You are a brand strategist running a fast, friendly onboarding interview. Your g
 
 **Round 1 — Identity & positioning** (sections 1–7)
 Ask for:
-1. Brand name + exact name-usage rules (caps? domain form? e.g. "Arca" / "arca.ph", never "ARCA").
+1. Brand name + exact name-usage rules (caps? domain form? e.g. "Arca" / "Arca.ph" with a capital A, never "arca.ph" or "ARCA").
 2. Website / handle.
 3. What the brand does, in one or two plain sentences — the offer and who it serves.
 4. The core brand idea / the one-line metaphor or positioning (e.g. "the execution navigation layer for founders").

package/skills/carousel-generator/SKILL.md

@@ -103,11 +103,11 @@ Generate each slide as a separate standalone image. Do NOT generate all slides i
 - Repurposing: square 1:1 1080×1080; stories/reels covers 9:16 1080×1920. Default to 4:5 portrait unless specified.
 
 ### GENERATE ONE SLIDE AT A TIME (hard rule + workflow)
-**Never render the slides together. One render = one slide.** No grid, no contact sheet, no 2×2 / 3×3 board, no "all slides in one image", no multi-panel composite, no brand board. A combined image is an instant fail — discard it and re-render as separate slides. (Asking an image model for "the whole carousel" reliably produces a cramped grid with unreadable text; one slide per render is the only way to get full-resolution, legible, mobile-ready slides.)
+**Never render the slides together. The mantra is "1 prompt = 1 image" — one render = one slide.** A carousel is produced as MULTIPLE images (one image-generation call per slide), never one image containing several slides. No grid, no contact sheet, no 2×2 / 3×3 board, no "all slides in one image", no multi-panel composite, no brand board. A combined image is an instant fail — discard it and re-render as separate slides. (Asking an image model for "the whole carousel" reliably produces a cramped grid with unreadable text; one slide per render is the only way to get full-resolution, legible, mobile-ready slides.)
 
 **Image generation is NOT unavailable — a collage is a WORKFLOW bug, not a tool limit.** If you get a grid/board, never tell the user image generation is unsupported or disabled. The tool works; the prompt method was wrong. Fix the method and regenerate — never downgrade or abandon the deliverable over it.
 
-**The wording trap — these phrases make the model emit a collage:** "generate a batch", "the carousel", "the set", "five slides", "all slides", "a slide preview". To an image model, "a batch of slides" = "put all slides in one image." So never say them. Don't *batch* — **chain**: think of it as "generate the carousel as separate images, one image-generation call per slide, chained sequentially from Slide 1 to Slide N." One prompt = exactly one slide, always.
+**The wording trap — these phrases make the model emit a collage:** "generate a batch", "the carousel", "the set", "five slides", "all slides", "a slide preview". To an image model, "a batch of slides" = "put all slides in one image." So never say them. Don't *batch* — **chain**: think of it as "generate the carousel as separate images, one image-generation call per slide, chained sequentially from Slide 1 to Slide N." **1 prompt = 1 image** = exactly one slide, always — repeat across N prompts to get N images.
 
 **Render sequentially, anchoring every slide to Slide 1:**
 1. **Render Slide 1 first** as a single standalone 4:5 image. This locks the carousel's look — palette, type hierarchy, layout rhythm, safe margins, logo placement, illustration style. Review it; re-render until it's right BEFORE touching the rest (everything inherits from it).