Skip to content
Skills Library
Programming · Testing

webapp-browser

/webapp-browser

Test anything in the local Rolebase webapp with the Playwright browser, signed in as a local test admin, with few tokens. Use to check a UI change, open a page or modal, take a screenshot, or test a flow end to end in the webapp (including /admin).

Repository
rolebase ↗
Licence
MIT
Last repository change
27.10.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
2
Scripts
1
HTML comments
0
URLs in SKILL.md
6
Deprecation

No signals detected. Repository changed on 27.10.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What to check before installing
  • 1 scripts in this package. Review them before installing, as Claude may execute them.

Scripts: scripts/ensure-account.mjs

What it does and when to use it

Test anything in the local Rolebase webapp with the Playwright browser, signed in as a local test admin, with few tokens. Use to check a UI change, open a page or modal, take a screenshot, or test a flow end to end in the webapp (including /admin).

Original author description

Test anything in the local Rolebase webapp with the Playwright browser, signed in as a local test admin, with few tokens. Use to check a UI change, open a page or modal, take a screenshot, or test a flow end to end in the webapp (including /admin).

How it works

  1. Sign in (one call)
  2. Save tokens
  3. Test data
Original SKILL.md headings · 39 lines, 340 words
SKILL.md preview
---
name: webapp-browser
description: Test anything in the local Rolebase webapp with the Playwright browser, signed in as a local test admin, with few tokens. Use to check a UI change, open a page or modal, take a screenshot, or test a flow end to end in the webapp (including /admin).
---

# Webapp browser tests

Local stack only: webapp `http://localhost:5175`, backend `http://localhost:8888/healthz`, Hasura `https://local.graphql.local.nhost.run/v1` (admin secret `nhost-admin-secret`), Mailhog `https://local.mailhog.local.nhost.run`. If the webapp or backend does not answer, ask the user to start the dev server.

## Sign in (one call)

1. Once per machine, create the test account (`browser-admin@skreo.net`, verified, admin role). The script is idempotent:
   `node .claude/skills/webapp-browser/scripts/ensure-account.mjs`
2. Open any webapp page with `browser_navigate`, then sign in with `browser_evaluate`. No email code needed:

```js
async () => {
  const r = await fetch('https://local.auth.local.nhost.run/v1/signin/email-password', { method: 'POST', headers: { 'content-type': 'application/json' }, body: JSON.stringify({ email: 'browser-admin@skreo.net', password: 'BrowserAdmin-local-2026!' }) })
  const { session } = await r.json()
  const p = JSON.parse(atob(session.accessToken.split('.')[1].replace(/-/g, '+').replace(/_/g, '/')))
  localStorage.setItem('nhostSession', JSON.stringify({ ...session, decodedToken: { ...p, iat: p.iat * 1000, exp: p.exp * 1000 } }))
  location.reload()
  return session.user.email
}
```

To test as a regular user, create another `@skreo.net` account the same way, without the admin role. "Log in as" in `/admin/users` also works.

## Save tokens

- `browser_navigate` and `browser_click` save the snapshot to `.playwright-mcp/*.yml`. Find refs with `grep -n "Label" <file>`, or `grep -n "Label" -A12 <file> | grep button`, instead of reading the snapshot.
- Read a part of the page with `browser_snapshot` and `target` (e.g. `[role=dialog]`) plus `depth`.
- Check a value with `browser_evaluate` returning a short string, not with a snapshot.
- Screenshots go in `.playwright-mcp/` (other paths are refused). Use `browser_resize` (e.g. 1280×1400) to fit a whole modal in a single screenshot.
- Batch independent calls in one message.

## Test data

- Seed through the admin GraphQL API with a `tsx` script outside the repo, run from `packages/backend` (`npx tsx /tmp/x/seed.ts`). Import `nhost` from `packages/backend/src/utils/nhost` and call `nhost.graphql.request({ query, variables })`. Throw if `nhost.graphql.url` does not contain `local`.
- Only `@skreo.net` emails. Use a recognizable prefix in emails and slugs so the cleanup can find them.
- Clean up at the end with `deleteOrgsForGood` and `deleteUserForGood` from `packages/backend/src/features/deletion/utils/`, then check that nothing with the prefix remains. Keep the `browser-admin` account.
- Sign-in codes and other emails: Mailhog API at `https://local.mailhog.local.nhost.run/api/v2/messages?limit=1`.
Files in this package (2)
  • SKILL.md 3 KB
  • scripts/ensure-account.mjs 2 KB

Versions

The database has no other skills named webapp-browser.

Database snapshot: 13.11.2026 · package version 995abb78d25d (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 95memstack-development-webapp-testing
    Use when the user says 'write browser tests', 'test this page', 'playwright test', 'e2e test', 'end to end test', 'browser test', 'test the UI', or needs Playwright-based browser testing for a web application. Do NOT use for unit tests, API tests, or non-browser testing.
  • 100webapp-testing
    Browser-tests a local webapp end to end — starts the app, installs Playwright if missing, writes a spec for the critical path plus edge cases, runs headless, captures screenshots, console and network logs on failure, and reports a pass/fail table with repro steps. Degrades to…
  • 100webapp-testing
    Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs. Use when testing web apps, automating browser interactions, or debugging frontend issues.
  • 100webapp-testing
    Toolkit for interacting with and testing local web applications using Playwright. Use when verifying frontend functionality, debugging UI behavior, capturing browser screenshots, or viewing browser logs.
  • 100webapp-testing
    Toolkit for interacting with and testing local web applications using Playwright. Use for browser smoke tests, verifying UI changes on localhost, end-to-end UI flows (login, forms, charts), Playwright MCP browser automation, debugging UI behavior, capturing browser screenshots,…
  • 100webapp-testing
    End-to-end web testing with Playwright - route discovery, critical flows, visual and API checks; use for e2e tests.

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.