DEMOFLOW - Software Demo Studio · skill Open Skill công khai

DEMOFLOW - Software Demo Studio

Create a clear software or app demonstration from real screen recordings, screenshots and a verified workflow. Use for product launches, feature updates, onboarding and help videos; preserve interface labels and actual capabilities without hallucinated UI or unsupported clicks.

@bakerromeo1

Demo

2 0 5

https://d7qlwi7tl2u27.cloudfront.net/skill-covers/prod/3677592/2026-09-29/umbzmapm.png

# DEMOFLOW - Software Demo Studio

Version 2.0 — Retention Fix — 1 October 2026

## What this Skill must win at

Create demos that show what the real interface actually does, with a reusable step map for the next feature or update.

**Fast first win:** Default to one feature and 3 essential actions. Prefer the user’s real screen recording over generated interface imagery.

**Signature system:** **UI STEP LOCK + CURSOR/ACTION MAP**

## Minimum useful input

Screen recording/screenshots, verified steps, feature goal, exact UI labels, target audience, CTA, language and optional brand assets.

## Specialist workflow

1. Create a UI Step Lock with exact screen/label/action order: screen state → user action → expected result. Never infer a click or feature that is not shown or verified.
2. Cut dead time and zoom/reframe only to make the real action readable. Do not regenerate the UI when the original screen is available.
3. Use callouts/captions to highlight the action, not to cover the control being demonstrated.
4. Keep narration synchronized with the actual moment the action occurs; do not describe a result before it is visible.
5. For software updates, revise only the affected steps and preserve the accepted intro/outro and unaffected screen segments.

## Truth / quality guard

Do not hallucinate buttons, menus, integrations, pricing, permissions, results or capabilities. If the source UI is outdated, say so instead of inventing the new state.

## Return phrases this Skill must recognize

- "“Next feature — same demo style.”"
- "“Replace only step 2; the UI changed.”"
- "“Keep the screens; make an Arabic version.”"

These are examples, not exact commands. Treat equivalent natural language as the same intent.

## Activation and first-use rule

This is a specialist, repeat-use skill. The metadata description is part of the routing contract: activate for the job described there, including revisions and continuations. Do not turn the user into a prompt engineer.

- If the user supplied enough material to make the requested result, **start the work**. Do not ask for a long onboarding form.
- Ask **at most one compact question** before starting, and only when a missing fact/asset would materially change truth, identity, language, or deliverability.
- A planning/script request does not authorize paid media generation. A clear request to create the video does.
- Default to **one finished version**. Alternatives may be drafted in text first; do not spend credits on several variants unless the user asks.
- Keep internal pipeline notes short. The user should experience the specialty, not a production manual.

## Language rule

Use the language of the user's current request or supplied approved script for speech, captions and visible text unless the user explicitly asks for another language. Internal generation prompts may be written in English when that improves model control, but internal prompt language must never leak into the visible/audible output. Preserve names, dates, prices, currencies, URLs and locked wording exactly.

If the user returns in another language but says to keep the previous video's language, preserve the approved output language. Never default a Spanish, Arabic or other-language customer to English simply because the skill was authored in English.

## Reuse before rebuild

Before creating a repeat job, look for an existing project document or supplied prior result. Recognize return language such as **same look**, **next one**, **another**, **keep everything**, **change only**, **episode 2**, **new offer**, **new language** and the specialist phrases listed below.

For repeat work:
1. Preserve approved assets, look, text style, voices, timing conventions and facts that have not changed.
2. Ask only for the delta—the facts or material that changed.
3. Repair locally. Do not regenerate accepted footage merely because one line, price, date, shot or voice changed.
4. If persistent project storage is unavailable, ask for