@iodes/releasekit 0.1.0 → 0.1.1

package/examples/feature-briefs.yaml

@@ -1,89 +1,96 @@
-- id: backup-encryption
-  releaseNote: Local backup files can now be encrypted before saving.
-  scene:
-    archetype: icon-tile
-    subject: A compact archive symbol with a closed padlock
-    message: Local backup files can be saved with encryption enabled.
-    focus: The closed padlock attached to the archive symbol
-    context: >-
-      Fictional capability illustration, not a shipped product claim. The lock represents
-      encryption of local backup files only; it does not claim protection of every product surface.
-    composition: >-
-      One compact archive silhouette occupies about 22 percent of an 8:5 canvas width,
-      centered optically. One small closed padlock overlaps its lower-right corner as a badge.
-      Keep the archive opening, lock body, and closed shackle distinguishable at small size.
-      Use neutral material values with one restrained accent on the lock. No surrounding interface.
-    elements:
-      - One archive silhouette
-      - One closed padlock badge
-    preserve:
-      - Closed shackle and attachment of the badge to the archive
-      - Relative symbol scale, overlap, and optical center
-    avoid:
-      - Open lock or a success badge implying that every file is already encrypted
-      - Additional devices, shields, or unrelated application controls
-    text: []
-    references: []
-
-- id: quiet-hours
-  releaseNote: Choose a daily time window to silence notifications.
-  scene:
-    archetype: ui-detail
-    subject: A quiet-hours setting with an enabled control and two time fields
-    message: Notifications can be silenced during a chosen daily time window.
-    focus: The enabled quiet-hours control and its associated start and end fields
-    context: >-
-      Fictional settings interface. The depicted state is enabled with a valid configured
-      interval. Exact hours are incidental and should be abstracted rather than invented.
-    composition: >-
-      A single straight-on settings panel occupies about 64 percent of an 8:5 canvas width.
-      A short abstract heading and one enabled toggle share the top group. Beneath them,
-      two equal-width time fields sit side by side inside the same panel, with consistent
-      padding and a clear gap. The left field represents the start and the right the end.
-      Use neutral bars for field labels and values. Accent only the enabled toggle.
-    elements:
-      - One settings panel
-      - One enabled toggle
-      - Two grouped time fields with abstract labels and values
-    preserve:
-      - Enabled toggle state and grouping with the time fields
-      - Start field on the left and end field on the right
-      - Equal field dimensions and containment inside the panel
-    avoid:
-      - Motion cues or unrelated gestures
-      - Literal hours or an extra scheduling capability absent from the note
-      - Disabled appearance while the control is enabled
-    text: []
-    references: []
-
-- id: storage-breakdown
-  releaseNote: View how saved files use storage by category.
-  scene:
-    archetype: data-view
-    subject: A storage breakdown with three categories
-    message: A category breakdown shows how saved files use storage.
-    focus: One stacked bar and its matching category legend
-    context: >-
-      Fictional view illustration. The proportions 20, 30, and 50 percent are explicitly
-      illustrative and are not measurements or a claim of improved storage efficiency.
-    composition: >-
-      A single panel occupies about 68 percent of an 8:5 canvas width. One horizontal
-      stacked bar contains three contiguous segments with lengths in the ratio 2:3:5.
-      Below it, three equally spaced legend items appear in the same order as the segments.
-      Each legend item has one matching swatch and an abstract label bar. The first two
-      categories use distinguishable neutral values; the largest category uses the accent.
-      Omit literal numbers, axes, trend lines, and unrelated controls.
-    elements:
-      - One panel
-      - One stacked bar containing exactly three contiguous segments
-      - Three matching legend swatches with abstract label bars
-    preserve:
-      - 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
-      - Accent assigned to the same largest category in both themes
-    avoid:
-      - Invented performance improvement or additional metrics
-      - Gaps, overlap, or proportions that disagree with the legend
-      - Category color changes between the bar and its legend
-    text: []
-    references: []
+- id: backup-encryption
+  releaseNote: Local backup files can now be encrypted before saving.
+  scene:
+    archetype: icon-tile
+    subject: One flat closed-padlock glyph inside a compact rounded square tile
+    message: Local backup files can be saved with encryption enabled.
+    focus: The closed shackle and simple keyhole of the monochrome padlock glyph
+    composition: A uniform 8:5 landscape canvas with one small flat rounded-square
+      tile centered exactly in the canvas. The tile side is about 22 percent of
+      canvas width, with a corner radius about 13 percent of its side. Inside
+      it, one front-facing filled padlock glyph occupies about 56 percent of the
+      tile width and 62 percent of its height. Use one solid mid-gray neutral
+      value for the complete glyph, including its closed arched shackle and
+      body. A simple keyhole is negative space in the body. Keep broad
+      uninterrupted canvas around the tile. There is no archive box, physical
+      object, perspective, material rendering, lighting, or colored badge.
+    context: Fictional capability illustration, not a shipped product claim. The
+      flat lock represents encryption of local backup files only. It does not
+      claim that every file is encrypted or that every product surface is
+      protected.
+    elements:
+      - One flat rounded-square background tile
+      - One solid monochrome closed-padlock glyph with a negative-space keyhole
+    preserve:
+      - Tile and glyph dimensions, optical center, and corner treatment
+      - Closed shackle and recognizable negative-space keyhole
+      - Completely flat monochrome graphic treatment in both themes
+    avoid:
+      - Perspective, extrusion, bevels, gradients, texture, highlights, or
+        shadows
+      - A physical archive box, metallic lock, or separate floating badge
+      - Decorative accent color or glow
+      - Open shackle, success mark, text, or additional controls
+    text: []
+    references: []
+- id: quiet-hours
+  releaseNote: Choose a daily time window to silence notifications.
+  scene:
+    archetype: ui-detail
+    subject: A quiet-hours setting with an enabled control and two time fields
+    message: Notifications can be silenced during a chosen daily time window.
+    focus: The enabled quiet-hours control and its associated start and end fields
+    context: Fictional settings interface. The depicted state is enabled with a
+      valid configured interval. Exact hours are incidental and should be
+      abstracted rather than invented.
+    composition: A single straight-on settings panel occupies about 64 percent of an
+      8:5 canvas width. A short abstract heading and one enabled toggle share
+      the top group. Beneath them, two equal-width time fields sit side by side
+      inside the same panel, with consistent padding and a clear gap. The left
+      field represents the start and the right the end. Use neutral bars for
+      field labels and values. Accent only the enabled toggle.
+    elements:
+      - One settings panel
+      - One enabled toggle
+      - Two grouped time fields with abstract labels and values
+    preserve:
+      - Enabled toggle state and grouping with the time fields
+      - Start field on the left and end field on the right
+      - Equal field dimensions and containment inside the panel
+    avoid:
+      - Motion cues or unrelated gestures
+      - Literal hours or an extra scheduling capability absent from the note
+      - Disabled appearance while the control is enabled
+    text: []
+    references: []
+- id: storage-breakdown
+  releaseNote: View how saved files use storage by category.
+  scene:
+    archetype: data-view
+    subject: A storage breakdown with three categories
+    message: A category breakdown shows how saved files use storage.
+    focus: One stacked bar and its matching category legend
+    context: Fictional view illustration. The proportions 20, 30, and 50 percent are
+      explicitly illustrative and are not measurements or a claim of improved
+      storage efficiency.
+    composition: A single panel occupies about 68 percent of an 8:5 canvas width.
+      One horizontal stacked bar contains three contiguous segments with lengths
+      in the ratio 2:3:5. Below it, three equally spaced legend items appear in
+      the same order as the segments. Each legend item has one matching swatch
+      and an abstract label bar. The first two categories use distinguishable
+      neutral values; the largest category uses the accent. Omit literal
+      numbers, axes, trend lines, and unrelated controls.
+    elements:
+      - One panel
+      - One stacked bar containing exactly three contiguous segments
+      - Three matching legend swatches with abstract label bars
+    preserve:
+      - 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
+      - Accent assigned to the same largest category in both themes
+    avoid:
+      - Invented performance improvement or additional metrics
+      - Gaps, overlap, or proportions that disagree with the legend
+      - Category color changes between the bar and its legend
+    text: []
+    references: []

package/examples/location-preferences/README.md

@@ -0,0 +1,18 @@
+# Location preferences
+
+An original fictional `symbol-pair` example: Preferences can be saved for an individually selected location.
+
+Original fictional example. The written scene is the complete product specification for this example, not evidence of a shipped product.
+
+| Dark | Light |
+| --- | --- |
+| ![An adjustment glyph associated with a saved location pin, dark presentation](dark.png) | ![An adjustment glyph associated with a saved location pin, light presentation](light.png) |
+
+Both selected PNGs are 1586 × 992 pixels.
+
+- [Shared scene specification](scene.yaml)
+- [Dark prompt](dark.prompt.md) and [light prompt](light.prompt.md), compiled from that scene and the default project palette
+- [Generation and pair review](pair-review.md)
+- [Current composition examples](../README.md#composition-gallery)
+
+The scene explains this feature only. Derive a new scene from each real note and its product evidence.

package/examples/location-preferences/dark.prompt.md

@@ -0,0 +1,52 @@
+# Release illustration — dark
+
+## 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: Preferences can be saved for an individually selected location.
+Subject: An adjustment glyph associated with a saved location pin
+Focal detail: A balanced association between preferences and one location
+Context: Original fictional example. The written scene is the complete product specification for this example, not evidence of a shipped product.
+
+## Composition contract
+Archetype: symbol-pair
+Target canvas: 1280 × 800 pixels; landscape 1280:800. Produce a single image, not a dark/light collage.
+Place two similarly weighted symbols on one horizontal optical axis, centered as a group; a short low-contrast divider can separate them.
+Specific scene layout: Two equal optical-weight symbols centered as a group on one horizontal axis. A three-slider adjustment glyph on the left and a simple location pin on the right, each about 16 percent of canvas width, separated by a short thin neutral vertical divider. The pin uses a restrained blue accent; the adjustment glyph is neutral. Broad empty space. Flat precise shapes with gently softened material depth.
+Elements:
+- One three-slider adjustment glyph
+- One blue location pin with a circular cutout
+- One short neutral vertical divider
+
+## Visual treatment
+Communicate one relationship with flat 2D filled glyphs. Match visual weight, corner treatment, and perceived size. Use an arrow only when direction itself is part of the feature. Prefer neutral gray; use color only for a stated interaction or semantic status. No rendered materials or sculpted 3D symbols.
+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.
+
+## 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 uniform flat color areas and crisp negative space. If a tile is present, use #18191B for its flat fill. Separate the neutral glyph and its background by value alone. Do not add lighting, shadows, gradients, texture, or physical material cues.
+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.
+Specific invariants:
+- Left adjustment glyph and right location pin with equal optical weight
+- Three slider tracks and their knob positions
+- Non-directional association; blue stays on the pin
+
+## 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
+- Arrows, routes, transfer or synchronization cues
+- Geofencing rings or automatic location triggers
+- Extra symbols or interface panels
+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 which two concepts are related and whether the relationship is directional. A connector must not imply transfer, synchronization, or automation unless supported by the note.
+
+## 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.

package/examples/location-preferences/light.prompt.md

@@ -0,0 +1,52 @@
+# 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: Preferences can be saved for an individually selected location.
+Subject: An adjustment glyph associated with a saved location pin
+Focal detail: A balanced association between preferences and one location
+Context: Original fictional example. The written scene is the complete product specification for this example, not evidence of a shipped product.
+
+## Composition contract
+Archetype: symbol-pair
+Target canvas: 1280 × 800 pixels; landscape 1280:800. Produce a single image, not a dark/light collage.
+Place two similarly weighted symbols on one horizontal optical axis, centered as a group; a short low-contrast divider can separate them.
+Specific scene layout: Two equal optical-weight symbols centered as a group on one horizontal axis. A three-slider adjustment glyph on the left and a simple location pin on the right, each about 16 percent of canvas width, separated by a short thin neutral vertical divider. The pin uses a restrained blue accent; the adjustment glyph is neutral. Broad empty space. Flat precise shapes with gently softened material depth.
+Elements:
+- One three-slider adjustment glyph
+- One blue location pin with a circular cutout
+- One short neutral vertical divider
+
+## Visual treatment
+Communicate one relationship with flat 2D filled glyphs. Match visual weight, corner treatment, and perceived size. Use an arrow only when direction itself is part of the feature. Prefer neutral gray; use color only for a stated interaction or semantic status. No rendered materials or sculpted 3D symbols.
+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.
+
+## 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 uniform flat color areas and crisp negative space. If a tile is present, use #ECEEF1 for its flat fill. Separate the neutral glyph and its background by value alone. Do not add lighting, shadows, gradients, texture, or physical material cues.
+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.
+Specific invariants:
+- Left adjustment glyph and right location pin with equal optical weight
+- Three slider tracks and their knob positions
+- Non-directional association; blue stays on the pin
+
+## 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
+- Arrows, routes, transfer or synchronization cues
+- Geofencing rings or automatic location triggers
+- Extra symbols or interface panels
+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 which two concepts are related and whether the relationship is directional. A connector must not imply transfer, synchronization, or automation unless supported by the note.
+
+## 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.

package/examples/location-preferences/pair-review.md

@@ -0,0 +1,17 @@
+# Pair review: Location preferences
+
+## Generation record
+
+Generated with the coding agent's built-in image tool. The CLI made no image-service calls. The dark asset was generated from dark.prompt.md; the light asset was created as a constrained edit of the selected dark image using light.prompt.md and an instruction to preserve input dimensions and composition. No color inversion was used.
+
+Two image-tool requests: dark generation and light counterpart.
+
+## Selected output
+
+- Two distinct decoded PNGs, both 1586 × 992 pixels, approximately 8:5. Original output dimensions are retained.
+- Reviewed at full size and approximately 350 pixels wide for feature meaning, focal clarity and pair correspondence.
+- Three slider tracks remain on the left, with the same knob positions; one blue pin stays on the right.
+- The thin divider communicates association without an arrow, transfer, synchronization or geofencing cue.
+- No readable text, logos or surrounding release-note viewer.
+
+The pair is visually consistent, not guaranteed to have pixel-identical edges or exact palette samples. Presentation lighting and surface shading can differ. This fictional image is an authoring reference; review real product imagery against its own evidence before acceptance.

package/examples/location-preferences/scene.yaml

@@ -0,0 +1,26 @@
+archetype: symbol-pair
+subject: An adjustment glyph associated with a saved location pin
+message: Preferences can be saved for an individually selected location.
+focus: A balanced association between preferences and one location
+composition: Two equal optical-weight symbols centered as a group on one
+  horizontal axis. A three-slider adjustment glyph on the left and a simple
+  location pin on the right, each about 16 percent of canvas width, separated by
+  a short thin neutral vertical divider. The pin uses a restrained blue accent;
+  the adjustment glyph is neutral. Broad empty space. Flat precise shapes with
+  gently softened material depth.
+context: Original fictional example. The written scene is the complete product
+  specification for this example, not evidence of a shipped product.
+elements:
+  - One three-slider adjustment glyph
+  - One blue location pin with a circular cutout
+  - One short neutral vertical divider
+preserve:
+  - Left adjustment glyph and right location pin with equal optical weight
+  - Three slider tracks and their knob positions
+  - Non-directional association; blue stays on the pin
+avoid:
+  - Arrows, routes, transfer or synchronization cues
+  - Geofencing rings or automatic location triggers
+  - Extra symbols or interface panels
+text: []
+references: []

package/examples/provided-media/README.md

@@ -0,0 +1,15 @@
+# Supplied-media example
+
+This is an input-request example, not a rendered asset. [The scene](scene.yaml) selects `object-detail` and `source: provided` without pretending that a product image exists. Put the scene fields under `scene` in a real note's visual file and adapt its message to the actual release.
+
+With no selected image, `releasekit image plan <version>` reports one request with `action: provide`, `theme: shared`, and `promptFile: null`. It reports zero generation requests. The agent looks for an approved project asset or asks for the specific capture or image, then continues independent writing work while waiting. Finalization remains blocked by the missing image.
+
+Once a suitable source is available, inspect it and import it once:
+
+```sh
+releasekit image import 1.4.0 product-detail --theme shared --file ./approved-capture.png
+```
+
+The shared image retains its native pixels and dimensions. Export contains one `variants.shared` entry and `fallbackTheme: shared`, so the consumer can use it in either viewer theme without duplicate files or recoloring. Actual distinct dark/light captures can instead be imported into the corresponding slots.
+
+The same source route applies to `editorial-scene` for actual content artwork or screenshots. Any other category may also choose `provided` when an authentic capture is the appropriate visual. No stock substitute, fictional model, or decorative illustration is needed to fill a missing input.

package/examples/provided-media/scene.yaml

@@ -0,0 +1,22 @@
+archetype: object-detail
+source: provided
+subject: The actual product control described by the release note
+message: Show the changed control using an approved product image.
+focus: The control as it appears in the real product
+composition: >-
+  Preserve the supplied image's product geometry, appearance, and native colors.
+  Select a useful crop only after inspecting the source. Do not invent the control
+  shape, viewpoint, surrounding assembly, or product materials.
+context: >-
+  Authoring example awaiting a real source. No screenshot, photograph, or approved
+  product image is supplied here. The planned asset must remain pending.
+elements:
+  - One approved capture or photograph of the actual product detail
+preserve:
+  - Authentic product appearance and relevant surrounding context
+  - Original source colors and feature meaning across viewer themes
+avoid:
+  - Generating a substitute physical object or 3D illustration
+  - Inventing geometry from a written description
+text: []
+references: []

package/examples/queue-action/README.md

@@ -1,15 +1,15 @@
-# Paired illustration example
-
-This fictional list interaction demonstrates the shared scene contract and theme-specific prompts. It is not a screenshot or a claim about an existing product.
-
-`scene.yaml` is the author-controlled brief. `dark.prompt.md` and `light.prompt.md` are compiled from that same brief and the default project palette. The selected raster pair is checked for interaction geometry, composition, visual hierarchy, and small-card readability.
-
-The resting rows and the blue action backplate share one fixed left boundary. Only the middle foreground row and its contents move to the right, by the width of the exposed action. This keeps the action inside the original list bounds. The [alignment edit prompt](alignment-edit.prompt.md) records the targeted correction to the earlier illustration.
-
-The generator is intentionally outside the CLI. In a real project, run `image plan`, generate the requested variants with the agent's available tool or an external service, inspect them, and use `image import` to record the selected files.
-
-| Dark | Light |
-| --- | --- |
-| ![A queue action revealed behind a list row on a charcoal canvas](dark.png) | ![The same queue action and list geometry on a near-white canvas](light.png) |
-
-Both selected PNGs are 1586 × 992 pixels. The generator returned a size close to the requested 8:5 ratio; the files retain their actual dimensions. See [the pair review](pair-review.md) for generation steps and visual checks.
+# Paired illustration example
+
+This fictional list interaction demonstrates the shared scene contract and theme-specific prompts. It is not a screenshot or a claim about an existing product.
+
+`scene.yaml` is the author-controlled brief. `dark.prompt.md` and `light.prompt.md` are compiled from that same brief and the default project palette. The selected raster pair is checked for interaction geometry, composition, visual hierarchy, and small-card readability.
+
+The resting rows and the blue action backplate share one fixed left boundary. Only the middle foreground row and its contents move to the right, by the width of the exposed action. This keeps the action inside the original list bounds. The [alignment edit prompt](alignment-edit.prompt.md) records the targeted correction to the earlier illustration.
+
+The generator is intentionally outside the CLI. In a real project, run `image plan`, generate the requested variants with the agent's available tool or an external service, inspect them, and use `image import` to record the selected files.
+
+| Dark | Light |
+| --- | --- |
+| ![A queue action revealed behind a list row on a charcoal canvas](dark.png) | ![The same queue action and list geometry on a near-white canvas](light.png) |
+
+Both selected PNGs are 1586 × 992 pixels. The generator returned a size close to the requested 8:5 ratio; the files retain their actual dimensions. See [the pair review](pair-review.md) for generation steps and visual checks.

package/examples/queue-action/alignment-edit.prompt.md

@@ -1,8 +1,8 @@
-Use case: precise-object-edit.
-Edit target: the attached dark release illustration. Correct only the horizontal alignment of the middle swipe-action row. Preserve the existing 1586 x 992 canvas and the entire first and third rows exactly.
-
-The first and third row backgrounds currently start at approximately x=267. This is the fixed list left boundary L. The current middle group is wrong: its blue action tile protrudes left to x=144, outside the list. TRANSLATE the entire middle group (blue tile, queue glyph, foreground card, neutral thumbnail, both label bars) approximately 123 pixels to the RIGHT. Do not shrink, stretch, or re-center that group. Its blue tile must start at L=267, perfectly aligned with the first and third row backgrounds. The middle foreground card must then start at about x=474 (=L+207) so it alone appears swiped right by the exposed action width. Keep its contents at exactly their existing internal padding; they move right with the foreground card. Keep the group's vertical position and height unchanged. The row's far right can remain clipped by the canvas.
-
-Required spatial relationship: left edge of top resting row = left edge of BLUE BACKPLATE = left edge of bottom resting row; left edge of middle FOREGROUND ROW is farther right by one blue action width. Nothing in the middle group extends to the left of that fixed boundary. Fill the vacated old protrusion area with the existing quiet charcoal canvas.
-
-Keep every other feature unchanged: three rows, rounded corners, row heights and vertical gaps, original materials and dark palette, blue interaction accent, glyph design, neutral flat thumbnail squares, label-bar dimensions, camera and crop. No photos, no words, no new objects, no gesture arrows, no diagram annotations. Render one corrected dark image only.
+Use case: precise-object-edit.
+Edit target: the attached dark release illustration. Correct only the horizontal alignment of the middle swipe-action row. Preserve the existing 1586 x 992 canvas and the entire first and third rows exactly.
+
+The first and third row backgrounds currently start at approximately x=267. This is the fixed list left boundary L. The current middle group is wrong: its blue action tile protrudes left to x=144, outside the list. TRANSLATE the entire middle group (blue tile, queue glyph, foreground card, neutral thumbnail, both label bars) approximately 123 pixels to the RIGHT. Do not shrink, stretch, or re-center that group. Its blue tile must start at L=267, perfectly aligned with the first and third row backgrounds. The middle foreground card must then start at about x=474 (=L+207) so it alone appears swiped right by the exposed action width. Keep its contents at exactly their existing internal padding; they move right with the foreground card. Keep the group's vertical position and height unchanged. The row's far right can remain clipped by the canvas.
+
+Required spatial relationship: left edge of top resting row = left edge of BLUE BACKPLATE = left edge of bottom resting row; left edge of middle FOREGROUND ROW is farther right by one blue action width. Nothing in the middle group extends to the left of that fixed boundary. Fill the vacated old protrusion area with the existing quiet charcoal canvas.
+
+Keep every other feature unchanged: three rows, rounded corners, row heights and vertical gaps, original materials and dark palette, blue interaction accent, glyph design, neutral flat thumbnail squares, label-bar dimensions, camera and crop. No photos, no words, no new objects, no gesture arrows, no diagram annotations. Render one corrected dark image only.

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

@@ -1,58 +1,58 @@
-# Release illustration — dark
-
-## 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: 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. No phone or outer application 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 and emphasize the changed control or state. 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. 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 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.
-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.
-Specific invariants:
-- Exact row count, positions, dimensions, spacing, and crop
-- Shared left boundary of the two resting rows and the blue 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
-
-## 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
-- 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. 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.
+# Release illustration — dark
+
+## 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: 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. No phone or outer application 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 and emphasize the changed control or state. 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. 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.
+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.
+Specific invariants:
+- Exact row count, positions, dimensions, spacing, and crop
+- Shared left boundary of the two resting rows and the blue 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
+
+## 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
+- 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. 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.