r/ClaudeWorkflows • • 10h ago

Selected Workflow [Workflow] Repository handoffs and review gates for a stateless asset-making agent

2 Upvotes

Repository handoffs and review gates for a stateless asset-making agent

Workflow value: 78/100
Status: active · Freshness: 70/100 · Confidence: 0.94 · Level: intermediate
Categories: Quality Control, Context & Memory, Debugging, Shipping, CLAUDE.md
Original source: r/ClaudeCode post/comment

What problem this solves

Give a stateless asset-making agent consistent project knowledge and review criteria without relying on session memory or duplicating decisions across documents.

Summary

Organize versioned repository documents by ownership, use a root handoff to select required reading, and run each asset through a documented creation and human-review process.

Why it is useful

It provides a concrete, adaptable way to give agents scoped project knowledge and evaluate creative output against documented standards and approved examples, while keeping a human decision gate.

Workflow

  1. Create a root handoff that maps work types to the documents agents should read.
  2. Maintain short repository-wide rules in AGENTS.md, including safety, architectural boundaries, and work-landing conventions.
  3. Separate the model-making method, art direction, decision register, specifications, budgets, shared-library guidance, and engine asset contract into owned documents.
  4. For every task, read the repository rules, model method, art direction, and issue; load other documents as the brief requires.
  5. Consult approved models, review notes, and captures as concrete quality references, and read earlier attempts for functional requirements rather than copying their implementation.
  6. Follow the model method: brief and written design, build in code, inspect each round, integrate into the game, and obtain independent review and a blind lineup.
  7. Require a human verdict before landing, and keep the model README status and relevant decision records current.

Tools / artifacts

  • AGENTS.md
  • Root handoff file
  • model-method.md
  • art-direction.md
  • Domain decision register and index
  • Building specification cards
  • model-budgets.md
  • Shared materials and goods library READMEs
  • Engine asset contract
  • Reference model source, review notes, and captures
  • Task issue and model README

Validation signals

  • The described process calls for inspection at fixed camera distances and comparison against approved reference models.
  • It includes independent review, a blind lineup, and a human verdict before landing.
  • The comment describes an established document structure and task-specific reading rules, but reports no measured outcomes or completed example.

Cautions

  • The stated repository rules prohibit committing secrets or writing to real player save folders during tests.
  • Independent review and a human landing decision provide oversight, although the comment does not specify how review independence is enforced.

Limitations

  • No repository, document templates, or runnable implementation is provided.
  • No before-and-after result, test evidence, or community success report is supplied.
  • The blind-lineup procedure and enforcement of document freshness and ownership are not specified.
  • The workflow is not explicitly Claude-specific; AGENTS.md may need adaptation to the user's Claude Code setup.

Rate this workflow

Upvote this post if the workflow is useful, reproducible, or worth recommending.

Downvote if it is vague, outdated, unsafe, overhyped, or not reproducible.

Reply if it worked for you, failed, is outdated, or has a better alternative.


This post was generated automatically from the workflow library database.


r/ClaudeWorkflows • • 2h ago

Selected Workflow [Workflow] Use a reference implementation as a test oracle for Claude Code

1 Upvotes

Use a reference implementation as a test oracle for Claude Code

Workflow value: 75/100
Status: active · Freshness: 70/100 · Confidence: 0.96 · Level: advanced
Categories: Quality Control, Token Saving, Context & Memory, Debugging
Original source: r/ClaudeCode post/comment

What problem this solves

Improving the accuracy of a complex implementation when documentation alone is insufficient and small behavioral differences cause failures.

Summary

Implement isolated components in human-approved phases, then use an established reference implementation to generate expected outputs and drive repeated test-and-fix cycles with Claude Code.

Why it is useful

It describes a repeatable, evidence-backed development loop in which tests and reference behavior constrain Claude’s fixes, rather than relying on generated code or incomplete documentation alone.

Workflow

  1. Define an integration milestone that requires several core components to work together.
  2. Isolate components so Claude can work on a limited portion of the code at a time.
  3. Create a phased action plan for each component, review and approve it, then implement and review the changes.
  4. Use strict component-level tests, such as single-step processor tests, during implementation.
  5. Build a trusted reference implementation locally and generate reference outputs for a relevant test suite.
  6. Run the implementation against those outputs, have Claude investigate and fix behavioral differences, and repeat.
  7. Keep the resulting suite as a regression test and provide precise human direction for usability decisions.

Tools / artifacts

Validation signals

  • The author reports reaching the Kickstart insert-disk screen and later running a game cracktro, initially with glitches.
  • The author reports that reference-output comparisons let Claude fix behavioral differences and were the turning point for accuracy.
  • The full resulting regression suite reportedly takes about five hours to run.
  • The author links a public project and reports a version 0.8.0 release.

Cautions

  • A reference implementation can also contain defects; verify important expectations against specifications or additional independent references.
  • Respect licensing and distribution restrictions for emulator ROMs, test media, and generated fixtures.

Limitations

  • No exact build commands, prompts, test invocation, or output-comparison procedure are provided.
  • Reported improvement is qualitative, with no before-and-after pass counts or independently verified accuracy claims.
  • The five-hour full suite may be costly to run frequently.

Rate this workflow

Upvote this post if the workflow is useful, reproducible, or worth recommending.

Downvote if it is vague, outdated, unsafe, overhyped, or not reproducible.

Reply if it worked for you, failed, is outdated, or has a better alternative.


This post was generated automatically from the workflow library database.


r/ClaudeWorkflows • • 2h ago

Selected Workflow [Workflow] Lead–worker Claude Code development with independent verification

1 Upvotes

Lead–worker Claude Code development with independent verification

Workflow value: 78/100
Status: active · Freshness: 70/100 · Confidence: 0.94 · Level: advanced
Categories: Quality Control, Token Saving, Debugging, Shipping, Hooks, Subagents, Multi-Agent
Original source: r/ClaudeCode post/comment

What problem this solves

Agent-written code can pass its own tests while still failing in real use, and benchmarks can be contaminated by unrelated plugins.

Summary

Use a lead Claude Code session to delegate changes to a worker, independently verify the results, and add adversarial review and real-environment checks before release.

Why it is useful

It combines a repeatable delegation pattern with independent test reruns, real-user checks, and concrete examples of defects and benchmark contamination that automated results alone missed.

Workflow

  1. Run a worker session in tmux and have a separate lead session write a task file for each change.
  2. Let the worker implement the change, then have the lead independently rerun typechecking and both test suites.
  3. Try the feature in a real terminal, including a fresh first-run experience, rather than relying on automated tests alone.
  4. Request independent reviews, including reviewers defending and attacking the implementation and a security review of untrusted inputs; turn findings into fixes.
  5. For prompt benchmarks, isolate settings sources and record individual runs; the author used --setting-sources project to exclude user settings.
  6. Bump the plugin version for each release so installed copies can receive updates.

Tools / artifacts

  • Claude Code sessions
  • tmux
  • Task files
  • Typechecker and test suites
  • Review agents
  • Real-terminal first-run check
  • --setting-sources project
  • bench/RESULTS.md

Validation signals

  • The author reports that a broken first-run redraw escaped passing tests and was discovered while recording a README demonstration.
  • The author reports that lead-session reruns and human screenshot inspection caught defects.
  • The author describes a benchmark with eight runs per arm after discovering that user-configured plugins contaminated earlier runs.

Cautions

  • Treat downloaded assets and other external inputs as untrusted during security review.
  • Use an isolated test environment for first-run checks rather than deleting existing user data.
  • Disclose model usage and any data sent externally before enabling such features.

Limitations

  • The post promotes its own plugin, although it provides a reusable development process.
  • It does not provide the task-file template, exact delegation commands, or review prompts.
  • Results are author-reported and lack independent community confirmation.
  • The benchmark finding is limited to the described task and settings; the isolated project configuration should still be inspected.

Rate this workflow

Upvote this post if the workflow is useful, reproducible, or worth recommending.

Downvote if it is vague, outdated, unsafe, overhyped, or not reproducible.

Reply if it worked for you, failed, is outdated, or has a better alternative.


This post was generated automatically from the workflow library database.


r/ClaudeWorkflows • • 5h ago

Selected Workflow [Workflow] Adapt and validate a scroll-driven GSAP site with Claude Code

1 Upvotes

Adapt and validate a scroll-driven GSAP site with Claude Code

Workflow value: 78/100
Status: active · Freshness: 70/100 · Confidence: 0.94 · Level: advanced
Categories: Quality Control, Context & Memory, Debugging, Shipping
Original source: r/ClaudeCode post/comment

What problem this solves

Build and adapt scroll-driven animated sites while checking that animations work across screen sizes and actual devices.

Summary

Use an open-source GSAP site as a template, preserve its scroll director and controls, adapt its content and visuals, and validate each change with production builds, browser checks, deliberate test failures, and real-device review.

Why it is useful

It combines a reusable adaptation prompt with a concrete animation architecture and a strong verification practice: deliberately proving that checks fail when the behavior is broken.

Workflow

  1. Choose a single visual concept and plan its scenes as a sequence measured in screens of scroll.
  2. Adapt a Sum, Meridian, or Datum site with Claude Code, explicitly listing what may change and preserving the scroll director, scene timing, buttons, arrow keys, and text-image separation rule.
  3. Keep text and numbers in content.ts and derive image-based measurements with scripts rather than entering them manually.
  4. Use paused GSAP timelines driven by scroll and sticky positioning for pinned scenes; adapt the visual assets to the concept.
  5. After each change, make a production build and run the site's checks at wide and phone-sized viewports. Review full-size frames of each resting scene.
  6. Deliberately break an animation rule and confirm that its check fails, then restore the implementation.
  7. Test on a real phone as well as in automated browsers, especially for animation and engine compatibility.

Tools / artifacts

  • Claude Code
  • GSAP
  • Puppeteer
  • CSS position: sticky
  • content.ts
  • Sum, Meridian, and Datum source code
  • Production builds and scene frames

Validation signals

  • The author reports browser checks covering scenes on desktop and phone-sized viewports.
  • A real iPhone reportedly exposed a GSAP scale-setting error that automated checks missed.
  • Deliberately breaking Datum revealed that its initial check passed even when lines were never drawn.

Cautions

  • Review third-party repository code and scripts before running them.
  • Check rights, privacy, and costs before uploading images to external generation or editing services.

Limitations

  • Results and test behavior are author-reported; no independent validation is provided.
  • The post does not provide exact build or check commands, or the implementation of the browser assertions.
  • The initial check failure illustrates that passing screenshots or assertions alone can miss incorrect motion.
  • The full approach requires substantial GSAP, browser-testing, and potentially WebGL expertise.

Rate this workflow

Upvote this post if the workflow is useful, reproducible, or worth recommending.

Downvote if it is vague, outdated, unsafe, overhyped, or not reproducible.

Reply if it worked for you, failed, is outdated, or has a better alternative.


This post was generated automatically from the workflow library database.


r/ClaudeWorkflows • • 10h ago

Selected Workflow [Workflow] Keep Claude's verification checks with CLAUDE.md rules and a bounded Stop hook

1 Upvotes

Keep Claude's verification checks with CLAUDE.md rules and a bounded Stop hook

Workflow value: 76/100
Status: active · Freshness: 70/100 · Confidence: 0.94 · Level: intermediate
Categories: Quality Control, Token Saving, Debugging, CLAUDE.md, Hooks
Original source: r/ClaudeCode post/comment

What problem this solves

Claude may verify a change with temporary scripts but leave few reusable tests in the repository.

Summary

Add verification requirements to CLAUDE.md and a bounded Stop hook that runs tests and asks Claude to fix failures. Encourage persistent property, differential, and performance tests rather than relying only on temporary checks.

Why it is useful

It provides a repeatable way to turn ephemeral verification into durable tests, with a concrete comparison and an explicit cost tradeoff.

Workflow

  1. Add project-specific verification rules to CLAUDE.md, including retaining useful checks as repository tests.
  2. Where appropriate, add property tests, differential tests against a preserved reference implementation, and performance tests.
  3. Configure a Stop hook to run the project verification script and return exit code 2 with a corrective message when tests fail.
  4. Check stop_hook_active to prevent repeated hook-triggered retries from looping indefinitely.
  5. Validate the setup by running representative checks and introducing a controlled defect to see whether the tests and hook catch it.

Tools / artifacts

  • CLAUDE.md verification section
  • Claude Code Stop hook
  • settings.json
  • verify.sh
  • Property, differential, and speed tests

Validation signals

  • The author reports that both the configured and plain runs passed a hidden grader using 3,000 random strings, 5,000 random orders, and 7 real files.
  • The configured run left 13 new tests in the repository, while the plain run left 4 small example tests and used temporary scripts for other checks.
  • A manually planted bug caused 4 of 16 tests to fail in the configured repository, versus 1 of 7 in the plain repository; the configured Stop hook returned exit code 2.
  • The reported configured run cost $0.55 and took 157 seconds, versus $0.35 and 104 seconds for the plain run.

Cautions

  • The bounded retry prevents an infinite loop but does not guarantee that every failing test is fixed before Claude stops; retain independent review and CI checks.
  • Review test failures rather than blindly changing either implementation or tests: tests themselves can be incorrect.
  • Inspect externally supplied hook scripts before running them and avoid verification commands with destructive side effects.

Limitations

  • The comparison used only one run per configuration on small Python tasks.
  • The defect was manually planted rather than introduced during a subsequent Claude session.
  • The exact five rules and hook implementation are not present in the post itself.
  • The measured outcome supports better retained regression coverage, not superior correctness on the original task.

Rate this workflow

Upvote this post if the workflow is useful, reproducible, or worth recommending.

Downvote if it is vague, outdated, unsafe, overhyped, or not reproducible.

Reply if it worked for you, failed, is outdated, or has a better alternative.


This post was generated automatically from the workflow library database.


r/ClaudeWorkflows • • 10h ago

Selected Workflow [Workflow] Audit Git hooks configuration after launching worktree-isolated subagents

1 Upvotes

Audit Git hooks configuration after launching worktree-isolated subagents

Workflow value: 76/100
Status: active · Freshness: 70/100 · Confidence: 0.93 · Level: intermediate
Categories: Quality Control, Debugging, CLAUDE.md, Hooks, Skills, Subagents, Multi-Agent
Original source: r/ClaudeCode post/comment

What problem this solves

Detect and mitigate a reported Claude Code worktree-subagent behavior that rewrites a repository's shared Git hooks configuration.

Summary

Compare the Git hooks path and config modification time before and after launching a worktree-isolated subagent, then avoid that isolation mode or enforce policy and verification gates if the issue reproduces.

Why it is useful

Provides a repeatable, narrowly scoped diagnostic for a potentially consequential configuration change, with practical mitigation and verification options.

Workflow

  1. In a disposable clone, record git config --show-origin --get core.hooksPath and the modification time of the main checkout's .git/config.
  2. Launch a no-op subagent with isolation: "worktree", then repeat the checks. Look for a relative hooks path changing to an absolute path.
  3. If affected, avoid automatic worktree isolation; create a worktree manually or use a disposable clone for reviews.
  4. Consider a PreToolUse policy that denies worktree-isolated Agent calls and relevant Bash configuration writes.
  5. Check the expected hooks path and actual hook behavior before push or merge; use an independent CI merge gate where possible.

Tools / artifacts

  • git config --show-origin --get core.hooksPath
  • stat on .git/config
  • git worktree add
  • git clone --no-hardlinks
  • PreToolUse hook
  • core.hooksPath

Validation signals

  • Author reports repeated config rewrites, including with a no-op subagent in a throwaway clone.
  • Author reports inspecting the relevant behavior in the Claude Code 2.1.321 binary.
  • The post provides before-and-after checks that readers can use to test their own installations.

Cautions

  • Test in a disposable clone and preserve existing Git configuration.
  • The .git/config stat commands assume a main checkout; linked worktrees generally have a .git file instead.
  • A manually created worktree still shares repository configuration; avoid subsequently invoking the affected automatic isolation mode.
  • A PreToolUse command filter needs careful implementation and should not be treated as a complete security boundary. A pre-push hook alone cannot enforce a gate if the hooks path is broken.

Limitations

  • The claimed behavior is version-specific and has not been independently confirmed in the supplied material.
  • The post does not provide an implementation for the proposed denial hook or CI gate.
  • Husky exposure and missing-hook-directory behavior are identified as untested.
  • A changed path and modification time are useful indicators but do not by themselves prove which process made the change.

Rate this workflow

Upvote this post if the workflow is useful, reproducible, or worth recommending.

Downvote if it is vague, outdated, unsafe, overhyped, or not reproducible.

Reply if it worked for you, failed, is outdated, or has a better alternative.


This post was generated automatically from the workflow library database.


r/ClaudeWorkflows • • 10h ago

Selected Workflow [Workflow] Preserve decision rationale across compaction with decision records and handoffs

1 Upvotes

Preserve decision rationale across compaction with decision records and handoffs

Workflow value: 76/100
Status: active · Freshness: 70/100 · Confidence: 0.96 · Level: intermediate
Categories: Quality Control, Context & Memory, Debugging, CLAUDE.md
Original source: r/ClaudeAI post/comment

What problem this solves

Long Claude Code sessions can lose the reasons behind decisions and negative constraints during context compaction, causing deliberate choices to be revisited or undone.

Summary

Preserve decision rationale and constraints both in guided compaction instructions and in persistent project files. For long tasks, review a written handoff before clearing the session and starting with fresh context.

Why it is useful

It provides a concrete, repeatable way to carry intent across context resets, including a human verification gate and durable artifacts. Its main limitation is the lack of independent validation.

Workflow

  1. Record significant choices in a decisions file using a concise format: choice, rejected alternative, reason, and conditions for revisiting.
  2. Add brief code comments near non-obvious deliberate behavior pointing to the relevant decision.
  3. Before automatic compaction, run /compact with instructions to retain decision rationales and exact negative constraints; optionally document compaction priorities in CLAUDE.md.
  4. For a longer task, ask Claude to write a handoff file covering the goal, decisions and reasons, constraints, and next step.
  5. Read and correct the handoff before using /clear, then instruct the fresh session to read the file.

Tools / artifacts

  • /compact
  • /clear
  • CLAUDE.md
  • decisions.md
  • Handoff file
  • Code comments

Validation signals

  • The author anecdotally reports that a nearby comment pointing to the decisions file helps prevent deliberate behavior from being changed.
  • The handoff workflow includes a human review step to catch drift before clearing context.

Cautions

  • Review the handoff for completeness before /clear; unsaved conversational context may otherwise be lost.
  • Do not rely on compaction instructions to preserve every constraint exactly; verify critical requirements in persistent files.
  • Avoid putting secrets or sensitive information into decision or handoff files that may be committed or shared.

Limitations

  • The effectiveness claims are anecdotal, with no controlled comparison or detailed success report.
  • The comment does not provide a complete handoff template or an automated check that decisions are followed.
  • Keeping decision files current requires ongoing manual discipline.

Rate this workflow

Upvote this post if the workflow is useful, reproducible, or worth recommending.

Downvote if it is vague, outdated, unsafe, overhyped, or not reproducible.

Reply if it worked for you, failed, is outdated, or has a better alternative.


This post was generated automatically from the workflow library database.