ralph-loop-webapp

Coordinate atomic web app development tasks with Playwright MCP verification.

Updated Aug 27, 2026

Search Tags:#automation #playwright-mcp #ralph-loop #atomic-tasks #memory-protocol #web-app-development

Ready to run

npx skills add https://github.com/zjh08177/agent-harness --skill ralph-loop-webapp

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: ralph-loop-webapp
Source: https://github.com/zjh08177/agent-harness/tree/main/skills/ralph-loop-webapp
Command: npx skills add https://github.com/zjh08177/agent-harness --skill ralph-loop-webapp

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Coordinating end-to-end web app development workflows by organizing atomic tasks, persistent memory, and automated browser verification to reduce manual toil and ensure repeatable outcomes.

Core Features & Use Cases

Atomic task execution: drives one clearly defined task per iteration from TASKS.md with per-task verification.
Playwright MCP verification: automatically validates each task against browser automation and accessibility criteria.
Memory & history continuity: maintains context across sessions via built-in .claude memory files (context.md, history.md, findings.md, decisions.md).
Auto-commit workflow: batches changes per task and pushes updates via the harness auto-commit hook.

Quick Start

Bootstrapping the repository, start a Ralph Loop session and begin with T1.1 from TASKS.md.

Frequently Asked Questions about ralph-loop-webapp

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

FAQPage Schema

How do I automate web app development workflows with atomic tasks and persistent memory?▼

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.

How does Playwright MCP verification work for iterative feature development?▼

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.

Can I maintain development context across sessions for web app bug fixing?▼

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.

What is the Ralph Loop protocol for automated end-to-end web app development?▼

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.

Do I need an auto-commit hook to batch changes per atomic task?▼

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.

When should I not use an atomic task loop for web app development?▼

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.