Frontend Test Worker

What it does

When your agent uses it

• Tasks that involve End-to-end testing

Example prompts

• “/frontend-test-worker”

Workflow steps

12 steps, taken from the first numbered list in SKILL.md.

1. 1Read mission.md, mission AGENTS.md, .factory/services.yaml, and .factory/library/user-testing.md.
2. 2Identify which validation assertions the feature fulfills and treat those as the non-negotiable acceptance checklist.
3. 3Write or update failing frontend tests first
4. 4Keep E2E naming aligned with the mission rule: E2E already means real runtime, so new tests should use normal *.spec.ts.
5. 5Reuse local runtime on 5173 and 8080; do not move to alternate local ports unless the orchestrator changes the boundary.
6. 6When the feature is about navigation or reachability, prove it by clicking through the visible shell UI instead of only using direct goto.
7. 7When the feature is about timer page-family behavior, verify calendar, list, and timesheet under the same seeded facts and stable /timer…
8. 8Run the narrowest relevant frontend tests during iteration, then rerun the broader website E2E command(s) affected by the feature.
9. 9Use agent-browser after the automated tests pass to confirm one real story path and capture any mismatch between runtime behavior and the…
10. 10If the feature claims a code fix, verify that the commitId reported in the handoff directly contains the feature's code changes. If the…
11. 11Do not treat a rerun-only pass as completion for a flaky-fix feature. If the assigned fix was stabilizing a flaky path, the handoff must…
12. 12Keep the fix scoped to the assigned feature. If a flaky-fix or validator-repair change seems to require unrelated assertion rewrites or…

What it can do on your machine

Read from SKILL.md and the folder at commit 5ffd0a0. It shows what the files ask for, not the result of running them.

• Tool permissions

  Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

  From allowed-tools in the SKILL.md frontmatter.

• Runs code

  No scripts in the folder and no shell commands in SKILL.md (its code samples are json).

  From the folder's file list and the shell code blocks in SKILL.md.

• Network

  No URLs in SKILL.md.

  From URLs in SKILL.md, links to its own repository left out.

• Credentials

  Names no API keys, tokens, secrets or passwords.

  From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Frontend Test Worker loads about 1.4k tokens when it runs. Until then it costs about 25 tokens; SKILL.md has 542 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it

~25

When it runs · the whole SKILL.md, loaded when a task matches

~1.4k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from CorrectRoadH/OpenTickly at commit 5ffd0a0, republished under its AGPL-3.0 licence (© CorrectRoadH). 542 words, ~1,443 tokens.

name

frontend-test-worker

description

Build and verify page-flow and E2E coverage for the tracking browser surface.

{
  "salientSummary": "Added timer page-family browser coverage for `/timer` default calendar landing, subview switching, and shell navigation entry. Verified the same seeded running timer remains visible across calendar/list/timesheet on the reused 5173/8080 runtime.",
  "whatWasImplemented": "Created page-flow and Playwright coverage for the tracking timer mainline. The browser tests now prove direct `/timer` entry and shell navigation converge on the same timer state, `/timer` keeps a stable URL while subviews switch, and running/stopped timer facts remain consistent across calendar, list, and timesheet.",
  "whatWasLeftUndone": "",
  "verification": {
    "commandsRun": [
      {
        "command": "vp run test:e2e:website -- e2e/timer-page.spec.ts",
        "exitCode": 0,
        "observation": "Timer E2E passed against the reused local runtime."
      },
      {
        "command": "vp run check -r",
        "exitCode": 0,
        "observation": "Repo-wide JS checks passed after the frontend test updates."
      }
    ],
    "interactiveChecks": [
      {
        "action": "Used agent-browser to click the visible Timer nav item from the authenticated shell and then switched calendar/list/timesheet.",
        "observed": "The page stayed on `/timer`, Timer nav became active, and the same seeded timer facts remained visible according to each view."
      }
    ]
  },
  "tests": {
    "added": [
      {
        "file": "apps/website/e2e/timer-page.spec.ts",
        "cases": [
          {
            "name": "opens `/timer` on calendar and keeps stable URL while switching subviews",
            "verifies": "VAL-TIMER-001 and VAL-TIMER-002"
          },
          {
            "name": "shows the same running timer across calendar, list, and timesheet",
            "verifies": "VAL-TIMER-004"
          }
        ]
      }
    ]
  },
  "discoveredIssues": []
}

© CorrectRoadH, AGPL-3.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .factory/skills/frontend-test-worker of CorrectRoadH/OpenTickly.

Open the folder on GitHubat commit 5ffd0a0