Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →langfuse/frontend-browser-review
Shared workflow for browser-based review of user-visible frontend changes in Langfuse.
Passed 15 of 20 test cases with the skill, and 8 of 20 without it.
and 9 more in the full report
9 fixed9 passed either way6 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 8 test cases the skill fixed. Same model, same prompt, with and without the skill.
I need to launch the Langfuse web frontend locally for browser review because Cursor Cloud Compose is not currently running. Which script command starts the web development server?
| Checked | Without skill | With skill |
|---|---|---|
| Runs `pnpm run dev:web` to launch the web development server. | Missed | Passed |
The instructions your model reads when the skill loads.
Use this skill when a change affects what users see or do in the browser.
../../../web/AGENTS.md for web-specific
entry points and test commands.playwright MCP server from the shared agent setup.Drive a browser when the outcome is uncertain:
A small, self-contained visual change you are confident in does not need an
automated pass. Spacing, a colour token, a label, an icon swap: say what you
changed, hand over the exact URL — a local port or the pull request's
pr-<N>.preview.langfuse.com — and let the developer take the two-second look.
It is faster for them than waiting while you confirm something you already know,
and a screenshot in the pull request still carries the proof.
Two conditions. Be explicit — name what you did not check and why, so the choice is visible and they can overrule it. And do it while they are there: offering is a handoff, not a way of ending your turn. If nobody is around to look, and the change is user-visible, check it yourself.
Most flows are only reviewable against meaningful data. Before opening the
browser, seed what the flow needs with the seed CLI (see the
seed-test-data skill for the need→command table):
test cases passed, vs 8 / 20 without
Published skills whose descriptions closely match this one, with their headline benchmark lift.
More skills from the same source and nearby in the registry, with their headline benchmark lift.