Tracking Frontend Worker

What it does

When your agent uses it

• Tasks that involve Time tracking and reporting
• Tasks that involve Refactoring

Example prompts

• “/tracking-frontend-worker”

Workflow steps

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

1. 1Read mission mission.md, mission AGENTS.md, .factory/services.yaml, .factory/library/architecture.md, .factory/library/user-testing.md…
2. 2Translate the feature's expectedBehavior bullets and fulfills assertions into a concrete UI acceptance checklist before editing.
3. 3Read only the source docs from the closed set in mission AGENTS.md that govern this feature.
4. 4Write failing frontend tests first
5. 5Reuse http://127.0.0.1:5173 and http://127.0.0.1:8080. Do not start a new main frontend/backend runtime.
6. 6Implement the UI/state refactor only after the new tests fail for the intended reason.
7. 7Keep the page-family rule intact: /timer stays one route, and calendar, list, timesheet are view modes, not new pages.
8. 8Update the mission status blocks for every directly used source doc you relied on for the feature. Keep exactly one active mission block…
9. 9Run the narrowest website checks during iteration, then rerun the broader affected commands from .factory/services.yaml.
10. 10Use canonical root vp entrypoints only for JS/TS formatting, lint, typecheck, and test commands. Do not switch to ad hoc npx, standalone…
11. 11Use agent-browser to replay at least one real story path after automated tests pass unless the feature is purely non-visual. If you cannot…
12. 12In the handoff, explicitly state

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

Tracking Frontend Worker loads about 1.2k tokens when it runs. Until then it costs about 27 tokens; SKILL.md has 380 words of instructions outside code blocks.

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

~27

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

~1.2k

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). 380 words, ~1,238 tokens.

name

tracking-frontend-worker

description

Refactor and verify website timer/time-entry surfaces on the reused local runtime.

{
  "salientSummary": "Split shared timer-page state out of `WorkspaceTimerPage`, kept `/timer` as one page family, and made selected TimerView persist across view changes and refresh. Added browser proof for calendar/list/timesheet sharing the same top composer and current timer.",
  "whatWasImplemented": "Refactored the website timer page so calendar, list, and timesheet remain one `/timer` workbench with one shared top composer/header state and one current-timer identity. Added failing-first browser tests for same-route view switching plus TimerView persistence, updated the relevant timer research status blocks, and verified the behavior on the reused 5173/8080 runtime.",
  "whatWasLeftUndone": "",
  "verification": {
    "commandsRun": [
      {
        "command": "vp run test:e2e:website -- e2e/timer-page.spec.ts --workers 1",
        "exitCode": 0,
        "observation": "Timer page real-runtime coverage passed."
      },
      {
        "command": "vp run check -r",
        "exitCode": 0,
        "observation": "Repo JS/TS checks passed after the timer page refactor."
      }
    ],
    "interactiveChecks": [
      {
        "action": "Opened `/timer` in the reused website runtime, switched calendar/list/timesheet, refreshed, and rechecked the selected view plus top composer state.",
        "observed": "The app stayed on `/timer`, the selected TimerView persisted, and the same composer/header state remained active across all three views."
      }
    ]
  },
  "tests": {
    "added": [
      {
        "file": "apps/website/e2e/timer-page.spec.ts",
        "cases": [
          {
            "name": "keeps `/timer` stable while switching calendar, list, and timesheet",
            "verifies": "VAL-ENTRY-001"
          },
          {
            "name": "persists selected TimerView after refresh and workspace switch",
            "verifies": "VAL-CROSS-005"
          }
        ]
      }
    ]
  },
  "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/tracking-frontend-worker of CorrectRoadH/OpenTickly.

Open the folder on GitHubat commit 5ffd0a0