human-sim

Simulates persona-driven user journeys through a live product UI using Playwright tests.

31|2|Updated Mar 21, 2026
One-click install
npx skills add https://github.com/letuhao/lore-weave --skill human-sim-letuhao
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: human-sim
Source: https://github.com/letuhao/lore-weave/tree/main/.claude/skills/human-sim
Command: npx skills add https://github.com/letuhao/lore-weave --skill human-sim-letuhao

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Automated tests often assert what the code does today rather than what a real user would experience, so defects like search that only reads the first page of results survive every test. This Skill drives real user journeys through the live UI as named personas and ends each journey in a claim that can be false, producing actionable failures instead of vague impressions. ## Core Features & Use Cases - Persona-based journeys: Two enforced personas — a newcomer on a fresh empty account and a frequent user seeded to at least 25 books — catch empty-state problems and scale-related defects like pagination and truncation bugs. - Evidence tooling: Per-step x-trace-id labels, a log collector (collect_run_evidence.py) that exits non-zero when a correlated query matches nothing, and a humanRun.ts helper that captures a full-page snapshot per step, pass or fail. - Calibration discipline: Every journey must be validated by deliberately breaking the behavior it protects and watching the test go red, ensuring checks can actually fail. - Use Case: A user with 83 books searches their library by exact title and gets nothing because the frontend filters only the first 20 loaded rows; the frequent persona journey catches this, while a fresh-account suite would report success forever. ## Quick Start Run the persona journey Playwright spec against the local lw-iso frontend on port 25174 and review the per-step snapshots and collected logs for any failing claim.

Frequently Asked Questions about human-sim

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run the persona journey Playwright tests?

Run npx playwright test tests/e2e/specs/persona-journeys.spec.ts from the frontend directory with PLAYWRIGHT_BASE_URL set to http://localhost:25174. The journeys write data, so the target must be loopback; non-loopback targets are refused.

Why does the frequent persona require at least 25 books?

Scale-dependent defects like search filtering only the first loaded page do not exist below 21 books. The minBooks requirement is enforced by seeding, so the journey actually exercises pagination and truncation behavior a small account cannot reach.

Why does login fail with AUTH_INVALID_CREDENTIALS against port 25174?

The documented account credentials belong to the infra stack on port 5174, not the lw-iso stack on 25174. This is a wrong-stack error, not a broken login; use the correct stack's credentials.

Why can't a freshly registered account run generation journeys?

Provider credentials and default models are configured per owner_user_id, so a new account has no model and the assistant cannot write prose. Use the documented account with a throwaway book for generation journeys.

What does exit code 2 from collect_run_evidence.py mean?

A correlated log query that matches nothing exits 2 rather than 0, because an empty result with a green exit would falsely suggest a clean step. Check that the frontend image predates the trace header, the id was pinned, and the id was not malformed.

When should I rebuild the container image before running journeys?

Rebuild before testing your own change, because the container serves a baked build and an un-rebuilt image silently tests the previous commit. Verify by grepping the running container for a string only your change contains, not by trusting the build log.