frontend visual qa

Other Community

Skill notes

Scope And Routing

Use this skill only after a rendered artifact exists. Select the smallest audit profile that covers the request: core visual — composition, typography, spacing, wrapping, clipping, images; responsive — breakpoints, reflow, mobile alternatives, scroll ownership; state and journey — conditional branches, transitions, recovery, routes;

Required Outcome

Produce all of the following: A scope contract naming the artifact, actor, job, target kind and canonical target identity, conditional state, viewports, affected journeys, reference/SSOT, and authorization. A verification status: verified, partial, or blocked.

Workflow

Track this checklist for nontrivial audits: [ ] 1. Establish the audit contract and authorization [ ] 2. Select the required evidence level and canonical harness [ ] 3. Prove the target, state, data, viewport, and claimed freshness [ ] 4. Capture and inspect macro, local, and responsive evidence

1. Establish The Audit Contract

Read the project instructions, design-system SSOT, tokens, approved assets, launcher/test SOP, and the changed code. Then write a falsifiable contract: Artifact/page type: Actor and job: Target kind + canonical identity:

2. Select The Evidence Level

Use the strongest level required by the claim: Level · Evidence · Claims it can support A · Real visible Chrome/browser or canonical native-app window, driven through the user journey · Browser/OS chrome, downloads, clipboard, popup blocking, file pickers/dialogs, print preview, permissions, native shell, actual visible-window complaints B · Same-state browser DevTools or project E2E/Playwright run with representative data · DOM geometry, routes, focus, overlays, interaction states, repeatable responsive behavior

Fluxly profile Runtime and permissions are inferred by Fluxly static checks, not author declarations or runtime test results.
Domain
Other
Author-declared agents
No explicit declaration found; this is not inferred or tested compatibility
Static check
88 / 100 · heuristic scan, not runtime safety proof
Runtime evidence
Not run; no isolated runtime test evidence is currently recorded
Author / version / license
@daymade · no license declared
Token usage
Heavy
Setup complexity
Guided setup
External API key
Not required
Operating systems
macOS · Linux · Windows
Runtime requirements
Node.js
Detected file/system behavior
  • Read-only
  • Write / modify
  • Shell exec
Network behavior
Local-only
Install commands
None (reference only)

Heads up: Tool permissions are not declared; actual access depends on the runtime.

Output preview frontend-visual-qa.preview
# 5. Exercise Journeys And Outputs

- click -> URL/state -> refresh -> deep link -> back/forward;
- drawer/modal/popover open, focus, background interaction, close, and mobile;
- transient notification lifecycle with observation armed before the trigger;
- advanced mode -> visible current mode and trigger owner -> one-step return to default;
- provider/model/runtime status -> selected configuration and current status evidence;
- download -> completed file -> opened recipient artifact;

Discussion

Powered by GitHub Discussions. Sign in with GitHub to comment, react, or subscribe.