media-and-asset-pipeline

name	media-and-asset-pipeline
description	Use when deciding whether to generate, retrieve, reference, transform, optimize, cache, license, or deliver images, video, audio, documents, icons, logos, fonts, generated media, CDN assets, or user-uploaded files.
activation	Activate when the description trigger applies to the current task.
required_inputs	Task request, relevant repository context, constraints, and authority dependencies.
required_outputs	Skill-specific artifact, verification evidence, canonical verdict, and next action.
authority_dependencies	00_start_here/SOURCE_OF_TRUTH.md; 10_governance/APIVR_EXECUTION_LIFECYCLE.md; 10_governance/source_of_truth/Elite_Build_Goals_v3.md.
evidence_requirements	Executed checks or an honest Unknown, Not Run, or Blocked state for every material claim.

Media And Asset Pipeline

Use this skill to route asset decisions safely and efficiently.

Required Inputs

• Asset purpose, audience, brand/quality requirement, and usage context.
• Existing asset sources, licensing/rights status, format, size, and delivery constraints.
• Whether the asset is generated, retrieved, referenced, transformed, user-uploaded, or externally hosted.

Routing Workflow

1. Read 40_knowledge/MEDIA_AND_ASSET_PIPELINE_GUIDANCE.md.
2. Choose the asset route:
   • retrieve existing approved asset;
   • reference external asset;
   • generate new asset;
   • transform/compress/resize;
   • cache/CDN;
   • user upload and moderation;
   • fallback/placeholder.
3. Define rights, attribution, storage, optimization, responsive delivery, accessibility, and failure behavior.
4. Decide whether external API, deployment/hosting, or reporting guidance also applies.
5. Verify rendered output and delivery behavior when user-facing.

Decision Graph

flowchart TD
  A["Asset needed"] --> B{"Approved asset already exists?"}
  B -- "Yes" --> C["Retrieve and optimize"]
  B -- "No" --> D{"Can external asset be licensed/referenced?"}
  D -- "Yes" --> E["Reference with rights and attribution"]
  D -- "No" --> F{"Should asset be generated?"}
  F -- "Yes" --> G["Generate, review, store provenance"]
  F -- "No" --> H["Use placeholder or request source asset"]
  C --> I["Optimize, cache, add alt/fallback"]
  E --> I
  G --> I
  H --> I
  I --> J["Rendered verification before PASS"]

Guardrails

• Do not use assets without rights, provenance, or user authorization.
• Do not rely on a single cinematic/decorative asset for essential content.
• Do not ship large media without responsive delivery or cost/performance awareness.
• Do not claim visual quality without rendered review.

Good / Bad

Grab a random image URL, place it in production, and assume it will stay available. Use an approved asset or generated asset with provenance, store it in the project/CDN, optimize responsive variants, add alt text, and verify rendering in the target layout.

Worked Example

Scenario: Add product imagery to a landing page.

• Route: retrieve approved brand images when available; generate only missing concept art.
• Connected skills: deployment guidance for CDN/storage and external API guidance if generation uses a provider.
• Evidence: asset source, rights/provenance, file size, responsive variants, alt text, screenshot/rendered review.