samples

Forge samples

Three exemplar projects, each shaped like one that's had /forge init run on it. Each sample includes a few seeded snippets — real forge output — and a walkthrough that has you run forge yourself to watch the library grow.

Sample	Target	What it exemplifies
shop/	practicesoftwaretesting.com	Auth + multiple test accounts. Includes the account-table hint pattern, a .env.example, and a four-step walkthrough covering library reuse, new authoring, spec mode, and teach mode. Read this one first if your project has authentication.
internet/	the-internet.herokuapp.com	Small isolated interaction patterns — dialogs, drag-and-drop, shadow DOM, async loading. No auth. Shows variant-arg parameterisation.
widgets/	demoqa.com	Legacy-widget gauntlet — Kendo, jQuery UI sortable, React date pickers, Bootstrap modals. Shows compositional decomposition (fill + read pairs).

What's in each sample

Each sample is a project root containing a forge/ subdir — the layout you get after running /forge init in a project, plus a couple of real forge runs:

• forge/hints/ — the authored hints (forge.md, plus curator.md if snippet conventions deviate) demonstrating what good hint authoring looks like for this kind of site.
• forge/playwright.config.ts — the scaffolded fallback Playwright config /forge init would create.
• forge/snippets/ — seeded with a small set of real forge output. The walkthrough builds on these.
• README.md (at the sample root) — meta-documentation explaining what the sample demonstrates, plus the walkthrough.
• .env.example (shop only, at the sample root) — the env keys the account-table references, with the seeded demo credentials filled in.

Everything not committed (gitignored, populated automatically when you run forge):

• New forge/snippets/ entries beyond the seeded ones — produced by forge:curator during your drives.
• forge/specs/ — composed by forge:driver during your spec-mode runs.
• forge/node_modules/ + forge/package.json — Playwright runner deps. Forge lazy-installs them on first invocation (~30s, one-time per sample). No manual npm install needed.
• forge/videos/, forge/test-results/, .env — local working state and your filled-in credentials.

How to use these samples for your own project

1. Pick the closest match. Shop for auth-bearing apps; internet for probe-shaped public sites; widgets for legacy-UI-library-heavy sites.
2. Read the chosen sample's README.md and forge/hints/. Note the structure — forge.md is the single operate-the-app file: account tables, then selector inventories and gotchas. Adapt the structure to your project.
3. Walk through the prompts. Each sample's README has a sequence of /forge invocations that demonstrate library reuse, new authoring, spec mode, and (for shop) teach mode. Run them. Watch the library grow.
4. Author your own forge/hints/forge.md following the same shape against your project. The smaller hint file (curator.md) is usually unnecessary; the agent defaults cover it.
5. Run forge against your project. Drive a task; the curator accretes a library; spec-mode adds verified specs on top.