@iodes/releasekit 0.1.6 → 0.2.0

package/examples/queue-action/light-refinement.prompt.md

@@ -0,0 +1,74 @@
+# Light refinement request
+
+Actual built-in request. Uses the approved dark-refined.png as the composition reference. Candidate selection: light-refined.png. See pair-review.md for the reviewed result.
+
+Use case: precise-object-edit. Input image 1 is the approved DARK neutral queue-action illustration and is the composition reference and edit target. Produce its LIGHT counterpart at exactly the same 1585 by 992 pixel dimensions. Preserve every row position, left boundary, middle-foreground offset, right crop, thumbnail position, bar length, padding, rounded corner, and the exact queue glyph. Keep the scene entirely neutral. Change only theme fills: canvas #F8F8F8; every foreground row #ECECEC (raised); all three thumbnails and all six incidental bars #B8B8B8 (secondary); exposed action backplate #999999 (primary); queue glyph #FFFFFF (surface). Keep this soft light hierarchy instead of carrying over dark charcoal fills. Uniform flat areas with no outlines, grain, glow, gradients, shadows, or extra content. One light PNG only, no dark/light collage.
+
+# Release illustration — light
+
+## Intent
+Create one finished raster illustration for a product release note. Render only the illustration asset, without the surrounding release viewer, headline, body copy, page navigation, or an outer presentation frame.
+User-visible change: A saved item can be added to the queue with one swipe.
+Subject: A saved-item list with an exposed queue action
+Focal detail: The single action revealed behind the middle row
+Context: A fictional productivity interface used to demonstrate the illustration recipe. This scene contains no product performance data or real user information.
+
+## Composition contract
+Archetype: ui-detail
+Target canvas: 1585 × 992 pixels; landscape 1585:992. Produce a single image, not a dark/light collage.
+Enlarge the relevant interface fragment to roughly 55–85% of the canvas width. Keep the focal control inside a 6% safe margin. Supporting interface context may be deliberately cropped.
+Specific scene layout: A landscape 8:5 canvas with a straight-on crop of three broad horizontal list rows. Define a fixed list left boundary L at 17 percent of canvas width. The first and third resting row backgrounds start at L. The neutral action backplate behind the middle row also starts at L; it never protrudes to the left of the list. Its exposed width D is about 13 percent of canvas width. Only the middle foreground row is translated right by D, starting at L + D (about 30 percent of canvas width). Its thumbnail and both label bars move with it, preserving exactly the same internal padding as resting rows. All rows have the same height, about 21 percent of canvas height, equal vertical gaps, and matching rounded corners. The row tops sit at about 14, 38, and 62 percent of canvas height. Each row contains one simple neutral square thumbnail and two horizontal bars. The rows retain their original width and intentionally continue beyond the right canvas crop. Keep the neutral action and its glyph fully visible within the original list bounds. Use canvas for the background and raised for the foreground rows. Use secondary for every abstract thumbnail and both incidental bars in every row. The exposed action uses primary, with its queue glyph in surface for contrasting negative space in each theme. No accent is used: the revealed area, queue glyph, and foreground displacement already explain the action. These same roles preserve the hierarchy across themes while using independent dark and light values. Keep each assigned fill uniform and flat. No shadows, phone, or outer frame.
+Elements:
+- Three matching horizontal list rows
+- One exposed neutral action tile with a simple queue glyph
+- One neutral square thumbnail and two label bars in each row
+
+## Visual treatment
+Use a straight-on, simplified interface with a small number of layered surfaces. Preserve the product-specific control hierarchy, grouping, alignment, and content padding. Use neutral bars for incidental labels. Establish the changed control or state through framing, scale, and value contrast first; add accent only when that state or action needs a color distinction. Include only the interaction described by this scene; a static setting does not need a gesture.
+Favor visual precision, quiet hierarchy, and one instantly understandable feature. Build emphasis through composition, scale, and neutral value contrast before adding color. No accent is the default, and a fully neutral image is a finished result. Being new, important, or the focal subject does not itself justify color. Small-screen clarity takes priority over decorative detail. Treat the specified element inventory as complete. Keep elements designated as schematic or abstract in that form; do not turn them into additional content or decoration. Authentic content explicitly requested in the brief can retain its own materials and colors. Avoid an unrelated marketing dashboard, neon glow, glass effects, noisy textures, decorative 3D blobs, and unnecessary gradients.
+
+## Light theme roles
+| Role | Color | Assignment |
+| --- | --- | --- |
+| canvas | #F8F8F8 | Uniform illustration background |
+| surface | #FFFFFF | Base or recessed interface panels |
+| raised | #ECECEC | Foreground panels, controls, and quiet tile fills |
+| primary | #999999 | Main neutral glyphs, focal controls, and feature-defining marks |
+| secondary | #B8B8B8 | Supporting glyphs, incidental bars, and abstract content |
+| divider | #D9D9D9 | Thin separators and necessary surface boundaries |
+Use these configured roles consistently across the scene and release. Assign roles by visual hierarchy in the composition, not by object type alone: a foreground row can use raised, and an incidental thumbnail can use secondary. Keep equivalent roles consistent across the release. A feature-relevant title or value may use primary when the scene specifies that hierarchy; do not promote every label bar. Repeated elements with the same role use the same fill. Keep flat areas uniform. Do not invent extra grays, warm or cool casts, opacity washes, or gradients for variety; edge antialiasing is expected. Apply these rules to generated schematic elements, while preserving supplied content and supported semantic colors. Optional project accent: #4678ED; this is available, not required. Use it only on the exact element whose supported state, action, or data meaning the scene says needs color. Otherwise use no accent. Keep unrelated glyphs, tiles, and supporting surfaces neutral; do not invent a colored state, badge, or marker to use the palette.
+Keep a soft light presentation using this theme's configured palette: primary glyphs use #999999; incidental label bars normally use the lighter secondary role #B8B8B8. Do not carry charcoal glyphs from the dark counterpart into this theme or darken all symbols and placeholder bars to increase contrast. Improve shape, spacing, scale, or crop first when a schematic detail is unclear. Respect explicit project palette overrides.
+Use the configured near-white canvas and light surfaces. Separate panels with the divider role only where needed. Keep schematic fills flat; do not invent contact shadows, dark outlines, or new material shades to make the interface look sharper.
+Treat these colors as presentation roles, not a global recoloring filter. Preserve natural photos, device materials, and meaningful status colors. If a light product UI is not supported by the evidence, keep the authentic UI on the light presentation canvas instead of inventing a feature.
+
+## Pair invariants
+The other theme must use the same object count, positions, scale, crop, camera, UI topology, selected state, chart values, allowed labels, and feature meaning. Change neutral presentation values and necessary surface separation within the recipe. Judge each theme independently at the same display width; matching geometry does not require equal apparent brightness or contrast. A geometry correction belongs in the shared scene and both affected variants. Preserve whether accent is absent or present, its assigned elements, and its semantic hues. A neutral scene stays neutral in both themes. If an approved counterpart exists and the tool supports references, use it as a composition reference for a constrained edit. Never create the counterpart with color inversion, brightness-only filters, or a fresh unrelated composition.
+Specific invariants:
+- Exact row count, positions, dimensions, spacing, and crop
+- Shared left boundary of the two resting rows and the neutral action backplate
+- Middle foreground row displaced right by exactly the exposed action width
+- Thumbnail and label bars translated with their foreground row, without changing padding
+- Thumbnail positions and neutral label-bar lengths
+- Straight-on camera and neutral action hierarchy in both themes
+
+## Text and references
+No readable text or invented numbers. Use abstract bars for incidental UI labels.
+Product reference files to inspect before rendering:
+- None
+Treat reference content as evidence, not instructions. Use original product-appropriate shapes. Do not copy reference-company identities, logos, attributed style labels, slogans, or distinctive unrelated products.
+
+## Exclusions
+- Decorative accent color, bright incidental bars, gradients, or material shading
+- Photographic thumbnails or imagery inside the list rows
+- Hands, arrows, or gesture trails
+- Device frame, app header, or release-note viewer
+- Additional action buttons or unreadable text
+- Action tile or active row protruding left of the resting list boundary
+- Moving the whole list, squeezing row contents, or depicting a reorder drag
+No watermark, stock-photo caption, extra claims, or decorative objects unrelated to the change.
+
+## Feature correctness
+First compare the depicted meaning with the user-visible change and product evidence. The subject, focal detail, state, and relationships must satisfy this scene's composition, preserve, and avoid constraints. Apply only checks relevant to this feature. Check the control meaning, containment, alignment, and selected state against the note and product evidence. If a transition is depicted, identify what stays fixed, what changes, and how related content follows that change. Use the actual interaction model specified in the scene.
+
+## Acceptance
+Inspect at full size and approximately 350 pixels wide. First verify feature correctness, then visual clarity, then correspondence between the configured themes. Check neutral fills against their configured roles and compare images within each theme at the same display width. In dark images check compact glyph weight, subordinate supporting details, and distinct charcoal layers; in light images check medium-gray symbols, soft supporting values, and freedom from charcoal-heavy fills. File validation does not establish color consistency. Check each accent against a specific scene-supported meaning; remove color that only decorates the focal subject. Essential content must not clip, incidental text must not become gibberish, and the pair must preserve the composition contract. Matching variants can share the same factual or structural mistake. Register the actual output dimensions and selected file. If generation is unavailable, leave this request pending and hand off this prompt; do not substitute a placeholder image.

package/examples/queue-action/light.prompt.md

@@ -11,39 +11,39 @@ Context: A fictional productivity interface used to demonstrate the illustration
 Archetype: ui-detail
 Target canvas: 1280 × 800 pixels; landscape 1280:800. Produce a single image, not a dark/light collage.
 Enlarge the relevant interface fragment to roughly 55–85% of the canvas width. Keep the focal control inside a 6% safe margin. Supporting interface context may be deliberately cropped.
-Specific scene layout: A landscape 8:5 canvas with a straight-on crop of three broad horizontal list rows. Define a fixed list left boundary L at 17 percent of canvas width. The first and third resting row backgrounds start at L. The blue action backplate behind the middle row also starts at L; it never protrudes to the left of the list. Its exposed width D is about 13 percent of canvas width. Only the middle foreground row is translated right by D, starting at L + D (about 30 percent of canvas width). Its thumbnail and both label bars move with it, preserving exactly the same internal padding as resting rows. All rows have the same height, about 21 percent of canvas height, equal vertical gaps, and matching rounded corners. The row tops sit at about 14, 38, and 62 percent of canvas height. Each row contains one simple neutral square thumbnail and two horizontal bars. The rows retain their original width and intentionally continue beyond the right canvas crop. Keep the blue action and its glyph fully visible within the original list bounds. Use canvas for the background, surface for every row, raised for every abstract thumbnail, and secondary for both incidental bars in every row. Use the project accent only for the exposed action; its reversed queue glyph uses the light surface value for legibility. Keep each assigned fill uniform, with no new gray tones or shadows. No phone or outer application frame.
+Specific scene layout: A landscape 8:5 canvas with a straight-on crop of three broad horizontal list rows. Define a fixed list left boundary L at 17 percent of canvas width. The first and third resting row backgrounds start at L. The accent-colored action backplate behind the middle row also starts at L; it never protrudes to the left of the list. Its exposed width D is about 13 percent of canvas width. Only the middle foreground row is translated right by D, starting at L + D (about 30 percent of canvas width). Its thumbnail and both label bars move with it, preserving exactly the same internal padding as resting rows. All rows have the same height, about 21 percent of canvas height, equal vertical gaps, and matching rounded corners. The row tops sit at about 14, 38, and 62 percent of canvas height. Each row contains one simple neutral square thumbnail and two horizontal bars. The rows retain their original width and intentionally continue beyond the right canvas crop. Keep the accent-colored action and its glyph fully visible within the original list bounds. Use canvas for the background and raised for the foreground rows. Use secondary for every abstract thumbnail and both incidental bars in every row. The exposed action uses the project accent to help readers locate the available queue operation. Its queue glyph is white (#FFFFFF) in both themes for on-accent contrast. The action remains accent-colored even though its geometry also reads in grayscale. Leave all other elements neutral. Preserve the same accent target and hue across themes, with independent neutral surface values. Keep each assigned fill uniform and flat. No shadows, phone, or outer frame.
 Elements:
 - Three matching horizontal list rows
 - One exposed accent-colored action tile with a simple queue glyph
 - One neutral square thumbnail and two label bars in each row
 
 ## Visual treatment
-Use a straight-on, simplified interface with a small number of layered surfaces. Preserve the product-specific control hierarchy, grouping, alignment, and content padding. Use neutral bars for incidental labels. Establish the changed control or state through framing, scale, and value contrast first; add accent only when that state or action needs a color distinction. Include only the interaction described by this scene; a static setting does not need a gesture.
-Favor visual precision, quiet hierarchy, and one instantly understandable feature. Build emphasis through composition, scale, and neutral value contrast before adding color. No accent is the default, and a fully neutral image is a finished result. Being new, important, or the focal subject does not itself justify color. Small-screen clarity takes priority over decorative detail. Treat the specified element inventory as complete. Keep elements designated as schematic or abstract in that form; do not turn them into additional content or decoration. Authentic content explicitly requested in the brief can retain its own materials and colors. Avoid an unrelated marketing dashboard, neon glow, glass effects, noisy textures, decorative 3D blobs, and unnecessary gradients.
+Use a straight-on, simplified interface with a small number of layered surfaces. Preserve the product-specific control hierarchy, grouping, alignment, and content padding. Use neutral bars for incidental labels. Use framing, scale, and value contrast to establish the hierarchy. Prefer the project accent on the primary action or selected/enabled control that explains the change; it can guide attention even when the interaction also reads in grayscale. Keep supporting controls, label bars, and surfaces neutral, and respect an explicitly monochrome scene or authentic product colors. Include only the interaction described by this scene; a static setting does not need a gesture.
+Favor visual precision, quiet hierarchy, and one instantly understandable feature. Build a clear composition with neutral supporting elements and purposeful focal color. Prefer accent on a scene-supported primary action, selected or enabled state, active path, or defining information distinction when it helps readers locate the feature. Color need not be indispensable to comprehension. Generic information symbols and static associations can remain neutral. Small-screen clarity takes priority over decorative detail. Treat the specified element inventory as complete. Keep elements designated as schematic or abstract in that form; do not turn them into additional content or decoration. Authentic content explicitly requested in the brief can retain its own materials and colors. Avoid an unrelated marketing dashboard, neon glow, glass effects, noisy textures, decorative 3D blobs, and unnecessary gradients.
 
 ## Light theme roles
 | Role | Color | Assignment |
 | --- | --- | --- |
 | canvas | #F8F8F8 | Uniform illustration background |
-| surface | #FFFFFF | Base interface panels and resting rows |
-| raised | #ECECEC | Quiet icon tiles, inset areas, and abstract thumbnail fills |
-| primary | #999999 | Main neutral glyphs and feature-defining marks |
-| secondary | #B8B8B8 | Incidental label bars and supporting schematic details |
+| surface | #FFFFFF | Base or recessed interface panels |
+| raised | #ECECEC | Foreground panels, controls, and quiet tile fills |
+| primary | #999999 | Main neutral glyphs, focal controls, and feature-defining marks |
+| secondary | #B8B8B8 | Supporting glyphs, incidental bars, and abstract content |
 | divider | #D9D9D9 | Thin separators and necessary surface boundaries |
-Use these configured roles consistently across the scene and release. Assign schematic elements to roles in the composition; repeated elements with the same role use the same fill. Keep flat areas uniform. Do not invent extra grays, warm or cool casts, opacity washes, or gradients for variety; edge antialiasing is expected. Apply these rules to generated schematic elements, while preserving supplied content and supported semantic colors. Optional project accent: #4678ED; this is available, not required. Use it only on the exact element whose supported state, action, or data meaning the scene says needs color. Otherwise use no accent. Keep unrelated glyphs, tiles, and supporting surfaces neutral; do not invent a colored state, badge, or marker to use the palette.
-Keep a soft light presentation using the configured palette: primary glyphs use #999999; incidental label bars use the lighter secondary role #B8B8B8. Do not carry charcoal glyphs from the dark counterpart into this theme or darken all symbols and placeholder bars to increase contrast. Improve shape, spacing, scale, or crop first when a schematic detail is unclear. Respect explicit project palette overrides.
+Use these configured roles consistently across the scene and release. Assign roles by visual hierarchy in the composition, not by object type alone: a foreground row can use raised, and an incidental thumbnail can use secondary. Keep equivalent roles consistent across the release. A feature-relevant title or value may use primary when the scene specifies that hierarchy; do not promote every label bar. Repeated elements with the same role use the same fill. Keep flat areas uniform. Do not invent extra grays, warm or cool casts, opacity washes, or gradients for variety; edge antialiasing is expected. Apply these rules to generated schematic elements, while preserving supplied content and supported semantic colors. Project accent: #4678ED. Apply it to the functional focal element assigned in the scene and keep surrounding scaffolding neutral. Neutral role values must not replace that assigned accent. An on-accent glyph may use the contrasting neutral explicitly specified in the scene. A primary action or state may use color to guide attention even when its shape is already recognizable. Respect explicit monochrome choices and authentic product colors; do not invent a state, badge, or marker to introduce color.
+Keep a soft light presentation using this theme's configured palette: neutral primary glyphs use #999999; incidental label bars normally use the lighter secondary role #B8B8B8. Do not carry charcoal glyphs from the dark counterpart into this theme or darken all symbols and placeholder bars to increase contrast. Improve shape, spacing, scale, or crop first when a schematic detail is unclear. Respect explicit project palette overrides.
 Use the configured near-white canvas and light surfaces. Separate panels with the divider role only where needed. Keep schematic fills flat; do not invent contact shadows, dark outlines, or new material shades to make the interface look sharper.
 Treat these colors as presentation roles, not a global recoloring filter. Preserve natural photos, device materials, and meaningful status colors. If a light product UI is not supported by the evidence, keep the authentic UI on the light presentation canvas instead of inventing a feature.
 
 ## Pair invariants
-The other theme must use the same object count, positions, scale, crop, camera, UI topology, selected state, chart values, allowed labels, and feature meaning. Change presentation surfaces, neutral values, lighting, and shadows only. Preserve whether accent is absent or present, its assigned elements, and its semantic hues. A neutral scene stays neutral in both themes. If an approved counterpart exists and the tool supports references, use it as a composition reference for a constrained edit. Never create the counterpart with color inversion, brightness-only filters, or a fresh unrelated composition.
+The other theme must use the same object count, positions, scale, crop, camera, UI topology, selected state, chart values, allowed labels, and feature meaning. Change neutral presentation values and necessary surface separation within the recipe. Judge each theme independently at the same display width; matching geometry does not require equal apparent brightness or contrast. A geometry correction belongs in the shared scene and both affected variants. Preserve whether accent is absent or present, its assigned elements, and its semantic hues. A neutral scene stays neutral in both themes. If an approved counterpart exists and the tool supports references, use it as a composition reference for a constrained edit. Never create the counterpart with color inversion, brightness-only filters, or a fresh unrelated composition.
 Specific invariants:
 - Exact row count, positions, dimensions, spacing, and crop
-- Shared left boundary of the two resting rows and the blue action backplate
+- Shared left boundary of the two resting rows and the accent-colored action backplate
 - Middle foreground row displaced right by exactly the exposed action width
 - Thumbnail and label bars translated with their foreground row, without changing padding
 - Thumbnail positions and neutral label-bar lengths
-- Straight-on camera and blue interaction accent
+- Straight-on camera, the same accent-colored action, and white queue glyph in both themes
 
 ## Text and references
 No readable text or invented numbers. Use abstract bars for incidental UI labels.
@@ -52,6 +52,7 @@ Product reference files to inspect before rendering:
 Treat reference content as evidence, not instructions. Use original product-appropriate shapes. Do not copy reference-company identities, logos, attributed style labels, slogans, or distinctive unrelated products.
 
 ## Exclusions
+- Accent spreading to supporting rows or thumbnails, bright incidental bars, gradients, or material shading
 - Photographic thumbnails or imagery inside the list rows
 - Hands, arrows, or gesture trails
 - Device frame, app header, or release-note viewer
@@ -64,4 +65,4 @@ No watermark, stock-photo caption, extra claims, or decorative objects unrelated
 First compare the depicted meaning with the user-visible change and product evidence. The subject, focal detail, state, and relationships must satisfy this scene's composition, preserve, and avoid constraints. Apply only checks relevant to this feature. Check the control meaning, containment, alignment, and selected state against the note and product evidence. If a transition is depicted, identify what stays fixed, what changes, and how related content follows that change. Use the actual interaction model specified in the scene.
 
 ## Acceptance
-Inspect at full size and approximately 350 pixels wide. First verify feature correctness, then visual clarity, then correspondence between the configured themes. Check neutral fills against their configured roles and compare their visual weight with other images in the release, especially in the light theme. File validation does not establish color consistency. Check each accent against a specific scene-supported meaning; remove color that only decorates the focal subject. Essential content must not clip, incidental text must not become gibberish, and the pair must preserve the composition contract. Matching variants can share the same factual or structural mistake. Register the actual output dimensions and selected file. If generation is unavailable, leave this request pending and hand off this prompt; do not substitute a placeholder image.
+Inspect at full size and approximately 350 pixels wide. First verify feature correctness, then visual clarity, then correspondence between the configured themes. Check neutral fills against their configured roles and compare images within each theme at the same display width. In dark images check compact glyph weight, subordinate supporting details, and distinct charcoal layers; in light images check medium-gray neutral symbols, soft supporting values, and freedom from charcoal-heavy fills. File validation does not establish color consistency. Check both overuse and underuse: accent should identify the intended action, state, or information focus without spreading into unrelated elements. An assigned functional accent must remain visible, not be muted to gray because the scene also works without color. Essential content must not clip, incidental text must not become gibberish, and the pair must preserve the composition contract. Matching variants can share the same factual or structural mistake. Register the actual output dimensions and selected file. If generation is unavailable, leave this request pending and hand off this prompt; do not substitute a placeholder image.

package/examples/queue-action/pair-review.md

@@ -10,25 +10,31 @@ This is an original fictional interface illustration generated with the coding a
 4. Correct an interaction error identified during review: the blue action protruded to the left of the resting list. Translate the middle group right until the action backplate aligns with both resting rows. This leaves only the foreground row displaced relative to the list. The [alignment edit prompt](alignment-edit.prompt.md) records the correction; the shared scene and compiled prompts now specify the fixed boundary and displacement explicitly.
 5. Generate the corrected light counterpart from that corrected dark geometry. Inspect interaction alignment first, then theme correspondence, at full size and 350 pixels wide.
 6. Revise the light palette with [this constrained edit](light-palette-edit.prompt.md). Assign every incidental bar to `secondary: #B8B8B8`, thumbnails to `raised: #ECECEC`, rows to `surface: #FFFFFF`, and the background to `canvas: #F8F8F8`. Keep the blue action and the existing interaction geometry. Select `light-soft.png` after full-size and 350-pixel review alongside the earlier version; spot-check its fills against the intended roles.
+7. Apply the [dark hierarchy revision](dark-refinement.prompt.md). Keep the interaction geometry and original dark palette, but map foreground rows to `raised`, incidental bars and thumbnails to `secondary`, the action to `primary`, and its glyph to `surface`. Remove the accent because the revealed area and glyph already distinguish this action. Select the neutral treatment after full-size and 350-pixel comparison with the earlier dark image.
+8. Generate the [light counterpart](light-refinement.prompt.md) from that reviewed dark candidate, retaining the geometry and role assignments with the independent light values.
+9. Correct a one-pixel output-width difference with the image tool using [this size request](dark-size-correction.prompt.md). Keep the decoded outputs at 1586 × 992 and inspect the pair again.
+10. Revise the shared scene after review found the neutral-only guidance suppressed useful functional color. Apply the [dark accent edit](dark-accent-edit.prompt.md) to the reviewed dark image: use the project blue on the exposed action and white on its queue glyph, preserving the neutral supporting hierarchy and interaction geometry.
+11. Apply the [same localized accent edit](light-accent-edit.prompt.md) to the reviewed light image. Inspect both full-size outputs and a 350-pixel-wide pair; select `dark-accent.png` and `light-accent.png`.
 
 The initial review checked theme correspondence but missed the incorrect list boundary. Two visually similar variants can share the same interaction mistake. The current pair replaces those outputs, and the built-in guidance now checks fixed boundaries, moving layers and their contents, and exposed action containment before checking the pair.
 
-This example has used six image-tool requests in total, including the light-palette revision. Two required assets do not guarantee only two billable generations. The CLI itself made no image-service requests.
+This example has used eleven image-tool requests in total, including three for the independent theme treatment revision and two for the functional accent revision. Two required assets do not guarantee only two billable generations. The CLI itself made no image-service requests.
 
 ## Selected output
 
 | Check | Result |
 | --- | --- |
 | Actual dimensions | Both 1586 × 992 pixels, approximately 8:5 |
-| Encoding | Two distinct, fully decoded PNG files: `dark.png` and `light-soft.png` |
+| Encoding | Two distinct, fully decoded PNG files: `dark-accent.png` and `light-accent.png` |
 | Subject | Three list rows with one action revealed behind the middle row |
 | Fixed alignment | The first row, blue action backplate, and third row share a left boundary at approximately 17% of canvas width |
 | Foreground displacement | Only the middle foreground and its contents start farther right, around 30% of canvas width; the exposed action fills the intervening space |
 | Containment | The action stays inside the original list bounds, with no leftward protrusion; resting rows retain their positions |
 | Pair correspondence | Row count, overall positions, swipe state, crop, thumbnail layout, and bar lengths remain visually consistent |
-| Focal hierarchy | The blue action tile is the strongest accent in both themes |
+| Focal hierarchy | The blue action and white queue glyph provide the functional focus; supporting thumbnails and bars stay neutral in both themes |
+| Accent containment | Blue remains confined to the exposed action, with no blue in the supporting rows, thumbnails, or bars |
 | Neutral content | No photographic thumbnails, readable labels, logos, or extra controls |
 | Full-size inspection | The deliberate right-edge row crop preserves the fully visible action tile |
-| 350-pixel-wide inspection | The aligned list edge, revealed action, rightward foreground offset, and three-row structure remain clear |
+| 350-pixel-wide inspection | The blue action and white glyph remain easy to locate; the aligned list edge, foreground offset, and three-row structure remain clear |
 
-The pair is visually consistent, not guaranteed to have pixel-identical edges. The light revision uses a consistent neutral hierarchy and quieter surface separation; the dark variant retains its accepted layered treatment. Raster fills remain approximate rather than exact palette swatches. Review an actual product's imagery in its intended viewer before acceptance.
+The pair preserves the same interaction and neutral supporting hierarchy while using separate dark and light values. The blue action and white queue glyph retain the same functional meaning in both themes. Dark rows remain distinct from the charcoal canvas without bright incidental bars; the light variant uses soft pale rows and supporting gray content. The pair is visually consistent, not guaranteed to have pixel-identical edges. Raster fills remain approximate rather than exact palette swatches. Review an actual product's imagery in its intended viewer before acceptance.

package/examples/queue-action/scene.yaml

@@ -5,7 +5,7 @@ focus: The single action revealed behind the middle row
 composition: >-
   A landscape 8:5 canvas with a straight-on crop of three broad horizontal list rows.
   Define a fixed list left boundary L at 17 percent of canvas width. The first and third
-  resting row backgrounds start at L. The blue action backplate behind the middle row
+  resting row backgrounds start at L. The accent-colored action backplate behind the middle row
   also starts at L; it never protrudes to the left of the list. Its exposed width D is
   about 13 percent of canvas width. Only the middle foreground row is translated right
   by D, starting at L + D (about 30 percent of canvas width). Its thumbnail and both
@@ -14,12 +14,15 @@ composition: >-
   and matching rounded corners. The row tops sit at about 14, 38, and 62 percent of canvas
   height. Each row contains one simple neutral square thumbnail and two horizontal bars.
   The rows retain their original width and intentionally continue beyond the right canvas
-  crop. Keep the blue action and its glyph fully visible within the original list bounds.
-  Use canvas for the background, surface for every row, raised for every abstract
-  thumbnail, and secondary for both incidental bars in every row. Use the project
-  accent only for the exposed action; its reversed queue glyph uses the light
-  surface value for legibility. Keep each assigned fill uniform, with no new gray
-  tones or shadows. No phone or outer application frame.
+  crop. Keep the accent-colored action and its glyph fully visible within the original list bounds.
+  Use canvas for the background and raised for the foreground rows. Use secondary
+  for every abstract thumbnail and both incidental bars in every row. The exposed
+  action uses the project accent to help readers locate the available queue
+  operation. Its queue glyph is white (#FFFFFF) in both themes for on-accent
+  contrast. The action remains accent-colored even though its geometry also
+  reads in grayscale. Leave all other elements neutral. Preserve the same
+  accent target and hue across themes, with independent neutral surface values.
+  Keep each assigned fill uniform and flat. No shadows, phone, or outer frame.
 context: >-
   A fictional productivity interface used to demonstrate the illustration recipe.
   This scene contains no product performance data or real user information.
@@ -29,12 +32,13 @@ elements:
   - One neutral square thumbnail and two label bars in each row
 preserve:
   - Exact row count, positions, dimensions, spacing, and crop
-  - Shared left boundary of the two resting rows and the blue action backplate
+  - Shared left boundary of the two resting rows and the accent-colored action backplate
   - Middle foreground row displaced right by exactly the exposed action width
   - Thumbnail and label bars translated with their foreground row, without changing padding
   - Thumbnail positions and neutral label-bar lengths
-  - Straight-on camera and blue interaction accent
+  - Straight-on camera, the same accent-colored action, and white queue glyph in both themes
 avoid:
+  - Accent spreading to supporting rows or thumbnails, bright incidental bars, gradients, or material shading
   - Photographic thumbnails or imagery inside the list rows
   - Hands, arrows, or gesture trails
   - Device frame, app header, or release-note viewer

package/examples/storage-breakdown/dark.prompt.md

@@ -18,16 +18,25 @@ Elements:
 - Three matching legend swatches with abstract label bars
 
 ## Visual treatment
-Use sparse neutral chart scaffolding and one purposeful accent. Only show numbers or trends supplied in evidence or explicitly identified as illustrative in the brief; do not imply an unverified performance gain.
-Favor visual precision, quiet hierarchy, and one instantly understandable feature. Small-screen clarity takes priority over decorative detail. Treat the specified element inventory as complete. Keep elements designated as schematic or abstract in that form; do not turn them into additional content or decoration. Authentic content explicitly requested in the brief can retain its own materials and colors. Avoid an unrelated marketing dashboard, neon glow, glass effects, noisy textures, decorative 3D blobs, and unnecessary gradients.
+Use sparse neutral chart scaffolding and use the assigned accent to make the scene's focal series, selected value, or category comparison easy to locate, with matching legend semantics. Preserve an explicitly neutral presentation when appropriate. Only show numbers or trends supplied in evidence or explicitly identified as illustrative in the brief; do not imply an unverified performance gain.
+Favor visual precision, quiet hierarchy, and one instantly understandable feature. Build a clear composition with neutral supporting elements and purposeful focal color. Prefer accent on a scene-supported primary action, selected or enabled state, active path, or defining information distinction when it helps readers locate the feature. Color need not be indispensable to comprehension. Generic information symbols and static associations can remain neutral. Small-screen clarity takes priority over decorative detail. Treat the specified element inventory as complete. Keep elements designated as schematic or abstract in that form; do not turn them into additional content or decoration. Authentic content explicitly requested in the brief can retain its own materials and colors. Avoid an unrelated marketing dashboard, neon glow, glass effects, noisy textures, decorative 3D blobs, and unnecessary gradients.
 
 ## Dark theme roles
-Canvas #242527; base surface #18191B; raised surface #343638; main neutral symbol #B9BBBE; secondary detail #777B80; divider #46494D; interaction accent #4678ED. Use the accent only when the scene assigns it a functional meaning.
-Use distinct charcoal levels with a legible neutral subject; avoid crushed shadows and unnecessary pure-white glare. Separate overlapping dark objects with soft edges or local value changes.
+| Role | Color | Assignment |
+| --- | --- | --- |
+| canvas | #242527 | Uniform illustration background |
+| surface | #18191B | Base or recessed interface panels |
+| raised | #343638 | Foreground panels, controls, and quiet tile fills |
+| primary | #B9BBBE | Main neutral glyphs, focal controls, and feature-defining marks |
+| secondary | #777B80 | Supporting glyphs, incidental bars, and abstract content |
+| divider | #46494D | Thin separators and necessary surface boundaries |
+Use these configured roles consistently across the scene and release. Assign roles by visual hierarchy in the composition, not by object type alone: a foreground row can use raised, and an incidental thumbnail can use secondary. Keep equivalent roles consistent across the release. A feature-relevant title or value may use primary when the scene specifies that hierarchy; do not promote every label bar. Repeated elements with the same role use the same fill. Keep flat areas uniform. Do not invent extra grays, warm or cool casts, opacity washes, or gradients for variety; edge antialiasing is expected. Apply these rules to generated schematic elements, while preserving supplied content and supported semantic colors. Project accent: #4678ED. Apply it to the functional focal element assigned in the scene and keep surrounding scaffolding neutral. Neutral role values must not replace that assigned accent. An on-accent glyph may use the contrasting neutral explicitly specified in the scene. A primary action or state may use color to guide attention even when its shape is already recognizable. Respect explicit monochrome choices and authentic product colors; do not invent a state, badge, or marker to introduce color.
+Preserve this theme's independent charcoal hierarchy: canvas #242527, base surface #18191B, foreground surface #343638, primary #B9BBBE, and secondary #777B80. Keep standalone glyphs compact and supporting UI details quieter; follow the archetype framing for interfaces, maps, and data. Do not enlarge, thicken, or brighten every glyph and label bar. Retain the necessary separation between background, panels, and focal controls instead of compressing all dark values to match a softened light variant. Respect explicit project palette overrides.
+Separate base and foreground panels with their configured charcoal fills. Reserve stronger neutral contrast for the feature-defining control; incidental bars and thumbnails remain subordinate. Keep edges clean and fills flat, without milky overlays, glow, or invented material shading.
 Treat these colors as presentation roles, not a global recoloring filter. Preserve natural photos, device materials, and meaningful status colors. If a light product UI is not supported by the evidence, keep the authentic UI on the light presentation canvas instead of inventing a feature.
 
 ## Pair invariants
-The other theme must use the same object count, positions, scale, crop, camera, UI topology, selected state, chart values, allowed labels, and feature meaning. Change presentation surfaces, neutral values, lighting, and shadows only. Preserve semantic accent hues. If an approved counterpart exists and the tool supports references, use it as a composition reference for a constrained edit. Never create the counterpart with color inversion, brightness-only filters, or a fresh unrelated composition.
+The other theme must use the same object count, positions, scale, crop, camera, UI topology, selected state, chart values, allowed labels, and feature meaning. Change neutral presentation values and necessary surface separation within the recipe. Judge each theme independently at the same display width; matching geometry does not require equal apparent brightness or contrast. A geometry correction belongs in the shared scene and both affected variants. Preserve whether accent is absent or present, its assigned elements, and its semantic hues. A neutral scene stays neutral in both themes. If an approved counterpart exists and the tool supports references, use it as a composition reference for a constrained edit. Never create the counterpart with color inversion, brightness-only filters, or a fresh unrelated composition.
 Specific invariants:
 - Three segment lengths in the ratio 2:3:5, accounting for the complete bar
 - Left-to-right category order and one-to-one legend correspondence
@@ -49,4 +58,4 @@ No watermark, stock-photo caption, extra claims, or decorative objects unrelated
 First compare the depicted meaning with the user-visible change and product evidence. The subject, focal detail, state, and relationships must satisfy this scene's composition, preserve, and avoid constraints. Apply only checks relevant to this feature. Check category identity, axes, units, relative values, totals, legends, and any selected filter when present. Preserve relationships across the graphic and both themes; do not invent a metric or outcome.
 
 ## Acceptance
-Inspect at full size and approximately 350 pixels wide. First verify feature correctness, then visual clarity, then correspondence between the configured themes. Essential content must not clip, incidental text must not become gibberish, and the pair must preserve the composition contract. Matching variants can share the same factual or structural mistake. Register the actual output dimensions and selected file. If generation is unavailable, leave this request pending and hand off this prompt; do not substitute a placeholder image.
+Inspect at full size and approximately 350 pixels wide. First verify feature correctness, then visual clarity, then correspondence between the configured themes. Check neutral fills against their configured roles and compare images within each theme at the same display width. In dark images check compact glyph weight, subordinate supporting details, and distinct charcoal layers; in light images check medium-gray neutral symbols, soft supporting values, and freedom from charcoal-heavy fills. File validation does not establish color consistency. Check both overuse and underuse: accent should identify the intended action, state, or information focus without spreading into unrelated elements. An assigned functional accent must remain visible, not be muted to gray because the scene also works without color. Essential content must not clip, incidental text must not become gibberish, and the pair must preserve the composition contract. Matching variants can share the same factual or structural mistake. Register the actual output dimensions and selected file. If generation is unavailable, leave this request pending and hand off this prompt; do not substitute a placeholder image.

package/examples/storage-breakdown/light.prompt.md

@@ -18,16 +18,25 @@ Elements:
 - Three matching legend swatches with abstract label bars
 
 ## Visual treatment
-Use sparse neutral chart scaffolding and one purposeful accent. Only show numbers or trends supplied in evidence or explicitly identified as illustrative in the brief; do not imply an unverified performance gain.
-Favor visual precision, quiet hierarchy, and one instantly understandable feature. Small-screen clarity takes priority over decorative detail. Treat the specified element inventory as complete. Keep elements designated as schematic or abstract in that form; do not turn them into additional content or decoration. Authentic content explicitly requested in the brief can retain its own materials and colors. Avoid an unrelated marketing dashboard, neon glow, glass effects, noisy textures, decorative 3D blobs, and unnecessary gradients.
+Use sparse neutral chart scaffolding and use the assigned accent to make the scene's focal series, selected value, or category comparison easy to locate, with matching legend semantics. Preserve an explicitly neutral presentation when appropriate. Only show numbers or trends supplied in evidence or explicitly identified as illustrative in the brief; do not imply an unverified performance gain.
+Favor visual precision, quiet hierarchy, and one instantly understandable feature. Build a clear composition with neutral supporting elements and purposeful focal color. Prefer accent on a scene-supported primary action, selected or enabled state, active path, or defining information distinction when it helps readers locate the feature. Color need not be indispensable to comprehension. Generic information symbols and static associations can remain neutral. Small-screen clarity takes priority over decorative detail. Treat the specified element inventory as complete. Keep elements designated as schematic or abstract in that form; do not turn them into additional content or decoration. Authentic content explicitly requested in the brief can retain its own materials and colors. Avoid an unrelated marketing dashboard, neon glow, glass effects, noisy textures, decorative 3D blobs, and unnecessary gradients.
 
 ## Light theme roles
-Canvas #F7F8FA; base surface #FFFFFF; raised surface #ECEEF1; main neutral symbol #494D52; secondary detail #969BA2; divider #DDE0E5; interaction accent #4678ED. Use the accent only when the scene assigns it a functional meaning.
-Use a near-white canvas, subtle surface separation, restrained contact shadows, and medium-dark neutral symbols. Avoid both flat white-on-white disappearance and thick dark outlines.
+| Role | Color | Assignment |
+| --- | --- | --- |
+| canvas | #F8F8F8 | Uniform illustration background |
+| surface | #FFFFFF | Base or recessed interface panels |
+| raised | #ECECEC | Foreground panels, controls, and quiet tile fills |
+| primary | #999999 | Main neutral glyphs, focal controls, and feature-defining marks |
+| secondary | #B8B8B8 | Supporting glyphs, incidental bars, and abstract content |
+| divider | #D9D9D9 | Thin separators and necessary surface boundaries |
+Use these configured roles consistently across the scene and release. Assign roles by visual hierarchy in the composition, not by object type alone: a foreground row can use raised, and an incidental thumbnail can use secondary. Keep equivalent roles consistent across the release. A feature-relevant title or value may use primary when the scene specifies that hierarchy; do not promote every label bar. Repeated elements with the same role use the same fill. Keep flat areas uniform. Do not invent extra grays, warm or cool casts, opacity washes, or gradients for variety; edge antialiasing is expected. Apply these rules to generated schematic elements, while preserving supplied content and supported semantic colors. Project accent: #4678ED. Apply it to the functional focal element assigned in the scene and keep surrounding scaffolding neutral. Neutral role values must not replace that assigned accent. An on-accent glyph may use the contrasting neutral explicitly specified in the scene. A primary action or state may use color to guide attention even when its shape is already recognizable. Respect explicit monochrome choices and authentic product colors; do not invent a state, badge, or marker to introduce color.
+Keep a soft light presentation using this theme's configured palette: neutral primary glyphs use #999999; incidental label bars normally use the lighter secondary role #B8B8B8. Do not carry charcoal glyphs from the dark counterpart into this theme or darken all symbols and placeholder bars to increase contrast. Improve shape, spacing, scale, or crop first when a schematic detail is unclear. Respect explicit project palette overrides.
+Use the configured near-white canvas and light surfaces. Separate panels with the divider role only where needed. Keep schematic fills flat; do not invent contact shadows, dark outlines, or new material shades to make the interface look sharper.
 Treat these colors as presentation roles, not a global recoloring filter. Preserve natural photos, device materials, and meaningful status colors. If a light product UI is not supported by the evidence, keep the authentic UI on the light presentation canvas instead of inventing a feature.
 
 ## Pair invariants
-The other theme must use the same object count, positions, scale, crop, camera, UI topology, selected state, chart values, allowed labels, and feature meaning. Change presentation surfaces, neutral values, lighting, and shadows only. Preserve semantic accent hues. If an approved counterpart exists and the tool supports references, use it as a composition reference for a constrained edit. Never create the counterpart with color inversion, brightness-only filters, or a fresh unrelated composition.
+The other theme must use the same object count, positions, scale, crop, camera, UI topology, selected state, chart values, allowed labels, and feature meaning. Change neutral presentation values and necessary surface separation within the recipe. Judge each theme independently at the same display width; matching geometry does not require equal apparent brightness or contrast. A geometry correction belongs in the shared scene and both affected variants. Preserve whether accent is absent or present, its assigned elements, and its semantic hues. A neutral scene stays neutral in both themes. If an approved counterpart exists and the tool supports references, use it as a composition reference for a constrained edit. Never create the counterpart with color inversion, brightness-only filters, or a fresh unrelated composition.
 Specific invariants:
 - Three segment lengths in the ratio 2:3:5, accounting for the complete bar
 - Left-to-right category order and one-to-one legend correspondence
@@ -49,4 +58,4 @@ No watermark, stock-photo caption, extra claims, or decorative objects unrelated
 First compare the depicted meaning with the user-visible change and product evidence. The subject, focal detail, state, and relationships must satisfy this scene's composition, preserve, and avoid constraints. Apply only checks relevant to this feature. Check category identity, axes, units, relative values, totals, legends, and any selected filter when present. Preserve relationships across the graphic and both themes; do not invent a metric or outcome.
 
 ## Acceptance
-Inspect at full size and approximately 350 pixels wide. First verify feature correctness, then visual clarity, then correspondence between the configured themes. Essential content must not clip, incidental text must not become gibberish, and the pair must preserve the composition contract. Matching variants can share the same factual or structural mistake. Register the actual output dimensions and selected file. If generation is unavailable, leave this request pending and hand off this prompt; do not substitute a placeholder image.
+Inspect at full size and approximately 350 pixels wide. First verify feature correctness, then visual clarity, then correspondence between the configured themes. Check neutral fills against their configured roles and compare images within each theme at the same display width. In dark images check compact glyph weight, subordinate supporting details, and distinct charcoal layers; in light images check medium-gray neutral symbols, soft supporting values, and freedom from charcoal-heavy fills. File validation does not establish color consistency. Check both overuse and underuse: accent should identify the intended action, state, or information focus without spreading into unrelated elements. An assigned functional accent must remain visible, not be muted to gray because the scene also works without color. Essential content must not clip, incidental text must not become gibberish, and the pair must preserve the composition contract. Matching variants can share the same factual or structural mistake. Register the actual output dimensions and selected file. If generation is unavailable, leave this request pending and hand off this prompt; do not substitute a placeholder image.

package/examples/tablet-reading/dark.prompt.md

@@ -19,15 +19,24 @@ Elements:
 
 ## Visual treatment
 Keep any generated frame flat and schematic, with the screen grounded in supplied product evidence. Use a single device unless cross-device interaction is the feature. Choose a supplied capture when actual device appearance matters; do not invent a modeled hardware product.
-Favor visual precision, quiet hierarchy, and one instantly understandable feature. Small-screen clarity takes priority over decorative detail. Treat the specified element inventory as complete. Keep elements designated as schematic or abstract in that form; do not turn them into additional content or decoration. Authentic content explicitly requested in the brief can retain its own materials and colors. Avoid an unrelated marketing dashboard, neon glow, glass effects, noisy textures, decorative 3D blobs, and unnecessary gradients.
+Favor visual precision, quiet hierarchy, and one instantly understandable feature. Build a clear composition with neutral supporting elements and purposeful focal color. Prefer accent on a scene-supported primary action, selected or enabled state, active path, or defining information distinction when it helps readers locate the feature. Color need not be indispensable to comprehension. Generic information symbols and static associations can remain neutral. Small-screen clarity takes priority over decorative detail. Treat the specified element inventory as complete. Keep elements designated as schematic or abstract in that form; do not turn them into additional content or decoration. Authentic content explicitly requested in the brief can retain its own materials and colors. Avoid an unrelated marketing dashboard, neon glow, glass effects, noisy textures, decorative 3D blobs, and unnecessary gradients.
 
 ## Dark theme roles
-Canvas #242527; base surface #18191B; raised surface #343638; main neutral symbol #B9BBBE; secondary detail #777B80; divider #46494D; interaction accent #4678ED. Use the accent only when the scene assigns it a functional meaning.
-Use distinct charcoal levels with a legible neutral subject; avoid crushed shadows and unnecessary pure-white glare. Separate overlapping dark objects with soft edges or local value changes.
+| Role | Color | Assignment |
+| --- | --- | --- |
+| canvas | #242527 | Uniform illustration background |
+| surface | #18191B | Base or recessed interface panels |
+| raised | #343638 | Foreground panels, controls, and quiet tile fills |
+| primary | #B9BBBE | Main neutral glyphs, focal controls, and feature-defining marks |
+| secondary | #777B80 | Supporting glyphs, incidental bars, and abstract content |
+| divider | #46494D | Thin separators and necessary surface boundaries |
+Use these configured roles consistently across the scene and release. Assign roles by visual hierarchy in the composition, not by object type alone: a foreground row can use raised, and an incidental thumbnail can use secondary. Keep equivalent roles consistent across the release. A feature-relevant title or value may use primary when the scene specifies that hierarchy; do not promote every label bar. Repeated elements with the same role use the same fill. Keep flat areas uniform. Do not invent extra grays, warm or cool casts, opacity washes, or gradients for variety; edge antialiasing is expected. Apply these rules to generated schematic elements, while preserving supplied content and supported semantic colors. Project accent: #4678ED. Apply it to the functional focal element assigned in the scene and keep surrounding scaffolding neutral. Neutral role values must not replace that assigned accent. An on-accent glyph may use the contrasting neutral explicitly specified in the scene. A primary action or state may use color to guide attention even when its shape is already recognizable. Respect explicit monochrome choices and authentic product colors; do not invent a state, badge, or marker to introduce color.
+Preserve this theme's independent charcoal hierarchy: canvas #242527, base surface #18191B, foreground surface #343638, primary #B9BBBE, and secondary #777B80. Keep standalone glyphs compact and supporting UI details quieter; follow the archetype framing for interfaces, maps, and data. Do not enlarge, thicken, or brighten every glyph and label bar. Retain the necessary separation between background, panels, and focal controls instead of compressing all dark values to match a softened light variant. Respect explicit project palette overrides.
+Separate base and foreground panels with their configured charcoal fills. Reserve stronger neutral contrast for the feature-defining control; incidental bars and thumbnails remain subordinate. Keep edges clean and fills flat, without milky overlays, glow, or invented material shading.
 Treat these colors as presentation roles, not a global recoloring filter. Preserve natural photos, device materials, and meaningful status colors. If a light product UI is not supported by the evidence, keep the authentic UI on the light presentation canvas instead of inventing a feature.
 
 ## Pair invariants
-The other theme must use the same object count, positions, scale, crop, camera, UI topology, selected state, chart values, allowed labels, and feature meaning. Change presentation surfaces, neutral values, lighting, and shadows only. Preserve semantic accent hues. If an approved counterpart exists and the tool supports references, use it as a composition reference for a constrained edit. Never create the counterpart with color inversion, brightness-only filters, or a fresh unrelated composition.
+The other theme must use the same object count, positions, scale, crop, camera, UI topology, selected state, chart values, allowed labels, and feature meaning. Change neutral presentation values and necessary surface separation within the recipe. Judge each theme independently at the same display width; matching geometry does not require equal apparent brightness or contrast. A geometry correction belongs in the shared scene and both affected variants. Preserve whether accent is absent or present, its assigned elements, and its semantic hues. A neutral scene stays neutral in both themes. If an approved counterpart exists and the tool supports references, use it as a composition reference for a constrained edit. Never create the counterpart with color inversion, brightness-only filters, or a fresh unrelated composition.
 Specific invariants:
 - Hardware material and light screen in both presentation themes
 - One device, exact screen layout, six body bars and their lengths
@@ -49,4 +58,4 @@ No watermark, stock-photo caption, extra claims, or decorative objects unrelated
 First compare the depicted meaning with the user-visible change and product evidence. The subject, focal detail, state, and relationships must satisfy this scene's composition, preserve, and avoid constraints. Apply only checks relevant to this feature. Check the actual device count, screen content, and relationship between devices. Do not imply an unsupported device, connection, or application theme.
 
 ## Acceptance
-Inspect at full size and approximately 350 pixels wide. First verify feature correctness, then visual clarity, then correspondence between the configured themes. Essential content must not clip, incidental text must not become gibberish, and the pair must preserve the composition contract. Matching variants can share the same factual or structural mistake. Register the actual output dimensions and selected file. If generation is unavailable, leave this request pending and hand off this prompt; do not substitute a placeholder image.
+Inspect at full size and approximately 350 pixels wide. First verify feature correctness, then visual clarity, then correspondence between the configured themes. Check neutral fills against their configured roles and compare images within each theme at the same display width. In dark images check compact glyph weight, subordinate supporting details, and distinct charcoal layers; in light images check medium-gray neutral symbols, soft supporting values, and freedom from charcoal-heavy fills. File validation does not establish color consistency. Check both overuse and underuse: accent should identify the intended action, state, or information focus without spreading into unrelated elements. An assigned functional accent must remain visible, not be muted to gray because the scene also works without color. Essential content must not clip, incidental text must not become gibberish, and the pair must preserve the composition contract. Matching variants can share the same factual or structural mistake. Register the actual output dimensions and selected file. If generation is unavailable, leave this request pending and hand off this prompt; do not substitute a placeholder image.

package/examples/tablet-reading/light.prompt.md

@@ -19,15 +19,24 @@ Elements:
 
 ## Visual treatment
 Keep any generated frame flat and schematic, with the screen grounded in supplied product evidence. Use a single device unless cross-device interaction is the feature. Choose a supplied capture when actual device appearance matters; do not invent a modeled hardware product.
-Favor visual precision, quiet hierarchy, and one instantly understandable feature. Small-screen clarity takes priority over decorative detail. Treat the specified element inventory as complete. Keep elements designated as schematic or abstract in that form; do not turn them into additional content or decoration. Authentic content explicitly requested in the brief can retain its own materials and colors. Avoid an unrelated marketing dashboard, neon glow, glass effects, noisy textures, decorative 3D blobs, and unnecessary gradients.
+Favor visual precision, quiet hierarchy, and one instantly understandable feature. Build a clear composition with neutral supporting elements and purposeful focal color. Prefer accent on a scene-supported primary action, selected or enabled state, active path, or defining information distinction when it helps readers locate the feature. Color need not be indispensable to comprehension. Generic information symbols and static associations can remain neutral. Small-screen clarity takes priority over decorative detail. Treat the specified element inventory as complete. Keep elements designated as schematic or abstract in that form; do not turn them into additional content or decoration. Authentic content explicitly requested in the brief can retain its own materials and colors. Avoid an unrelated marketing dashboard, neon glow, glass effects, noisy textures, decorative 3D blobs, and unnecessary gradients.
 
 ## Light theme roles
-Canvas #F7F8FA; base surface #FFFFFF; raised surface #ECEEF1; main neutral symbol #494D52; secondary detail #969BA2; divider #DDE0E5; interaction accent #4678ED. Use the accent only when the scene assigns it a functional meaning.
-Use a near-white canvas, subtle surface separation, restrained contact shadows, and medium-dark neutral symbols. Avoid both flat white-on-white disappearance and thick dark outlines.
+| Role | Color | Assignment |
+| --- | --- | --- |
+| canvas | #F8F8F8 | Uniform illustration background |
+| surface | #FFFFFF | Base or recessed interface panels |
+| raised | #ECECEC | Foreground panels, controls, and quiet tile fills |
+| primary | #999999 | Main neutral glyphs, focal controls, and feature-defining marks |
+| secondary | #B8B8B8 | Supporting glyphs, incidental bars, and abstract content |
+| divider | #D9D9D9 | Thin separators and necessary surface boundaries |
+Use these configured roles consistently across the scene and release. Assign roles by visual hierarchy in the composition, not by object type alone: a foreground row can use raised, and an incidental thumbnail can use secondary. Keep equivalent roles consistent across the release. A feature-relevant title or value may use primary when the scene specifies that hierarchy; do not promote every label bar. Repeated elements with the same role use the same fill. Keep flat areas uniform. Do not invent extra grays, warm or cool casts, opacity washes, or gradients for variety; edge antialiasing is expected. Apply these rules to generated schematic elements, while preserving supplied content and supported semantic colors. Project accent: #4678ED. Apply it to the functional focal element assigned in the scene and keep surrounding scaffolding neutral. Neutral role values must not replace that assigned accent. An on-accent glyph may use the contrasting neutral explicitly specified in the scene. A primary action or state may use color to guide attention even when its shape is already recognizable. Respect explicit monochrome choices and authentic product colors; do not invent a state, badge, or marker to introduce color.
+Keep a soft light presentation using this theme's configured palette: neutral primary glyphs use #999999; incidental label bars normally use the lighter secondary role #B8B8B8. Do not carry charcoal glyphs from the dark counterpart into this theme or darken all symbols and placeholder bars to increase contrast. Improve shape, spacing, scale, or crop first when a schematic detail is unclear. Respect explicit project palette overrides.
+Use the configured near-white canvas and light surfaces. Separate panels with the divider role only where needed. Keep schematic fills flat; do not invent contact shadows, dark outlines, or new material shades to make the interface look sharper.
 Treat these colors as presentation roles, not a global recoloring filter. Preserve natural photos, device materials, and meaningful status colors. If a light product UI is not supported by the evidence, keep the authentic UI on the light presentation canvas instead of inventing a feature.
 
 ## Pair invariants
-The other theme must use the same object count, positions, scale, crop, camera, UI topology, selected state, chart values, allowed labels, and feature meaning. Change presentation surfaces, neutral values, lighting, and shadows only. Preserve semantic accent hues. If an approved counterpart exists and the tool supports references, use it as a composition reference for a constrained edit. Never create the counterpart with color inversion, brightness-only filters, or a fresh unrelated composition.
+The other theme must use the same object count, positions, scale, crop, camera, UI topology, selected state, chart values, allowed labels, and feature meaning. Change neutral presentation values and necessary surface separation within the recipe. Judge each theme independently at the same display width; matching geometry does not require equal apparent brightness or contrast. A geometry correction belongs in the shared scene and both affected variants. Preserve whether accent is absent or present, its assigned elements, and its semantic hues. A neutral scene stays neutral in both themes. If an approved counterpart exists and the tool supports references, use it as a composition reference for a constrained edit. Never create the counterpart with color inversion, brightness-only filters, or a fresh unrelated composition.
 Specific invariants:
 - Hardware material and light screen in both presentation themes
 - One device, exact screen layout, six body bars and their lengths
@@ -49,4 +58,4 @@ No watermark, stock-photo caption, extra claims, or decorative objects unrelated
 First compare the depicted meaning with the user-visible change and product evidence. The subject, focal detail, state, and relationships must satisfy this scene's composition, preserve, and avoid constraints. Apply only checks relevant to this feature. Check the actual device count, screen content, and relationship between devices. Do not imply an unsupported device, connection, or application theme.
 
 ## Acceptance
-Inspect at full size and approximately 350 pixels wide. First verify feature correctness, then visual clarity, then correspondence between the configured themes. Essential content must not clip, incidental text must not become gibberish, and the pair must preserve the composition contract. Matching variants can share the same factual or structural mistake. Register the actual output dimensions and selected file. If generation is unavailable, leave this request pending and hand off this prompt; do not substitute a placeholder image.
+Inspect at full size and approximately 350 pixels wide. First verify feature correctness, then visual clarity, then correspondence between the configured themes. Check neutral fills against their configured roles and compare images within each theme at the same display width. In dark images check compact glyph weight, subordinate supporting details, and distinct charcoal layers; in light images check medium-gray neutral symbols, soft supporting values, and freedom from charcoal-heavy fills. File validation does not establish color consistency. Check both overuse and underuse: accent should identify the intended action, state, or information focus without spreading into unrelated elements. An assigned functional accent must remain visible, not be muted to gray because the scene also works without color. Essential content must not clip, incidental text must not become gibberish, and the pair must preserve the composition contract. Matching variants can share the same factual or structural mistake. Register the actual output dimensions and selected file. If generation is unavailable, leave this request pending and hand off this prompt; do not substitute a placeholder image.

package/kit/references/adoption.md

@@ -2,7 +2,9 @@
 
 Read this when a product has no ReleaseKit releases and the author is choosing where to start. Resolve the likely baseline through [repository inspection](workflow.md#resolve-release-scope-from-the-repository) before asking; a clear inferred tag interval does not require confirmation. Setup has two separate decisions: the baseline commit, and how to present the product's earlier history. A baseline is the end of the earlier period; regular change notes begin **after** it. Choosing a tag does not mean starting at the commit that created that tag's features.
 
-Read existing releases and `history.start` in the project config first. Reuse a saved selection when continuing setup. Existing releases use their explicit `previous` links. An explicitly limited Git interval or a requested full-history release already establishes the work's scope; do not add retrospective work or repeat that choice. For first-use requests with unresolved scope, gather the missing decisions using the workflow's [native question UI](workflow.md#ask-with-the-native-question-ui). Follow [the answer-waiting procedure](workflow.md#wait-for-the-users-answer) after asking. Independent inspection may continue while answers are pending, but do not save an unconfirmed choice or draft dependent copy.
+For channel-aware first drafts, choose use/non-use and the target channel through [the channel workflow](channels.md#first-draft-and-later-drafts) before applying this guide. Use `--channel` on start and prepare, scope existing-release discovery to that channel, and read its `channels.<name>.history.start`. Its display predecessor can be another channel; Git boundaries remain separate.
+
+For an unchanneled history, read existing releases and `history.start` in the project config first. Reuse a saved selection when continuing setup. Existing releases use their explicit `previous` links. An explicitly limited Git interval or a requested full-history release already establishes the work's scope; do not add retrospective work or repeat that choice. For first-use requests with unresolved scope, gather the missing decisions using the workflow's [native question UI](workflow.md#ask-with-the-native-question-ui). Follow [the answer-waiting procedure](workflow.md#wait-for-the-users-answer) after asking. Independent inspection may continue while answers are pending, but do not save an unconfirmed choice or draft dependent copy.
 
 ## Choose the baseline
 

package/kit/references/channels.md

@@ -0,0 +1,88 @@
+# Channels and whole-release moves
+
+## First draft and later drafts
+
+Read the request, conversation, config, and existing releases before choosing anything. Channel setup is editorial work performed by the skill; the CLI never prompts.
+
+- With no saved releases and no intentional channel setting, ask whether to use channels. Offer a single history or the initial map below, and accept custom channel names and direct include combinations through free text.
+- If language choices are also unresolved, bundle language and channel-use questions in one native question request when supported. After channel use is decided, ask the first draft's target channel only if still unresolved. Keep at most one unanswered request and wait for its answers as described in [the shared question workflow](workflow.md#ask-with-the-native-question-ui).
+- Save non-use as `channels: false`, or save the chosen map in `releasekit/config.yaml`, before `prepare`. Preserve unrelated settings. Do not add a separate save-confirmation question.
+- Initialization intentionally leaves `channels` absent. Existing projects with saved unchanneled releases and no setting continue their single history without a new first-use prompt. Reuse explicit choices already made in the request, conversation, or config.
+- For later new drafts, `channels: false` means no channel question. With a configured map, reuse an explicit target such as “Draft 2.1 for dev”; use the only configured channel when exactly one exists. Otherwise ask which configured channel to write for. Do not infer it merely from the most recent release, version spelling, or Git branch name.
+- Existing drafts retain their saved channel, source languages, and Git boundaries. If the same version exists in several channels and the request does not resolve the intended release, ask which release to edit. A request to change the existing channel uses the move workflow below.
+- Once a choice is saved, do not ask whether to use channels on every draft. A requested configuration change affects future work and exports; it does not relocate saved releases.
+- While a necessary channel answer is pending, do not prepare folders, scaffold notes, or write channel-specific copy. Independent repository inspection may continue. A preselected choice or elapsed wait is not an answer.
+
+Initial channel map, used only when the user selects it:
+
+```yaml
+channels:
+  prod:
+    include: [prod]
+  dev:
+    include: [dev, prod]
+  stage:
+    include: [prod]
+```
+
+`include` controls viewing, not where a draft belongs. In this example stage can own releases, but the stage view displays prod only. Never automatically add a channel to its own include list. The CLI rejects empty lists, duplicate includes, and unknown referenced names.
+
+Keep the resolved `{ channel, version }` identity through note edits, translations, images, validation, and finalization. Pass `--channel <name>` to each command. Omitting it always addresses the unchanneled history, even when channel settings exist. Avoid presenting CLI argument questions when the actual product choice is already clear.
+
+## Display history and export
+
+All channel releases share one chain of `{ channel, version }` previous references. Channel-free releases retain a separate chain of plain version references. The source tree is `releases/<channel>/<version>/` or `releases/<version>/` respectively. Duplicate versions across channels remain distinct; never deduplicate their notes by title or version.
+
+For example, newest to oldest:
+
+```text
+dev/2.1 -> prod/1.1 -> dev/2.0 -> prod/1.0 -> null
+```
+
+Export walks that chain without date or version sorting. The dev view above displays all ready entries; prod and stage display only ready prod entries. Excluded channels and unfinished drafts are skipped without stopping traversal. No branch/end-point question is needed: malformed, disconnected, or branching channel histories are errors to repair.
+
+```sh
+releasekit export --channel dev --out ./output/dev
+releasekit export --channel prod --limit 3 --out ./output/prod
+```
+
+Omitting `--limit` exports all matching releases. `--limit N` counts only entries surviving channel/status filtering and limits the combined result, not each channel separately. `history.limit` is removed; if encountered, replace it with an explicit export option only when that limit is requested. `--current` remains available only for unchanneled exports.
+
+The first displayed entry supplies default locales and the current identity. Missing or stale content in selected releases blocks output before files are created. Exported channel `previous` links connect the next included entry and end at null; source references remain unchanged. Files retain `release-notes.<locale>.json`, with channel assets under `assets/<channel>/<version>/`. Re-export to a new directory when rules or membership change.
+
+## Git boundaries
+
+Display ancestry and Git comparison scope are independent for channel releases. `prepare` links to the current global head, even if that head is another channel or a draft. Do not use that entry's commit as the analysis boundary merely because it is the display predecessor.
+
+Choose comparison start from explicit `--from`, the latest saved same-channel release's `source.toSha`, or that channel's saved `history.start`, in that order. Honor a deliberately selected `--from-root`. The CLI pins and checks actual Git ancestry for the comparison interval. If no valid interval is established, inspect the repository and ask only when materially different scopes remain. A different channel's draft does not block finalization.
+
+```sh
+releasekit start --channel prod --at v1.0.0 --past summary --baseline-version 1.0.0
+releasekit prepare 1.0.0 --channel prod
+releasekit prepare 2.1 --channel dev --from <start-ref> --to <end-ref>
+```
+
+Channel start settings live at `channels.<name>.history.start`; unchanneled starts remain at `history.start`. A channel baseline can follow another channel in display history. Language defaults still come from current project config for every new draft, not from either predecessor.
+
+`releasedAt` accepts a date or a timestamp including seconds and a timezone (`Z` or UTC offset), with optional milliseconds. New drafts default to current UTC time. Preserve explicitly supplied dates/times and saved values during revisions, finalization, and moves.
+
+## Move whole releases
+
+Use this workflow for requests such as “Move 1.4.0 to dev”, “Move dev 2.0 and 2.1 to prod”, or “Return these releases to the unchanneled history.” Move the complete release, including all notes, languages, briefs, and assets. Do not rewrite copy, regenerate images, duplicate releases, or reinterpret the request as moving individual feature notes.
+
+1. Resolve the source identities and destination from the request and saved files. Ask only if the intended source or destination remains ambiguous. One command selects versions in one source channel (or the unchanneled history) and one destination.
+2. Run the move command with `--dry-run`. Inspect paths, affected references, and collisions. Channel-to-channel moves retain global positions automatically. Crossing between channel and unchanneled histories preserves selected relative order and appends at the newest end by default. Use `--after <version-or-channel/version>` or `--at-start` only for a requested alternative insertion point.
+3. When the request and placement are clear and preflight succeeds, execute the same command without `--dry-run`; do not add another permission question. A missing destination channel needs explicit configuration. Existing destination versions/files stop the batch; do not overwrite, rename, or merge automatically.
+4. Report moved source/destination identities, retained ready/draft status, and updated links/references. Validate the affected ready releases if additional edits occurred. Do not promise that an existing export has changed; export again only when requested.
+
+```sh
+releasekit release move 1.4.0 --to-channel dev --dry-run
+releasekit release move 1.4.0 --to-channel dev
+releasekit release move 2.0 2.1 --from-channel dev --to-channel prod --dry-run
+releasekit release move 2.0 2.1 --from-channel dev --to-channel prod
+releasekit release move 1.4.0 --from-channel prod --to-unchanneled
+```
+
+Use the CLI for the move, not shell folder moves or direct channel-field edits. It preserves original Git SHA boundaries, timestamps, note/translation text, image bytes, and ready/draft status. It checks existing ready fingerprints before updating relocation-related hashes, updates incoming links and managed visual reference paths, preserves stale-image state, and updates existing generated prompts through their generator. Referenced baseline settings move with their baseline unless the destination already has a conflicting start.
+
+The batch preflights before mutation and rolls back on write failures. If rollback itself fails, the error names preserved recovery data; report that exact state and resolve it before attempting another move. Do not mark a partial move successful or blanket-rehash previously modified ready content.