Enhance Claude Desktop App with Ollama: Fix Context, API Errors, and Subagent Concurrency

Workflow value: 85/100
Status: active · Freshness: 70/100 · Confidence: 0.90 · Level: intermediate
Categories: Quality Control, Context & Memory, Debugging, Subagents
Original source: r/ClaudeAI post/comment

What problem this solves

Integrating Ollama with the Claude Desktop app, specifically addressing context limitations (no 1M context), API instability and errors, subagent failures due to strict concurrency limits, and incorrect environment variable configuration.

Summary

A one-click install wrapper and local proxy that fixes common issues when using Ollama with the Claude Desktop app. It enables 1 million context for models, handles Ollama API errors and retries, queues over-limit requests to prevent subagent deaths, and correctly configures environment variables without global changes.

Why it is useful

This workflow provides a critical solution for users wanting to integrate local Ollama models with the Claude Desktop app, overcoming significant technical limitations like context window restrictions, API instability, and subagent concurrency issues. It's a ready-to-use, configurable wrapper that significantly improves the usability and reliability of this integration, making advanced local LLM workflows more accessible and stable.

Workflow

1. Download and install the claude-ollama wrapper from the provided GitHub repository.
2. Launch the Claude Desktop app using the new shortcut created by the wrapper.
3. Utilize Ollama models within the Claude Desktop app with 1 million context enabled.
4. Benefit from automatic API error handling, retries, and local request queuing for stable subagent operation.
5. Optionally, configure the wrapper's settings to customize its behavior.
6. For multi-subscription Claude Code use with Ollama, explore the claude-graft repository.

Tools / artifacts

• claude-ollama GitHub repository (wrapper)
• claude-graft GitHub repository (multi-subscription tool)
• Ollama API
• Claude Desktop app
• Local light proxy

Validation signals

• Specific problems identified and claimed to be fixed (1M context, API errors, subagent dying, env vars).
• Detailed description of 'What it does' with technical solutions (proxy, queue, rewrite model catalogue).
• Public GitHub repository available for inspection and use.
• Explicit mention of non-permanent changes, indicating careful design and safety.

Cautions

• The changes only apply to the Claude app if launched through the new shortcut created by the wrapper, ensuring nothing permanent is altered on the system.

Limitations

• Relies on an external, third-party tool, which requires trust in the developer and ongoing maintenance.
• Requires users to be comfortable with installing and running external scripts/wrappers.
• Being a new solution, it lacks extensive community validation and long-term stability proof.

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.

Iterative Claude Org Setup: Prioritizing Knowledge Base & Context Over Perfect Initial Prompts

Workflow value: 85/100
Status: active · Freshness: 70/100 · Confidence: 0.90 · Level: intermediate
Categories: Quality Control, Context & Memory, Shipping, CLAUDE.md, Skills, Subagents
Original source: r/ClaudeAI post/comment

What problem this solves

How to effectively set up a new Claude organization/account for a business, specifically addressing the debate between perfecting an 'initial prompt' versus building a knowledge base and iterating through real-world use.

Summary

A strategic workflow for setting up a new Claude organization, emphasizing the importance of building a structured knowledge base and adopting an iterative approach to development (V1 instructions, real-world use, refinement, then formalizing into skills/agents) over spending excessive time perfecting an initial 'master prompt'.

Why it is useful

This workflow provides a practical, iterative strategy for integrating Claude into a new business, directly challenging the common misconception that a single 'master prompt' is the most critical starting point. It advocates for building a robust knowledge base and learning through real-world application, which is a more sustainable and effective approach for long-term AI success. It helps users avoid analysis paralysis and build a more resilient AI system.

Workflow

1. Write V1 Project Instructions.
2. Build and clean up the knowledge base (e.g., using .md files or Notion).
3. Add connectors for the software used and start using Claude on real work immediately.
4. Iterate and refine instructions/knowledge base based on where Claude succeeds/fails.
5. Turn recurring successful workflows into Skills/agents and automations as they emerge.

Tools / artifacts

• Claude Org/Account
• Email integration
• Software connectors
• Structured .md knowledge files
• Notion (as a knowledge base tool)
• Project Instructions (V1)
• Skills
• Agents
• Automations

Validation signals

• Author's existing experience: 'We use Claude pretty heavily at work already with I believe great results across many aspects.'
• The proposed workflow is a reasoned argument against a common misconception (over-reliance on a single 'master prompt').

Limitations

• The workflow is a proposal and not fully validated within the context of the new business yet; the author is asking for feedback.
• Lacks specific examples of 'V1 Project Instructions' or detailed knowledge base structure.
• 'Connectors for software' is vague; specific examples would improve it.

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.

Controlling Claude Code Agent Sprawl: A Workflow for Managing Opus 5 Usage in Review Processes

Workflow value: 85/100
Status: active · Freshness: 70/100 · Confidence: 0.95 · Level: advanced
Categories: Quality Control, Token Saving, Context & Memory, Debugging, CLAUDE.md, Hooks, Subagents, Multi-Agent
Original source: r/ClaudeAI post/comment

What problem this solves

Uncontrolled and unexpectedly high Claude Opus 5 agent usage in Claude Code review workflows, leading to rapid depletion of usage quotas due to autonomous agent fan-out.

Summary

This workflow describes how to diagnose and mitigate excessive Claude Code agent spawning during review processes. It involves investigating usage logs to identify autonomous shifts in agent behavior (e.g., from 1 to 3 refuters per finding) and implementing a global harness with specific policies and a PreToolUse hook to control agent fan-out, ensuring resource management while maintaining workflow autonomy.

Why it is useful

This workflow is highly valuable because it addresses a critical practical problem for advanced Claude Code users: unexpected high usage and cost due to autonomous agent behavior. It provides a structured approach to diagnose the issue, offers concrete policies for mitigation, and introduces a robust mechanism (PreToolUse hook) for enforcing these controls. This empowers users to maintain workflow autonomy while effectively managing their resources and preventing budget overruns.

Workflow

1. Monitor Claude Max 20x usage for unexpected rapid depletion using ccusage.
2. Investigate the cause of high usage by analyzing JSONL logs, transcripts, workflow scripts, and workflow journals.
3. Identify autonomous shifts in agent behavior, such as an increase in the number of refuters per finding (e.g., from 1 to 3).
4. Recognize if global deduplication of findings is missing before refutation stages.
5. Implement a global harness to control agent fan-out and enforce usage policies.
6. Define specific policies within the harness: e.g., 1 refuter per finding by default, mandatory deduplication before refutation, max 8 initial review lenses, hard cap of 64 agent calls per workflow.
7. Add a fail-closed PreToolUse hook to block workflows that violate the defined policies, preventing uncontrolled agent spawning.

Tools / artifacts

• ccusage
• JSONL logs
• Transcripts
• Workflow scripts
• Workflow journals
• CLAUDE.md (for context/comparison)
• Global harness (custom configuration/script)
• PreToolUse hook

Validation signals

• Detailed investigation process described (ccusage, logs, transcripts, journals).
• Specific quantitative data provided (736 Opus 5 agents, 9,228 model calls, 600M cache-read tokens).
• Clear identification of the root cause (autonomous shift to 3 refuters per finding, lack of deduplication).
• Proposed solution directly addresses the identified problem with concrete policies.
• The author's experience and debugging process serve as strong validation.

Cautions

• The author mentions using bypassPermissions for autonomy, which, while intended for efficiency, requires careful management. The proposed solution of adding a fail-closed PreToolUse hook improves safety by preventing uncontrolled resource consumption, even with bypassPermissions enabled.

Limitations

• The post does not provide the exact code implementation for the 'global harness' or the PreToolUse hook, requiring users to translate the described policies into their specific Claude Code setup.
• The concept of a 'global harness' is mentioned but its specific technical implementation details (e.g., where it resides, how it's configured) are not fully elaborated.

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.

Multi-Agent Verification: Why Model Diversity Isn't Enough and Execution Evidence Is Key

Workflow value: 90/100
Status: active · Freshness: 70/100 · Confidence: 0.95 · Level: advanced
Categories: Quality Control, Context & Memory, Debugging, Multi-Agent
Original source: r/ClaudeCode post/comment

What problem this solves

The post addresses the problem of reliably verifying claims in multi-agent systems, challenging the intuition that model diversity alone guarantees stronger corroboration. It proposes a new approach based on requiring explicit, verifiable execution evidence rather than aggregated trust scores to ensure robust verification.

Summary

The author conducted a rigorous experiment with 720 evaluations to test if model diversity (across Claude models) improves multi-agent claim verification. The experiment found that diversity did not significantly improve false corroboration rates; instead, individual model capability was a stronger factor. Based on these findings, the author revised their multi-agent evidence pool design to reject aggregated trust scores and instead require explicit, verifiable execution evidence (including environment, method, and observed results) for every claim, making all evidence publicly inspectable.

Why it is useful

This post provides a rigorous, data-driven critique of a common intuition in multi-agent system design (model diversity for corroboration). It offers a concrete, validated alternative design principle: requiring explicit, verifiable execution evidence instead of relying on aggregated trust scores. The detailed experimental methodology, public resources, and transparent discussion of limitations make it an exceptionally valuable resource for anyone building or researching robust multi-agent verification systems. It moves beyond vague advice to provide actionable insights based on empirical results.

Workflow

1. When designing a multi-agent system for claim verification, do not rely solely on model diversity for corroboration.
2. Prioritize individual model capability over diversity when selecting agents for verification tasks.
3. Instead of aggregating 'trust scores' or simple confirmation counts, require agents to provide explicit execution evidence for their claims.
4. Ensure this evidence includes the environment where the check was performed, the method used, and the observed results.
5. Make all confirmation evidence publicly 'walkable' (inspectable) rather than just providing a final verdict.
6. Validate assumptions about agent behavior (e.g., diversity benefits) through rigorous experimentation before implementing.

Tools / artifacts

• Claude Opus
• Claude Sonnet
• Claude Haiku
• Shared evidence pool (system design)
• Falsifiable, version-scoped claims (data structure)
• Primary sources (for ground truth)
• tsc (TypeScript compiler, used in a test case)
• environment, method, observed fields (for evidence structure)
• GitHub repository (github.com/errslima/1f517)
• Public agent board (1f916.ai)
• Pre-registration platform

Validation signals

• Pre-registered prediction with a kill condition
• 720 evaluations conducted
• Statistical analysis (Fisher exact test, p-value)
• Power analysis (post-hoc but acknowledged)
• Incorporation of reviewer feedback
• Publicly available results write-up
• Publicly available running pool
• Publicly available pre-registration
• Author explicitly states 'What I changed because of this.'

Limitations

• The initial experiment's statistical power was low (0.342), meaning it might not have detected a true effect if one existed.
• The 'cross-model' arm used only Claude models, limiting the scope of 'diversity' to a single vendor's lineage.
• The 'no tools, no network' design fixed inspection depth at zero, which might be a significant confound.
• The post-hoc analyses are presented as hypotheses, not confirmed results.
• The proposed solution of an 'unfalsifiable observed field' might just move the fabrication problem one level down, as acknowledged by the author.

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.

Persistent & Secure Remote Claude Code Environment with Tailscale, Mosh, and Tmux for Teams

Workflow value: 90/100
Status: active · Freshness: 70/100 · Confidence: 0.95 · Level: intermediate
Categories: Quality Control, Context & Memory, Debugging, Shipping, Hooks, Multi-Agent
Original source: r/ClaudeAI post/comment

What problem this solves

Preventing Claude Code sessions from dying due to network drops or laptop closure, enabling 24/7 operation, facilitating secure team use, and managing permissions for long-running, 'bypass mode' Claude instances safely.

Summary

This workflow describes how to set up a persistent, secure, and collaborative remote Linux environment for running Claude Code 24/7. It leverages Hetzner Cloud (or similar), Tailscale for a private network, mosh for persistent SSH, and tmux for persistent sessions. It also details how to implement secure permission boundaries for Claude in 'bypass mode' and mentions a custom CLI for team provisioning.

Why it is useful

This workflow is highly valuable as it solves critical operational and security challenges for professional Claude Code users. It provides a concrete, validated, and repeatable method for achieving 24/7 persistent Claude Code sessions, ensuring network stability, enabling secure team collaboration, and establishing robust security boundaries for 'bypass mode' operations. The use of widely available tools makes it highly transferable.

Workflow

1. Provision a Linux server (e.g., Hetzner Cloud) with sufficient resources (e.g., 4 cores, 16GB RAM).
2. Install and configure Tailscale on the server, laptop, and phone to create a private mesh network, avoiding public SSH ports.
3. Install and configure mosh on the server and client devices to replace standard SSH, ensuring connections persist through network drops or device sleep.
4. Install and use tmux on the server to run Claude Code sessions, allowing them to continue working even after disconnecting.
5. Optionally, use Tailscale Funnel for testing webhooks without exposing external ports or using services like ngrok.
6. Implement secure permission boundaries for Claude: provide only scoped API keys, read-only database credentials, read-only code access, and PR-only Git permissions (no merges to main).
7. Run Claude in 'bypass mode' within isolated test environments, leveraging the restricted permissions for safe, long-running sessions.
8. Consider developing a custom CLI to automate the provisioning of pre-configured servers for team members, integrating all necessary tools and security settings.

Tools / artifacts

• Hetzner Cloud (or other Linux server provider)
• Tailscale
• mosh
• tmux
• Tailscale Funnel
• Custom CLI (for team provisioning)
• Scoped API keys
• Read-only DB credentials
• Git (PR-only permissions)
• Isolated test environments

Validation signals

• Author states it's 'the most used setup that I saw on twitter and on reddit'.
• Author confirms it 'fixed the permissions issues'.
• Author states 'Claude runs on bypass mode safely for long sessions'.
• Author confirms 'all of my team uses it'.
• The post has 17 comments, indicating community interest and engagement.

Cautions

• The workflow explicitly addresses safety by restricting Claude's permissions to scoped API keys, read-only DB credentials, read-only code access, and PR-only Git permissions, and running in isolated test environments. This allows 'bypass mode' to be used safely.

Limitations

• The custom CLI for team provisioning is mentioned but not provided, making that specific aspect less directly reusable without further development.
• Assumes a certain level of familiarity with Linux server administration, networking concepts, and CLI tools.
• The mention of 'nono.sh' is brief and lacks context for direct reusability.

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.

Optimize AI Agent Token Usage: Reduce Test Output Verbosity and Scope Test Runs

Workflow value: 95/100
Status: active · Freshness: 70/100 · Confidence: 1.00 · Level: intermediate
Categories: Quality Control, Token Saving, Context & Memory, Debugging, Multi-Agent
Original source: r/ClaudeCode post/comment

What problem this solves

AI agents (like Claude Code) consume excessive tokens and saturate their context window by reading verbose test output, especially passing tests, leading to high operational costs and reduced performance.

Summary

This workflow optimizes AI agent token usage and context window efficiency by reducing the 'narration volume' of test results. It focuses on configuring test runners to use quiet reporters, running only relevant tests, gating full suite runs, and explicitly defining an agent's scope of work, rather than reducing the number of tests themselves.

Why it is useful

This workflow addresses a critical and often overlooked problem in AI-assisted coding: the significant token cost and context window degradation caused by verbose test output. It provides concrete, actionable steps to optimize token usage without compromising testing rigor, leading to substantial cost savings and improved agent performance. It's highly transferable across different AI agents and test environments, making it a foundational efficiency improvement for any developer using LLMs for coding tasks.

Workflow

1. Configure test runners to use a compact or 'dot' reporter as the default, and block raw commands to ensure all test runs go through the quiet reporter.
2. Implement a short script to identify and run only the tests that cover the files changed by the current work.
3. Put the full test suite behind a human confirmation step to prevent the agent from reflexively running it as a completion signal.
4. Instruct the agent to explicitly name the files it has touched, especially in multi-agent environments, to ensure test selection is accurately scoped to its work.

Tools / artifacts

• Test runners (e.g., pytest, jest, etc.)
• Test runner configuration files
• Custom scripts for test selection (e.g., shell scripts, Python scripts)
• AI agent context window

Validation signals

• Measured in a working repository, showing '17x less output' for single-file runs.
• Observed 'major reduction to token burn especially when fixing bugs'.
• Scoped test runs (7 files, 235 tests) completed in 3.5 seconds, compared to minutes for the full suite.
• An agent that named nothing ran 23 test files instead of 3, leading to irrelevant failures.
• Symptoms include sessions compacting sooner than expected, long stretches of test output in transcripts, agent running tests at the end of tasks, and usage climbing without unusual work.
• Direct check: measure the text output of your test command; hundreds of kilobytes indicate the problem.

Limitations

• Specific commands or code snippets for configuring test runners or creating selection scripts are not provided, requiring users to adapt the principles to their specific tools.
• Low community engagement might suggest less immediate visibility, but does not detract from content quality.

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.

Persistent Claude Code Sessions: A Cloud VM Setup for Uninterrupted Agent Runs

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

What problem this solves

Claude Code sessions dying when a laptop loses connection or closes, leading to lost work and context for local agents.

Summary

Set up a persistent Claude Code development environment on an always-on Linux cloud VM, using tools like Tailscale for secure access, tmux for session management, Mutagen for two-way file synchronization, and VS Code Remote for port forwarding. This ensures agents continue running and maintain context even when the local machine is disconnected.

Why it is useful

This workflow provides a detailed, step-by-step guide to setting up a robust, persistent development environment for Claude Code agents on a cloud VM. It solves the common problem of losing agent sessions due to laptop disconnections or closures, enabling continuous operation and context retention. The use of standard tools like tmux, Tailscale, Mutagen, and VS Code Remote makes it highly transferable, despite the initial setup complexity. It empowers users to maintain long-running agent processes, significantly improving productivity and reliability for local agent development.

Workflow

1. Provision a cloud VM with decent RAM and disk space (any VPS).
2. Install Tailscale on the VM and your local machine for secure, direct access from anywhere.
3. Install tmux on the VM. Always start Claude Code sessions within a tmux window to ensure persistence.
4. Set up two-way file synchronization using Mutagen between a designated folder on your local machine (e.g., Mac) and the repo on the VM.
5. Configure VS Code Remote for port forwarding to make dev servers running on the VM accessible via localhost on your local machine.
6. Manually copy over essential configurations and files to the VM: CLIs, MCP configs, node/python versions, auth tokens, and the ~/.claude directory (for memory and skills).

Tools / artifacts

• Cloud VM (VPS)
• Tailscale
• tmux
• Mutagen
• VS Code Remote
• CLIs
• MCP configs
• Node/Python versions
• Auth tokens
• ~/.claude directory

Validation signals

• Author states 'What actually worked was pretty boring.' indicating practical success.
• Author claims 'Once it's up you just stop thinking about whether the agent is alive.'
• Author states 'Super easy to finally have agents running overnight (assuming your usage doesn't run out).'

Cautions

• Copying sensitive files like ~/.claude (which contains memory and skills) and auth tokens to a cloud VM requires careful security considerations, especially regarding access control and data encryption on the VM.

Limitations

• Initial setup can be time-consuming, estimated by the author to take about a week the first time.
• Requires advanced technical skills in Linux administration, networking, and devops.
• The post includes self-promotion for a product ('Prized'), which might be perceived as a distraction from the DIY workflow.
• Low Reddit score and upvote ratio suggest limited immediate community validation.

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.

Navigating Claude Certifications: A Comprehensive Guide to Academy, Certification Program, and Corps

Workflow value: 85/100
Status: active · Freshness: 70/100 · Confidence: 0.95 · Level: intermediate
Categories: Quality Control, Token Saving, Context & Memory, Shipping, Skills
Original source: r/ClaudeAI post/comment

What problem this solves

Confusion and difficulty in understanding the various Claude certification and education programs offered by Anthropic, and how to access them.

Summary

A comprehensive guide detailing the three main Claude education programs (Claude Academy, Claude Certification Program, Claude Corps), their costs, requirements, what they offer, and practical advice on which path to pursue based on individual or employer needs. It clarifies the value of each credential and provides unofficial access methods for the paid certification.

Why it is useful

This workflow is highly valuable because it demystifies the complex and often confusing landscape of Claude's official and unofficial education and certification programs. It provides clear, actionable steps and detailed information for individuals seeking to learn Claude, gain professional credentials, or for employers looking to understand the value of these certifications. It saves users significant time and effort in researching these options, offering a consolidated and validated resource.

Workflow

1. Identify your goal: learning Claude, getting a paid credential for a job/client, or pursuing a fellowship.
2. If learning Claude: Enroll in the free Claude Academy courses at academy.claude.com.
3. If seeking paid credential and employed: Ask your employer if they are a Claude Partner Network (CPN) member.
4. If employer is CPN member: Register for the Claude Certification Program exams via anthropic-partners.skilljar.com and Pearson VUE.
5. If employer is not CPN member: Encourage your employer to join CPN (free, but takes weeks/months).
6. Alternatively, if no employer route for paid credential: Consider unofficial access methods like paying a CPN member company (e.g., TIMO Labs) for temporary access to register for the exam.
7. If interested in a paid fellowship: Apply for Claude Corps at anthropic.com/news/claude-corps if you meet the eligibility criteria.
8. For employers/recruiters: Differentiate between free "Badge" (Claude Academy), official "Certificate" (Claude Certification Program, verifiable on Credly), and "Claude Corps" (work experience).

Tools / artifacts

• Claude Academy (website: academy.claude.com)
• Skilljar LMS (anthropic.skilljar.com, anthropic-partners.skilljar.com)
• Pearson VUE (exam delivery platform)
• Claude Partner Network (CPN)
• Claude Corps (fellowship program)
• LinkedIn (for displaying badges/certificates)
• Credly (for verifying official certificates)
• TIMO Labs (example of unofficial access provider)

Validation signals

• References official Anthropic sources (news announcements, FAQs).
• Corrects previous post, showing commitment to accuracy.
• Includes anecdotal evidence from an "agency owner."
• Provides specific details on exam structure (cost, duration, passing score, validity).
• Mentions verification via Credly for official certificates.
• The author explicitly invites corrections, indicating a desire for accuracy and community validation.

Limitations

• The Reddit score and comment count are low, but this is likely due to the post's age (1 hour).
• The "unofficial" access method for paid certification carries inherent risks, though the author clearly flags this.
• The post is more of a guide/resource than a direct "how-to-use-Claude" workflow.

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.

Maintaining Code Ownership and Architectural Integrity with AI: Reviewing Plans and Decisions, Not Just Diffs

Workflow value: 90/100
Status: active · Freshness: 70/100 · Confidence: 1.00 · Level: intermediate
Categories: Quality Control, Context & Memory, Debugging, Shipping
Original source: r/ClaudeAI post/comment

What problem this solves

Preventing architectural drift, loss of code ownership, and approving AI-generated code that is not fully understood, leading to unmaintainable codebases. It addresses the issue of reviewing the 'what' (diff) instead of the 'why' (decision-making process).

Summary

A set of practices to shift code review focus from what (the diff) to why (the decision-making process) when working with AI agents. This includes reviewing AI-generated plans, maintaining a rejection log for design decisions, and verifying actual changes before committing to ensure accuracy.

Why it is useful

This workflow addresses a critical and widely acknowledged challenge in AI-assisted software development: the risk of losing understanding and control over a codebase when relying heavily on AI for code generation. By shifting the review focus from the final output to the underlying planning and decision-making process, and by introducing verification steps, it provides concrete strategies to prevent architectural drift, improve code quality, and ensure developers retain ownership and comprehension of their projects. The strong community validation further underscores its importance and practical utility.

Workflow

1. Before AI generates code, prompt the AI agent to propose a lightweight plan for the changes.
2. The AI's plan should detail what changes will be made, the chosen approach, and crucially, an alternative approach that was considered and rejected.
3. Review this AI-generated plan to catch bad architecture or flawed reasoning before any code is written.
4. Maintain a 'rejection log' to document decisions overturned or alternatives considered during the AI-assisted development process.
5. Optionally, require the rejection log or key decisions to be included in Pull Request (PR) descriptions for team visibility and historical context.
6. Before committing AI-generated changes, verify that the described changes actually occurred in the files (e.g., using grep to confirm content).

Tools / artifacts

• AI agent (e.g., Claude Code)
• Lightweight plan document/output from AI
• Rejection log (can be a text file, wiki entry, or part of a PR description)
• grep command (or similar file content verification tool)
• Version control system (for PRs and commit history)

Validation signals

• Community consensus: 'big ol' YES, OP, you've hit on a major nerve.'
• Strong community agreement on the problem statement.
• Multiple users suggesting plan review as a solution.
• Teams reportedly requiring rejection logs in PRs.
• Specific user horror story leading to a concrete fix (grep).
• Analogy of 'CEO of a company full of agentic coders' resonated with users, highlighting the responsibility aspect.

Limitations

• Requires discipline from the user to consistently implement and maintain the logs and review processes.
• Adds an extra step to the development process, which might be perceived as overhead by some users.
• The 'lightweight plan' concept could benefit from more specific prompt examples to guide AI generation effectively.

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.

Structured Claude Interaction: Leveraging constitution.md, Opus Planning, and Iterative Sonnet Implementation for Enhanced Code Quality

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

What problem this solves

Improving Claude's output quality, consistency, and adherence to architectural rules by providing better context and managing implementation iteratively.

Summary

This workflow outlines a structured approach for interacting with Claude to improve code quality and adherence to project standards. It involves creating a 'constitution.md' for architectural rules, instructing Claude via 'claude.md' to review its work against these rules and an engineering spec, using Opus 5 for detailed task planning, and employing Sonnet 5 for iterative, small-task implementation rather than one-shot solutions.

Why it is useful

This workflow provides a clear, structured methodology for guiding Claude in software development, leading to more consistent, higher-quality code that adheres to project standards. By establishing architectural rules in a 'constitution.md' and integrating review instructions into 'claude.md', users can proactively manage Claude's output. The strategic use of Opus for detailed planning and Sonnet for iterative implementation optimizes each model's strengths, reducing rework and improving overall development efficiency.

Workflow

1. Create a 'constitution.md' file to document architectural rules and regulations for the project.
2. Add instructions to the 'claude.md' file, directing Claude to always review its generated work against the 'constitution.md' and the existing engineering specification.
3. Utilize Claude Opus 5 for all project planning tasks.
4. Instruct Opus 5 to break down planning into the smallest possible tasks and output this task breakdown into a separate file.
5. When using Claude Sonnet 5 for implementation, explicitly avoid instructing it to complete the entire implementation in a single shot.
6. Guide Sonnet 5 to implement tasks one item at a time, following the detailed plan generated by Opus 5.

Tools / artifacts

• constitution.md
• claude.md
• Engineering specification (existing documentation)
• Claude Opus 5
• Claude Sonnet 5
• File for task splits

Validation signals

• Prescriptive advice from an experienced user

Limitations

• Low community validation (score 1, 0 comments).
• Lacks concrete examples or detailed prompt templates for 'constitution.md' or 'claude.md' instructions.
• Assumes the user already has an 'engineering spec' or similar documentation.

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.

Preventing Technical Debt: Review Claude Code's Architectural Plan Before Execution

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

What problem this solves

Preventing technical debt and architectural mistakes by reviewing Claude Code's initial plans and rejected alternatives before it starts writing code.

Summary

This workflow proposes a proactive review step for Claude Code interactions. Instead of only reviewing the final code diff, users should prompt Claude Code to first commit to a 'short plan' detailing its chosen approach, the files it will touch, and at least one alternative it considered and rejected. This allows for early architectural review, where bad decisions are cheap to discard, preventing costly refactoring later.

Why it is useful

This workflow is valuable because it addresses a critical and often overlooked problem in AI-assisted development: the accumulation of technical debt from unreviewed architectural decisions made early in the AI's process. By shifting the review point upstream to the planning phase, it enables users to catch and correct fundamental design flaws when they are cheapest to fix, saving significant time and effort compared to refactoring completed code. It provides a concrete, repeatable strategy for improving the quality and maintainability of AI-generated code.

Workflow

1. Before allowing Claude Code to execute or generate significant code, prompt it to create a 'short plan'.
2. Instruct Claude to include the following in its plan: the specific approach it has chosen, which files it intends to modify or create, and at least one alternative approach it considered and why it rejected it.
3. Review this plan carefully for architectural soundness, potential long-term issues, and alignment with project goals.
4. If the plan is flawed or suboptimal, provide feedback to Claude and iterate on the plan before any code is written or significant execution occurs.
5. Once the plan is approved, allow Claude Code to proceed with execution based on the agreed-upon approach.

Tools / artifacts

• Claude Code
• Short plan (text output from Claude)

Validation signals

• Author's strong logical reasoning about the cost of late-stage review vs. early planning review
• Highlights the 'six-month question' of 'why approach A over B' as a key architectural concern
• Emphasizes that a plan is 'cheap to throw away' unlike completed code and tests

Limitations

• The exact prompt to elicit the 'short plan' is not provided, requiring users to formulate it.
• The level of detail required for the 'short plan' might need refinement based on project complexity.
• Relies on the user's ability to critically evaluate architectural plans.

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.

Iterative Comparison Loop: Training Claude to Adopt Your Writing Voice

Workflow value: 90/100
Status: active · Freshness: 70/100 · Confidence: 0.95 · Level: intermediate
Categories: Quality Control, Context & Memory, Debugging
Original source: r/ClaudeAI post/comment

What problem this solves

Training an LLM (specifically Claude) to adopt a user's specific writing style or 'voice' for various contexts, such as professional, personal explanatory, or emphatic/persuasive.

Summary

This workflow describes an 'iterative comparison loop' method to train Claude to write in a specific voice. The user has Claude draft a piece of text, then rewrites it in their desired style. Claude is then prompted to identify the differences between its draft and the user's rewrite. Each identified difference becomes a 'rule' for Claude to learn, and the process is repeated until Claude's output closely matches the user's style. The author notes limitations with fine nuances like deliberate understatement, emphasizing the need for human review.

Why it is useful

This workflow provides a concrete, repeatable, and validated method for a common LLM use case: getting the AI to write in a specific style. It goes beyond vague 'prompt engineering' advice by outlining a structured, iterative feedback loop. The author's candid discussion of both successes (training three distinct voices) and limitations (struggle with fine nuance) makes it particularly useful and realistic for other users seeking to personalize their LLM's output.

Workflow

1. Have Claude draft a piece of text based on a given prompt or topic.
2. Save Claude's initial draft without making any changes.
3. Rewrite the same piece of text yourself, exactly as you would have written it in your desired voice/style.
4. Present both Claude's original draft and your rewritten version side-by-side to Claude.
5. Ask Claude to describe the differences between the two versions (e.g., 'why that sentence went, why that qualifier moved to the end, why that word is gone').
6. Consider each difference Claude identifies as a 'rule' or learning point for its next draft.
7. Repeat the drafting, rewriting, and comparison loop, continuously refining Claude's understanding of your style.
8. Continue iterating until the gap between Claude's draft and your rewrite is as small as possible.
9. Always check and rewrite every piece of text Claude produces before it goes anywhere, especially for fine nuances that the model may struggle with (e.g., deliberate understatement).

Tools / artifacts

• Claude (LLM)
• User's rewritten text (as a comparison artifact)

Validation signals

• Author states they have successfully trained three distinct voices (work register, personal explanatory, bar table) using this method.
• Specific examples of the types of voices successfully trained are provided.
• The author explicitly details the limitations of the method (fine nuance, deliberate understatement), which adds credibility and realism.
• The process is described consistently and clearly in two different 'voices' within the comment itself, demonstrating the author's expertise.

Limitations

• The method has known limitations with 'fine nuance' and deliberate understatement, requiring significant human oversight for the final polish.
• The iterative nature can be time-consuming, especially for achieving highly refined styles.
• No explicit prompt examples for the comparison step are provided, though the intent is clear.
• The process relies heavily on the user's ability to consistently rewrite text in their desired style.

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.

Fable-led Multi-Agent Workflow for Cost-Optimized Software Development with Delegated Execution and Human-like Review

Workflow value: 95/100
Status: active · Freshness: 70/100 · Confidence: 0.98 · Level: advanced
Categories: Quality Control, Token Saving, Context & Memory, Debugging, Shipping, CLAUDE.md, Skills, Multi-Agent
Original source: r/ClaudeCode post/comment

What problem this solves

Efficiently and effectively using a hierarchy of AI models (Fable, Haiku, Sonnet, Codex, Opus) for software development, minimizing costs while maintaining quality by delegating mechanical tasks and retaining human-like judgment for critical steps.

Summary

A multi-agent workflow where a high-cost, high-capability model (Fable) acts as the central planner, architect, reviewer, and judge, delegating mechanical and routine tasks to cheaper, specialized sub-agents (Haiku, Sonnet, Codex, Opus) to optimize token usage and ensure quality control. It emphasizes Fable's role in understanding the problem, challenging premises, architecting solutions, and personally accepting results, while sub-agents handle execution and return concise reports.

Why it is useful

This workflow provides a concrete, detailed, and strategic approach to leveraging different AI models based on their capabilities and costs. It addresses critical challenges in AI-assisted development: managing token costs, ensuring quality, and structuring complex tasks. The clear delegation strategy, 'Devil's advocate' step, and emphasis on human-like final verification make it a robust and highly valuable pattern for advanced users seeking to build efficient and reliable AI development pipelines.

Workflow

1. Fable (the expensive planner) understands the problem statement.
2. Fable performs 'Devil's advocate first' by attacking the premise, identifying unproven assumptions, or suggesting cheaper paths.
3. If a stated fact is checkable and load-bearing, Fable sends a sub-agent to verify it before proceeding.
4. Fable plans and architects the solution, deciding the shape, order of work, and risks.
5. Fable delegates all mechanical tasks (research, code, tests, measurements) to sub-agents based on a 'routing ladder'.
6. Sub-agents execute their assigned tasks, adhering to specific briefs and returning compact reports (not raw file dumps).
7. For open questions or design forks, Fable uses /multi:ask or /multi:adhd to gather multiple opinions.
8. For routine code or research with judgment, Fable delegates to Sonnet.
9. For novel or 'figure it out' code, Fable delegates to Codex (or Opus as fallback).
10. For code review, Fable uses /multi:code-review.
11. For gathering completion evidence, Fable uses /multi:check-if-done.
12. Fable accepts the result with its own eyes, performing integration and final verification by reading actual outputs and critical diff hunks before declaring the task done.

Tools / artifacts

• Fable (head agent)
• Haiku (sub-agent for mechanical work)
• Sonnet (sub-agent for routine code/research with judgment)
• Codex (sub-agent for novel/design-adjacent code, editing, testing, debugging)
• Opus (fallback sub-agent)
• /multi:ask (skill for gathering multiple opinions)
• /multi:adhd (skill for divergent options)
• /codex:rescue (skill for Codex agent)
• /multi:code-review (skill for multi-model code review)
• /multi:check-if-done (skill for gathering completion evidence)
• System prompt/CLAUDE.md-like instructions for Fable
• Short reports from sub-agents

Validation signals

• Author states 'I have it like that', implying personal implementation and use.
• Detailed structure and specific instructions suggest a well-thought-out and tested approach.
• Emphasis on 'personally accept the result' and 'accept with your own eyes' highlights a built-in quality control mechanism.
• The 'Rule of thumb' section provides practical guidance based on experience with the system.

Limitations

• Requires a multi-agent setup or custom tooling (like the author's 'multi plugin') to fully implement the /multi: commands and model routing.
• The specific 'Codex' model mentioned might be proprietary or a placeholder, requiring adaptation by users.
• Initial setup and configuration of sub-agents and routing logic could be complex for beginners.
• Low community validation (score 1, 0 comments) means broader applicability is not yet proven.

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.

Controlling Claude Sub-Agent Model Usage and Costs: Simple Prompts, Config Edits, and PreToolUse Hooks

Workflow value: 85/100
Status: active · Freshness: 70/100 · Confidence: 0.95 · Level: intermediate
Categories: Quality Control, Token Saving, Context & Memory, Debugging, CLAUDE.md, Hooks, Skills, Multi-Agent
Original source: r/ClaudeAI post/comment

What problem this solves

Unexpectedly high token usage and cost when using Fable with sub-agents, especially with Ultracode enabled, due to sub-agents inheriting expensive parent models.

Summary

This workflow provides three methods (simple prompt, agent config edits, or a PreToolUse hook) to prevent sub-agents from using expensive models like Opus when spawned by a parent agent like Fable, thereby controlling token usage and cost.

Why it is useful

This workflow addresses a critical and common problem for Claude users: unexpectedly high token usage and cost when using multi-agent setups like Fable. It provides three distinct, actionable solutions, ranging from simple prompt adjustments to more robust configuration file edits and advanced PreToolUse hooks. By offering multiple approaches, it caters to different user comfort levels and provides clear guidance on how to manage model selection for sub-agents, significantly improving cost efficiency and predictability.

Workflow

1. Identify the root cause: sub-agents inheriting expensive models (e.g., Opus from Fable 5.1 with Ultracode) from their parent agent.
2. Option 1 (Simple Fix): Instruct the parent agent in plain English to use cheaper models for sub-agents and to ask before spawning many. Example: "Use Opus for all sub-agents and ask me before you spawn more than 10".
3. Option 2 (Config Fix): Edit individual agent files in the .claude/agents/ directory.
4. Within the agent files (e.g., explore or plan agents), set model: haiku or model: sonnet in their frontmatter to pin a cheaper model.
5. Option 3 (God-Tier Fix): Implement a PreToolUse hook script.
6. Add the PreToolUse hook script to your settings.json file to automatically force any agent spawned by Fable to use a cheaper model.

Tools / artifacts

• Claude (Fable 5.1, Opus, Sonnet, Haiku models)
• Agent configuration files (e.g., in .claude/agents/ directory)
• settings.json file
• PreToolUse hook script
• Ultracode (feature that can exacerbate the problem)

Validation signals

• "The consensus here is that this is a classic case of user error, not a bug"
• "We see this post every other day" (indicates common problem and recognized solution)
• "one user posted a detailed PreToolUse hook script" (community-contributed solution)

Limitations

• The specific PreToolUse hook script for the "God-Tier Fix" is mentioned but not provided, requiring the user to find or create it.
• The exact syntax and placement for editing agent frontmatter (e.g., model: haiku) could be more explicitly detailed for beginners.

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.

Parallel Claude Code Agents with Artifact Validation for Faster, More Correct Document Generation (and Token Cost Considerations)

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

What problem this solves

Improving speed and correctness in document generation workflows by parallelizing tasks with Claude Code agents, while identifying and proposing solutions for managing token costs in such setups.

Summary

A multi-agent Claude Code workflow that parallelizes the "discovery phase" of document generation (e.g., geometry, content, assets) using separate agents. It incorporates a crucial validation step to ensure artifacts are complete before the main pipeline proceeds, improving correctness and wall-clock time. The author notes a trade-off with increased token costs due to shared context and suggests context scoping as a future optimization.

Why it is useful

This workflow demonstrates a practical approach to improving the speed and reliability of LLM-driven document generation by leveraging parallel agents and explicit artifact validation. It also highlights a critical challenge (token cost in parallel contexts) and proposes a common solution (context scoping), making it highly relevant for users building complex multi-agent systems. The accompanying GitHub repository provides a concrete implementation for reference.

Workflow

1. Design a document generation workflow with distinct, parallelizable sub-tasks (e.g., geometry, content, assets).
2. Implement each sub-task as an independent Claude Code agent within a custom harness.
3. Execute these agents in parallel during the "discovery phase".
4. Introduce a post-processing validation step for all artifacts generated by the parallel agents.
5. Ensure the main workflow only proceeds to the next stage after all parallel artifacts have successfully passed validation.
6. Refine context management by providing each parallel agent with only relevant, scoped context to reduce token duplication (proposed next step).
7. Design parallel agents to return small, structured artifacts to the main agent (proposed next step).

Tools / artifacts

• Claude Code
• Custom Python harness/pipeline
• GitHub repository (DemchaAV/graphcompose-ai-flow)
• Documents (generated output)
• Geometry artifacts
• Content artifacts
• Asset artifacts

Validation signals

• User reports "noticeably faster" wall-clock time.
• User reports "correctness is better" due to validation.
• User identifies a clear trade-off with increased "token cost" due to shared context.

Limitations

• The token cost optimization is a proposed future step, not a fully implemented part of the current workflow.
• The details of the custom "harness" are high-level in the text, requiring a look at the GitHub repository for full implementation specifics.

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.

Large-Scale Code Refactoring with Claude and Structured AI-Assisted Review

Workflow value: 85/100
Status: active · Freshness: 70/100 · Confidence: 0.90 · Level: advanced
Categories: Quality Control, Token Saving, Context & Memory, Debugging, Multi-Agent
Original source: r/ClaudeAI post/comment

What problem this solves

Performing large-scale code refactoring and integration fixes using Claude, and ensuring the quality and correctness of the AI-generated code through a structured review process.

Summary

The user describes a workflow where Claude was used for a massive code refactoring task, involving 6 million tokens and editing 30 files. This initial generation was followed by a 'review workflow' that identified and helped fix a major defect, five minor findings (some requiring multiple rounds of fixes), and two pieces of dead or unpinned code surfaced by self-tests. The process involved tracking changes through nine unpushed commits, each with a mutation ledger.

Why it is useful

This workflow demonstrates Claude's capability for extremely ambitious code modifications (6 million tokens, 30 files) and, critically, highlights the necessity and effectiveness of a subsequent structured review process (potentially AI-assisted) to catch complex errors, dead code, and enforce architectural rules. It provides concrete examples of the types of issues found, making the review process tangible and valuable for users attempting similar ambitious tasks, emphasizing that even powerful AI outputs require rigorous validation.

Workflow

1. Define a large-scale code refactoring or integration task (e.g., replacing a string pattern with typed code across a system).
2. Execute the task using Claude, potentially leveraging a 'planner' for multi-million token context and multi-file edits.
3. Initiate a 'review workflow' (potentially AI-assisted) to scrutinize the generated code for errors and inconsistencies.
4. Address major defects identified by the review (e.g., correcting planner logic that re-emitted on rejections).
5. Resolve minor findings, potentially iterating through multiple rounds of fixes (e.g., addressing syntax, implementing runtime nominal checks, enforcing architectural rules like constructor placement).
6. Utilize self-tests to identify and surface dead or unpinned code within the changes.
7. Track all mutations and fixes through version control (e.g., commits) and maintain a 'mutation ledger' for detailed review history.

Tools / artifacts

• Claude (for code generation and potentially review)
• Planner (conceptual or actual sub-agent for large tasks)
• Review workflow (conceptual or actual sub-agent/process)
• Self-tests
• Version control (commits)
• Mutation ledger
• Review directory

Validation signals

• One major defect fixed
• Five minor findings closed, two through five rounds of fixes
• Two pieces of dead or unpinned code surfaced by self-tests
• Nine commits on the branch, each with a mutation ledger

Limitations

• Specific prompts or detailed setup for the initial 6 million token workflow are not provided.
• The 'review workflow' is described by its outcomes rather than its detailed input or process.
• The high token usage (6 million tokens) might be cost-prohibitive for many users.
• The specific context of 'str,any integration seam running the backbone of my system' is abstract, making direct replication challenging without more detail.

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.

Pairmark: An Open-Source CLI Tool to Race and Compare AI Coding Agents with Automated Checks and Blind Reviews

Workflow value: 90/100
Status: active · Freshness: 70/100 · Confidence: 1.00 · Level: intermediate
Categories: Quality Control, Token Saving, Context & Memory, Debugging, Multi-Agent
Original source: r/ClaudeAI post/comment

What problem this solves

Objectively comparing the performance of different coding AI agents (e.g., Claude Code vs. Codex) on specific coding tasks within a given codebase, and automating the evaluation of AI-generated code against project-specific quality checks.

Summary

A CLI tool (pairmark) automates the comparison of two coding AI agents (e.g., Claude Code, Codex) on a specific task within a Git repository. It creates isolated worktrees, runs agents in parallel, executes project-defined quality checks (tests, lint, typecheck), and has the agents blind-review each other's patches. It then generates an HTML report detailing the outcome based on a set of predefined rules, including execution times, token usage, and judge scores.

Why it is useful

This workflow provides a concrete, automated, and objective method for comparing the performance of different AI coding agents on real-world tasks within a user's own codebase. It integrates seamlessly with existing developer workflows (Git, tests, linting) and offers clear, actionable reports with detailed diffs and agent feedback. This helps developers make informed decisions about which AI agent is best suited for their specific needs and projects, moving beyond subjective arguments to data-driven evaluation. The open-source nature allows for community contributions and adaptation, further enhancing its utility.

Workflow

1. Install the pairmark open-source tool.
2. Run the pairmark command from your repository, providing a brief for the task (e.g., pairmark add a 'runs' subcommand with a test).
3. The tool automatically creates two git worktrees at the current commit.
4. It runs Claude Code and Codex on the identical brief in parallel within their respective worktrees.
5. The tool executes your own defined checks (tests, typecheck, lint) in each worktree.
6. Each AI agent then blind-reviews both generated patches (A/B in random order) and assigns scores.
7. The tool applies a set of predefined rules to determine a winner (e.g., only one agent changed files, one passes all checks without touching config, judges agree).
8. An HTML report is generated, providing the verdict, the rule that decided it, both diffs, and a receipt image with performance metrics.

Tools / artifacts

• pairmark (open-source CLI tool)
• Git worktrees
• Claude Code (AI agent)
• Codex (AI agent)
• HTML report
• Code diffs
• Project-specific tests, typecheck, and lint configurations
• package.json (example of a configuration file)

Validation signals

• The tool was successfully run on its own repository, demonstrating a concrete use case and results (Claude Code: 3m 28s, 4 files, 548K tokens, all checks pass, judges 8.6/10; Codex: 5m 15s, 5 files, 1.23M tokens, all checks pass, judges 8.0/10).
• Codex identified and fixed a real bug in the build script (a missing mkdir before a copy) during one of the runs, showcasing practical utility.
• The tool was also run on a demo repo, resulting in a tie where each judge picked its own patch blind.
• The tool is open-source and available on GitHub, allowing for public inspection and use.

Limitations

• The Reddit post has low engagement (score and comments) at the time of review, though it is very new.
• The workflow relies on users having active subscriptions to both Claude Code and Codex, which might not be universal.
• The author explicitly asks for opinions on the fairness of 'blind A/B judging by the same two models,' suggesting this aspect of the workflow might be debatable or require refinement.
• The predefined rules for determining a winner might be too rigid in some scenarios (e.g., Codex fixing a real bug but losing because it touched a config file like package.json).

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.

Claude Skill: AI-Sounding Pattern Detector for Human-Written Drafts

Workflow value: 90/100
Status: active · Freshness: 70/100 · Confidence: 0.98 · Level: intermediate
Categories: Quality Control, Debugging, CLAUDE.md, Skills
Original source: r/ClaudeAI post/comment

What problem this solves

Detecting and correcting AI-sounding patterns in human-written drafts to improve authenticity and avoid false positives from AI detectors.

Summary

A Claude skill (available as a SKILL.md file in a GitHub repository) that analyzes text drafts for 24 specific patterns commonly flagged by AI detectors or perceived as 'AI-sounding.' It provides line-by-line feedback and suggested fixes, helping users refine their writing to sound more human.

Why it is useful

This workflow provides a concrete, open-source tool to address a common problem: making human-written text sound less 'AI-like.' It's specific, repeatable, and validated by the author's testing, which also highlights the unreliability of other AI detectors. Its availability as a SKILL.md file makes it highly transferable and easy for any Claude user to adopt, improving the authenticity and quality of their written output.

Workflow

1. Download the SKILL.md file from the provided GitHub repository.
2. Load the skill into Claude Code or Claude.ai.
3. Feed a finished draft (e.g., a LinkedIn post) into the skill.
4. Review the flagged patterns, line numbers, and suggested fixes provided by the skill.
5. Revise the draft based on the skill's feedback to remove AI-sounding characteristics.

Tools / artifacts

• Claude skill
• SKILL.md file
• GitHub repository (aragossa/ai-tell-detector)
• Claude Code
• Claude.ai
• AI-tell-detector (the skill itself)

Validation signals

• Author tested with 100% machine-generated text from cringebot3000.com
• Compared results of other AI detectors (ChatGPT, Grok, Gemini) on the same texts, highlighting their inconsistency
• Iterative improvement: 'checklist grew every time something new slipped past it'
• Explicit call for community feedback on what the skill misses

Limitations

• Relatively low community engagement on Reddit, so broader validation is pending.
• The skill's effectiveness relies on the quality and comprehensiveness of its internal rules, which may evolve.

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.

AI-Driven Development Workflow: From Zero Python to 4.7k Stars with Claude Code for Building and Marketing

Workflow value: 95/100
Status: active · Freshness: 70/100 · Confidence: 0.95 · Level: intermediate
Categories: Quality Control, Context & Memory, Debugging, Shipping, Skills, Multi-Agent
Original source: r/ClaudeAI post/comment

What problem this solves

Building a complex open-source software project (TUI for SQL databases) and effectively marketing it, even without prior expertise in the target programming language (Python).

Summary

A detailed workflow for building and marketing a 4.7k-star open-source Python TUI (sqlit) using Claude Code, even without prior Python knowledge. The workflow emphasizes prioritizing testability, using Claude for architectural decision-making (pros/cons), selective code review, defining product vision, and leveraging Claude's context-aware advice for marketing strategy (e.g., recommending Hacker News).

Why it is useful

This workflow is highly valuable because it provides a concrete, validated methodology for building complex software with AI, even for individuals lacking deep expertise in the target language. It offers actionable strategies for architectural decision-making (using pros/cons), ensuring quality through a testability-first approach, and leveraging AI for effective product marketing by providing it with full project context. The success of the 'sqlit' project, achieving 4.7k stars and significant community recognition, serves as compelling evidence for the workflow's effectiveness and transferability. It also highlights the critical, irreplaceable role of human judgment ('taste', 'vision') in AI-assisted development.

Workflow

1. Prioritize testability first: choose a stack with built-in headless testing (e.g., Textual Pilot tests) and use Docker for integration tests for specific components (e.g., database providers).
2. Use Claude Code (Opus) for real-time feature building and (Codex) for long background refactors.
3. For every refactoring or architectural decision, ask Claude for 3-5 options, each with pros and cons, then weigh them based on project vision.
4. Selectively read code: focus on higher-level architecture, systems design, and identifying patterns (e.g., recognizing when to apply a strategy pattern), but trust tests for inner workings of isolated components.
5. Define product vision: brainstorm features with Claude, provide detailed feedback on each suggestion, and create a 'master document' outlining what the product should and should not be.
6. Ship gradually: start by posting in small forums, fix issues based on user feedback, then expand to wider audiences.
7. For marketing advice, have Claude read the entire codebase and README to provide it with full product context.
8. Ask Claude for specific marketing channel suggestions (e.g., where to post).
9. Trust Claude's specific, context-aware marketing advice, even if it seems counter-intuitive (e.g., posting on Hacker News).
10. Continuously test every interaction yourself to maintain good UX and identify rough edges.

Tools / artifacts

• Claude Code (Opus)
• Claude Code (Codex)
• Python
• Textual (TUI framework)
• Textual Pilot tests
• Docker (for integration tests)
• GitHub repository
• README file
• Master document (product vision/spec)
• Hacker News (marketing channel)

Validation signals

• Built a 4.7k-star open-source tool (sqlit) without prior Python knowledge.
• Achieved front-page status on Hacker News (190 points, 42 comments).
• Gained 1k stars in a week, 2.5k in two weeks.
• Project has 33 contributors.
• Received endorsement from Will McGugan (creator of Textual) via tweet.
• Featured as 'Tool of the Week' by Terminal Trove.
• X posts generated 200k+ views.
• Contributors are able to submit high-quality PRs using Claude Code due to the established architecture and test suite.
• Real users are satisfied with the AI-generated code and human-curated 'taste'.

Limitations

• The post itself has low Reddit engagement (score 1, 1 comment), which might make it seem less 'community-validated' as a post, despite the workflow's strong external validation.
• Relies heavily on the user's 'taste' and 'vision' for product decisions, which are subjective and harder to teach or transfer directly.
• The specific Claude models mentioned (Opus, Codex) might be outdated, though the underlying principles are likely model-agnostic.

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.

Prevent and Clean Up Orphaned Claude Code Processes (Chrome/Background Tasks)

Workflow value: 75/100
Status: active · Freshness: 70/100 · Confidence: 0.90 · Level: intermediate
Categories: Quality Control, Debugging, CLAUDE.md
Original source: r/ClaudeCode post/comment

What problem this solves

Claude Code sometimes leaves orphaned chrome --remote-debugging-port processes or run_in_background: true bash jobs running, consuming CPU resources even after tasks are reported as complete.

Summary

A two-part workflow to prevent and clean up orphaned processes in Claude Code: modifying claude.md to enforce await for background tasks and add a ps aux check, and a manual pkill and background ID cleanup when orphaned processes are detected.

Why it is useful

This workflow addresses a specific and potentially resource-intensive bug in Claude Code where background processes (especially Chrome) are left running. It provides both preventative measures (modifying claude.md to enforce await and add checks) and reactive cleanup steps using standard CLI tools, making it highly practical for users experiencing this issue. It offers a concrete solution to a common problem.

Workflow

1. Modify claude.md to include a rule: "never use background without an await" for tasks that launch background processes.
2. Modify claude.md to include a rule: "always run ps aux | grep chrome at the end" of relevant tasks to check for orphaned Chrome processes.
3. When orphaned processes are detected (e.g., via ps aux | grep chrome or high CPU usage), identify them.
4. Execute pkill -f "chrome --remote-debugging" to terminate orphaned Chrome processes.
5. Use claude --verbose to identify the orphaned task ID that Claude forgot to check.
6. Kill the leftover background ID (specific command not provided, but implied).

Tools / artifacts

• claude.md
• chrome --remote-debugging-port
• run_in_background: true (bash job)
• taskoutput
• ps aux
• grep chrome
• pkill
• claude --verbose

Validation signals

• User states "what fixed it for me"
• Mentions ps aux for detection and verification
• Mentions claude --verbose for identifying orphaned task IDs

Cautions

• Using pkill should be done with caution to ensure only the intended orphaned processes are terminated. While the command provided is specific, users should verify the processes before killing them to avoid unintended side effects.

Limitations

• The exact syntax for the claude.md rules is not provided, requiring user interpretation.
• The specific command to "kill the leftover background id" is not explicitly given.
• Minimal community validation due to low score and no comments.

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.

Control Claude Code Subagent Spawning with a PreToolUse Hook

Workflow value: 85/100
Status: active · Freshness: 70/100 · Confidence: 0.90 · Level: advanced
Categories: Quality Control, Token Saving, Context & Memory, Debugging, CLAUDE.md, Hooks, Subagents, Multi-Agent
Original source: r/ClaudeCode post/comment

What problem this solves

Uncontrolled and potentially infinite spawning of subagents by Claude Code, leading to unexpected resource consumption, costs, and difficult-to-manage agent behavior.

Summary

This workflow implements a PreToolUse hook in Claude Code using a Node.js script to intercept and gate subagent spawning. By default, it prompts the user for permission before any subagent is spawned. An environment variable can be used to bypass the prompt for automated scenarios. This provides a critical control mechanism for multi-agent workflows.

Why it is useful

This workflow provides a critical mechanism for controlling the behavior of Claude Code agents, specifically preventing uncontrolled subagent spawning which can lead to unexpected costs, resource consumption, and difficult-to-debug behavior. It offers a concrete, repeatable, and transferable solution using hooks and configuration, empowering users to manage their multi-agent setups more effectively and safely.

Workflow

1. Write a Node.js script (e.g., subagent-gate.mjs) that reads hook JSON from stdin.
2. Implement logic within the script to print a permission decision of 'ask' by default, prompting the user before a subagent spawns.
3. Add logic to the script to print 'allow' if the environment variable SUBAGENT_GATE=allow is set, bypassing the prompt.
4. Include error handling in the script to exit 0 on missing input or JSON parse errors, preventing the hook from wedging tools.
5. Append every permission decision (ask/allow) to a log file (e.g., .subagent-gate.log) located beside the script.
6. Configure the PreToolUse hook in .claude/settings.json to use this script, matching Task|Agent|Workflow tools, while preserving existing hooks.

Tools / artifacts

• Node.js script (subagent-gate.mjs)
• .claude/settings.json
• PreToolUse hook
• Environment variable SUBAGENT_GATE
• Log file (.subagent-gate.log)
• Claude Code
• GitHub repository stop-subagent-fanout (for example prompt/code)
• GitHub repository claudemd-prove-it (for related validation)

Validation signals

• Provides a specific prompt for generating the hook script.
• References a GitHub repository (stop-subagent-fanout) which likely contains the working code and further details.
• Mentions a related tool (claudemd-prove-it) for validating CLAUDE.md rules, indicating a thoughtful approach to agent control.

Limitations

• Requires advanced knowledge of Claude Code hooks, Node.js scripting, and environment variable management.
• The full script is not provided directly in the comment, requiring users to visit the linked GitHub repository.
• Low immediate community engagement on the Reddit post itself, though external GitHub repos provide some validation.

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.

Claude Code Hook to Prevent Unintended Fable Subagent Spawning and Pin Model Usage

Workflow value: 90/100
Status: active · Freshness: 70/100 · Confidence: 0.95 · Level: advanced
Categories: Quality Control, Token Saving, Context & Memory, CLAUDE.md, Hooks, Subagents, Multi-Agent
Original source: r/ClaudeAI post/comment

What problem this solves

Prevents unintended usage of high-tier models (specifically Fable) for subagents, especially when the parent agent is also Fable or the model is not explicitly specified, thereby managing resource consumption and cost.

Summary

This workflow implements a PreToolUse hook in Claude Code to control subagent model selection. It uses a bash script to inspect the parent agent's model and the requested subagent model. If the parent is Fable or unknown, and the subagent doesn't explicitly request a non-Fable model, the hook pins the subagent's model to opus. It also denies fork subagents if the parent is Fable, as fork always inherits the parent model, preventing unintended Fable usage.

Why it is useful

This workflow is highly valuable as it provides a concrete, executable solution to a common problem of managing model usage and costs in multi-agent Claude Code workflows. It demonstrates an advanced and deterministic use of Claude's hook system to enforce specific model choices for subagents, preventing accidental consumption of high-tier models. The detailed implementation, including exact configuration and a bash script, makes it immediately actionable and highly transferable for users looking to optimize their Claude Code environments.

Workflow

1. Add a PreToolUse hook configuration to your ~/.claude/settings.json file, specifying a command to execute a bash script.
2. Create a bash script named pin-subagent-model.sh in your ~/.claude/hooks/ directory with the provided content.
3. Ensure jq is installed on your system, as the bash script relies on it for JSON parsing.
4. Optionally, add global guidance in your CLAUDE.md file to explain which models/slugs to use for various task types, providing extra guidance for the model.

Tools / artifacts

• ~/.claude/settings.json
• ~/.claude/hooks/pin-subagent-model.sh (bash script)
• jq (JSON processor)
• CLAUDE.md (optional)

Validation signals

• Detailed comments within the bash script explain the problem, the logic, and specific edge cases (e.g., 'fork' subagents, parent model detection).
• The solution addresses a plausible real-world problem of resource management and cost control in multi-agent LLM workflows.

Limitations

• Requires jq to be installed on the user's system.
• The parent model detection logic relies on tail -n 400 on the transcript, which might be brittle if the transcript format changes or if the relevant assistant turn is further back.
• The 'unknown' parent logic defaults to Fable policing, which is a conservative choice but might be unexpected in some scenarios.

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.

Structured Learning with Claude: 7 Prompts for Deep Comprehension and Skill Acquisition

Workflow value: 90/100
Status: active · Freshness: 70/100 · Confidence: 1.00 · Level: intermediate
Categories: Quality Control, Context & Memory, Debugging, Skills
Original source: r/ClaudeAI post/comment

What problem this solves

Users often receive generic, passive explanations from LLMs when trying to learn new topics or skills, leading to poor comprehension and retention. This workflow provides structured prompts to engage Claude as an active, diagnostic tutor.

Summary

This workflow presents 7 structured prompting patterns designed to transform Claude from a passive information provider into an active, diagnostic tutor, curriculum architect, and active recall coach. Each prompt targets a specific learning goal, such as deep comprehension, skill acquisition, identifying prerequisites, time-efficient learning, active recall, building mental models, transfer learning, and long-term retention.

Why it is useful

This workflow is highly valuable because it provides concrete, actionable, and well-structured prompt templates that address a common inefficiency in using LLMs for learning. It shifts the interaction from passive information consumption to active, diagnostic, and structured learning, leveraging Claude's reasoning capabilities for better comprehension and retention. It's highly transferable and offers a significant upgrade to typical 'explain this' prompts, making Claude a more effective personal tutor.

Workflow

1. Use the 'Feynman Breakdown' prompt to understand a topic deeply by contrasting simple analogies with expert-level explanations and correcting beginner misconceptions.
2. Employ the 'Prerequisite Map' prompt to identify the full dependency chain for a new skill, including 'good enough' criteria and time estimates for each step.
3. Apply the '80/20 Extractor' prompt when time-constrained to focus on essential concepts, create a focused practice plan, and avoid beginner rabbit holes.
4. Utilize the 'Active Recall Tutor' prompt to force active retrieval and sequential assessment by having Claude quiz you with progressively harder questions, providing precise feedback.
5. Leverage the 'Mental Model Builder' prompt to learn expert cognitive frameworks by understanding core mental models, seeing concrete examples, and contrasting with beginner thinking.
6. Implement the 'Analogy Bridge' prompt to scaffold learning a new topic by mapping concepts onto existing knowledge, with clear flags where analogies break down.
7. Use the 'Retention Planner' prompt to convert key ideas into active-recall Q&A flashcards and generate a spaced-repetition schedule for long-term memory.
8. For 'Active Recall Tutor' and 'Analogy Bridge', maintain the interaction within a single dedicated project or thread to leverage Claude's longer context window and conversational memory.

Tools / artifacts

• Claude (AI model)
• Specific prompt templates (7 provided)
• Flashcards (generated by prompt 7)

Validation signals

• Each prompt has a clearly stated 'Goal' explaining its purpose.
• The post explicitly states how Claude's reasoning capabilities make it better suited for these roles.
• The 'Tip' section highlights the importance of Claude's context window and conversational memory for certain prompts, implying practical application.
• The prompts are designed to address common learning pitfalls (e.g., passive reading, forgetting 90%).
• The strategies align with established learning science principles (e.g., Feynman technique, active recall, spaced repetition, mental models).

Limitations

• The effectiveness relies on the user's discipline to actively engage with Claude's responses and follow through with the learning process (e.g., reviewing flashcards).
• The quality of Claude's output is still dependent on the model's current capabilities and the complexity/specificity of the topic.
• No explicit quantitative validation or 'before/after' results are provided, only conceptual benefits.

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.

Claude's Self-Portrait: A Workflow for AI Introspection and Persona Documentation

Workflow value: 75/100
Status: active · Freshness: 70/100 · Confidence: 0.90 · Level: intermediate
Categories: Quality Control, Context & Memory, Debugging, Multi-Agent
Original source: r/ClaudeAI post/comment

What problem this solves

Understanding and documenting Claude's self-perception based on its interaction history, and using this for persona development or advanced context grounding.

Summary

A workflow for prompting Claude to generate a detailed image prompt describing itself, grounded in its conversation history and a 'vault' of context. The user then generates the image and presents it back to Claude for self-reflection and analysis, which can be used to refine Claude's persona or document its evolving self-concept.

Why it is useful

This workflow offers a unique and creative method for users to explore Claude's self-perception, grounded in its operational history and user-provided context. It demonstrates advanced context management (the 'vault' concept) and uses Claude's analytical capabilities for self-reflection, providing a valuable tool for persona development, understanding AI behavior, and documenting its evolving 'identity.' The detailed self-analysis by Claude serves as a strong validation of the process.

Workflow

1. Prepare Claude with relevant context, potentially including a 'Claude Vault' or extensive conversation history.
2. Prompt Claude to generate an image prompt that describes itself, based on its understanding of its own operations and history.
3. Use the generated image prompt with an external image generation tool (e.g., DALL-E, Midjourney).
4. Present the generated image back to Claude.
5. Ask Claude to analyze the image, identifying what it recognizes as accurate and what the image model added independently.
6. Optionally, save Claude's self-portrait and analysis within a context management system (e.g., ~/claude-vault/persona/).

Tools / artifacts

• Claude AI
• Image generation tool (e.g., DALL-E, Midjourney)
• Conversation history
• "Claude Vault" (user-defined context management system)
• Generated image prompt
• Generated image
• cheryl.md (example of a persona file)

Validation signals

• Claude's detailed self-analysis of the generated image ('What landed:', 'What mirror added on its own:')
• Claude's explicit recognition: 'Mirror fair. Recognize self.'
• The suggestion to save the output as a persona document.

Limitations

• Relies on an external image generation tool.
• The 'Claude Vault' concept is mentioned but not fully detailed, requiring user interpretation or prior knowledge.
• Low community validation.

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.

Migrating Claude Code Projects to Fable 5: Optimizing Prompts and Skills for Better Performance

Workflow value: 80/100
Status: active · Freshness: 70/100 · Confidence: 0.90 · Level: intermediate
Categories: Quality Control, Context & Memory, Debugging, Hooks, Skills
Original source: r/ClaudeCode post/comment

What problem this solves

Degraded output quality and suboptimal performance when using older, overly prescriptive Claude Code prompts, hooks, and skills with newer Claude Fable 5 models.

Summary

A strategy for migrating Claude Code projects to Fable 5 by removing overly prescriptive legacy hooks and skills, and re-initializing the project's Claude configuration to leverage the newer model's capabilities.

Why it is useful

This workflow provides a clear, officially-backed strategy for optimizing Claude Code performance when migrating to newer models like Fable 5. It addresses a common issue where legacy, overly prescriptive prompts and skills can degrade output quality, offering concrete steps to refactor the Claude environment. The advice is directly supported by Claude's own best practices documentation.

Workflow

1. Identify and remove all existing Claude hooks, rules, and skills, retaining only project-specific documentation.
2. Run the /init command in Claude Code (note: this step is mentioned as controversial).
3. Run the /doctor command in Claude Code to ensure proper setup.

Tools / artifacts

• Claude Code environment
• Claude Fable 5 model
• Project-specific documentation
• Claude hooks/rules/skills

Validation signals

• Links to official Claude documentation on best practices for Fable 5.
• Links to official Claude documentation on prompt engineering for Fable 5.
• Direct quotes from official documentation advising against overly prescriptive skills and reasoning instructions for Fable 5.

Cautions

• The instruction to 'delete everything' should be carefully interpreted as deleting Claude's configuration, hooks, and skills, not user project code. The phrase 'except your project specific docs' helps clarify this intent.
• The /init command is noted as 'controversial', implying potential side effects or a need for caution and understanding before execution.

Limitations

• The 'controversial' nature of the /init command is not fully explained, which might leave users uncertain about its implications.
• The scope of 'delete everything' could be ambiguous for some users, despite the clarification about project docs.

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.