AnyCap Media
Own explicit AnyCap production after the medium or delegated technical branch is
clear. Keep detailed variants behind one-level references so only the selected
workflow enters context.
Route one production job
| Need |
Read |
| photo, product shot, hero, image edit |
image-production.md |
| logo, avatar, app icon, small-size brand mark |
brand-mark-production.md |
| text/image-to-video |
video-production.md |
| narrow Gemini Omni video edit |
gemini-omni-video-edit.md |
| music, speech, dialogue, audio scene |
audio-production.md |
| brand/launch film or hero loop |
style-reference.md, storyboard-template.md, and video-workflow-reference.md |
| reference-led social, UGC, repair, transformation, one-take promo |
social-video-production.md |
| meme, reaction visual, exact caption |
meme-workflows.md |
| delegated or explicit AnyCap T1/T2 technical visual |
image-skill-ownership-map.md, image-decision-system.md, and anycap-image-workflow.md |
For a technical branch, add only the relevant specialist reference:
- hybrid T1 explanation: generated-technical-diagrams.md
- complete short-label Chinese candidate: nano-banana-technical-diagrams.md
- report visual redesign: report-visual-redesign-workflow.md
- coordinated architecture set: architecture-report-diagram-playbook.md
Semantic boundary
- Use this Skill only when AnyCap is explicit or an upstream semantic owner
delegated an eligible branch. Ordinary bitmap work belongs to
imagegen.
- Generic
配图 begins at image-gen; architecture/process/state/decision at
image-gen-system; exact numeric charts at chart-gen; real maps at their
map owner; software architecture/request/state/incident/release video at
video-gen.
- Annotation or narrated/spatial human feedback routes to
anycap-human-interaction. Use anycap-access only for setup/auth/schema or
low-level command failure.
- When auth is required, delegate to
anycap-access and reuse the current controlled Chrome Google session under
its standing AnyCap-login authorization. Authentication does not authorize
Drive/Page delivery or publication.
Shared production workflow
- Freeze asset role, consumer surface, subject/fact graph, composition, aspect,
required/forbidden text, protected regions, references, rights, and
acceptance checks.
- Discover the selected live model/mode schema. Do not load a stale catalog or
spend on unapproved variants/fallbacks.
- Generate to descriptive local paths. Keep exact logo, UI, URLs, labels,
captions, connectors, and truth-bearing geometry deterministic unless the
T1 contract explicitly permits audited generated text.
- Inspect the artifact at original and consumer size. Verify type,
dimensions/duration, identity, composition, text/data, relationships,
watermarks, sensitive content, motion/audio, and reference fidelity.
- Fix concrete failures. A transport/download failure does not authorize a
different paid model. Preserve prompt/provenance sidecars when exactness,
delegation, rejection history, or reproducibility requires them.
For the compatibility Mermaid renderer and boundary tests, use the scripts in
scripts/; new exact system visuals remain owned by image-gen-system.
Delivery
Local files are the default. Drive/Page upload/share, publication, account/logo
replacement, or another remote delivery runs only when the current user
authorizes the exact operation, destination, environment, and audience.
Production approval is not publication approval. When delegated, return asset
paths, editable source/spec, dimensions, validation, limitations, and
return_to to the semantic owner.
1---2name: anycap-media3description: Produce explicit AnyCap media: photos, product shots, brand marks, decorative images, image edits, non-software video, music/audio/speech, campaign and social/UGC films, memes with deterministic captions, and eligible AnyCap T1/T2 technical visuals selected by image-gen/image-gen-system or explicitly requested. Not for generic visual-family routing, exact charts/maps/evidence, software technical video, research, or publication.4---56# AnyCap Media78Own explicit AnyCap production after the medium or delegated technical branch is9clear. Keep detailed variants behind one-level references so only the selected10workflow enters context.1112## Route one production job1314| Need | Read |15| --- | --- |16| photo, product shot, hero, image edit | [image-production.md](references/image-production.md) |17| logo, avatar, app icon, small-size brand mark | [brand-mark-production.md](references/brand-mark-production.md) |18| text/image-to-video | [video-production.md](references/video-production.md) |19| narrow Gemini Omni video edit | [gemini-omni-video-edit.md](references/gemini-omni-video-edit.md) |20| music, speech, dialogue, audio scene | [audio-production.md](references/audio-production.md) |21| brand/launch film or hero loop | [style-reference.md](references/style-reference.md), [storyboard-template.md](references/storyboard-template.md), and [video-workflow-reference.md](references/video-workflow-reference.md) |22| reference-led social, UGC, repair, transformation, one-take promo | [social-video-production.md](references/social-video-production.md) |23| meme, reaction visual, exact caption | [meme-workflows.md](references/meme-workflows.md) |24| delegated or explicit AnyCap T1/T2 technical visual | [image-skill-ownership-map.md](references/image-skill-ownership-map.md), [image-decision-system.md](references/image-decision-system.md), and [anycap-image-workflow.md](references/anycap-image-workflow.md) |2526For a technical branch, add only the relevant specialist reference:2728- hybrid T1 explanation: [generated-technical-diagrams.md](references/generated-technical-diagrams.md)29- complete short-label Chinese candidate: [nano-banana-technical-diagrams.md](references/nano-banana-technical-diagrams.md)30- report visual redesign: [report-visual-redesign-workflow.md](references/report-visual-redesign-workflow.md)31- coordinated architecture set: [architecture-report-diagram-playbook.md](references/architecture-report-diagram-playbook.md)3233## Semantic boundary3435- Use this Skill only when AnyCap is explicit or an upstream semantic owner36 delegated an eligible branch. Ordinary bitmap work belongs to `imagegen`.37- Generic `配图` begins at `image-gen`; architecture/process/state/decision at38 `image-gen-system`; exact numeric charts at `chart-gen`; real maps at their39 map owner; software architecture/request/state/incident/release video at40 `video-gen`.41- Annotation or narrated/spatial human feedback routes to42 `anycap-human-interaction`. Use `anycap-access` only for setup/auth/schema or43 low-level command failure.44- When auth is required, delegate to45 `anycap-access` and reuse the current controlled Chrome Google session under46 its standing AnyCap-login authorization. Authentication does not authorize47 Drive/Page delivery or publication.4849## Shared production workflow50511. Freeze asset role, consumer surface, subject/fact graph, composition, aspect,52 required/forbidden text, protected regions, references, rights, and53 acceptance checks.542. Discover the selected live model/mode schema. Do not load a stale catalog or55 spend on unapproved variants/fallbacks.563. Generate to descriptive local paths. Keep exact logo, UI, URLs, labels,57 captions, connectors, and truth-bearing geometry deterministic unless the58 T1 contract explicitly permits audited generated text.594. Inspect the artifact at original and consumer size. Verify type,60 dimensions/duration, identity, composition, text/data, relationships,61 watermarks, sensitive content, motion/audio, and reference fidelity.625. Fix concrete failures. A transport/download failure does not authorize a63 different paid model. Preserve prompt/provenance sidecars when exactness,64 delegation, rejection history, or reproducibility requires them.6566For the compatibility Mermaid renderer and boundary tests, use the scripts in67`scripts/`; new exact system visuals remain owned by `image-gen-system`.6869## Delivery7071Local files are the default. Drive/Page upload/share, publication, account/logo72replacement, or another remote delivery runs only when the current user73authorizes the exact operation, destination, environment, and audience.74Production approval is not publication approval. When delegated, return asset75paths, editable source/spec, dimensions, validation, limitations, and76`return_to` to the semantic owner.