Skip to main content
skill CX Codex

demo — Claude Code skill: visual checks and installation

Prints Prismantis’s demo reply so you can inspect rendering after UI changes or before capturing a release screenshot.

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add NahumLitvin/prismantis --skill demo -a claude-code
Open on GitHub

What demo does

The skill tells the agent to output docs/demo.md as the entire final message of a turn. Its checklist covers tables, diagrams, code blocks, links, copy buttons, colors, and right-to-left text. A short visual test.

After a change, run the demo again and fix anything that looks wrong. Add each new feature to both docs/demo.md and the checklist. In Claude Code, the demo must end the turn: text written before a tool call can be condensed.

What it helps with

  • inspect rendering after a visual change
  • check table alignment and diagram colors
  • verify links and copy buttons in the terminal
  • review mixed right-to-left and left-to-right text
  • check the interface before a release screenshot

Example prompts for the agent

  • Show the Prismantis visual demo.
  • Check every rendering feature after my UI change.
  • Print the demo before I capture a release screenshot.

How to install demo

1Skills CLI (Vercel)

npx skills add NahumLitvin/prismantis --skill demo -a claude-code

2Manually: put the files in place

~/.claude/skills/demo/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/demo/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about demo

How do I install demo in Claude Code?

Run npx skills add NahumLitvin/prismantis --skill demo -a claude-code. The skill file is placed at ~/.claude/skills/demo/SKILL.md.

What does the demo skill do?

It prints docs/demo.md as the turn’s final message, giving you a visual check of Prismantis rendering.

Which rendering details does the demo check?

The checklist covers tables, diagrams, code blocks, colors, links, and copy buttons. It also checks right-to-left text.

Source text

SKILL.md · MIT
---
name: demo
description: Print the prismantis demo reply to eyeball every rendering feature after a change. Use after any visual change, when asked for "the demo", "show all features", "visual test", or before a release screenshot.
---

# Demo

The visual test. Unit tests prove the tree; this proves the look.

1. **Load the working copy** in this session (see `live-check` step 1). The new version shows only after the turn that made the edit ends.
2. **Print `docs/demo.md` verbatim as the whole final message of a turn**, with nothing before it and no tool call after it. Claude Code condenses text written right before a tool call, so the demo must close the turn.
3. **The person looks at it**, or screenshots it on the next turn (`live-check` step 3). Check:
   - `prismantis` in a heavy box on the first line, and `Roster` with a heavy rule under it
   - the table: yellow header, rules between rows, the right-aligned `Size` column, colored numbers
   - the four diagrams and the table on one row on a wide terminal, wrapping on a narrow one
   - every flowchart box and sequence participant in its own color, with matching colors at both ends of the sequence
   - a value above each bar, the tallest bar highlighted and the rest muted, labels without quotes, dim gridlines, colored axis numbers
   - shell colors: command, flags, the quoted string, `&&`
   - code blocks with a language header and no frame, and Prism colors in the TypeScript block
   - path, link and inline-code colors, the paths opening their files on click in a terminal that draws hyperlinks while `/kick` stays unlinked text, the quote bar running down its paragraph and both list rows, and the green `Tip` alert box
   - accent `⧉ md`, `⧉ art` and `⧉ html` buttons on the table (`⧉ html` in a local macOS or Linux terminal only), and an accent `[ ⧉ copy ]` button on every diagram, the list, the shell block, the alert and the quote
   - the timeline figure: drawn line by line with no `── figure` header, the caption in the comment color, the `▏───▏` axis and the Provider bar in the diagram color, `✗` and `2 twice` in the theme's reddest accent color, the Handler bar and `1` in its greenest, the time labels in its most amber, those three different from each other and from the diagram color, the bars ending on the axis ticks, `⧉ source` and `⧉ art` above it
   - the Hebrew section: lines read right to left (the first bullet shows `eu-west` and `us-east` after the Hebrew, mirrored parentheses), bullets and `1.` on the right, the quote bar on the right, the table cells right aligned, and the shell comment reversed while `ls -la` stays
4. **Fix what looks wrong**, then run the demo again.
5. **Keep it current.** A new feature adds a line to `docs/demo.md` and to the checklist above. All data stays invented and neutral.

© NahumLitvin · MIT · NahumLitvin/prismantis

Similar skills

All skills for Testing and QA →

From the same set5

Project sponsors

Companies that keep this analytics open
Gold sponsor

Impressions, clicks and code copies — open statistics. We keep the numbers public for the same reason NeBlask itself is public. Become a sponsor