@slatesvideo/shared 0.5.3 → 0.5.5

package/dist/prompts/prompting-tips.js

@@ -9,11 +9,19 @@
 // matching entry here in the same pass. Keys are model FAMILIES — the
 // desktop maps concrete model ids to a family key with its MODEL_REGISTRY
 // helpers (the runtime truth for ids lives in slate/src/shared/pricing.ts).
+//
+// Cards whose content is ALSO doctrine (not just model trivia) compose their
+// copy from skills/_partials/*.md via PARTIALS rather than restating it. The
+// NANO_BANANA reference card is why: it shipped "label every role" — retired
+// doctrine — for thirteen months after the reversal, in the same package as
+// the rule forbidding it. Hand-sync didn't merely drift, it survived a
+// reversal. Add a short partial; don't hand-copy a rule into a card.
+import { PARTIALS } from './partials.generated.js';
 const SEEDANCE = {
     label: 'Seedance 2.0',
     intro: [
-        'Seedance 2.0 wants natural prose with narrative timing beats. Not shot brackets, not bullet points. Audio is always generated alongside video at no extra cost.',
-        "Follow ByteDance's official 6-step formula: Subject, Action, Environment, Camera, Style, Constraints. Sweet spot 60-150 words for single shots, longer for multi-shot.",
+        'Seedance 2.0 is a multimodal director: it reads your text, images, video and audio at once and splits them into a "spatial layer" (what is in frame) and a "temporal layer" (how it changes). So a good prompt is an engineering-style instruction, not a piece of copywriting. Audio is always generated alongside video at no extra cost.',
+        "ByteDance's official advanced formula has 8 slots: precise subject + action details + scene/environment + lighting & color tone + camera movement + visual style + image quality + constraints. Sweet spot 60-150 words for a single shot, longer for multi-shot.",
     ],
     columns: [
         [
@@ -23,37 +31,55 @@ const SEEDANCE = {
                 note: "The first 20-30 words are the identity anchor. If the subject isn't locked in immediately, Seedance will hallucinate new subjects mid-generation.",
             },
             {
-                heading: 'Narrative timing beats',
-                example: 'At 2 seconds, the camera begins a slow dolly forward. At 4 seconds, the lid opens in slow-motion...',
-                note: 'Use "At N seconds" — not SHOT brackets. 2 beats for a 5s clip, 3 for 10s, 4-5 for 15s.',
+                heading: 'Shot 1 / Shot 2 / Shot 3 — never time stamps',
+                example: 'Shot 1: Side shot of the alley; the man slowly starts running.\nShot 2: He knocks over a fruit stand; the camera shakes and cuts to his face.\nShot 3: He climbs a low wall; the camera pulls back onto the empty street.',
+                note: 'ByteDance: write a "Shot 1 / Shot 2 / Shot 3" storyboard in the order events occur, then merge it into one prompt. Do NOT write "At 4 seconds" or "0:00–0:03" and do not set per-shot durations — official docs say precise timing is unstable and forcing it "may lead to abnormal generation results." Let the plot set the pacing.',
+                critical: true,
             },
             {
-                heading: 'Lighting is the #1 quality lever',
+                heading: 'Order inside each shot',
+                example: 'camera move → action + expression → position change → audio',
+                note: "ByteDance's recommended per-shot order. Lead with the camera (\"slowly push in from a wide shot\", \"fixed camera position\", \"cut to...\"), then what the subject does, then where they end up, then the sound.",
+            },
+            {
+                heading: 'Lighting is a top quality lever',
                 example: 'A cool-white diagonal beam from upper left, dust particles drifting through...',
-                note: 'ByteDance says lighting has the biggest impact on quality of any prompt element. Describe it before or alongside the subject.',
+                note: 'Lighting & color tone has its own slot in the official formula. Describe it before or alongside the subject.',
             },
         ],
         [
             {
-                heading: '8 supported camera moves',
-                example: 'push-in · pull-out · pan · tracking · orbit · aerial · handheld · fixed',
-                note: 'Use these exact terms. "Dolly in" not "zoom in." "Orbit" not "circle." One primary camera move per beat — never stack them.',
+                heading: 'Standard camera terms — including shot size',
+                example: 'medium shot · close-up · wide shot · slow push-in · smooth lateral tracking · fixed shot',
+                note: 'ByteDance: the model has a strong understanding of camera terminology, so use it directly — this is an open vocabulary, not a fixed list, and shot size counts as camera direction. Only ONE camera movement per shot: asking for push, pull, pan and move at once increases image instability.',
+            },
+            {
+                heading: 'Slow, gentle, continuous movement',
+                example: 'slowly raise a hand · quickly turn the head · walk slowly · sit down naturally with the motion',
+                note: 'Official rule: name the body part and quantify range, speed and force — and prefer small continuous movement over sprints, big jumps and violent rolls. Slow-motion is supported in natural language; "fast" is a known quality-degrading word.',
             },
             {
-                heading: 'Slow-motion works ("fast" doesn\'t)',
-                example: 'the lid opens in slow-motion · the blade whips through the air',
-                note: 'Speed ramps and slow-motion are supported in natural language. Avoid the word "fast" — it\'s ByteDance\'s #1 quality-degrading keyword.',
+                heading: 'Externalize emotion',
+                example: '❌ she looks very sad\n✅ head lowering, shoulders trembling slightly, eyes reddening, fingers clutching the corner of her clothing',
+                note: 'Replace abstract emotion words with the physical detail that shows them. This is the single highest-leverage habit in ByteDance\'s guide — the model renders bodies, not adjectives.',
             },
             {
                 heading: 'Separate camera from subject motion',
                 example: 'The earbud rises smoothly. The camera tracks upward.',
-                note: 'Two different sentences. Mixing them ("the camera speed ramps as the earbud rises") is the #1 cause of shaky, glitchy output.',
+                note: 'Two different sentences. Mixing them ("the camera speed ramps as the earbud rises") is a common cause of shaky, glitchy output.',
+            },
+            {
+                heading: 'Multi-character shots — forbid twins',
+                example: 'Throughout the video, characters with completely identical appearance, clothing, and accessories are prohibited. Do not generate duplicate avatars or a twin effect.',
+                note: 'With several characters in frame, Seedance can render the same person twice. ByteDance\'s fix: bind each character to its image ("Marcus (image 1)"), append that constraint verbatim at the end, and prefer single-person reference photos. Past 4 reference people, stability drops — compose a group still first.',
             },
         ],
     ],
     footer: [
+        'Quality and constraint slots have their own official vocabulary: ask for "HD, rich details, cinematic texture, natural colors, soft lighting" — not "8K / masterpiece / trending on artstation." Seedance has no negative-prompt field, so constraints go inline: "keep it subtitle-free", "do not generate a logo", "do not generate a watermark".',
         'Style block at the end: one primary anchor plus 2-3 supporting details. End with "Single continuous take" if you want one shot with no cuts. Never write "no cut" or "seamless transition" — those aren\'t in the training vocabulary.',
-        'Multi-modal: up to 9 images + 1 video + audio refs. Reference in prompt with @character, @environment, @audio1. Max length: 4,000 characters.',
+        'Multi-modal: up to 9 images, 3 videos and 3 audio references. Cite them by type and index — "Zhang San@Image 1", or the "Marcus (image 1)" form Slates composes from your @mentions. Never cite an asset ID instead of the image number; the model can\'t associate the two. Max length: 4,000 characters.',
+        'Don\'t cross-pollinate image-model syntax: named lenses, apertures and film stocks ("85mm f/1.4", "Kodak Portra 400") are a Nano Banana lever and a Seedance anti-pattern. Translate them into shot size, depth of field and colour tone instead.',
     ],
 };
 const KLING = {
@@ -186,7 +212,7 @@ const OMNI_FLASH = {
         [
             {
                 heading: 'Name references inline',
-                example: 'Marcus (images 1 and 2) walks into the cafe...',
+                example: 'Marcus (image 1) walks into the cafe...',
                 note: 'Up to 7 reference images merge into one list — refer to them by number in the prompt.',
             },
             {
@@ -269,6 +295,11 @@ const NANO_BANANA = {
                 example: 'Kodak Portra 400 · Fuji Velvia 50 · Ilford HP5 Plus · CineStill 800T',
                 note: 'Portra = natural skin warmth. Velvia = saturated landscape. HP5 = gritty B&W grain. CineStill 800T = tungsten night with halation. Never mix stocks.',
             },
+            {
+                heading: "Don't carry lens + stock into a video prompt",
+                example: '85mm f/1.4, Portra 400\n→ close-up, shallow depth of field, warm natural colors, cinematic texture',
+                note: 'Lenses, apertures, film stocks and camera bodies are an image-model lever and a video-model anti-pattern — ByteDance\'s Seedance guide never mentions f-stops, lens millimetres, fps or shutter angle. When you animate a frame you made here, translate the look into shot size, depth of field and colour tone instead of pasting the gear list across.',
+            },
             {
                 heading: 'Physics-based lighting',
                 example: 'Single key light at 45 degrees from upper left. Color temperature 4500K. Crisp catchlights in the eyes.',
@@ -293,9 +324,9 @@ const NANO_BANANA = {
                 note: 'Reframe positively first. Use inline "without" / "free of" only when positive framing can\'t suppress the unwanted element.',
             },
             {
-                heading: 'Reference images — label every role',
-                example: 'Image 1: Character ref — facial features, body proportions\nImage 2: Environment ref — architecture, lighting\nImage 3: Style ref — mood, aesthetic',
-                note: "Up to 14 refs (10 object + 4 character — caps don't trade). The @ and # mention system labels these automatically. Start with 2-3 focused refs.",
+                heading: 'Reference images — name them, never label roles',
+                example: 'Marcus (image 1) sits across from the woman (image 2) in the cafe (image 3).',
+                note: `Up to 14 refs (10 object + 4 character — caps don't trade). ${PARTIALS['reference-tips-short']}`,
             },
             {
                 heading: 'Common fixes',

package/dist/prompts/reference-composer.d.ts

@@ -14,7 +14,7 @@ export interface ReferenceGroup {
     /** Display + citation name: 'Marcus' | 'the cafe' | 'noir'. Used verbatim. */
     name: string;
     kind: ReferenceKind;
-    /** A group can carry several images (e.g. turnaround + expression). */
+    /** A group can carry several images for workflows that genuinely need them. */
     media: ReferenceMedia[];
 }
 export interface ComposedReferences {

package/dist/prompts/reference-composer.js

@@ -14,10 +14,9 @@
 // the desktop generation + rail read from this one function, so the rail's badge
 // numbers and the prompt's "image N" citations can never desync.
 //
-// Naming is the ONLY identity signal. Citing both of a subject's images as the
-// SAME name ("Marcus (images 1 and 2)") tells the model they are ONE entity —
-// which is what prevents a multi-image bucket from averaging into a blended
-// face. This IS each model's own official consistency lever (NB2 "assign a
+// Naming is the identity signal. Citing the canonical subject image inline
+// ("Marcus (image 1)") tells the model which reference owns that entity. This
+// is each model's own official consistency lever (NB2 "assign a
 // distinct name", Seedance "Reference Subject_N in Image_N", Kling "reuse a fixed
 // label verbatim"); the heavy role-essay block was the off-doctrine part.
 // Normalize a name/token for matching: drop the sigil, lowercase, strip

package/dist/prompts/reference-rules.d.ts

@@ -1,3 +1,4 @@
+export { PARTIALS } from './partials.generated.js';
 export type SourceGrade = 'Eric-test' | 'community' | 'code-verified' | 'creator-demo';
 export interface ReferenceRule {
     id: string;
@@ -11,24 +12,52 @@ export interface ReferenceRule {
  * are the reusable text the templates compose.
  */
 export declare const REFERENCE_RULES: ReferenceRule[];
-/** Flat, even, shadowless identity lighting on a plain neutral background. */
+/** Flat, even, shadowless identity lighting on a deep neutral-grey plate. */
 export declare const IDENTITY_LIGHTING = "flat, even, shadowless lighting";
-export declare const IDENTITY_BACKGROUND = "a plain neutral-grey background";
-export declare const IDENTITY_LIGHTING_CLAUSE = "Render on a plain neutral-grey background with flat, even, shadowless lighting so the sheet captures the character's identity, not scene lighting.";
+/**
+ * The plate value is deliberate, not decorative: **white bleeds into the
+ * generated video and washes out the location; black eats edge detail and
+ * crushes hair and wardrobe silhouettes.** A deep neutral grey holds both.
+ */
+export declare const IDENTITY_PLATE_HEX = "#3a3a3c";
+export declare const IDENTITY_BACKGROUND = "a plain, deep neutral-grey background (#3a3a3c)";
+export declare const IDENTITY_LIGHTING_CLAUSE = "Render on a plain, deep neutral-grey background (#3a3a3c) with flat, even, shadowless lighting so the sheet captures the character's identity, not scene lighting.";
+/**
+ * Craft clauses every identity reference wants — the eye and skin detail that
+ * survives downstream, plus the two "reads literally" guards. Crushed-black
+ * irises carry no light information, so eye tone drifts between generations;
+ * no catchlight reads as dead eyes; perfect mirroring reads as synthetic and
+ * the model PRESERVES that reading; a game-render look gets ANIMATED like game
+ * footage. See skills/_partials/references-read-literally.md.
+ */
+export declare const IDENTITY_CRAFT_CLAUSE: string;
 /** Inherit the source's artistic medium unless told otherwise. */
 export declare const INHERIT_SOURCE_STYLE = "Preserve the artistic medium and visual style of the reference image (photograph, anime, illustration, 3D render, painterly, etc.).";
 /** Environment plate guidance: one clean, naturally-lit establishing image. */
-export declare const ENVIRONMENT_NATURAL_LIGHT = "natural, even ambient lighting that reads as the location's real light, not a studio setup";
-/** One-line summary used as a header in skills + the lead magnet. */
-export declare const REFERENCE_RULES_HEADLINE = "Identity = a few flat-lit neutral angles; one reference per role, labeled; 2-4 refs not 12; describe environments instead of feeding a grid.";
+export declare const ENVIRONMENT_NATURAL_LIGHT = "natural ambient lighting that reads as the location's real light, not a studio setup";
+/**
+ * One-line summary used as a header in skills + the lead magnet. DERIVED from
+ * the partial's opening line — a hand-authored copy here would be a ninth
+ * wording of the same rule, which is the thing this whole mechanism exists to
+ * stop. Edit `skills/_partials/reference-rules-core.md`.
+ */
+export declare const REFERENCE_RULES_HEADLINE: string;
 /**
- * Canonical markdown block — the SOURCE OF TRUTH the skill markdown and the
- * lead-magnet are reconciled AGAINST. NOTE: nothing imports this yet — the
- * skills hand-author their own reference-rule prose and embed-skills.mjs ships
- * the raw .md as-is, so a change here must be propagated to the per-model skill
- * blocks + lead-magnet by hand until the skill-embed wiring lands (see
- * plans/2026-06-25-slates-prompting-system-overhaul.md). The TARGET is to
- * inject this text so it can't drift; today it's reconciled manually.
+ * Canonical markdown block — the SOURCE OF TRUTH for reference-image doctrine
+ * across every Slates surface.
+ *
+ * ✅ WIRED 2026-07-21. This is no longer hand-reconciled prose. The text lives
+ * in `skills/_partials/reference-rules-core.md`; `scripts/sync-partials.mjs`
+ * injects it between the `@inject:reference-rules-core` markers in the
+ * per-model skills AND emits it here via `partials.generated.ts`. One edit to
+ * the partial now moves the markdown skills, this export, the MCP
+ * prompting-guide op, the CLI-installed skills, and the Studio Agent together.
+ *
+ * The build runs `sync-partials.mjs --check`, so a hand-edit inside a marker
+ * block fails the build with a diff instead of silently forking.
+ *
+ * To change reference doctrine: edit `skills/_partials/reference-rules-core.md`.
+ * Do NOT edit this file, and do NOT edit between markers in a skill.
  */
-export declare const REFERENCE_RULES_TEXT = "## Reference rules (how to use reference images)\n\nIdentity = a few flat-lit neutral angles; one reference per role, labeled; 2-4 refs not 12; describe environments instead of feeding a grid.\n\n1. **2-4 strong references beat both extremes.** Not 1 (warps toward itself), not 12 (averages worse). Start with 2-3 focused refs.\n2. **One reference per ROLE, labeled in the prompt.** Identity / style-grade / environment. The model does not infer roles from order \u2014 name each role in the prompt text. Same-role competitors drift.\n3. **Attach both sheets \u2014 NAME them as one entity, don't gate them.** Attach the full-body turnaround (body/proportion/outfit) AND the close-up expression sheet (high-res facial detail: eyes, skin, teeth, bone structure). NAME both inline as the same subject (\"Marcus (images 1 and 2)\") \u2014 the shared name tells the model they are ONE person, which is what stops the varied expressions from averaging the face. Do **not** inject a role essay (\"use for identity, ignore the outfit/lighting, render neutral\") \u2014 that drags the studio-lit sheet's wardrobe + lighting into the scene; the user's prompt owns wardrobe, expression, and lighting. Naming-as-one-entity IS each model's official lever (NB2 \"assign a distinct name\"; Seedance \"Reference Subject_N in Image_N\"; Kling \"reuse a fixed label verbatim\"). The trend is MORE references \u2014 addressing each by name is what makes many refs work.\n4. **Flat-light identity refs.** Prep identity refs with flat, even, shadowless lighting on a plain neutral background. Studio-lit / scene-lit sheets bleed their lighting into every generation (the studio-lit sheet \u2192 \"green-screen-pasted in front of mountains\" failure). Reference prep beats prompting here.\n5. **Environment: describe it, don't feed a grid.** Default to describing the location in words. Reserve an environment reference for a mandatory exact-match, and then use ONE clean establishing image with natural, even ambient lighting that reads as the location's real light, not a studio setup \u2014 never a multi-panel grid fed whole.\n6. **Grids: explore, don't input.** Use grids to explore compositions cheaply, then pick a cell. Never feed a grid back in as a reference \u2014 cells share a split detail budget and generate jointly, so flaws propagate.\n7. **Reuse the same refs across all shots.** Lock a set and reuse it; swapping refs mid-sequence causes drift.\n8. **Legible in-shot text \u2192 bake it into an image start frame, never trust text-to-video.** Animate from the locked frame.\n9. **I2V / own-footage superpower.** Restyle your own clip keeping the performance; delayed-VFX on \"video one\"; marker-object insertion; video-as-ref for a series. Describe ONLY what changes.\n10. **Style transform by natural language.** Default keeps the source's art style; an optional plain-text instruction transforms it (\"anime \u2192 real person\"). No preset pickers.";
+export declare const REFERENCE_RULES_TEXT: string;
 //# sourceMappingURL=reference-rules.d.ts.map

package/dist/prompts/reference-rules.js

@@ -5,6 +5,10 @@
 // Source grades: [Eric-test] = Eric's own hands-on result (doctrine-grade);
 // [community] = multi-guide consensus; [code-verified] = verified against
 // the slate codebase; [creator-demo] = single creator demonstration.
+// The generated partial store — one entry per skills/_partials/*.md file.
+// Re-exported so consumers can reach any partial, not just the rules block.
+export { PARTIALS } from './partials.generated.js';
+import { PARTIALS } from './partials.generated.js';
 /**
  * The 10 verified reference rules. These are the WHY; the fragments below
  * are the reusable text the templates compose.
@@ -26,9 +30,9 @@ export const REFERENCE_RULES = [
     },
     {
         id: 'identity-name-as-one-entity',
-        title: 'Attach both sheets — NAME them as one entity, don\'t gate them',
-        rule: 'Attach BOTH the full-body turnaround (body/proportion/outfit) AND the close-up expression sheet (high-res facial detail). NAME both inline as the SAME subject ("Marcus (images 1 and 2)") — that shared name is what tells the model they are ONE person and stops the varied expressions from averaging the face. Do NOT inject a role essay ("use for identity, ignore the outfit/lighting, render neutral"): the user\'s prompt owns wardrobe, expression, and lighting.',
-        why: 'Naming both images as one entity IS each model\'s OWN official consistency lever — NB2 "assign a distinct name to each character/object"; Seedance "Reference <Subject_N> in <Image_N>"; Kling "reuse a fixed label verbatim". The old heavy role-essay was the OFF-doctrine part: telling the model to "use for identity" while injecting "ignore the outfit" dragged the studio-lit sheet\'s wardrobe + lighting into scenes that explicitly wanted otherwise (the movie-still injection failure). The close-ups still carry far more facial signal (eyes, skin, teeth, bone structure) than a turnaround\'s postage-stamp faces, so attach both — the NAME, not an instruction, is what makes many refs work. The trend is MORE references (video/audio/3D into Seedance-class models), all addressed by name.',
+        title: 'One identity sheet per character, named inline',
+        rule: 'Attach the character\'s single identity sheet (dominant portrait + body panels) rather than a pile of views — fewer competing renderings of a face is better, because the model cannot tell which is authoritative and averages them. Cite it inline as the subject ("Marcus (image 1)"). Do not inject a role essay ("use for identity, ignore the outfit/lighting, render neutral"): the user\'s prompt owns wardrobe, expression, and lighting.',
+        why: 'Distinct inline naming is each model\'s own consistency lever — NB2 "assign a distinct name to each character/object"; Seedance "Reference <Subject_N> in <Image_N>"; Kling "reuse a fixed label verbatim". One canonical identity image removes same-role competition before it starts.',
         grade: 'Eric-test',
     },
     {
@@ -84,37 +88,57 @@ export const REFERENCE_RULES = [
 // ── Reusable text fragments (the template-assembly building blocks) ──
 // These are the exact strings the desktop prompt templates, MCP skills,
 // and lead-magnet compose. Change a rule HERE and every consumer follows.
-/** Flat, even, shadowless identity lighting on a plain neutral background. */
+/** Flat, even, shadowless identity lighting on a deep neutral-grey plate. */
 export const IDENTITY_LIGHTING = 'flat, even, shadowless lighting';
-export const IDENTITY_BACKGROUND = 'a plain neutral-grey background';
+/**
+ * The plate value is deliberate, not decorative: **white bleeds into the
+ * generated video and washes out the location; black eats edge detail and
+ * crushes hair and wardrobe silhouettes.** A deep neutral grey holds both.
+ */
+export const IDENTITY_PLATE_HEX = '#3a3a3c';
+export const IDENTITY_BACKGROUND = `a plain, deep neutral-grey background (${IDENTITY_PLATE_HEX})`;
 export const IDENTITY_LIGHTING_CLAUSE = `Render on ${IDENTITY_BACKGROUND} with ${IDENTITY_LIGHTING} so the sheet captures the character's identity, not scene lighting.`;
+/**
+ * Craft clauses every identity reference wants — the eye and skin detail that
+ * survives downstream, plus the two "reads literally" guards. Crushed-black
+ * irises carry no light information, so eye tone drifts between generations;
+ * no catchlight reads as dead eyes; perfect mirroring reads as synthetic and
+ * the model PRESERVES that reading; a game-render look gets ANIMATED like game
+ * footage. See skills/_partials/references-read-literally.md.
+ */
+export const IDENTITY_CRAFT_CLAUSE = 'Crisp catchlights in the eyes and open, readable irises — never crushed to black. ' +
+    "Render surface texture at the medium's own natural level of detail — skin, hair and fabric should read as material, not airbrushed or plastic. " +
+    'Break perfect symmetry — avoid a mirrored face or dead-square framing. ' +
+    'Whatever the medium, avoid the over-clean 3D-game-model look.';
 /** Inherit the source's artistic medium unless told otherwise. */
 export const INHERIT_SOURCE_STYLE = 'Preserve the artistic medium and visual style of the reference image (photograph, anime, illustration, 3D render, painterly, etc.).';
 /** Environment plate guidance: one clean, naturally-lit establishing image. */
-export const ENVIRONMENT_NATURAL_LIGHT = 'natural, even ambient lighting that reads as the location\'s real light, not a studio setup';
-/** One-line summary used as a header in skills + the lead magnet. */
-export const REFERENCE_RULES_HEADLINE = 'Identity = a few flat-lit neutral angles; one reference per role, labeled; 2-4 refs not 12; describe environments instead of feeding a grid.';
+export const ENVIRONMENT_NATURAL_LIGHT = 'natural ambient lighting that reads as the location\'s real light, not a studio setup';
 /**
- * Canonical markdown block — the SOURCE OF TRUTH the skill markdown and the
- * lead-magnet are reconciled AGAINST. NOTE: nothing imports this yet — the
- * skills hand-author their own reference-rule prose and embed-skills.mjs ships
- * the raw .md as-is, so a change here must be propagated to the per-model skill
- * blocks + lead-magnet by hand until the skill-embed wiring lands (see
- * plans/2026-06-25-slates-prompting-system-overhaul.md). The TARGET is to
- * inject this text so it can't drift; today it's reconciled manually.
+ * One-line summary used as a header in skills + the lead magnet. DERIVED from
+ * the partial's opening line — a hand-authored copy here would be a ninth
+ * wording of the same rule, which is the thing this whole mechanism exists to
+ * stop. Edit `skills/_partials/reference-rules-core.md`.
+ */
+export const REFERENCE_RULES_HEADLINE = PARTIALS['reference-rules-core'].split('\n')[0];
+/**
+ * Canonical markdown block — the SOURCE OF TRUTH for reference-image doctrine
+ * across every Slates surface.
+ *
+ * ✅ WIRED 2026-07-21. This is no longer hand-reconciled prose. The text lives
+ * in `skills/_partials/reference-rules-core.md`; `scripts/sync-partials.mjs`
+ * injects it between the `@inject:reference-rules-core` markers in the
+ * per-model skills AND emits it here via `partials.generated.ts`. One edit to
+ * the partial now moves the markdown skills, this export, the MCP
+ * prompting-guide op, the CLI-installed skills, and the Studio Agent together.
+ *
+ * The build runs `sync-partials.mjs --check`, so a hand-edit inside a marker
+ * block fails the build with a diff instead of silently forking.
+ *
+ * To change reference doctrine: edit `skills/_partials/reference-rules-core.md`.
+ * Do NOT edit this file, and do NOT edit between markers in a skill.
  */
 export const REFERENCE_RULES_TEXT = `## Reference rules (how to use reference images)
 
-${REFERENCE_RULES_HEADLINE}
-
-1. **2-4 strong references beat both extremes.** Not 1 (warps toward itself), not 12 (averages worse). Start with 2-3 focused refs.
-2. **One reference per ROLE, labeled in the prompt.** Identity / style-grade / environment. The model does not infer roles from order — name each role in the prompt text. Same-role competitors drift.
-3. **Attach both sheets — NAME them as one entity, don't gate them.** Attach the full-body turnaround (body/proportion/outfit) AND the close-up expression sheet (high-res facial detail: eyes, skin, teeth, bone structure). NAME both inline as the same subject ("Marcus (images 1 and 2)") — the shared name tells the model they are ONE person, which is what stops the varied expressions from averaging the face. Do **not** inject a role essay ("use for identity, ignore the outfit/lighting, render neutral") — that drags the studio-lit sheet's wardrobe + lighting into the scene; the user's prompt owns wardrobe, expression, and lighting. Naming-as-one-entity IS each model's official lever (NB2 "assign a distinct name"; Seedance "Reference Subject_N in Image_N"; Kling "reuse a fixed label verbatim"). The trend is MORE references — addressing each by name is what makes many refs work.
-4. **Flat-light identity refs.** Prep identity refs with ${IDENTITY_LIGHTING} on a plain neutral background. Studio-lit / scene-lit sheets bleed their lighting into every generation (the studio-lit sheet → "green-screen-pasted in front of mountains" failure). Reference prep beats prompting here.
-5. **Environment: describe it, don't feed a grid.** Default to describing the location in words. Reserve an environment reference for a mandatory exact-match, and then use ONE clean establishing image with ${ENVIRONMENT_NATURAL_LIGHT} — never a multi-panel grid fed whole.
-6. **Grids: explore, don't input.** Use grids to explore compositions cheaply, then pick a cell. Never feed a grid back in as a reference — cells share a split detail budget and generate jointly, so flaws propagate.
-7. **Reuse the same refs across all shots.** Lock a set and reuse it; swapping refs mid-sequence causes drift.
-8. **Legible in-shot text → bake it into an image start frame, never trust text-to-video.** Animate from the locked frame.
-9. **I2V / own-footage superpower.** Restyle your own clip keeping the performance; delayed-VFX on "video one"; marker-object insertion; video-as-ref for a series. Describe ONLY what changes.
-10. **Style transform by natural language.** Default keeps the source's art style; an optional plain-text instruction transforms it ("anime → real person"). No preset pickers.`;
+${PARTIALS['reference-rules-core']}`;
 //# sourceMappingURL=reference-rules.js.map