{
  "schemaVersion": "1",
  "revision": "22ce5d34dbcb5a78",
  "id": "factory-image-prompts-discussion",
  "slug": "image-prompts-discussion",
  "title": "Images as precise task evidence — discussion and evidence",
  "summary": "Detailed companion accounts of concepts, questions, demonstrations, exercises, and unresolved observations.",
  "category": "Context",
  "tags": [
    "image-prompts",
    "discussion",
    "evidence"
  ],
  "sources": [
    {
      "label": "Published evidence reference",
      "url": "https://proud-anchor-53zn.here.now/resource-manifest.json"
    },
    {
      "label": "Recorded discussion",
      "url": "https://proud-anchor-53zn.here.now/watch.html"
    }
  ],
  "sourceUnits": [
    "resource-manifest.json#videoEvidence.concepts[80]",
    "resource-manifest.json#videoEvidence.concepts[81]",
    "resource-manifest.json#videoEvidence.concepts[82]",
    "resource-manifest.json#videoEvidence.concepts[83]",
    "resource-manifest.json#videoEvidence.concepts[84]",
    "resource-manifest.json#videoEvidence.concepts[85]",
    "resource-manifest.json#videoEvidence.concepts[86]",
    "resource-manifest.json#videoEvidence.concepts[87]",
    "resource-manifest.json#videoEvidence.concepts[88]",
    "resource-manifest.json#videoEvidence.concepts[89]",
    "resource-manifest.json#videoEvidence.concepts[90]",
    "resource-manifest.json#videoEvidence.concepts[91]",
    "resource-manifest.json#videoEvidence.concepts[92]",
    "resource-manifest.json#videoEvidence.concepts[93]",
    "resource-manifest.json#videoEvidence.concepts[94]",
    "resource-manifest.json#videoEvidence.questionsAndAnswers[29]",
    "resource-manifest.json#videoEvidence.questionsAndAnswers[30]",
    "resource-manifest.json#videoEvidence.exercises[8]",
    "resource-manifest.json#videoEvidence.timeline[379]",
    "resource-manifest.json#videoEvidence.timeline[380]",
    "resource-manifest.json#videoEvidence.timeline[381]",
    "resource-manifest.json#videoEvidence.timeline[383]",
    "resource-manifest.json#videoEvidence.timeline[384]",
    "resource-manifest.json#videoEvidence.timeline[385]",
    "resource-manifest.json#videoEvidence.timeline[387]",
    "resource-manifest.json#videoEvidence.timeline[388]",
    "resource-manifest.json#videoEvidence.timeline[389]",
    "resource-manifest.json#videoEvidence.timeline[390]",
    "resource-manifest.json#videoEvidence.timeline[391]",
    "resource-manifest.json#videoEvidence.timeline[392]",
    "resource-manifest.json#videoEvidence.timeline[393]",
    "resource-manifest.json#videoEvidence.timeline[396]",
    "resource-manifest.json#videoEvidence.timeline[398]",
    "resource-manifest.json#videoEvidence.timeline[402]",
    "resource-manifest.json#videoEvidence.timeline[403]",
    "resource-manifest.json#videoEvidence.timeline[406]",
    "resource-manifest.json#videoEvidence.timeline[408]",
    "resource-manifest.json#videoEvidence.timeline[411]",
    "resource-manifest.json#videoEvidence.timeline[417]",
    "resource-manifest.json#videoEvidence.timeline[420]",
    "resource-manifest.json#videoEvidence.timeline[422]",
    "resource-manifest.json#videoEvidence.timeline[423]",
    "resource-manifest.json#videoEvidence.timeline[425]",
    "resource-manifest.json#videoEvidence.timeline[426]",
    "resource-manifest.json#videoEvidence.timeline[427]",
    "resource-manifest.json#videoEvidence.timeline[428]",
    "resource-manifest.json#videoEvidence.timeline[429]",
    "resource-manifest.json#videoEvidence.timeline[430]",
    "resource-manifest.json#videoEvidence.timeline[431]",
    "resource-manifest.json#videoEvidence.timeline[432]",
    "resource-manifest.json#videoEvidence.timeline[433]",
    "resource-manifest.json#videoEvidence.timeline[434]",
    "resource-manifest.json#videoEvidence.uncertainties[27]",
    "resource-manifest.json#videoEvidence.uncertainties[28]",
    "resource-manifest.json#videoEvidence.demos[45]",
    "resource-manifest.json#videoEvidence.demos[46]",
    "resource-manifest.json#videoEvidence.demos[47]",
    "resource-manifest.json#videoEvidence.demos[48]",
    "resource-manifest.json#videoEvidence.demos[49]",
    "resource-manifest.json#videoEvidence.demos[50]",
    "resource-manifest.json#videoEvidence.demos[51]",
    "resource-manifest.json#videoEvidence.demos[52]"
  ],
  "collection": "factory",
  "categoryId": "context",
  "wordCount": 1837,
  "url": "/topics/factory-image-prompts-discussion/",
  "markdownUrl": "/markdown/factory-image-prompts-discussion.md?raw=1&v=22ce5d34dbcb5a78",
  "jsonUrl": "/api/v1/documents/factory-image-prompts-discussion.json",
  "headings": [
    {
      "id": "concepts-and-distinctions",
      "text": "Concepts and distinctions",
      "level": 2
    },
    {
      "id": "prompting-with-images",
      "text": "Prompting with Images",
      "level": 3
    },
    {
      "id": "screen-annotation-workflow",
      "text": "Screen Annotation Workflow",
      "level": 3
    },
    {
      "id": "visual-prompting-multimodal-input",
      "text": "Visual Prompting / Multimodal Input",
      "level": 3
    },
    {
      "id": "before-after-conversation-artifacts",
      "text": "Before/After Conversation Artifacts",
      "level": 3
    },
    {
      "id": "image-diffing",
      "text": "Image Diffing",
      "level": 3
    },
    {
      "id": "arrow-to-text-to-action-workflow",
      "text": "Arrow-to-Text-to-Action Workflow",
      "level": 3
    },
    {
      "id": "code-review-artifact-generator",
      "text": "Code Review Artifact Generator",
      "level": 3
    },
    {
      "id": "context-aware-automation-script-kit",
      "text": "Context-Aware Automation (Script Kit)",
      "level": 3
    },
    {
      "id": "information-architecture-information-ux",
      "text": "Information Architecture / Information UX",
      "level": 3
    },
    {
      "id": "commit-hooks-push-gates",
      "text": "Commit Hooks / Push Gates",
      "level": 3
    },
    {
      "id": "gpui-framework",
      "text": "GPUI Framework",
      "level": 3
    },
    {
      "id": "commit-hooks",
      "text": "Commit Hooks",
      "level": 3
    },
    {
      "id": "cargo-crate-disk-space-management",
      "text": "Cargo Crate Disk Space Management",
      "level": 3
    },
    {
      "id": "visual-prompting-prompting-with-images",
      "text": "Visual Prompting / Prompting with Images",
      "level": 3
    },
    {
      "id": "gpui-framework-2",
      "text": "GPUI Framework",
      "level": 3
    },
    {
      "id": "questions-and-answer-status",
      "text": "Questions and answer status",
      "level": 2
    },
    {
      "id": "what-is-the-arrow-pointing-to",
      "text": "--- What is the arrow pointing to?",
      "level": 3
    },
    {
      "id": "a-participant-when-you-say-commit-gate-what-does-that-translate-to",
      "text": "a participant: 'When you say commit gate, what does that translate to?'",
      "level": 3
    },
    {
      "id": "exercises",
      "text": "Exercises",
      "level": 2
    },
    {
      "id": "observed-actions-and-statements",
      "text": "Observed actions and statements",
      "level": 2
    },
    {
      "id": "unresolved-the-exact-application-layout-type-running-at-02-26-28-550",
      "text": "Unresolved: The exact application layout type running at 02:26:28.550.",
      "level": 3
    },
    {
      "id": "unresolved-the-exact-hosting-deployment-or-resolution-path-of-the-changelog-site-interface",
      "text": "Unresolved: The exact hosting deployment or resolution path of the changelog site interface.",
      "level": 3
    },
    {
      "id": "demonstration-detail-02-17-10",
      "text": "Demonstration detail: 02:17:10",
      "level": 3
    },
    {
      "id": "demonstration-detail-02-19-28",
      "text": "Demonstration detail: 02:19:28",
      "level": 3
    },
    {
      "id": "demonstration-detail-02-20-37",
      "text": "Demonstration detail: 02:20:37",
      "level": 3
    },
    {
      "id": "demonstration-detail-02-23-21",
      "text": "Demonstration detail: 02:23:21",
      "level": 3
    },
    {
      "id": "demonstration-detail-02-25-21",
      "text": "Demonstration detail: 02:25:21",
      "level": 3
    },
    {
      "id": "demonstration-detail-02-27-04",
      "text": "Demonstration detail: 02:27:04",
      "level": 3
    },
    {
      "id": "demonstration-detail-02-28-10",
      "text": "Demonstration detail: 02:28:10",
      "level": 3
    },
    {
      "id": "demonstration-detail-02-31-35",
      "text": "Demonstration detail: 02:31:35",
      "level": 3
    }
  ],
  "markdown": "# Images as precise task evidence — discussion and evidence\n\nDetailed companion accounts of concepts, questions, demonstrations, exercises, and unresolved observations.\n\nThese are the companion’s accounts of the recorded discussion. Model capabilities, subscription rules, prices, version-specific flags, and predictions are contextual claims, not current guidance. An observed action is not proof that the attempted result succeeded. Distinct answers and uncertainties remain separate.\n\n## Concepts and distinctions\n\n### Prompting with Images\n\nUsing annotated visual context (such as screenshots with hand-drawn arrows) to precisely identify specific components or UI sections when prompting vision-capable large language models or software agents.\n\n### Screen Annotation Workflow\n\nA design/development shortcut involving a localized area capture tool that supports instant vector overlays (arrows, rectangles), streamlining the communication of UI components to an AI model with minimal steps.\n\n### Visual Prompting / Multimodal Input\n\nSupplying an LLM or autonomous agent with annotated screenshots containing simple drawings like arrows to establish spatial or element context instead of relying entirely on raw string selectors.\n\n### Before/After Conversation Artifacts\n\nRetaining original and updated web element screenshots inside chat history logs to allow easy visual diffs or visual reference verification by both the user and the agent.\n\n### Image Diffing\n\nAutomated pixel or feature-based comparison between an output page layout and the intended design asset to verify code correctness.\n\n### Arrow-to-Text-to-Action Workflow\n\nA technique using visually annotated screenshots (with arrows, shapes, and minimal text) to define tasks or movement trajectories for automated agents or video generators.\n\n### Code Review Artifact Generator\n\nAn automated AI pipeline that scans recent commits and generates a comprehensive, formatted report detailing security alerts, topology changes, and executive summaries.\n\n### Context-Aware Automation (Script Kit)\n\nEmpowering automated workflow tools to analyze screenshots, clipboard data, and screen layouts to infer user intent and build a personal memory repository.\n\n### Information Architecture / Information UX\n\nDesigning documentation layouts with bolding, italics, underlines, and explicit sections to avoid dense walls of text and allow rapid scannability.\n\n### Commit Hooks / Push Gates\n\nAutomating automated validation checks (e.g., formatting, syntax checking, rule exclusions) on a developer's machine prior to allowing a code commit or remote repository push.\n\n### GPUI Framework\n\nA high-performance, Rust-based user interface framework used to build native desktop application experiences.\n\n### Commit Hooks\n\nAutomated scripts running before a git commit is finalized to enforce quality checks like linters and formatters.\n\n### Cargo Crate Disk Space Management\n\nThe process of cleaning up or handling large disk consumption (e.g., 50 gigabytes) from Rust compilation artifacts.\n\n### Visual Prompting / Prompting with Images\n\nAn agent workflow leveraging an annotated image (e.g., with CleanShot arrows) paired with a clear, concise instruction sentence to guide an AI agent directly to a visual layout bug or asset.\n\n### GPUI Framework\n\nA user interface framework mentioned by the presenter in relation to layout shifts under exploration in his tools.\n\n## Questions and answer status\n\n### --- What is the arrow pointing to?\n\n**Status: answered.** The pi agent processes the screenshot and correctly returns: 'The arrow points to the highlighted \"Build\" text.'\n\n### a participant: 'When you say commit gate, what does that translate to?'\n\n**Status: answered.** John explains that a commit gate translates directly to a Git commit hook. He highlights that developers can prompt an AI agent to build a customized commit hook containing tailored project requirements, such as blocklisting specific file types (like log files), checking code metrics, running formatters, or maintaining linter baselines.\n\n## Exercises\n\n- **Try:** Capture with the CleanShot hotkey, draw ONE red arrow at the element in question, drag from the annotate overlay into your agent, and type one sentence of intent. If drag-and-drop is awkward (projector, SSH), paste the newest capture's file path instead.\n  **Basis:** On-screen instructional sequence text located under 'Quick Start' header on the document page at 02:15:42.500.\n\n## Observed actions and statements\n\nThese timestamped observations retain troubleshooting detail and the limits of what was visible. Commands mentioned here are observations, not vetted installation instructions; use the topic’s prepared recipes for runnable examples.\n\n- [02:15:50](https://proud-anchor-53zn.here.now/watch.html?t=8150#recording-player) — John discusses screen capture tools across operating systems and recommends CleanShot.\n\n- [02:16:30](https://proud-anchor-53zn.here.now/watch.html?t=8190#recording-player) — John describes critical features for screen capture tools, such as binding global keyboard shortcuts and drawing on screen.\n\n- [02:16:45](https://proud-anchor-53zn.here.now/watch.html?t=8205#recording-player) — a participant shares a link to Flameshot: 'https://flameshot.org/'.\n\n- [02:17:04](https://proud-anchor-53zn.here.now/watch.html?t=8224#recording-player) — a participant shares a link to Shottr: 'https://shottr.cc/'.\n\n- [02:17:10](https://proud-anchor-53zn.here.now/watch.html?t=8230#recording-player) — John searches for 'notion' on Google and opens notion.com. He uses CleanShot X to capture an area of the homepage and draws a red arrow pointing to the 'Build' pill badge.\n\n- [02:17:37](https://proud-anchor-53zn.here.now/watch.html?t=8257#recording-player) — John explains that CleanShot keeps the image overlay available for drag-and-drop or saves it as the most recent clipboard entry.\n\n- [02:18:05](https://proud-anchor-53zn.here.now/watch.html?t=8285#recording-player) — John types and runs 'take dev/notion-header' and then 'notion-header pi' in the terminal to spawn his workspace agent.\n\n- [02:18:15](https://proud-anchor-53zn.here.now/watch.html?t=8295#recording-player) — John pastes the screenshot file path via Cmd+V into the pi terminal prompt, followed by the text: '--- What is the arrow pointing to?'.\n\n- [02:18:50](https://proud-anchor-53zn.here.now/watch.html?t=8330#recording-player) — The terminal agent completes processing and outputs: 'The arrow points to the highlighted \"Build\" text.'.\n\n- [02:19:15](https://proud-anchor-53zn.here.now/watch.html?t=8355#recording-player) — John inputs a multi-line code generation request to replicate the layout in HTML/CSS into the terminal agent: '--- I want to build a header like this in HTML and CSS where there's a pill like this build inset inside of the header text. Please build that out for me.'.\n\n- [02:19:28](https://proud-anchor-53zn.here.now/watch.html?t=8368#recording-player) — The cmux workspace environment is active under the workspace label 'notion-header', displaying automated planning commands and text prompt inputs.\n\n- [02:19:30](https://proud-anchor-53zn.here.now/watch.html?t=8370#recording-player) — John Lindquist explains that while vision models might not match fonts or sizes exactly, they are highly capable of locating elements indicated by user markings.\n\n- [02:19:44](https://proud-anchor-53zn.here.now/watch.html?t=8384#recording-player) — The terminal executes repository mapping scripts and lists directory setup commands to track workspace artifacts.\n\n- [02:20:37](https://proud-anchor-53zn.here.now/watch.html?t=8437#recording-player) — The CleanShot X annotation overlay is opened, and the presenter draws multiple colorful arrows and markings to demonstrate screenshot annotation flexibility.\n\n- [02:21:37](https://proud-anchor-53zn.here.now/watch.html?t=8497#recording-player) — John Lindquist suggests prompting an agent to take a screenshot after generating HTML to perform an automated layout comparison diff.\n\n- [02:23:16](https://proud-anchor-53zn.here.now/watch.html?t=8596#recording-player) — John Lindquist mentions grabbing any sort of screenshot tool.\n\n- [02:23:21](https://proud-anchor-53zn.here.now/watch.html?t=8601#recording-player) — John notes that CleanShot has been solid for him for years and reliably does what it promises.\n\n- [02:23:54](https://proud-anchor-53zn.here.now/watch.html?t=8634#recording-player) — John calls this a workflow you can teach to anyone on the team.\n\n- [02:24:13](https://proud-anchor-53zn.here.now/watch.html?t=8653#recording-player) — John mentions that you can add text if you want to.\n\n- [02:24:35](https://proud-anchor-53zn.here.now/watch.html?t=8675#recording-player) — John explains using annotated images as instructions for video generators in a storyboarding approach.\n\n- [02:25:52](https://proud-anchor-53zn.here.now/watch.html?t=8752#recording-player) — John highlights the code review it did with a very loose prompt.\n\n- [02:26:37](https://proud-anchor-53zn.here.now/watch.html?t=8797#recording-player) — John states that an AI configuration left in some OAuth files that stayed local and did not pass push gates.\n\n- [02:27:04](https://proud-anchor-53zn.here.now/watch.html?t=8824#recording-player) — John Lindquist describes an AI feature like 'what's going on today'.\n\n- [02:27:10](https://proud-anchor-53zn.here.now/watch.html?t=8830#recording-player) — John Lindquist explains that it is using the Codex account to build up its own AI functionality.\n\n- [02:27:26](https://proud-anchor-53zn.here.now/watch.html?t=8846#recording-player) — John Lindquist expresses his ambition to make Script Kit gather context directly from the screen view.\n\n- [02:27:32](https://proud-anchor-53zn.here.now/watch.html?t=8852#recording-player) — John Lindquist suggests actions like taking a screenshot of an app or summarizing the screen text.\n\n- [02:27:58](https://proud-anchor-53zn.here.now/watch.html?t=8878#recording-player) — John Lindquist discusses the challenge of working with Rust and the GPUI framework regarding asset bundle sizes.\n\n- [02:28:10](https://proud-anchor-53zn.here.now/watch.html?t=8890#recording-player) — John Lindquist reviews the past week of local commits and mentions that he has been experimenting rather than pushing changes.\n\n- [02:28:28](https://proud-anchor-53zn.here.now/watch.html?t=8908#recording-player) — John Lindquist states his dislike for the table layout and recommends a template with better information architecture or information UX.\n\n- [02:29:13](https://proud-anchor-53zn.here.now/watch.html?t=8953#recording-player) — John Lindquist characterizes massive data tables as information overload with excessive amounts of text.\n\n- [02:29:28](https://proud-anchor-53zn.here.now/watch.html?t=8968#recording-player) — John Lindquist defines a commit gate as a Git commit hook.\n\n- [02:30:22](https://proud-anchor-53zn.here.now/watch.html?t=9022#recording-player) — John Lindquist outlines constraints run by commit hooks, including line limits, specific design patterns, linters, benchmarks, and code formatters.\n\n- [02:30:46](https://proud-anchor-53zn.here.now/watch.html?t=9046#recording-player) — John explains how to prompt an agent to set up standard commit hooks with linters and formatters.\n\n- [02:31:16](https://proud-anchor-53zn.here.now/watch.html?t=9076#recording-player) — John discusses disk space management challenges when compiling Rust projects and Cargo builds.\n\n### Unresolved: The exact application layout type running at 02:26:28.550.\n\nThe view flashes briefly on screen for less than two seconds, showing a custom workspace tree with agent identifiers alongside a source editor block.\n\n**Discriminating evidence:** Verify with future or past shards covering code execution panel structure.\n\n### Unresolved: The exact hosting deployment or resolution path of the changelog site interface.\n\nText is rendered standard-scale on screen and can match varying development server distributions.\n\n**Discriminating evidence:** Cross-reference with project configurations inside neighboring Script Kit repositories.\n\n### Demonstration detail: 02:17:10\n\n- Navigated to notion.com in Chrome browser.\n- Took a screenshot layout and drew an analytical arrow target using CleanShot X.\n- Opened a Ghostty terminal window session.\n- Created and changed workspace context using 'take dev/notion-header'.\n- Initialized the interactive prompt environment using 'notion-header pi'.\n- Pasted the screenshot asset file path and submitted a query to verify arrow targeting.\n- Submitted a detailed design prompt requesting corresponding HTML and CSS structure generation.\n\n**Tools observed:** Chrome Browser, CleanShot X, Ghostty Terminal, pi prompt agent.\n\n**Command or prompt observations (not a verified recipe):**\n\n```text\ntake dev/notion-header\nnotion-header pi\n```\n\n### Demonstration detail: 02:19:28\n\n- Automated workspace mapping scripts run inside the terminal environment, printing configuration details and generating layout artifacts.\n\n**Tools observed:** cmux.\n\n**Command or prompt observations (not a verified recipe):**\n\n```text\npwd && print '\n-- files --\n' && find . -maxdepth 2 -type f | sort | head -200\nmkdir -p .artifacts\n```\n\n### Demonstration detail: 02:20:37\n\n- Draws a red line arrow targeting webpage headers, draws a red crossing mark, creates multi-colored secondary indicator arrows, and selects 'Don't Save' to clear modifications.\n\n**Tools observed:** CleanShot X, Google Chrome.\n\n### Demonstration detail: 02:23:21\n\n- Initiated screenshot frame frozen overlay with CleanShot X.\n- Drew a red circle markup around the avatar elements.\n- Selected the text tool option.\n- Drew a red rounded rectangle over the avatars.\n- Added a red direction arrow pointing to the right.\n- Closed the screenshot overlay window and clicked 'Don't Save' on the confirmation modal.\n\n**Tools observed:** CleanShot X.\n\n### Demonstration detail: 02:25:21\n\n- Navigated to amber-willow-n6aj.here.now and scrolled through prompt documentation.\n- Switched tab to liminal-voga-nyfw.here.now to view automated AI code review guide outputs.\n- Briefly pulled up terminal view displaying script-kit-gpui workspace.\n- Returned to the automated guide page and highlighted specific sections concerning OAuth security flags.\n\n**Tools observed:** Google Chrome.\n\n### Demonstration detail: 02:27:04\n\n- John prompts an overlay interface to highlight sample user context gathering strategies.\n\n**Tools observed:** Script Kit Launcher.\n\n### Demonstration detail: 02:28:10\n\n- John scrolls through generated documentation to assess text spacing, layout readability, and layout issues.\n\n**Tools observed:** Web Browser.\n\n### Demonstration detail: 02:31:35\n\n- Presenter switches focus to Google Chrome and cycles through open documentation tabs.\n- Presenter navigates to the workshop index page on ember-bodhi-wcm.here.now and scrolls through sections.\n\n**Tools observed:** Google Chrome."
}
