無料GitHub で公開

feature-demo

Record at least one captioned demo for every covered CUJ through its real entry point.

omnigent-ai/omnigent

インストール方法を見る

含まれるファイル（1）

SKILL.md2.4 KB

SKILL.md（原文）

インストールする前に、エージェントに与えられる指示の中身を確認できます。

Demo recordings

The demo is required. Record at least one clip for every covered CUJ; a CUJ with several entry points or steps may have more. Each clip shows the user action and the product's response through the CUJ's real entry point, never pytest output, assertions, test source, or debug logs.

Follow dev/recording-lanes.md for the recorder, the per-surface mechanics, and captioning. Use the CUJ ID as the facet and demo as the kind:

Save each raw capture as recordings/<ticket-key>/raw/demo-<cuj>.<ext> (add a short suffix, e.g. demo-cuj-1-edit, for extra clips of the same CUJ).
Burn timed captions into each clip with dev/caption_recording.py, rendering to recordings/<ticket-key>/demo-<cuj>.mp4. Captions list the actions shown and end with the observed result.
Play and inspect each render before declaring it in the handoff and PR Demo. If captioning fails, use the guide's uncaptioned fallback path and say why in that clip's caption and the PR Demo. A usable uncaptioned clip still counts.
For API or configuration CUJs, record a VHS terminal session that runs the real CLI or API call and shows its output. Written evidence alone is not a demo.
Build the SPA before starting the recorder. Inside a server-spawned runner (OMNIGENT_RUNNER_ID is set), strip the inherited runner variables as the guide describes, and retry before reporting a blocker.

Never commit recordings; they ride in the PR Demo section and the CI artifact bundle.

When a recording can't be made

Recording should almost always work. When a covered CUJ really can't be recorded (the recorder can't start in this environment, or the surface needs hardware or an external account the sandbox doesn't have), still publish a ready PR and drive it as usual. For that CUJ:

set recording_blocker to the specific blocker, with the command and error;
write manual_test: step-by-step instructions a human can follow to test the journey, including setup, the inputs to give, and what they should see;
put both in the PR's Demo section in place of the clip.

The outcome is then partially_implemented, with that CUJ's recording in remaining_work. Only declare clips you actually produced. Then load feature-publish.

レビュー

まだレビューはありません。使ってみた感想をお寄せください。

同じリポジトリのスキル

概要と使いどころ

antigravity-native-e2e-dev

無料

Spin up a live local Omnigent server + runner and exercise the native Antigravity (agy) TUI harness (antigravity-native) end-to-end — launch the real `agy` CLI via `omnigent antigravity`, drive turns through the web UI, smoke-test, and bug-bash. Load when developing, testing, or debugging the antigravity-native harness (omnigent/inner/antigravity_native_executor.py, omnigent/antigravity_native.py, antigravity_native_bridge.py, antigravity_native_rpc.py, antigravity_native_reader.py, antigravity_native_launch.py) or its agy launch / RPC mirror / tmux delivery / OAuth / MCP-relay behavior. NOT the in-process `antigravity` Gemini SDK harness.

日本語の概要は準備中です。原文の説明を表示しています。