visual-qa
Check a built UI in a real browser at several widths: states, screenshots, visible breakage.
Install
npx skills add https://github.com/wjgoarxiv/litgravity/tree/main/plugin/skills/visual-qa
claude plugin marketplace add https://llmmart.ai/marketplace.json && claude plugin install wjgoarxiv-litgravity@llmmart
git clone https://github.com/wjgoarxiv/litgravity.git
The skills CLI installs just this skill, for any of its supported agents. Claude Code installs the whole wjgoarxiv/litgravity collection as a plugin from our marketplace. Git is the plain clone.
Skill manifest
visual-qa: a LitFamily extension in wjgoarxiv-skills
visual-qa checked a built interface the way a user sees it: its states at several widths in a real browser, screenshots, and visible breakage reported with that evidence or a named blocker. It no longer ships inside LitGravity. It is a LitFamily extension now, and the whole skill folder lives in the separate wjgoarxiv-skills repository at variants/litgravity/visual-qa/, a copy written for agy, so a LitGravity install stays small and anyone who wants a visual check copies in this one folder.
This file keeps the id. lit visual-qa …, /litgravity:visual-qa, review-work lane 5 and a litwork surface check that reach a user interface still land here, and the steps below take it from there.
Install it in agy
The short route is LitGravity's own command, run in a terminal: npx @litfamily/litgravity extensions install visual-qa prints what it would do, and the same with --yes does it (--project for one workspace). It fetches the skill, stops if another skill named visual-qa sits where agy loads skills, moves an old copy aside and writes the receipt; extensions update, remove and check do the rest. The lines below are the same steps by hand.
wjgoarxiv-skills is public at https://github.com/wjgoarxiv/wjgoarxiv-skills. Clone it (git clone https://github.com/wjgoarxiv/wjgoarxiv-skills), then paste these four lines one at a time (zsh or bash) in the workspace you use agy in. They put the skill in agy's user skills, which every workspace sees:
find .agents/skills _agents/skills ~/.gemini/config/skills ~/.gemini/skills -maxdepth 2 -name SKILL.md -exec grep -l -E '^name: *"?visual-qa"? *$' {} + 2>/dev/null
if [ -e ~/.gemini/config/skills/visual-qa ] || [ -L ~/.gemini/config/skills/visual-qa ]; then b=~/.gemini/extension-backups/$(date +%Y%m%d-%H%M%S); mkdir -p "$b" && mv ~/.gemini/config/skills/visual-qa "$b/" && echo "moved to $b/visual-qa"; fi
mkdir -p ~/.gemini/config/skills && [ ! -e ~/.gemini/config/skills/visual-qa ] && cp -R "<path to your wjgoarxiv-skills clone>/variants/litgravity/visual-qa" ~/.gemini/config/skills/visual-qa
printf '{"id":"%s","source":"%s","variant":"litgravity","installed_at":"%s"}\n' visual-qa "<path to your wjgoarxiv-skills clone>/variants/litgravity/visual-qa" "$(date -u +%Y-%m-%dT%H:%M:%SZ)" > ~/.gemini/config/skills/visual-qa/.litfamily-extension.json
Line one only looks: it prints every SKILL.md named visual-qa that agy could load, and nothing when there is none. agy keeps one same-name skill without a word, a workspace copy first, so move any other one it names aside too. Line two moves an existing copy whole into a dated folder under ~/.gemini/extension-backups/, which agy never loads; line three copies into the emptied place; line four writes the receipt .litfamily-extension.json inside the copy.
For one workspace only, run line one, then these three in the workspace root:
if [ -e .agents/skills/visual-qa ] || [ -L .agents/skills/visual-qa ]; then b=~/.gemini/extension-backups/$(date +%Y%m%d-%H%M%S)-project; mkdir -p "$b" && mv .agents/skills/visual-qa "$b/" && echo "moved to $b/visual-qa"; fi
mkdir -p .agents/skills && [ ! -e .agents/skills/visual-qa ] && cp -R "<path to your wjgoarxiv-skills clone>/variants/litgravity/visual-qa" .agents/skills/visual-qa
printf '{"id":"%s","source":"%s","variant":"litgravity","installed_at":"%s"}\n' visual-qa "<path to your wjgoarxiv-skills clone>/variants/litgravity/visual-qa" "$(date -u +%Y-%m-%dT%H:%M:%SZ)" > .agents/skills/visual-qa/.litfamily-extension.json
The folder is the whole skill, with its own scripts, references and engine locks. Its neighbours (frontend-ui-ux, the builder this check accepts work from) install the same way, one folder each. Start a new conversation, or type /skills reload; the skill then answers as /visual-qa, and lit prompts that reach this stub hand over to it. To update it, run the same lines again: the old copy moves to a new dated backup and the receipt is rewritten. To remove it, run the second line alone. Nothing is deleted; clear old backups out of ~/.gemini/extension-backups/ when you no longer need them. The LitGravity installer writes only its own plugin folder, so upgrading or removing LitGravity leaves the copy alone, and the names never clash: this stub is litgravity:visual-qa, the copy is visual-qa.
When this stub is read
- Look for the installed copy with
read_file: first~/.gemini/config/skills/visual-qa/SKILL.md, then.agents/skills/visual-qa/SKILL.mdin the workspace. - Found. Read it and follow it for this task; its folder is the root for every relative path it names. It was written for agy and needs no LitGravity hook: every check it names is a command it tells you to run.
- Not found, asked directly. Reply in a few lines: what visual-qa did, that it is a LitFamily extension now, kept in wjgoarxiv-skills (
variants/litgravity/visual-qa/), theextensions installcommand and the install lines above, and that you made nothing yet. Do not describe the page from its source and call that a visual check. - Not found, inside a workflow. Inside review-work or litwork, record
visual-qa not installedin the lane and give no visual verdict: the surface stays unchecked, not passed.
Hard stops
- Give the install lines with the placeholder; never a path from this machine.
- Never say a visual check exists unless the installed copy made it and you looked at the result.
- A headless run (
agy -p) never copies the skill in itself: give the install lines and stop.
Files (litgravity)
-
SKILL.md 5.7 KB
--- name: visual-qa description: "Checking a built interface in a real browser at several widths. A LitFamily extension in wjgoarxiv-skills: this stub loads the installed copy, or gives the agy install line." --- # visual-qa: a LitFamily extension in wjgoarxiv-skills visual-qa checked a built interface the way a user sees it: its states at several widths in a real browser, screenshots, and visible breakage reported with that evidence or a named blocker. It no longer ships inside LitGravity. It is a LitFamily extension now, and the whole skill folder lives in the separate wjgoarxiv-skills repository at `variants/litgravity/visual-qa/`, a copy written for agy, so a LitGravity install stays small and anyone who wants a visual check copies in this one folder. This file keeps the id. `lit visual-qa …`, `/litgravity:visual-qa`, review-work lane 5 and a litwork surface check that reach a user interface still land here, and the steps below take it from there. ## Install it in agy The short route is LitGravity's own command, run in a terminal: `npx @litfamily/litgravity extensions install visual-qa` prints what it would do, and the same with `--yes` does it (`--project` for one workspace). It fetches the skill, stops if another skill named visual-qa sits where agy loads skills, moves an old copy aside and writes the receipt; `extensions update`, `remove` and `check` do the rest. The lines below are the same steps by hand. wjgoarxiv-skills is public at https://github.com/wjgoarxiv/wjgoarxiv-skills. Clone it (`git clone https://github.com/wjgoarxiv/wjgoarxiv-skills`), then paste these four lines one at a time (zsh or bash) in the workspace you use agy in. They put the skill in agy's user skills, which every workspace sees: ```bash find .agents/skills _agents/skills ~/.gemini/config/skills ~/.gemini/skills -maxdepth 2 -name SKILL.md -exec grep -l -E '^name: *"?visual-qa"? *$' {} + 2>/dev/null if [ -e ~/.gemini/config/skills/visual-qa ] || [ -L ~/.gemini/config/skills/visual-qa ]; then b=~/.gemini/extension-backups/$(date +%Y%m%d-%H%M%S); mkdir -p "$b" && mv ~/.gemini/config/skills/visual-qa "$b/" && echo "moved to $b/visual-qa"; fi mkdir -p ~/.gemini/config/skills && [ ! -e ~/.gemini/config/skills/visual-qa ] && cp -R "<path to your wjgoarxiv-skills clone>/variants/litgravity/visual-qa" ~/.gemini/config/skills/visual-qa printf '{"id":"%s","source":"%s","variant":"litgravity","installed_at":"%s"}\n' visual-qa "<path to your wjgoarxiv-skills clone>/variants/litgravity/visual-qa" "$(date -u +%Y-%m-%dT%H:%M:%SZ)" > ~/.gemini/config/skills/visual-qa/.litfamily-extension.json ``` Line one only looks: it prints every `SKILL.md` named visual-qa that agy could load, and nothing when there is none. agy keeps one same-name skill without a word, a workspace copy first, so move any other one it names aside too. Line two moves an existing copy whole into a dated folder under `~/.gemini/extension-backups/`, which agy never loads; line three copies into the emptied place; line four writes the receipt `.litfamily-extension.json` inside the copy. For one workspace only, run line one, then these three in the workspace root: ```bash if [ -e .agents/skills/visual-qa ] || [ -L .agents/skills/visual-qa ]; then b=~/.gemini/extension-backups/$(date +%Y%m%d-%H%M%S)-project; mkdir -p "$b" && mv .agents/skills/visual-qa "$b/" && echo "moved to $b/visual-qa"; fi mkdir -p .agents/skills && [ ! -e .agents/skills/visual-qa ] && cp -R "<path to your wjgoarxiv-skills clone>/variants/litgravity/visual-qa" .agents/skills/visual-qa printf '{"id":"%s","source":"%s","variant":"litgravity","installed_at":"%s"}\n' visual-qa "<path to your wjgoarxiv-skills clone>/variants/litgravity/visual-qa" "$(date -u +%Y-%m-%dT%H:%M:%SZ)" > .agents/skills/visual-qa/.litfamily-extension.json ``` The folder is the whole skill, with its own scripts, references and engine locks. Its neighbours (frontend-ui-ux, the builder this check accepts work from) install the same way, one folder each. Start a new conversation, or type `/skills reload`; the skill then answers as `/visual-qa`, and `lit` prompts that reach this stub hand over to it. To update it, run the same lines again: the old copy moves to a new dated backup and the receipt is rewritten. To remove it, run the second line alone. Nothing is deleted; clear old backups out of `~/.gemini/extension-backups/` when you no longer need them. The LitGravity installer writes only its own plugin folder, so upgrading or removing LitGravity leaves the copy alone, and the names never clash: this stub is `litgravity:visual-qa`, the copy is `visual-qa`. ## When this stub is read 1. Look for the installed copy with `read_file`: first `~/.gemini/config/skills/visual-qa/SKILL.md`, then `.agents/skills/visual-qa/SKILL.md` in the workspace. 2. **Found.** Read it and follow it for this task; its folder is the root for every relative path it names. It was written for agy and needs no LitGravity hook: every check it names is a command it tells you to run. 3. **Not found, asked directly.** Reply in a few lines: what visual-qa did, that it is a LitFamily extension now, kept in wjgoarxiv-skills (`variants/litgravity/visual-qa/`), the `extensions install` command and the install lines above, and that you made nothing yet. Do not describe the page from its source and call that a visual check. 4. **Not found, inside a workflow.** Inside review-work or litwork, record `visual-qa not installed` in the lane and give no visual verdict: the surface stays unchecked, not passed. ## Hard stops - Give the install lines with the placeholder; never a path from this machine. - Never say a visual check exists unless the installed copy made it and you looked at the result. - A headless run (`agy -p`) never copies the skill in itself: give the install lines and stop.
Comments (0)
Sign in to join the conversation.
Reviews (0)
No reviews yet.
No comments yet.