agentleFS
NahumLitvinNahumLitvin/prismantis/.claude/skills/live-check/SKILL.md

live-check

Skill426 starsChanged 3 days agoMITView on GitHub

Load the working copy of prismantis into a real Claude Code session and render how replies draw, with no screenshot. Use after any visual change, when asked to "screenshot", "see it", "try it live", or before claiming a rendering fix works.

  • Installs packages

4 other projects use a version of this, 1 of them edited.

Adopted by

Most recently taken up by

  • Other versions4 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 1

    1. iamrohithrnair/merman★ 4290% same

    Wrote their own version · 3

    1. markneonin/paneline★ 10same name
    2. nadavnaveh/skills★ 3same name
    3. Cohozen/magasins-u-mcp-server★ 1same name

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • In this repository7 other files it gives its agents.

The file

Files
SKILL.md

Live check

Tests prove the tree. Only a real render proves the look.

  1. Load the working copy:
    • From a new terminal: claude --plugin-dir <repo path>/plugin. Saving files hot-reloads it.
    • From inside a session that loaded the plugin-authoring skill: copy plugin/.claude-plugin/plugin.json, plugin/hooks/ and plugin/types/ into that session's dev-mods folder. The person answers the one-time "Enable hot reloading" prompt, and the mod loads when the turn ends. Copy again after every edit.
  2. Print a sample reply containing everything the change touches: a table with numbers and an aligned column, a bash block with flags and a quoted string, a path, a link, a heading and a mermaid block.
  3. Render it, never screenshot. Window captures are blocked for agents and grab whatever else is open. Instead run the session in a hidden terminal, record every byte it draws, and replay that into xterm.js in headless Chrome. This works with the screen locked and in parallel:
    npm i -s --prefix <scratch> @xterm/xterm
    python3 .claude/skills/live-check/capture.py <scratch>/demo.bin <repo> 110 80 '[[45,""]]' claude --plugin-dir <repo>/plugin "/prismantis demo"
    node .claude/skills/live-check/render.mjs <scratch>/demo.bin <scratch>/demo.png 110 80 <scratch>/node_modules/@xterm/xterm
    Then read the PNG. capture.py takes the output file, working directory, columns, rows and a JSON list of [seconds to wait, keys to type] steps, then the command. It stops the command once the last step's wait is over, so it needs no timeout (which macOS does not ship). Raise the rows to see more of a long reply. render.mjs finds Chrome or Chromium itself, or reads CHROME. On Windows, ask the person for a Win+Shift+S capture. xterm.js draws no kitty images and no desktop surface, so say those are unchecked.
  4. Check column alignment, rule lengths, colors against the theme tokens, wrapping at narrow widths, and that nothing falls back to the engine renderer. A dim line naming prismantis in the transcript means a hook was refused; fix that first. Hebrew, every time: also render /prismantis demo-rtl and read every Hebrew line right to left against rtlShowcaseText in plugin/hooks/help.ts: sentences, list items, table cells, quotes and every diagram label. Word order and letter order both count. If something looks off, read the bytes in the .bin before blaming the render: on a terminal without bidi they must be in display order (םולש, not שלום).
  5. Before publishing a render, check it, including the status line under the prompt, shows no private repo names, hostnames, internal versions or other work data. Use a neutral sample for README images.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.