product-demo-seeding

Solid

Seed coherent, disposable Kandev demo scenarios for screenshots, product films, landing-page media, and reproducible UI captures. Use when media needs believable tasks, workflows, agents, executors, integrations, plans, sessions, diffs, reviews, or native-mobile states; invoke before product-video-capture and never use a developer's main instance or data.

Code & Development 502 stars 69 forks Updated today AGPL-3.0

Install

View on GitHub

Quality Score: 87/100

Stars 20%
90
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# Product Demo Seeding Build a truthful product state before recording pixels. Treat narrative, data, and UI route as one artifact. ## Current-Main Source Gate Product capture represents current Kandev, so old checkouts and old builds are invalid even when their scripts still run. 1. Fetch `origin/main` immediately before capture setup. 2. Create a clean detached capture worktree from `origin/main`; do not reuse the task worktree or a landing branch. 3. Record both SHAs and prove `HEAD` equals `origin/main`. Require an empty `git status --porcelain` before building and before capture. 4. Install dependencies and build frontend/backend from that worktree. Verify it contains `scripts/dev-isolated` and `apps/web/e2e/`. 5. Stage specs, raw masters, configs, proofs, logs, and delivery candidates under a fresh artifact root outside production assets. Reject stale UI, selector, script, or capture choreography until current source is built and the complete route passes rehearsal. Never substitute an old server, cached bundle, or last month's working selectors for this gate. ## Workflow 1. Read `/e2e` and the relevant existing specs/page objects under `apps/web/e2e/`. 2. Write a one-sentence story: user goal, visible action, visible result. 3. Identify separate desktop and native-mobile routes. Mobile must use native mobile surfaces, not a desktop crop. 4. Explore manually with `scripts/dev-isolated --web` when needed. For reproducible capture, use the worker-scoped E2E fixture...

Details

Author
kdlbs
Repository
kdlbs/kandev
Created
6 months ago
Last Updated
today
Language
Go
License
AGPL-3.0

Integrates with

Similar Skills

Semantically similar based on skill content — not just same category

Code & Development Solid

product-video-capture

Record, camera-process, encode, stage, and validate polished Kandev product films, landing-page loops, screenshots, and alternate framing from isolated demo data. Use when the user asks for product videos, GIF-like feature demos, cursor-follow camera motion, desktop/mobile captures, recaptures, landing media, or different framing; always invoke product-demo-seeding first.

502 Updated today
kdlbs
AI & Automation Listed

capturing-product-media

Regenerate DorkOS product screenshots and video loops from the real UI, and manage the shot registry, human overrides, and version archives that feed the marketing site, docs, and changelogs. Use when marketing/docs media is stale after UI changes, a new feature or docs page needs a money shot, a person wants to override an automated capture, or a release calls for a fresh capture or archive — anything under apps/site/public/product/ or the apps/e2e/capture pipeline.

8 Updated today
dork-labs
Code & Development Listed

demo-video

Produce a polished, ScreenStudio-style 60fps product demo video of a web app with a tiny, dependency-light pipeline — Playwright frame capture + a multiprocess Pillow compositor streaming into ffmpeg (no Node/Remotion). Drives the app one step per frame so playback is true 60fps regardless of capture speed, then renders a gradient background, rounded panel + shadow, a crisp vector cursor, and smooth cinematic zoom/pan that holds steady during the action and eases out at the end; HD=1 re-renders the same capture at retina resolution. Use whenever asked to create/record/improve a demo video, walkthrough, feature showcase, or screencast of a web UI.

1 Updated 1 weeks ago
surajshetty3416