ralph-loop-webapp

Automate web app development by coordinating one atomic task per iteration from TASKS.md, maintaining context across sessions via memory files, and verifying results with Playwright MCP to ensure repeatable outcomes.

Playwright MCP verification automatically validates each atomic task against browser automation and accessibility criteria, ensuring that iterative feature development and bug fixes meet expected behavioral outcomes before proceeding.

Yes, you can maintain development context across sessions using built-in memory files like context.md, history.md, findings.md, and decisions.md, which preserve project state for continuous bug fixing and feature work.

The Ralph Loop protocol requires atomized TASKS.md entries, persistent memory files, Playwright MCP browser verification, and auto-commit integration to coordinate end-to-end web app development workflows with minimal manual toil.

Yes, the workflow batches code changes per atomic task and pushes updates via the harness auto-commit hook, ensuring that repository state remains synchronized with the completed task verification.

An atomic task loop is not suited for ad-hoc prototyping or exploratory coding lacking clear definitions, as it requires atomized TASKS.md entries and explicit Playwright MCP verification criteria for each iteration.