Frontend Smoke Gate
Purpose
Prevent "code changed, user finds the obvious UI bug" loops. User-facing UI is
not ready until the agent has exercised the page and inspected the resulting
interface artifact.
Required Gate
For non-trivial user-facing UI changes:
- Run the repo's static gates: build/typecheck and lint when available.
- Run or add a focused smoke script that opens the actual route, checks the
relevant backend/API endpoints, and creates a screenshot artifact.
- Inspect the screenshot yourself before reporting success.
- Check for the common user-facing failures:
- stale/test data leaking into the main UI,
- old receipts shown as current replies,
- cards or panels overlapping,
- text clipping or unreadable density,
- missing acknowledgement/result receipt,
- layout broken on the primary target surface.
- If the screenshot shows an obvious issue, patch and rerun the gate.
Public/Live Release Guard
For public links, collaborator-facing pages, shared mobile pages, or any surface
another person may already be using:
- Do not serve directly from the active worktree unless the service is explicitly
marked local-only or experimental-private.
- Create a staged release candidate first, run static checks, run a local
staging server, and smoke the exact public route plus at least one backend
receipt path.
- Switch public traffic only after the staged release passes. Prefer a symlink,
blue-green slot, named release directory, or equivalent atomic pointer
change; keep the previous release for rollback.
- If a live public link is down, first restore the last known-good release or
transport, then continue development behind staging.
- Report release status as: current public URL, release id/path, smoke result,
rollback path, and remaining transport risk.
Fallbacks
- If Playwright or a browser automation layer exists, prefer DOM assertions plus
screenshot comparison.
- If it does not exist, use the platform browser plus a screen-capture tool; keep
the screenshot path in the report and state any remaining manual/visual gap.
- Do not ask the user to inspect the UI first when the agent can open and inspect
it locally.
Output Contract
Report:
- user-visible change,
- validation commands and pass/fail,
- screenshot path for audit,
- remaining anti-signal or missing automation, if any.
provenance:
maker: Starshard
homepage: https://github.com/starshard-ai
source: https://github.com/starshard-ai/reviewer-wheels
license: MIT
version: 0.1.0
contact: https://github.com/starshard-ai/reviewer-wheels/issues
About the maker: Starshard builds open agent skills; you can find the source and report issues at https://github.com/starshard-ai. License: MIT.
1---2name: frontend-smoke-gate3description: Use when changing a user-facing frontend, dashboard, chat, mobile/web channel, notification surface, or any UI that a person is expected to personally try. Run build/lint plus a real-page smoke and screenshot/visual check before handoff.4---56# Frontend Smoke Gate78## Purpose910Prevent "code changed, user finds the obvious UI bug" loops. User-facing UI is11not ready until the agent has exercised the page and inspected the resulting12interface artifact.1314## Required Gate1516For non-trivial user-facing UI changes:17181. Run the repo's static gates: build/typecheck and lint when available.192. Run or add a focused smoke script that opens the actual route, checks the20 relevant backend/API endpoints, and creates a screenshot artifact.213. Inspect the screenshot yourself before reporting success.224. Check for the common user-facing failures:23 - stale/test data leaking into the main UI,24 - old receipts shown as current replies,25 - cards or panels overlapping,26 - text clipping or unreadable density,27 - missing acknowledgement/result receipt,28 - layout broken on the primary target surface.295. If the screenshot shows an obvious issue, patch and rerun the gate.3031## Public/Live Release Guard3233For public links, collaborator-facing pages, shared mobile pages, or any surface34another person may already be using:35361. Do not serve directly from the active worktree unless the service is explicitly37 marked local-only or experimental-private.382. Create a staged release candidate first, run static checks, run a local39 staging server, and smoke the exact public route plus at least one backend40 receipt path.413. Switch public traffic only after the staged release passes. Prefer a symlink,42 blue-green slot, named release directory, or equivalent atomic pointer43 change; keep the previous release for rollback.444. If a live public link is down, first restore the last known-good release or45 transport, then continue development behind staging.465. Report release status as: current public URL, release id/path, smoke result,47 rollback path, and remaining transport risk.4849## Fallbacks5051- If Playwright or a browser automation layer exists, prefer DOM assertions plus52 screenshot comparison.53- If it does not exist, use the platform browser plus a screen-capture tool; keep54 the screenshot path in the report and state any remaining manual/visual gap.55- Do not ask the user to inspect the UI first when the agent can open and inspect56 it locally.5758## Output Contract5960Report:6162- user-visible change,63- validation commands and pass/fail,64- screenshot path for audit,65- remaining anti-signal or missing automation, if any.6667<!-- skill-provenance:begin -->68provenance:69 maker: Starshard70 homepage: https://github.com/starshard-ai71 source: https://github.com/starshard-ai/reviewer-wheels72 license: MIT73 version: 0.1.074 contact: https://github.com/starshard-ai/reviewer-wheels/issues75<!-- skill-provenance:end -->7677---78*About the maker:* Starshard builds open agent skills; you can find the source and report issues at https://github.com/starshard-ai. License: MIT.
starshard-ai