Run any Skill in Manus with one click

demo

Stars63

Forks10

UpdatedJuly 2, 2026 at 09:31

Generate a visual proof/demo document for completed Jant work using Showboat and Rodney screenshots. Use when the user invokes $demo by itself, asks for a demo, visual proof, proof document, screenshots showing the current work, or to prove a feature/fix works.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

jant-me

jant-me/jant

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software DevelopersComputer and Mathematical Occupations·SOC 15-1252

File Explorer

2 files

SKILL.md

readonly

name	demo
description	Generate a visual proof/demo document for completed Jant work using Showboat and Rodney screenshots. Use when the user invokes $demo by itself, asks for a demo, visual proof, proof document, screenshots showing the current work, or to prove a feature/fix works.

Generate a Visual Demo

Create a Showboat demo document with real Rodney screenshots that demonstrate the current feature or fix works. The document streams to the remote datasette-showboat instance configured by SHOWBOAT_REMOTE_URL.

Default Invocation

When invoked with no additional user instructions, treat the invocation as a request to generate a visual demo for the current work. Start by checking the Showboat and Rodney command usage and verifying SHOWBOAT_REMOTE_URL.

Workflow

Run uvx showboat --help and uvx rodney --help to confirm current usage.
Verify SHOWBOAT_REMOTE_URL is set. If it is missing, stop and ask the user to configure it.
Derive the demo filename from the current branch name, for example feat-login becomes /tmp/demos/feat-login.md.
Create /tmp/demos/ if it does not exist.
Use showboat init to create or overwrite the demo file. This assigns the Showboat UUID and streams the title to the remote instance.
Start the app if screenshots need a running local site. Use mise run dev-debug and the printed local login URL when authentication is required.
Start Rodney, navigate to the relevant pages, interact with the feature, and save screenshots under /tmp/.
Use Showboat commands such as note, exec, and image to assemble the demo. Do not edit the generated Markdown file directly.
Stop Rodney and any dev server started for the demo.
Report the remote viewer URL. Build it as {SHOWBOAT_REMOTE_URL_origin}/-/showboat/{showboat-id}, where {showboat-id} comes from the  line in the demo file.

Rules

Keep all demo output in /tmp/; do not write demo files or screenshots into the repository.
Always overwrite the demo document so it reflects the final state, not debug history.
Use only real evidence from actual execution: screenshots, command output, and observed behavior. Do not fabricate demo content.
Stop background processes started for the demo before finishing.

More from this repository

same repository

release

jant-me/jant

Create a Jant release changeset for @jant/core and create-jant using the repository's fixed-version workflow. Use when the user invokes $release by itself, asks to release, prepare a changeset, add a changeset, cut release notes, or run the old Claude release command.

2026-07-0263

jant-http-api

jant-me/jant

Automate a Jant site over HTTP. Use for creating and updating posts, uploading media, managing collections, editing settings, and running public or authenticated queries against the documented Jant API.

2026-04-3063

building-jant-site

jant-me/jant

Customize a standalone Jant site created with create-jant. Use for project structure decisions, local development, theme work, deployment setup, settings-driven customization, and deciding whether a change belongs in the site repo or in Jant core.

2026-04-3063

jant-site-ops

jant-me/jant

Operate a standalone Jant site from the command line. Use for local development, deploys, migrations, password resets, site export/import, snapshot recovery, SQL export, and static asset preparation.

2026-04-2963

name	demo
description	Generate a visual proof/demo document for completed Jant work using Showboat and Rodney screenshots. Use when the user invokes $demo by itself, asks for a demo, visual proof, proof document, screenshots showing the current work, or to prove a feature/fix works.

Generate a Visual Demo

Default Invocation

Workflow

Run uvx showboat --help and uvx rodney --help to confirm current usage.
Verify SHOWBOAT_REMOTE_URL is set. If it is missing, stop and ask the user to configure it.
Derive the demo filename from the current branch name, for example feat-login becomes /tmp/demos/feat-login.md.
Create /tmp/demos/ if it does not exist.
Use showboat init to create or overwrite the demo file. This assigns the Showboat UUID and streams the title to the remote instance.
Start the app if screenshots need a running local site. Use mise run dev-debug and the printed local login URL when authentication is required.
Start Rodney, navigate to the relevant pages, interact with the feature, and save screenshots under /tmp/.
Use Showboat commands such as note, exec, and image to assemble the demo. Do not edit the generated Markdown file directly.
Stop Rodney and any dev server started for the demo.
Report the remote viewer URL. Build it as {SHOWBOAT_REMOTE_URL_origin}/-/showboat/{showboat-id}, where {showboat-id} comes from the  line in the demo file.

Rules

Keep all demo output in /tmp/; do not write demo files or screenshots into the repository.
Always overwrite the demo document so it reflects the final state, not debug history.
Use only real evidence from actual execution: screenshots, command output, and observed behavior. Do not fabricate demo content.
Stop background processes started for the demo before finishing.