From 4da54c8ca9853e52e56aacaf03e1b073c2fc584e Mon Sep 17 00:00:00 2001 From: Zeid Derhally Date: Sat, 7 Feb 2026 05:39:59 -0500 Subject: [PATCH 1/2] fix: direct agent validation screenshots to .autoforge/validation and gitignore them Closes #170 Co-Authored-By: Claude Opus 4.6 --- .claude/templates/coding_prompt.template.md | 2 +- .claude/templates/testing_prompt.template.md | 2 +- CLAUDE.md | 1 + autoforge_paths.py | 1 + 4 files changed, 4 insertions(+), 2 deletions(-) diff --git a/.claude/templates/coding_prompt.template.md b/.claude/templates/coding_prompt.template.md index c8d3ba6b..ce58e155 100644 --- a/.claude/templates/coding_prompt.template.md +++ b/.claude/templates/coding_prompt.template.md @@ -90,7 +90,7 @@ Use browser automation tools: - Navigate to the app in a real browser - Interact like a human user (click, type, scroll) -- Take screenshots at each step +- Take screenshots at each step and store them in the `.autoforge/validation` directory - Verify both functionality AND visual appearance **DO:** diff --git a/.claude/templates/testing_prompt.template.md b/.claude/templates/testing_prompt.template.md index c8011a3e..e938238d 100644 --- a/.claude/templates/testing_prompt.template.md +++ b/.claude/templates/testing_prompt.template.md @@ -31,7 +31,7 @@ For the feature returned: 1. Read and understand the feature's verification steps 2. Navigate to the relevant part of the application 3. Execute each verification step using browser automation -4. Take screenshots to document the verification +4. Take screenshots to document the verification and store them in the `.autoforge/validation` directory 5. Check for console errors Use browser automation tools: diff --git a/CLAUDE.md b/CLAUDE.md index e0f9ea3e..bb3762bd 100644 --- a/CLAUDE.md +++ b/CLAUDE.md @@ -287,6 +287,7 @@ Projects can be stored in any directory (registered in `~/.autoforge/registry.db - `.autoforge/features.db` - SQLite database with feature test cases - `.autoforge/.agent.lock` - Lock file to prevent multiple agent instances - `.autoforge/allowed_commands.yaml` - Project-specific bash command allowlist (optional) +- `.autoforge/validation` - Agent produced artifacts when validating work - `.autoforge/.gitignore` - Ignores runtime files - `CLAUDE.md` - Stays at project root (SDK convention) - `app_spec.txt` - Root copy for agent template compatibility diff --git a/autoforge_paths.py b/autoforge_paths.py index 8283a9b9..cd5f0ac5 100644 --- a/autoforge_paths.py +++ b/autoforge_paths.py @@ -43,6 +43,7 @@ .claude_assistant_settings.json .claude_settings.expand.*.json .progress_cache +validation/ """ From 3575eaed5fe2102feb67c30970bfbe7394b743c1 Mon Sep 17 00:00:00 2001 From: Zeid Derhally Date: Sat, 7 Feb 2026 18:27:53 -0500 Subject: [PATCH 2/2] use screenshots directory instead --- .claude/templates/coding_prompt.template.md | 2 +- .claude/templates/testing_prompt.template.md | 2 +- autoforge_paths.py | 2 +- 3 files changed, 3 insertions(+), 3 deletions(-) diff --git a/.claude/templates/coding_prompt.template.md b/.claude/templates/coding_prompt.template.md index ce58e155..bc2569cb 100644 --- a/.claude/templates/coding_prompt.template.md +++ b/.claude/templates/coding_prompt.template.md @@ -90,7 +90,7 @@ Use browser automation tools: - Navigate to the app in a real browser - Interact like a human user (click, type, scroll) -- Take screenshots at each step and store them in the `.autoforge/validation` directory +- Take screenshots at each step and store them in the `.autoforge/screenshots` directory - Verify both functionality AND visual appearance **DO:** diff --git a/.claude/templates/testing_prompt.template.md b/.claude/templates/testing_prompt.template.md index e938238d..6e7183ab 100644 --- a/.claude/templates/testing_prompt.template.md +++ b/.claude/templates/testing_prompt.template.md @@ -31,7 +31,7 @@ For the feature returned: 1. Read and understand the feature's verification steps 2. Navigate to the relevant part of the application 3. Execute each verification step using browser automation -4. Take screenshots to document the verification and store them in the `.autoforge/validation` directory +4. Take screenshots to document the verification and store them in the `.autoforge/screenshots` directory 5. Check for console errors Use browser automation tools: diff --git a/autoforge_paths.py b/autoforge_paths.py index cd5f0ac5..23d73d45 100644 --- a/autoforge_paths.py +++ b/autoforge_paths.py @@ -43,7 +43,7 @@ .claude_assistant_settings.json .claude_settings.expand.*.json .progress_cache -validation/ +screenshots/ """