dot-matrix-brand-wordmark-motion
Create one exact brand wordmark dot-matrix motion from supplied inputs. Use when the distinct result and its preservation contract matter; unlike make-kinetic-typography (relationship 0.68), choose th
SKILL.mdskills/dot-matrix-brand-wordmark-motion/SKILL.md
GitHubDot Matrix Brand Wordmark Motion
Catalog
- Display name: Dot Matrix Brand Wordmark Motion
- Categories: Commercial Production, Video
- Status: Ready
- Route label: Independent outcome contract
- Tone: purple
- Short description: Produce one exact brand wordmark dot-matrix motion with explicit inputs, boundaries, and acceptance checks.
- Similar skills: brand-stream-mg, make-video-intro, poster-motion
What this skill does
- Captures the specific requested outcome and supplied asset roles.
- Produces a reviewable plan before media routing.
- Hands only approved atomic work to currently verified native Atoms.
How to use
Provide the desired result, supplied inputs, preservation requirements, ratio/duration when relevant, and acceptance criteria.
Example
Create one exact brand wordmark dot-matrix motion from my supplied assets; preserve the stated facts and show the plan before media generation.
Workflow
- Confirm the user-visible outcome, supplied inputs, fixed facts, delivery format, and exclusions.
- Produce a concise plan and continue through the requested supported route without a client-side payment confirmation.
- Select the narrowest verified existing Atom for any media operation; use only its live schema and never hard-code source-provider models or tools.
- Persist one durable operation key for each intended run, poll receipts, and surface the API outcome as returned.
- Review the requested preservation facts, output scope, ratio/duration, visible quality, and unwanted text or unsupported claims. Repair only the failing stage.
User-facing output
- Media type: One exact brand wordmark dot-matrix motion
- Default quantity: 1
- Content per artifact: Approved plan, requested deliverable, and acceptance result
- Default layout: User-requested format
- Model policy: Existing verified native Atoms only
- Downstream use: Review, assembly, or publication according to the API result, without client-side confirmation