tandryukha

landing-page

Maintain the aidemo marketing/landing page (docs/index.html, served by GitHub Pages at https://tandryukha.github.io/aidemo/) and its indexing plumbing (llms.txt, robots.txt, sitemap.xml). Use when the user says "update the landing page", "add a section to the site", "change the hero", "update positioning", "fix the site", or asks to reflect a new feature/integration on the page. Do NOT use for: the GitHub README (separate, hand-curated), the docs/internal/ planning docs, or recording demo videos (that's record-demo).

record-demo

Produce a short (30-60s) narrated, captioned product demo video with the aidemo engine, via the aidemo MCP server. Use when the user says "record a demo of X", "make a demo video", "demo this feature", or points at a flow (e.g. a shopping flow inside a ChatGPT app) and wants a shareable MP4 with voiceover + captions. The skill authors a storyboard.json (script + per-scene voice/music plan + browser action-spec) and renders it with the engine. Do NOT use for: live screen-sharing, editing an already-rendered MP4, or demos of native/mobile apps (browser only).

release

Cut an aidemo release: bump package.json, commit, push to main — CI (release.yml) then creates the vX.Y.Z tag, moves `stable`, and publishes the GitHub Release. Use when the user says "cut a release", "release vX.Y.Z", "bump and release", "ship a new version", or "move stable". Knows the gotchas: the version lives ONLY in package.json, pushing a version bump to main IS the ship trigger, CI tagging is idempotent, npm caches the moving `stable` tag (--prefer-online to force-fresh). Do NOT use for: publishing to npm (the engine is npx-from-git only), or installing/updating the skill in consumer repos (that's `aidemo skill update`).

Testing & QA Listed

verify

Verify an engine change end-to-end by rendering the bundled fixture (examples/local-demo) and inspecting the output MP4 and intermediates. Use when the user says "verify", "run the smoke test", "e2e this change", "does the fixture still render", or before committing a nontrivial engine change. Knows the gotchas: OPENAI_API_KEY (or a local OPENAI_BASE_URL server) is needed for voice/captions but not probe/record/compose, stage-by-stage re-runs beat full re-renders, AIDEMO_KEEP_TMP=1 keeps .compose-tmp for compose debugging, logs/fail-*.png from failed takes. Do NOT use for: recording real product demos (use record-demo) or doc-only changes with no runtime surface.

blog-wave

RETIRED 2026-07-20 — this local pre-engine wave-orchestration skill has been superseded by the centralized blog-engine. If you land here for "new blog wave", "next blog wave", "write blog articles", "add blog topics", "expand the blog", "more articles", or growing aidemo.top/blog to N articles, use the `aidemo-blog` skill instead (it drives the engine). This stub only exists to redirect; it carries no orchestration logic.