Choose a film that fits your product
Close-Up suits software demos and feature walkthroughs: a product window, cursor movement and camera zooms. Watch its 29-second template preview before buying. That preview demonstrates the direction, rather than showing your product or establishing what your next run will produce.
The product page also labels its published first-party examples and validation conditions. Those are separate from this suggested workflow. If you have no interface to show, choose a more suitable film instead of forcing a screen-demo format.
Check the local rendering tools first
The current Close-Up package requires Node.js 20 or later, FFmpeg available on PATH, and playwright-core installed in the project. It also needs Google Chrome or a compatible Playwright Chromium installation. Choose a maintained Node release that meets the package minimum; consult the official setup links below.
This package renders an HTML film through a browser and FFmpeg; it does not require Remotion. A skill folder alone does not supply these tools. Ask your agent to verify the installed versions and browser launch before starting the film. Record any missing dependency rather than calling setup complete.
Install, then confirm the agent loaded the skill
Close-Up is a paid package, available through its individual purchase or eligible Pro access. Check the current product and pricing pages, sign in with your checkout email, then choose Claude Code or Codex in the install guide. Use your own generated install prompt; personal links expire after seven days and should not be shared.
Follow the selected agent’s reload and verification instructions in the setup guide. Claude Code and Codex discover and invoke skills differently. Confirm that taste-film-close-up appears in that agent, then ask it to identify the installed SKILL.md it read. A download or a visible skill name does not establish a successful render.
Provide assets and approve a storyboard
Supply screenshots or a screen recording you can use, your actual product facts, audience, message, call to action, duration and destination format. Close-Up does not automatically record arbitrary applications. A drawn reconstruction must be identified as such, and placeholders need your review. Approve the scene order and timing before detailed animation.
Use the installed taste-film-close-up skill for a launch video about [product]. My audience is [audience], the message is [message], and the call to action is [CTA and URL]. Use these authorized screenshots or recording: [files]. Target [duration and format]. First confirm the skill file and local rendering tools, then propose a timed storyboard for approval. Preserve the product facts; list missing assets and placeholders. After approval, build, run the package checks and visual QA, inspect the contact sheets, then render an MP4. Report actual results, file paths and anything not run.Check the film before exporting
Use the installed package’s documented checks on the working film folder. Resolve errors and inspect warnings. Generate its QA contact sheet and open the individual frames, including the relevant zoom holds and both sides of cuts. Recheck after each change.
Look for clipped text, mismatched interface states, unreadable captions and claims unsupported by the brief. Automated checks cover specific rules; they cannot judge every frame or establish that the demonstrated feature works. Keep the check results and your visual observations with the project.
Render an MP4 and watch the actual file
Follow the installed version’s rendering instructions after checks and visual QA are clean. Set the agreed output size and file location. Add audio only when you have permission to use it; a silent export is a valid choice.
Open the exported MP4 from beginning to end. Confirm its dimensions, frame rate, duration, audio choice and legibility at the intended viewing size. Review captions with sound muted. Save the final file and QA results; an HTML preview alone does not verify the encoded video.
Investigate the failing stage
If discovery fails, check the selected agent’s folder and reload instructions. If browser launch fails, check the project dependency and installed browser. If rendering cannot find FFmpeg, confirm it is on PATH in the agent’s environment. If the export looks wrong, inspect the source assets, contact sheet and export settings. Report the actual error and uncompleted stage instead of claiming success.
Keep access, costs and results clear
You supply the coding agent, model access and any associated usage fees. The package license permits personal and commercial work but prohibits redistributing the skill package. This guide exposes setup facts, not its private design rules or scripts. No independent installation, customer result or conversion improvement is established by following the instructions on this page.
Continue with a real project
Open Close-Up to inspect the current package, price, license and supported agents. For another film structure, compare Playhead and Ship Week.
Related field guides
Sources and scope
This is Taste Stack’s own product guidance. The package files and published product examples are the source for its visual rules. The suggested prompts are exercises, not additional completed benchmarks.