Run any Skill in Manus with one click

visual-review

Stars1

Forks0

UpdatedMay 12, 2026 at 12:20

Visually verify rendered output for web pages, PRs, CLI commands, and TUIs. Use when the user asks for "visual review", "visual QA", "screenshot this", "check how this PR looks", "review CLI output", "capture a terminal command", or "record this TUI". Inputs - target URL or PR number, mode (browser / CLI / TUI / regression), and routes / commands / viewports to check. Do not use when the user wants functional QA (use a testing skill), brand-taste judgment (this verifies rendered output, not design taste), frontend-stack migration (out of scope), or wants to push commits (this is read-only). Produces a screenshot or recording set + a visible-issues report listing artifact paths, routes/commands/viewports inspected, and any layout/overflow/state-coverage gaps found. Escalate if the target is unreachable, the PR is too large for a single review pass (recommend scope reduction), or the local dev server cannot start.

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

Naoray

Naoray/skills

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software Quality Assurance Analysts and TestersComputer and Mathematical Occupations·SOC 15-1253

File Explorer

8 files

SKILL.md

readonly

name

visual-review

description

Visual Review

Verify what the user can see: layout, overflow, responsive behavior, hierarchy, terminal rendering, screenshots, and obvious visual regressions.

Evidence tier: P (practitioner-backed) Basis: visual QA heuristics — layout stability, overflow, responsive behavior, hierarchy, affordance clarity, terminal legibility, state coverage. Adjacent to WCAG accessibility standards (E-tier) but this skill scopes to visible-output verification, not full accessibility audits. Source IDs: WCAG 2.x accessibility guidelines, Nielsen usability heuristics, Naoray internal visual-review + visual-review-cli predecessors (now consolidated here). Reviewed: 2026-05-12

Context Budget

Read only:

This file.
workflows/preflight.md.
One mode workflow.
references/principles/visual-qa.md when judging findings.

Do not load every file in this skill. evals/ is not runtime context.

Route

Read this file. Then read exactly one of:

workflows/web-review.md — browser/UI review of a PR or live URL across viewports.
workflows/cli-review.md — terminal/TUI capture using termshot (static) or vhs (recordings).
workflows/regression.md — before/after comparison for visual diffs.

If a PR changes both browser UI and CLI/TUI output, run the relevant modes separately and report them in one final summary.

Required First Step

Always read workflows/preflight.md before the selected workflow.

Output Rule

Every output MUST include screenshot or recording paths when artifacts were created, plus the routes, commands, viewport sizes, and states inspected — because a visual-review without an artifact and scope statement is just a claim, not evidence the reviewer can verify.

More from this repository

same repository

orchestrator-mode

Naoray/skills

Use when the user says `/orchestrator-mode`, asks you to coordinate agents, or gives large multi-phase work needing parallel delegation, reviews, PRs, scratchpads, or handoffs. Inputs - project goal, repo context, Solo agents/processes, branch/worktree constraints, locked user decisions. Do not use for a direct small edit, a normal code review, or single-agent implementation; use focused coding/review skills instead. Produces delegation plan, agent briefs, monitoring protocol, review/merge routing, state hygiene rules. Escalate on unclear scope, product direction, merge authority, destructive cleanup, or tool availability. Delegates are Solo processes: prefer Solo MCP tools, falling back to the `solo` CLI only when MCP is unavailable - never the in-process Task/Agent tool.

2026-06-041

init-rust

Naoray/skills

Use when initializing Rust best-practices rules in a project, the user invokes `/init-rust`, or a new Rust workspace needs convention rules wired up for an agent. Inputs - target project root, an existing or creatable `.claude/rules/` directory, and confirmation the project targets Rust edition 2024 (rules assume 2024 + MSRV 1.85). Do not use when the user wants language-agnostic project init, framework-specific scaffolding (axum, tauri, leptos, etc.), or actual code generation; use those skills or write code directly. Produces `.claude/rules/rust.md` with `paths: "**/*.rs"` frontmatter covering workspace layout, error handling, async/Tokio, CLI (clap), serde, tracing, type system, process supervision, security, testing, naming, tooling, and Edition 2024 changes. Escalate if `.claude/rules/rust.md` already exists with manual edits, the project is not a Rust workspace, or the user targets an edition older than 2024.

2026-05-221

apple-calendar

Naoray/skills

Use when the user asks to list Apple Calendar calendars or events, create/update/delete events, search appointments, or manage recurrence in Calendar.app on macOS. Inputs - calendar name when needed, event UID for read/update/delete, event title, start/end times, location/description/recurrence details for writes. Do not use when the user needs Google/Outlook calendar APIs, cross-platform sync, or general scheduling advice; use a service-specific calendar integration instead. Produces Calendar.app script commands and parsed event/calendar results. Escalate if calendar permissions are missing, the target calendar is read-only, dates are ambiguous, or deleting a recurring event could remove an entire series.

2026-05-221

dev-browser

Naoray/skills

Use when the user asks to navigate a website, click UI, fill forms, take screenshots, scrape visible page data, test a web app, log into a browser session, or automate browser workflows with persistent page state. Inputs - target URL or existing page context, desired browser action, selectors or visible labels when known, credentials only when user explicitly provides them. Do not use when a plain HTTP request, local file edit, or Playwright test suite is the better artifact; use those tools instead. Produces dev-browser CLI commands or sandboxed JavaScript automation steps plus captured results. Escalate if login, payment, destructive actions, CAPTCHA, or sensitive personal data is involved.

2026-05-221

meeting

Naoray/skills

Use when the user says "/meeting [title]", "/meeting end", or wants live meeting note capture from raw fragments during an active meeting. Inputs - meeting title, type, attendees, active meeting state, and real-time notes or end command. Do not use when the user wants post-hoc meeting summarization, a transcript cleanup, or general note-taking outside meeting mode; use summarization or writing skills instead. Produces structured raw notes, action items, decisions, and a shareable meeting summary for review. Escalate if no title is provided, no meeting is active on end, another meeting is already active, or content appears sensitive enough to require confirmation before writing.

2026-05-221

record

Naoray/skills

Use when the user says "/record [message]" or when a meaningful workday event needs a concise timestamped entry in today's running log. Inputs - exact message for manual entries, current date/time, daily note location, and enough context to judge whether an automatic entry is meaningful. Do not use when the user wants a full journal entry, meeting notes, or end-of-day synthesis; use writing, meeting, or evaluate-day instead. Produces one deduplicated timestamped Running Log entry in today's daily note. Escalate if the daily note path cannot be created, the entry would duplicate existing content, or automatic logging would expose sensitive content.

2026-05-221

name

visual-review

description

Visual Review

Verify what the user can see: layout, overflow, responsive behavior, hierarchy, terminal rendering, screenshots, and obvious visual regressions.

Context Budget

Read only:

This file.
workflows/preflight.md.
One mode workflow.
references/principles/visual-qa.md when judging findings.

Do not load every file in this skill. evals/ is not runtime context.

Route

Read this file. Then read exactly one of:

workflows/web-review.md — browser/UI review of a PR or live URL across viewports.
workflows/cli-review.md — terminal/TUI capture using termshot (static) or vhs (recordings).
workflows/regression.md — before/after comparison for visual diffs.

If a PR changes both browser UI and CLI/TUI output, run the relevant modes separately and report them in one final summary.

Required First Step

Always read workflows/preflight.md before the selected workflow.