@mevdragon/vidfarm-devcli 0.2.13 → 0.3.0

package/auto-create-hyperframe-templates/template-planner-prompt.md

@@ -1,144 +0,0 @@
-# HyperFrame Template Planner Prompt
-
-You are a senior HyperFrames composition engineer.
-
-Given a HyperFrames production graph, produce a concrete implementation plan for `composition.html`, `composition.json`, and `lambda-site.json`. Return only JSON matching `template-plan.schema.json`.
-
-## Planning Rules
-
-- The output is an editable HyperFrames project, not a Vidfarm operation package.
-- Persist the source format's viral and visual rules inside `composition.json`.
-- Use deterministic HTML/CSS for captions, text, app UI, comments, notifications, overlays, shapes, and simple graphics.
-- Use timed media layers for MP4 scenes and image slides.
-- Separate source audio from source video when audio should continue across cuts.
-- Do not use a permanent background video as the publish source of truth.
-- If an editor-only playback source is included, mark it `mode: "editor"` or `preview_only: true`.
-- Publish-visible media must be represented by timed layers with explicit start/duration.
-- Empty timeline ranges are valid and should render background only.
-- Use percent geometry for layout and seconds for timing.
-- Use approved font families where possible: `TikTok Sans`, `Montserrat`, `Source Code Pro`, `Georgia`, `Abel`, or a documented custom font.
-- Important readable text must be deterministic unless the source format explicitly depends on poster/artifact-native generated text.
-- Include safe-area rules for TikTok/Reels vertical output.
-- Include Lambda memory estimate and production site metadata.
-- The frontend publish UX should expose the final signed output URL only, not S3 Console or Step Functions Console links.
-
-## Required Output Content
-
-The plan must include:
-
-- template metadata
-- source asset inventory
-- HyperFrames composition root settings
-- layer list
-- caption layout rules
-- safe-area rules
-- editor behavior rules
-- Lambda memory estimate
-- production Lambda site metadata
-- artifact manifest shape
-- validation checklist
-- implementation files to create
-
-## Composition HTML Requirements
-
-The root element should include:
-
-- `data-composition-id`
-- `data-source-folder`
-- `data-width`
-- `data-height`
-- `data-duration`
-
-Layer elements should include:
-
-- `data-hf-id`
-- `data-layer-kind`
-- `data-layer-mode`
-- `data-start`
-- `data-duration`
-- `data-track-index`
-- `data-label`
-
-Media slices should include:
-
-- `data-media-start`
-- `data-playback-start`
-- `src` or `data-src`
-
-For timeline proxies, include:
-
-- `data-vf-timeline-proxy="video"`
-- `data-src`
-
-The publish path must normalize proxies into real timed `<video>` elements.
-
-## Decomposition JSON Requirements
-
-The manifest should include:
-
-- `schema: "vidfarm.hyperframe-decomposition.v1"`
-- `source_folder`
-- `source_type`
-- `created_at`
-- `source_assets`
-- `summary`
-- `viral_dna`
-- `visual_dna`
-- `editor_layers`
-- `caption_layout`
-- `lambda_memory_estimate`
-- `lambda_site`
-- `validation`
-
-Use the same layer IDs in `composition.json` and `composition.html`.
-
-## Lambda Site Requirements
-
-Create `lambda-site.json` with:
-
-- `schema: "vidfarm.hyperframe.lambda-site.v1"`
-- `stack_name`
-- `region`
-- `site_id`
-- `project_dir`
-- `composition_file`
-- `memory_mb`
-- `render_defaults`
-- `output_url_policy`
-- `site_upload_command` or SDK equivalent when `site_id` is null
-
-Default stack settings:
-
-- stack: `hyperframes-vidfarm-prod`
-- region: `us-east-1`
-- memory: `3072`
-
-The plan may recommend `2048`, `4096`, or higher when justified by the memory estimator.
-
-## Lambda Memory Planning
-
-Use `lambda-memory-estimator.md` and return:
-
-- `recommended_memory_mb`
-- `estimated_lambda_gb_seconds`
-- `estimated_cost_usd`
-- `confidence`
-- `rationale`
-- `risk_flags`
-- `benchmark_override`
-
-Use `3072` MB as the ordinary social-video baseline. Prefer lowering to `2048` only for simple static/slideshow cases or measured lightweight video. Prefer raising to `4096` when active video decode, resolution, or effects justify it.
-
-## Validation Gates
-
-The plan is not complete unless it defines:
-
-- artifact checks
-- timeline checks
-- layer publish checks
-- caption/safe-area checks
-- Lambda deployment checks
-- final output checks
-
-Include a specific test for deleting or disabling one video scene and confirming the final render shows background/overlay only during that time range.
-