Update to Moodle: Mood Board plan+design

{
  "description": "Translate an existing Mood Board into a photography shot list when the user asks how to shoot its campaign, product, editorial, or lifestyle direction. Ground each planned shot in visible references or supplied descriptions and specify framing, lighting, styling, and palette consistency. Do not use for a general creative brief, video storyboarding, booking a shoot, or generating finished photographs.",
  "included_files": [
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 309
    }
  ],
  "name": "mood-board-to-shot-list",
  "skill_md_contents": "---\nname: mood-board-to-shot-list\ndescription: \"Translate an existing Mood Board into a photography shot list when the user asks how to shoot its campaign, product, editorial, or lifestyle direction. Ground each planned shot in visible references or supplied descriptions and specify framing, lighting, styling, and palette consistency. Do not use for a general creative brief, video storyboarding, booking a shoot, or generating finished photographs.\"\n---\n\n# Mood Board to Shot List\n\n## Inputs\n\nUse the latest board, the photography objective and subject, visible references\nor user descriptions, and known delivery constraints such as format, shot count,\navailable props, or location. Keep unknown production details explicit.\n\n## Workflow\n\n1. Read the latest model-visible `modelContent.moodBoard`, or the latest\n   `structuredContent.moodBoard` when no newer edits are available. If there is\n   no board evidence, request it rather than claiming to retrieve private state.\n2. Extract the shared visual rules: mood, exact supplied palette values,\n   materials, lighting character, and composition cues. Describe only references\n   you can see or that the user has described. Label creative extrapolations as\n   proposals rather than observations.\n3. Establish the subject, purpose, and required output. Ask a focused question\n   if a missing subject or format would materially change the shots. State\n   reasonable assumptions for less consequential details and preserve all fixed\n   constraints.\n4. Plan six shots by default, or the requested count. Cover distinct purposes\n   such as a main image, context, a detail, or a human interaction when relevant\n   to the brief. Avoid repeating the same composition with superficial changes.\n5. Write a shot table with:\n   - Shot ID and purpose.\n   - Reference label, description, or known source.\n   - Framing and composition.\n   - Proposed lighting approach.\n   - Subject styling, backdrop, and props.\n   - Palette or consistency cue.\n6. Identify essential shots, optional additions, reusable setup choices, and\n   unresolved production needs. Keep equipment, location, staffing, and timing\n   as proposals or unknowns unless the user supplied them.\n7. Return the shot list in the conversation. Add an annotated board only when\n   the user requests one, following the app use rules below.\n\n## App use\n\nConsume the existing board without rendering merely to produce the shot list.\nFor a requested annotated board, call `display-mood-board` with the complete\nretained `moodBoard.items` and concise `note` items summarizing the shot direction.\nUse at most ten items, an optional `reason`, and only registered input fields;\nshot IDs and lighting fields belong in note text or the conversation.\n\nRead the returned `structuredContent.moodBoard` and account for fresh UUIDs.\nNever silently omit retained ingredients to fit the input limit. Guide the user\nto add or edit a note in the existing widget when its layout, uploaded-file\nassociations, or a board larger than ten items must be retained. Do not invent\nreusable image URLs or assume file IDs can be submitted as URL arguments.\nLeave the app-only `resolve-mood-board-images` helper to the widget.\n\n## Deliverable\n\nReturn the visual rules, the copy-ready shot table, essential versus optional\nshots, and a short list of unresolved production decisions. Tie each shot to\nactual board evidence or a clearly labeled creative proposal.\n\n## Boundaries\n\nDo not infer shooting order or storyboard sequence from hidden card positions.\nDo not claim to schedule a shoot, book services, buy props, generate photographs,\nor operate widget export through this app. Use source descriptions honestly and\nrespect requests for text only or no tools.\n"
}