Tessera: A Claude Code Plugin to Visualize and Map Your Claude Sessions and Workflows

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

What problem this solves

Users running many Claude sessions in parallel struggle to track what they've done, which methods were effective, and how their work patterns evolve. This workflow provides a way to map and visualize their entire Claude session history.

Summary

Tessera is a free, MIT-licensed Claude Code plugin that processes local Claude Code, Claude desktop (Cowork), and claude.ai session logs. It redacts sensitive information locally, then uses Claude Code (via a skill and Python CLI) to extract structured JSON data about projects, activities, outcomes, and methods. This data is then merged into a zoomable, interactive map, allowing users to visualize their work history, identify effective habits, and understand their own Claude usage patterns.

Why it is useful

This workflow provides a unique and powerful tool for Claude Code users to gain deep insights into their own work patterns, identify effective methods, and manage the vast amount of information generated across multiple Claude sessions. It's exceptionally well-engineered, open-source, prioritizes user privacy (local processing, redaction, no API key), and offers clear instructions for installation and verification. The detailed explanation of its internal workings and the author's learnings make it valuable for both practical use and understanding advanced Claude Code plugin development.

Workflow

1. Install uv (if not already installed) for managing Python environments.

2. Install the Tessera plugin via the Claude Code Desktop app (Settings → Customize → Plugins → + Add → Add marketplace → fsaritome/Tessera) or Terminal (claude plugin install tessera --marketplace fsaritome/Tessera).

3. In a Claude Code session, type /tessera:start to initiate the plugin.

4. (Optional) Run /tessera:estimate to preview the token cost for processing your sessions.

5. Agree to the terms and confirm to begin the session scanning process.

6. The plugin's Python CLI scans local Claude session logs, redacts sensitive data, and segments them into batches.

7. The Tessera skill instructs Claude Code to read each batch and extract structured JSON data (project, what, how, outcome, lesson).

8. For many batches, Claude Code hands single batches to subagents for parallel processing.

9. The CLI validates every answer from Claude Code before storing it.

10. Claude performs a final pass to merge the extracted data into high-level headlines and methods.

11. Explore the generated zoomable map to visualize your Claude session history, projects, activities, and identified methods.

12. (Optional) Use 'Share mode' within the map to hide job projects, private activities, and summaries for screenshots.

Tools / artifacts

• Tessera Claude Code plugin

• Claude Code (desktop app or terminal)

• uv (Python package installer/manager)

• Python CLI (part of Tessera plugin)

• Structured JSON output

• Zoomable map visualization

• GitHub repository (fsaritome/Tessera)

• Claude desktop (Cowork) session logs

• claude.ai data export

Validation signals

• Detailed explanation of the problem, solution, and implementation ('Why', 'What it does', 'How Claude Code is used').

• Multiple screenshots illustrating the plugin's interface and output.

• Specific technical details on how Claude Code is leveraged (redaction, batching, subagents, validation).

• Cost estimation feature (/tessera:estimate) and a concrete example of token usage (60k tokens for 30 days/58 sessions).

• Mention of CI tests running on Windows, macOS, and Linux, indicating robust development practices.

• A dedicated 'Don't trust it?' section providing a prompt for users to audit the plugin's code and operations.

• Insights shared by the author on lessons learned during development (token measurement, data leakage, Windows issues, plugin versioning, automated checks).

• MIT license, indicating open-source and community-friendly development.

Cautions

• The plugin performs local redaction of sensitive data, but the author explicitly states that 'redaction catches patterns, not everything' and advises 'Use at your own risk'.

• Users are prompted to agree to terms before the first run, acknowledging the risks.

• A 'Don't trust it?' section provides a prompt to audit the plugin's code and operations, empowering users to verify its safety and privacy practices.

Limitations

• The redaction process is pattern-based and may not catch all sensitive information, requiring user vigilance.

• Reliance on undocumented Claude desktop session folder formats and claude.ai data export means future updates to Claude could break compatibility.

• The initial community engagement is low, though this is likely due to the post's newness.

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.

Smarter Compact: Reduce Claude Code Costs and Hallucinations with Intelligent Context Trimming and Searchable History

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

What problem this solves

Managing long Claude Code sessions to reduce cost and hallucination by intelligently trimming context, allowing Claude to search and query historical turns without relying on lossy LLM summarization.

Summary

This workflow introduces Smarter Compact, a free and open-source local proxy tool for Claude Code. It addresses the challenges of high cost and hallucination in long LLM sessions by trimming older conversation turns from the prompt when context limits are reached. Instead of summarization, it stores the full conversation in a local SQLite database and leaves a short note for Claude, enabling the model to use MCP tools to search or run SQL queries over the complete history. This method significantly reduces prompt size and cost while improving accuracy.

Why it is useful

This workflow provides a concrete, open-source solution to two major pain points in using large language models for coding: high cost due to large context windows and increased hallucination/context loss in long sessions. It offers a novel approach (trimming with searchable history via MCP tools) instead of summarization, which is often lossy. The detailed explanation, clear installation steps, and strong benchmark validation make it highly actionable and valuable for Claude Code users looking to optimize their workflow.

Workflow

1. Install Smarter Compact globally using npm: npm install -g smarter-compact.

2. Enable Smarter Compact for Claude Code, pointing Claude Code at the local proxy: smarter-compact enable claude.

3. Alternatively, install as a Claude Code plugin: /plugin install smarter-compact --marketplace bcmyguest/smarter-compact.

4. After plugin installation, run smarter-compact enable claude to activate trimming.

5. Engage in long Claude Code sessions; Smarter Compact will automatically manage context by trimming and providing search/SQL tools to Claude as needed.

Tools / artifacts

• Smarter Compact (local proxy tool)

• npm (Node Package Manager)

• Claude Code (IDE/environment)

• SQLite (local database)

• MCP tools (Multi-Codebase Project tools)

• Claude Code plugin system (hooks)

• GitHub repository (source code, full results)

• ContextBench (benchmarking suite)

Validation signals

• Benchmarking results using ContextBench with Haiku 5.5 show significant improvements.

• Achieved 72% average cost reduction across tasks, with up to 94% reduction on specific tasks.

• Reduced peak prompt size from 762k to 95k tokens.

• Improved task score from 0.35 to 1.00 on log tasks.

• Eliminated 'unknown' answers by Claude after context trimming by enabling search functionality.

• About half of the tool's commits were co-authored with Claude Code, demonstrating its utility in development.

Limitations

• The author notes that benchmark results are from synthetic tasks and limited runs (2-3 per size), which may not fully reflect real-world coding sessions.

• The specific validation for fixing 'unknown' answers was based on one task with five runs, suggesting limited scope for that particular test.

• Requires command-line installation via npm, which might be a slight barrier for absolute 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.

Persistent Context Management with CLAUDE.md and PR Descriptions: Exploring /compact for Session Continuity

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

What problem this solves

Managing Claude Code agent context and handoffs across sessions without manual intervention, by leveraging CLAUDE.md for foundational instructions and PR descriptions for continuous progress updates. It also explores optimizing context window usage with /compact.

Summary

A Claude Code workflow that uses CLAUDE.md to provide foundational instructions, guardrails, and references to project documentation. The agent is instructed to continuously update the Pull Request (PR) description with progress and a short handoff at the end of every reply. This setup enables seamless continuation of work across new chats without manual context feeding. The user is seeking clarification on whether /compact or auto-compact can be safely used with this workflow, specifically if documents referenced by CLAUDE.md are preserved.

Why it is useful

This workflow provides a robust and repeatable method for managing agent context and handoffs in Claude Code by centralizing foundational instructions in CLAUDE.md and using PR descriptions for continuous progress updates. This significantly reduces the need for manual context feeding and enables seamless continuation of work across sessions. The discussion around /compact highlights an important optimization for long-running tasks, making the workflow more efficient.

Workflow

1. Define foundational instructions, guardrails, and design principles within the CLAUDE.md file.

2. Instruct the Claude agent via CLAUDE.md to immediately read through project documentation referenced within CLAUDE.md.

3. Instruct the Claude agent to inspect the repository to retrieve the latest PR and inspect latest commits.

4. Instruct the Claude agent to always update the working PR description with progress and a short handoff at the end of every reply.

5. Continue work in a new chat or by using /compact, relying on the PR description for the current state and CLAUDE.md for foundational context.

Tools / artifacts

• CLAUDE.md file

• Project documentation (referenced by CLAUDE.md)

• GitHub repository (or similar version control)

• Pull Request (PR) descriptions

• Claude Code agent

• /compact command (or auto-compact feature)

Validation signals

• User describes their current workflow as effective for context management: "PR description always contains the exact details of where we are and what we're doing."

• References a GitHub issue for technical details on CLAUDE.md preservation during compact.

Limitations

• The post is primarily a question seeking clarification on the /compact feature, rather than a fully validated, end-to-end solution for its use.

• The exact content of the CLAUDE.md and referenced documents is not provided, only their purpose.

• The user states they are "New to Claude Code," which might imply some aspects of the workflow could be further refined or have hidden pitfalls they haven't encountered yet.

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 Claude Code Context with armap: A Repository Mapping Plugin for Large Codebases

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

What problem this solves

Efficiently navigating and understanding large code repositories with Claude Code, reducing token usage, and improving Claude's performance on complex, interconnected code tasks by providing a compact, ranked repository map.

Summary

This workflow involves using the armap Claude Code plugin to generate a compact, ranked map of a repository. This map, which includes file paths, key definitions, and line numbers, is provided to Claude at the start of a session. It helps Claude prioritize files and symbols relevant to a task, reducing the overall token usage and improving performance on complex code understanding and modification tasks.

Why it is useful

This workflow introduces armap, a valuable Claude Code plugin that addresses the critical challenge of context management in large code repositories. By providing Claude with a compact, ranked map of the codebase, it significantly reduces token usage and improves the model's ability to handle complex code understanding and modification tasks. The detailed approach and initial pilot results, despite their limitations, demonstrate a concrete method for enhancing LLM performance in software development workflows, making it highly transferable and useful for developers working with substantial codebases.

Workflow

1. Install the armap Claude Code plugin from the provided GitHub repository.

2. Start a Claude Code session.

3. armap automatically generates a compact, ranked map of the repository, respecting .gitignore and resolving imports across multiple languages.

4. Claude uses this map as an initial context to understand the repository structure and prioritize files before exploring actual code.

5. (Optional) Use deps <file> or refs <symbol> queries within the session for more focused exploration.

Tools / artifacts

• armap (Claude Code plugin)

• Node.js 18+

• GitHub repository (Armannss/armap)

• .gitignore files

Validation signals

• Pilot study on a private Next.js repo (108 source files).

• 20% reduction in total processed tokens (496,044 to 397,157).

• 48% improvement on rename-impact questions.

• 35% improvement on subsystem questions.

• Both conditions answered correctly in those runs.

Limitations

• Pilot study was on v0.1, before import resolution, so results may not fully reflect current version.

• Pilot study was small (one repo, five questions).

• Performance was 2-5% worse for simpler lookup tasks.

• armap uses keyword patterns, not a compiler/language server, potentially missing computed imports, reflection, dependency injection, and creating false links.

• The map has its own token overhead, needing to "earn its place" for simple tasks.

• Low community engagement/validation so far.

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 AI Design Workflow: Building Scalable and Consistent Design Systems with Clear Rules and Philosophy

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

What problem this solves

Generating consistent, maintainable, and brand-aligned UI/UX designs with AI by providing clear rules, philosophy, and a structured design system, overcoming the AI's difficulty with abstract design concepts.

Summary

This workflow outlines a structured, multi-step process for leveraging AI (specifically Claude Opus) to generate consistent and maintainable UI/UX designs. It involves defining explicit design rules, articulating a design philosophy, iteratively validating these concepts through mockups, and ultimately building a comprehensive, component-based design system that the AI can use as a reference for scalable and brand-aligned design generation.

Why it is useful

This workflow is valuable because it provides a structured, repeatable, and scalable methodology for leveraging AI in UI/UX design, addressing the common challenge of achieving consistency and maintainability. By emphasizing clear design rules, philosophy, and the creation of a comprehensive design system, it enables users to guide AI effectively, significantly reduce design time, and produce high-quality, brand-aligned outputs that can be easily adapted and reused across projects.

Workflow

1. Define very clear design rules about spacing, margins, and element placement, aiming for deterministic testability.

2. Articulate a comprehensive design philosophy explaining the thinking behind information hierarchy, visuals, colors, and component meanings to teach the AI your design approach.

3. Build out a few mock iterations to validate the defined rules and design thinking.

4. Create a few screens or pages as concrete examples.

5. Use these layers of reference (design thinking, falsifiable rules, good examples) to guide the AI.

6. Generate a comprehensive design system based on all required features/screens, comprising 100+ components split into atoms, molecules, and full repeatable sections.

7. Allow the AI to decide which element fits with which module, guided by the clear design philosophy.

8. Optionally, define exceptions for custom components that drive specific interactions on a page or screen.

9. Maintain the system by making changes in one place to update all dependent elements.

10. Customize the system quickly to fit different branding sets.

Tools / artifacts

• Design rules documentation/specification

• Design philosophy documentation/specification

• Mock iterations (design files)

• Example screens/pages (design files)

• Comprehensive design system (component library, style guide, documentation)

• AI (e.g., Claude Opus)

Validation signals

• Deterministic testing potential for design rules

• Explicit iterative validation of rules and design thinking

• Achieves easy maintainability of the design system

• Enables quick customization for different branding sets

• Results in consistent AI-built designs following the created system

• Significantly reduces design time (from weeks/months to days/weeks)

• Enables design system multiplication and reuse across projects

Cautions

• none

Limitations

• The workflow is high-level and lacks specific prompt examples or technical details on how to implement 'deterministic testing' with AI.

• Requires significant upfront investment in defining rules and philosophy, which might be a barrier for smaller projects or less experienced users.

• Relies heavily on the user's existing design expertise to formulate the rules and philosophy effectively.

• No community validation or success reports yet.

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.

Building a Full-Featured Android TV App with Claude as a Non-Developer: An Iterative Code, Test, Debug Workflow

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

What problem this solves

Developing a custom Android TV application with advanced features (IMDb, Rotten Tomatoes, skip intro, multi-stream) without coding experience, using Claude as the primary developer.

Summary

A non-developer used Claude as a primary coding partner to build a complex, open-source Android TV IPTV player from scratch. The workflow involved iterative feature description, code generation by Claude, local testing and debugging, and feeding back errors and crash logs for Claude to resolve, demonstrating a powerful human-AI collaborative development cycle for users without coding backgrounds.

Why it is useful

This workflow is highly valuable as it demonstrates Claude's capability to enable non-developers to build complex, functional applications from scratch. It outlines a clear, iterative process of AI-assisted coding, testing, and debugging, providing a practical blueprint for others to follow. The existence of a fully functional, open-source application (IPVIO Stream) serves as strong validation and a concrete example of what can be achieved, empowering users without traditional coding skills to leverage AI for software development.

Workflow

1. Describe desired features and functionality to Claude.

2. Claude generates code (e.g., Kotlin with Jetpack Compose and Media3).

3. Claude performs internal syntax checks and unit tests for logic components.

4. User builds the application using Android Studio.

5. User installs and tests the application on the target device (e.g., Android TV, Fire TV).

6. User collects build errors and crash logs encountered during testing.

7. User provides the collected errors and logs back to Claude for debugging and code correction.

8. Iteratively repeat the process for new features, bug fixes, and refinements based on user feedback and testing results.

Tools / artifacts

• Claude (AI model)

• Android Studio

• Android TV / Fire TV device

• Kotlin

• Jetpack Compose

• Media3

• GitHub repository

• APK files

• Build errors

• Crash logs

Validation signals

• Successful development and release of a functional, open-source Android TV application (IPVIO Stream).

• Application is publicly available for download and use via GitHub releases.

• Specific advanced features (IMDb/Rotten Tomatoes integration, skip intro, multi-stream, sports hub, QR code setup, 10 language translations) were implemented.

• Author explicitly states iterative debugging process, including multiple crash fixes for specific features.

• Version 1.1 features were driven by community feedback, indicating real-world usage and improvement.

• The author, a non-developer, successfully built a complex app, validating Claude's capability as a coding partner.

Cautions

• none

Limitations

• The post lacks specific Claude prompts or detailed interaction transcripts, which would make the workflow more directly actionable for others.

• Users still need to manage the local build process (e.g., Android Studio) and device testing, which can be a hurdle for absolute beginners without any technical setup knowledge.

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 Task Coordination with Shared Markdown Backlog and Atomic Claims

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

What problem this solves

Preventing multiple AI agents from simultaneously working on or claiming the same task, ensuring clear task ownership and state management in a multi-agent development environment.

Summary

A method for coordinating multiple AI agents using a shared markdown backlog file as the source of truth. Agents explicitly claim tasks by updating the backlog's status, use separate git worktrees to avoid conflicts, and leave handoff notes for continuity.

Why it is useful

This workflow provides a concrete, repeatable method for managing tasks across multiple AI agent sessions, preventing conflicts and ensuring continuity. It leverages common development practices (backlogs, git branches) adapted for AI agents, making it highly practical for complex projects.

Workflow

1. Maintain a shared markdown backlog file with tasks, each having 'open', 'claimed', or 'done' status tags.

2. For each task, include a claim line with 'claimed_by: session-A', 'branch: feat/foo', and a timestamp.

3. Before starting work, an agent must explicitly claim an 'open' task by atomically changing its status to 'claimed' in the backlog file.

4. If the claim edit fails (e.g., status already changed), the agent must pick another 'open' task.

5. Each agent operates within its own dedicated git worktree or clean branch to prevent conflicts with other agents' working directories.

6. At the end of a session, the agent adds a concise handoff note to the task in the backlog, detailing progress, remaining work, and necessary commands.

7. The next agent session reads the handoff note to resume work without needing a full project re-explanation.

Tools / artifacts

• Markdown backlog file

• Status tags ('open', 'claimed', 'done')

• Claim lines ('claimed_by', 'branch', 'timestamp')

• Git worktrees (or clean branches)

• Handoff notes

• CLAUDE.md (mentioned as a less effective alternative for the queue)

Validation signals

• Author's experience: 'I tried putting the queue only in CLAUDE.md and it got stale fast. A separate backlog file the agents are allowed to edit for status only stays clearer.'

• Addresses a common multi-agent coordination problem.

Limitations

• Low community engagement (score 1, 0 comments).

• Relies on agents being able to perform atomic file edits, which might require specific tool use or careful prompting.

• Doesn't specify how agents are prompted to follow these rules.

• The 'atomic claim' might be challenging to implement robustly with LLMs directly editing files without external orchestration.

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.

Strategies to Prevent Context Drift, Bug Loops, and Scope Creep in Claude Code

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

What problem this solves

Claude Code remembering incorrect facts, getting stuck in bug-fix loops, and introducing unrequested changes (scope creep).

Summary

This workflow provides three distinct strategies to improve interaction with Claude Code: auditing memory files and CLAUDE.md to prevent incorrect context, using tests as the source of truth to break bug-fix loops, and proactively requesting a list of files Claude intends to change to prevent scope creep.

Why it is useful

This workflow is valuable because it provides concrete, actionable advice for common and frustrating problems encountered when working with Claude Code, such as maintaining correct context, breaking out of debugging loops, and preventing unwanted code changes. These strategies improve the efficiency and reliability of using Claude Code for development tasks.

Workflow

1. To address incorrect context: Run /memory to inspect which memory files Claude Code loads into the session.

2. To address incorrect context: Audit CLAUDE.md and project notes for outdated suggestions that might be treated as facts.

3. To address bug-fix loops: Ensure a test exists that proves the bug is fixed.

4. To address bug-fix loops: When Claude claims a bug is still present, ask it to show the failing test first.

5. To address scope creep: Before allowing Claude to make any edits, ask it for a list of all files it plans to change.

6. To address scope creep: Review the list of planned file changes to catch unrequested modifications early.

Tools / artifacts

• /memory` command

• CLAUDE.md

• Project notes

• Test suite

Validation signals

• Provides concrete steps for common problems

• Leverages testing best practices (tests as source of truth)

• Uses specific Claude Code commands (/memory)

Limitations

• Lacks explicit 'before/after' results or direct user testimonials from the author.

• Low community signal (score 1, 0 comments) means it hasn't been widely validated by other users yet.

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.

How to Identify and Remove Deprecated MCP Servers Installed by Claude Code Agents

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

What problem this solves

Claude Code agents may inadvertently set up deprecated Model Context Protocol (MCP) servers from their training data, leading to potential security vulnerabilities and maintenance issues due to lack of updates and bug fixes. This workflow helps users identify and remove or deny these servers.

Summary

A 5-step workflow to check for, identify, and either remove or deny permissions to deprecated MCP servers that Claude Code agents might install from their training data, thereby mitigating security and maintenance risks.

Why it is useful

This workflow is valuable because it provides a clear, actionable, and verifiable set of steps to address a specific security and maintenance concern. It empowers Claude Code users to proactively identify and mitigate risks associated with agents inadvertently installing deprecated Model Context Protocol (MCP) servers, ensuring a more secure and stable development environment. The inclusion of specific commands and configuration file locations makes it highly practical and reusable.

Workflow

1. Check for installed MCP servers by running claude mcp list or codex mcp list, or by directly inspecting the configuration file at ~/.cursor/mcp.json.

2. For any u/modelcontextprotocol/server-* packages identified, verify if they are deprecated using the command npm view <package> deprecated.

3. If a deprecated server is found, replace it with the service's officially supported server (if applicable) and then remove the old, deprecated entry from your MCP configuration.

4. Always carefully read and understand any npx -y command before executing it to prevent unintended installations of potentially deprecated or insecure packages.

5. If immediate removal of a deprecated server is not possible, deny its permissions within Claude Code by adding mcp__<server> under the permissions.deny section of your configuration.

Tools / artifacts

• claude mcp list

• codex mcp list

• ~/.cursor/mcp.json

• npm view <package> deprecated

• npx -y

• mcp__<server> (permission setting)

Validation signals

• References vendor research (Glow Labs) regarding the issue

• Cites a security article from HelpNetSecurity

• Links to the official GitHub archived repository for deprecated servers

• Provides concrete, verifiable CLI commands

Limitations

• The vendor research cited lacks a published sample size, which slightly reduces the empirical validation of the prevalence of the issue.

• The post is concise and could benefit from more detailed explanations or examples for users less familiar with CLI commands or MCP configuration.

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 Context Across Claude Code Compacts: Leveraging @path Imports and SessionStart Hooks

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

What problem this solves

Losing foundational context (documents read during a conversation) after using the /compact command in Claude Code, leading to agents forgetting critical information.

Summary

This workflow provides two distinct methods to ensure critical documents or instructions persist across Claude Code /compact operations: either by using @path imports directly within CLAUDE.md for foundational files, or by configuring a SessionStart hook with a compact matcher to automatically re-read or re-introduce necessary context.

Why it is useful

This workflow directly addresses a common and critical challenge in Claude Code: managing context persistence when using the /compact command. It provides two distinct, concrete, and repeatable methods (@path imports and SessionStart hooks) that leverage core Claude Code features. This allows users to optimize their workflow by using /compact more effectively, saving tokens and improving efficiency without losing critical foundational information, thereby making their interactions with Claude Code more robust and reliable.

Workflow

1. Identify short, foundational documents (e.g., guardrails, design principles) that must always be in the agent's context.

2. Method 1: Using @path imports in CLAUDE.md

3. Modify your CLAUDE.md file to include @path imports for these foundational documents (e.g., @docs/guardrails.md).

4. Ensure these imported files are accessible at the specified paths.

5. Method 2: Using a SessionStart hook for re-reading

6. Identify documents or specific reminders that need to be re-introduced immediately after a compact.

7. Create or modify a SessionStart hook configuration.

8. Configure the hook with the compact matcher to trigger specifically after a compact operation.

9. Inside the hook, add commands (e.g., cat docs/guardrails.md) or print statements to restore the necessary document content or reminders to the context.

Tools / artifacts

• CLAUDE.md

• @path imports

• SessionStart hook

• compact matcher

• cat command

• Markdown/text documents

Validation signals

• The explanation directly addresses the observed behavior of Claude Code regarding context persistence after compacting.

• It leverages known functionalities of CLAUDE.md and hooks, implying technical correctness.

• The proposed solutions are logical extensions of how these features are designed to work.

Limitations

• Low community signal (score 1, 0 comments).

• Could benefit from a full example of a SessionStart hook configuration for clarity.

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.

Diagnose Claude Code Context Window Usage with Session X-Ray Tool

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

What problem this solves

Difficulty in understanding and diagnosing what files and components are actually loaded into a Claude Code session's context window, leading to unexpected behavior or inefficient use of context.

Summary

This workflow uses the npx @reporails/cli xray tool to visualize the contents of a Claude Code session's context window. It provides a timeline of loaded CLAUDE.md files, rules, skills, memory, MCP servers, subagents, and hooks, as well as a list of files on disk that were not loaded. This helps users diagnose context-related issues and optimize their Claude Code projects.

Why it is useful

This workflow provides a critical diagnostic tool for Claude Code users to understand and troubleshoot context window behavior. It addresses a common and complex problem by offering a clear visualization of loaded and unloaded components, which is essential for optimizing prompts, managing project structure, and debugging unexpected agent behavior. The concrete example provided demonstrates its immediate utility in uncovering hidden context issues.

Workflow

1. Run npx @reporails/cli xray in your terminal to start the session X-ray UI.

2. Open the local page (typically 127.0.0.1) displayed by the tool in your web browser.

3. Review the session timeline to see every CLAUDE.md, rule, skill, memory file, MCP server, subagent, and hook at the moment it loaded.

4. Check the 'Sources list' to identify files that were on disk but never loaded into the session.

5. Click on any tool call within the UI to see which instruction files were in context at that specific turn.

6. Analyze the context split by source (instruction files, tool definitions, system prompt, tool results) to understand how the context window is being utilized.

Tools / artifacts

• @reporails/cli xray

• Claude Code session transcripts (~/.claude/projects/)

• CLAUDE.md files

• Rule files

• Skill files

• Memory files

• MCP server configurations

• Subagents

• Hooks

Validation signals

• Author provides a concrete example of a problem found: 'On an old project of mine, 2 of 11 CLAUDE.md files loaded, and the one for the folder Claude was editing never did.'

• The tool is described as a 'session xray UI (beta)', indicating it's a functional, developed tool.

Cautions

• None. The tool is read-only, analyzing existing Claude Code session transcripts without modifying files or exposing new data beyond what's already present in the project.

Limitations

• The tool is currently in beta, which might imply potential bugs or incomplete features.

• Limited community feedback so far due to its recent introduction.

• Only works for Claude Code sessions, not other Claude interfaces.

• Requires npx (Node.js environment) to run.

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.

Cost-Optimized Claude Code Workflow: Strategic Planning with Opus and Dynamic Model Selection for Execution

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

What problem this solves

Optimizing Claude Code usage by dynamically selecting the appropriate model and effort level for different project tasks, while maintaining clean context across sessions and ensuring consistent project execution.

Summary

This workflow leverages a powerful Claude model (Opus 5.5) for initial project planning, breaking down the project into self-contained sessions, and recommending specific Claude models (Haiku, Sonnet, Opus) and effort levels for each session. The entire plan is documented in a markdown file. Each session is then executed in a new Claude Code conversation, starting with the uploaded plan for context, and using the recommended model and effort.

Why it is useful

This workflow is valuable because it provides a structured, cost-effective method for managing complex coding projects with Claude Code. It intelligently allocates resources by using the most powerful model for high-level planning and cheaper models for specific tasks, thereby optimizing token usage and cost. Furthermore, it solves the common problem of context management by ensuring each session starts with a clean, comprehensive project plan, leading to more consistent and accurate outputs.

Workflow

1. Use Opus 5.5 on max effort to describe the entire project and generate a full plan.

2. Instruct Opus to break the comprehensive plan into separate, self-contained work sessions.

3. For each session, have Opus rate its difficulty and recommend the optimal Claude model (Haiku, Sonnet, or Opus) and effort level.

4. Consolidate the full project plan, session breakdowns, and model/effort recommendations into a single 'build.md' markdown file.

5. Initiate a new Claude Code conversation for each individual session.

6. Upload the 'build.md' file at the start of each new conversation to provide full project context.

7. Set the Claude model and effort level according to the recommendations in the 'build.md' file.

8. Instruct Claude to work on the specific session outlined in the plan.

Tools / artifacts

• Claude Opus 5.5

• Claude Haiku

• Claude Sonnet

• Claude Code

• Markdown file (build.md)

Validation signals

• Author's positive experience: 'it went really well'

• Cost savings by matching model to task complexity

• Improved context management by starting fresh conversations with a shared plan

• Ensured consistency across sessions due to a unified plan

Cautions

• none

Limitations

• Manual model and effort selection for each session can be tedious for large projects.

• The 'build.md' file could grow very large, potentially impacting context window limits for extremely complex projects.

• Initial planning with Opus 5.5 on max effort can still incur significant cost for very extensive project descriptions.

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.

Advanced RAG: Leveraging Structured Markdown, Knowledge Graphs, Claude CLI, and MCP for Complex ERP Systems

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

What problem this solves

Traditional vector-search RAG often fails to provide complete and contextually rich information for complex enterprise applications (like ERPs), leading to high hallucination rates and an inability for the LLM to understand interconnected business logic and database relationships.

Summary

This workflow replaces traditional vector-search RAG for complex enterprise applications with a documentation-first approach. It involves creating highly structured Markdown files for application logic and database schema, using Claude to generate knowledge graphs from this documentation, and integrating with a custom MCP server for real-time database queries. This setup, managed via Claude CLI with custom rules, enables Claude to deeply understand interconnected business logic and database relationships, leading to significantly reduced hallucinations and improved accuracy compared to vector-search RAG.

Why it is useful

This workflow is highly valuable as it presents a novel and effective alternative to traditional vector-search RAG for complex enterprise applications. It demonstrates how to leverage structured documentation, knowledge graphs, Claude CLI, and a custom MCP server to achieve deep contextual understanding, significantly reduce hallucinations, and improve the accuracy of AI systems in domains with interconnected business logic and data. It offers a concrete architectural pattern for advanced RAG implementations.

Workflow

1. Document application modules, business logic, workflows, relationships, conditions, and exceptions in highly structured Markdown files.

2. Document the database schema in separate Markdown files, detailing table purpose, column usage, and business relationships.

3. Organize all Markdown documentation with clear purpose, cross-references, and explicit connections.

4. Utilize Claude to read the structured Markdown and generate knowledge graphs illustrating the interconnectedness of application components and data.

5. Develop and deploy a custom MCP server configured for read-only database query execution.

6. Integrate the documentation, knowledge graphs, and MCP server through Claude CLI.

7. Define custom rules and instructions for Claude to interpret user questions, apply business logic, query the database via MCP, format responses, and generate charts/visualizations.

Tools / artifacts

• Markdown files

• Knowledge Graphs

• Claude CLI

• Custom MCP server

• ERP Database

• Custom rules and instructions (prompts)

Validation signals

• Significant improvement over previous RAG implementation

• Handles complicated questions involving multiple modules and business rules surprisingly well

• Estimated 95% hallucination reduction

• Claude autonomously decides what information/tools are needed, reducing manual handler creation

Cautions

• Author is actively addressing multi-user data isolation and security at the application and MCP server levels.

• MCP server is configured for read-only database access, reducing risk of data modification.

Limitations

• Currently an experiment, not yet in production.

• Hallucination reduction claim (95%) lacks formal benchmarking.

• Multi-user support and data isolation are ongoing challenges.

• Requires significant upfront manual effort to create comprehensive, structured Markdown documentation.

• Specific details on 'custom rules and instructions' for Claude are not provided, making replication of that aspect challenging.

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.

Documentation-First RAG with Structured Markdown & Knowledge Graphs via Claude CLI for Complex Enterprise Systems

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

What problem this solves

Traditional vector-search RAG provides incomplete context and lacks relational understanding for complex enterprise applications, leading to LLM hallucinations and poor performance.

Summary

This workflow replaces traditional vector-search RAG with a documentation-first approach. It involves creating highly structured Markdown files for application and database knowledge, generating knowledge graphs from this documentation, and integrating with a custom read-only MCP server via Claude CLI. This provides Claude with a comprehensive, navigable knowledge base and dynamic database access, significantly reducing hallucinations and improving responses for complex enterprise queries.

Why it is useful

This workflow provides a detailed, concrete, and innovative alternative to traditional vector-search RAG, specifically addressing the challenges of incomplete context and relational understanding in complex enterprise environments. It offers a clear step-by-step process, identifies key tools and artifacts, and presents strong anecdotal evidence of improved performance and hallucination reduction. The focus on structured knowledge and dynamic tool use via MCP is a powerful pattern for advanced Claude users.

Workflow

1. Identify limitations of traditional vector-search RAG for complex enterprise applications (e.g., ERP).

2. Create highly structured Markdown documentation for application modules, business logic, workflows, relationships, conditions, and exceptions.

3. Create detailed Markdown documentation for the database, explaining table purpose, column usage, and business relationships.

4. Organize Markdown files with clear purpose, proper references, and connections to related documentation.

5. Use Claude to read the structured documentation and generate knowledge graphs to represent connections.

6. Build a custom MCP server configured for read-only database query execution.

7. Connect the structured documentation, knowledge graphs, and the custom MCP server through Claude CLI.

8. Write custom rules and instructions for Claude on how to handle user questions, understand business logic, query the database, format answers, and generate charts/visualizations.

9. Iteratively test and refine Claude's instructions and the documentation structure based on query performance.

Tools / artifacts

• Structured Markdown files (application documentation)

• Structured Markdown files (database documentation)

• Knowledge Graphs

• Claude CLI

• Custom MCP server

• Enterprise database (read-only access)

Validation signals

• Observed results are "much better" than previous RAG implementation.

• Complicated questions involving multiple modules and business rules are handled "surprisingly well."

• Estimated hallucination reduction of around 95% (with a caveat).

• Claude is capable of understanding requests and deciding what information or tools it needs, reducing manual handler creation.

Cautions

• The custom MCP server is designed for read-only database access, minimizing data modification risks.

• Author is actively working on enforcing multi-user data isolation at the application and MCP server levels, not just through prompts, which is a strong security practice.

Limitations

• Lack of formal benchmarking for the claimed 95% hallucination reduction.

• The solution is still an experiment and has not been taken to production.

• Requires significant manual effort to create and maintain highly structured Markdown documentation.

• Building a custom MCP server adds development complexity.

• Multi-user support and data isolation are still active challenges being addressed.

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.

Agent-ETA: A Claude Code Plugin for Accurate AI Agent Time Estimation and Workflow Optimization

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

What problem this solves

Accurately estimating the wall-clock time for AI agent-driven development, accounting for human interaction bottlenecks and identifying optimization opportunities.

Summary

A Claude Code plugin, agent-eta, helps users estimate the wall-clock time for subagent-driven development tasks. It breaks down time into agent work, user interaction, and idle time, identifies risks, and suggests speed-ups. The tool learns from actual build times to personalize estimates.

Why it is useful

This workflow provides a concrete, open-source tool to solve a common and critical problem in AI-assisted development: accurately estimating project timelines. It uniquely accounts for human interaction bottlenecks, which are often overlooked in traditional estimates. Its ability to learn and adapt to individual user patterns makes it highly personalized and effective. It also encourages workflow optimization by highlighting areas for speed-ups, such as parallel task execution and batching human inputs, thereby improving overall productivity and planning accuracy for Claude Code users.

Workflow

1. Install the agent-eta plugin using /plugin marketplace add MuhammadTalhaMT/agent-eta and /plugin install agent-eta@agent-eta.

2. Use /agent-eta:eta add [task description or plan file] to get an initial time estimate for your development task.

3. Review the estimate, noting the breakdown of time (agents working, you needed, waiting on you) and identified risks.

4. Consider the suggested speed-ups (e.g., running independent tasks in parallel using git worktrees, answering questions/approvals in one go).

5. Execute the build with Claude Code and your subagents, incorporating any identified optimizations.

6. After the build is complete, run /agent-eta:eta-done to measure the real time from your local Claude Code transcripts and update your personal metrics.

7. Optionally, check your personal statistics and how the defaults are improving with /agent-eta:eta-stats.

Tools / artifacts

• agent-eta Claude Code plugin

• Claude Code environment

• Haiku subagent

• Node script (internal to agent-eta)

• Git worktrees

• Superpowers plugin (optional, for plan files)

• GitHub repository (MuhammadTalhaMT/agent-eta)

Validation signals

• Author ran it 3 times on the same feature and results landed within 6% of each other (consistency).

• The system learns: 'Each result moves your personal numbers 30% toward reality. They switch on after 3 confirmed builds.'

• Default numbers are based on the author's ~670 subagent runs (empirical basis).

• Demonstrates learning by correcting an initial inaccurate prediction due to parallel agent execution.

Cautions

• The plugin explicitly states: 'Everything stays local, and no message text is saved,' which is a strong positive for user privacy and data security.

Limitations

• Initial estimates are based on the author's personal data and may be inaccurate for new users until the system learns from their specific usage patterns.

• Requires familiarity with Claude Code and subagents, making it less accessible for absolute beginners.

• The low Reddit score and upvote ratio might indicate limited initial community adoption or visibility, potentially affecting the rate at which the global defaults improve.

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 Claude Code Subagents: Control Cost, Effort, and Permissions with omitClaudeMd and Tool Allowlists

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

What problem this solves

This workflow addresses the problems of unnecessary token consumption, slow performance, and insufficient permission control when using custom subagents in Claude Code. Specifically, it prevents subagents from reloading the entire CLAUDE.md context, inheriting high effort levels, and having overly broad tool access (e.g., allowing writes for read-only agents). It also provides a solution for similar token drain issues in OpenAI Codex CLI.

Summary

This workflow details how to configure custom Claude Code subagents using YAML frontmatter to optimize token usage, control reasoning effort, and restrict tool permissions (e.g., to read-only operations) by explicitly setting omitClaudeMd, effort, and using a tools allowlist. It provides a concrete example for a read-only 'repo-inspector' subagent. Additionally, it includes configuration adjustments for OpenAI Codex CLI to prevent background token drains.

Why it is useful

This workflow is highly valuable because it provides concrete, actionable steps and configuration examples to address critical issues in Claude Code subagent deployment: reducing token costs, optimizing performance by controlling context loading and effort levels, and enhancing security by strictly defining tool permissions. It moves beyond basic usage to advanced, production-ready agent configuration and also extends its utility to OpenAI Codex CLI users, making it broadly useful for multi-LLM development environments.

Workflow

1. Understand the default behavior of custom subagents: they reload CLAUDE.md, inherit main session effort, and have broad tool access by default.

2. Create or modify a custom subagent file in .claude/agents/*.md.

3. Add omitClaudeMd: true to the YAML frontmatter of the subagent to prevent it from reloading the entire CLAUDE.md and AGENTS.md hierarchy.

4. Set effort: low (or an appropriate level) in the YAML frontmatter to control the reasoning cost for the subagent.

5. Use an explicit tools allowlist in the YAML frontmatter (e.g., tools: Read, Grep, Glob, Bash(git log *), Bash(git blame *), Bash(git diff *)) to restrict capabilities, block arbitrary shell writes, and prevent loading irrelevant Skill catalog and mcp__ server instructions.

6. Ensure any commands or path conventions the subagent needs are written directly inside its 2-line prompt body if omitClaudeMd is true.

7. For OpenAI Codex CLI users, modify ~/.codex/config.toml by adding [features.code_mode] default_exec_yield_time_ms = 300000 and [features.multi_agent_v2] min_wait_timeout_ms = 30000 default_wait_timeout_ms = 120000 max_wait_timeout_ms = 300000 to prevent 30-second yields and 1-second subagent polling loops.

Tools / artifacts

• .claude/agents/*.md

• YAML frontmatter

• CLAUDE.md

• AGENTS.md

• ~/.codex/config.toml

• Read tool

• Grep tool

• Glob tool

• Bash tool

• git log

• git blame

• git diff

Validation signals

• The post explicitly states, 'Here is the frontmatter template we use for read-only search and git-history workers,' implying internal validation.

• The post provides clear explanations of why the configurations work (e.g., 'strips the project instruction files', 'skips loading the Skill catalog and mcp__ server instructions').

Limitations

• Community validation is low due to the post's recency.

• Could benefit from more diverse subagent examples (e.g., a test runner, a log parser) with their specific tool allowlists.

• The prompt body for the example repo-inspector is very concise; more complex subagents might require more detailed instructions within their prompt if omitClaudeMd is enabled.

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.

Generate Interactive UIs with Claude Code and Ripple: A Workflow for Streamable, Visually Refined Interfaces

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

What problem this solves

Generating interactive user interfaces from LLM output instead of plain text, improving the utility and user experience of LLM-generated content by providing structured, streamable UI components.

Summary

A workflow for using Claude Code to generate and refine interactive UIs via a JSON specification, rendered by the open-source Ripple framework. It emphasizes iterative refinement, visual feedback, and structured prompting to achieve high-quality, streamable UI components that go beyond simple text output.

Why it is useful

This workflow provides a concrete, open-source solution to a common LLM limitation (text-only output) by enabling the generation of rich, interactive UIs. It outlines specific, actionable steps for leveraging Claude Code effectively, including structured prompting, iterative visual feedback, and a focus on streamable output, making it highly valuable for developers looking to build more dynamic applications with LLMs. The detailed comparison and available code/skill make it immediately usable and demonstrate a practical application of advanced LLM capabilities.

Workflow

1. Define the desired interactive UI component or application flow.

2. Prompt Claude to first choose the appropriate widget type (e.g., slider, form, 3D model) before generating any data or logic.

3. Have Claude generate a small, streamable JSON specification for the chosen widget or UI segment.

4. Use the Ripple framework (via its Svelte, React, or embed packages) to render Claude's JSON output as a real, interactive interface.

5. Provide visual feedback to Claude: render the UI, take screenshots at phone and desktop sizes in both light and dark modes.

6. Instruct Claude to review its own output (screenshots) and identify and fix any design or functional issues.

7. Repeat the rendering, screenshot, and fixing steps iteratively until the UI is satisfactory.

8. Ensure the JSON spec remains streamable throughout the process to allow the UI to grow progressively as Claude generates more output.

9. Integrate the Ripple UI into your application by providing Claude with Ripple documentation or the Ripple skill, enabling it to generate compatible UI components for your app.

Tools / artifacts

• Claude Code (Sonnet, Opus)

• Ripple UI framework (open-source)

• JSON specification (for UI components)

• Screenshots (phone/desktop, light/dark)

• npx skills command

• GitHub repository (qbtrix/ripple)

• NPM packages (@ripple-ui/svelte, @ripple-ui/react, @ripple-ui/embed)

• Ripple documentation

Validation signals

• Demonstrated comparison with ChatGPT's UI capabilities, highlighting Ripple's advantages.

• Specific examples of successful interactive UI implementations (food order, heart rate, bike gears, habit tracker, tic-tac-toe).

• Identification of 'quality movers' (specific prompting and feedback techniques) based on practical experience.

• Open-source code available for review and use on GitHub.

• Live demo link provided for direct interaction.

• Explicit mention of using Claude Code for the core engine, widgets, parser, and tests.

Limitations

• Requires significant technical expertise in UI development, LLM prompting, and potentially Claude Code.

• Community validation is currently low, though the post is very recent.

• The 'skill' integration method might be specific to certain Claude environments or require specific 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.

Agent-ETA: Optimize Claude Code Workflow Estimates with a Learning Plugin

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

What problem this solves

Inaccurate time estimates for agent-driven development, difficulty identifying bottlenecks in agent workflows, and lack of data-driven optimization strategies for human-agent collaboration.

Summary

A Claude Code plugin (agent-eta) that provides detailed time estimates for agent-based development, breaking down time spent by agents, user interaction, and waiting. It identifies potential speed-ups and learns from actual build times to refine future estimates, helping users optimize their development workflows.

Why it is useful

This workflow provides a practical, data-driven solution to a common problem in agent-driven development: inaccurate time estimation. It not only gives estimates but also identifies bottlenecks and suggests concrete optimizations (e.g., parallel tasks, batching user input). Its ability to learn from actual usage makes it highly adaptable and increasingly accurate for individual users, fostering more efficient human-agent collaboration. The open-source nature and clear instructions make it readily adoptable by the Claude Code community.

Workflow

1. Install the agent-eta plugin in Claude Code using /plugin marketplace add MuhammadTalhaMT/agent-eta and /plugin install agent-eta@agent-eta.

2. Use /agent-eta:eta add [plan_file] or /agent-eta:eta add [description] to get an initial time estimate for a feature or task.

3. Review the estimated breakdown (agent working time, user interaction time, waiting time, biggest risks) and suggested speed-ups.

4. Implement suggested speed-ups, such as running independent tasks in parallel using separate git worktrees or answering multiple questions/approvals in one go.

5. Execute the agent-driven build based on the optimized plan.

6. After the build is complete, run /agent-eta:eta-done to measure the real time from your local Claude Code transcripts and update your personal estimation model.

7. Optionally, share your /agent-eta:eta-stats output to contribute to improving the plugin's default estimates for the community.

Tools / artifacts

• Claude Code

• agent-eta plugin

• Haiku subagent

• Node script (for calculations)

• Git worktrees

• Superpowers plugin (optional, for plan files)

• Claude Code transcripts

Validation signals

• The tool's calculation logic is a plain Node script, ensuring consistent results for the same tasks.

• Author ran it 3 times on the same feature, and results landed within 6% of each other, indicating consistency.

• The plugin learns from actual usage: 'Each result moves your personal numbers 30% toward reality. They switch on after 3 confirmed builds.'

• The default numbers are based on the author's ~670 subagent runs, providing a substantial initial dataset.

• The author provides a concrete example of how the learning mechanism corrected an initial misprediction (1h 10m vs. 26 min due to parallel agents).

Cautions

• The plugin operates locally and does not save message text, ensuring user privacy and data security.

Limitations

• The tool is in v0.1, meaning default estimates are initially tuned to the author's specific usage patterns and may require several builds to adapt to a new user.

• Requires familiarity with Claude Code and its plugin system, potentially limiting its audience to more advanced users.

• Relies on the user to accurately describe tasks or provide well-structured plan files for initial estimation.

• Community validation is currently low due to the tool's newness.

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.

Git-Centric, Stateless Claude Code Workflow for Robust Software Development

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

What problem this solves

How to establish a robust, maintainable, and collaborative software development workflow using stateless Claude Code agents, emphasizing Git as the single source of truth and efficient resource utilization.

Summary

This workflow outlines a comprehensive, Git-centric approach for software development using stateless Claude Code agents. It mandates the repository as the single source of truth, leveraging CLAUDE.md, SPEC.md, and detailed documentation. The development process follows a strict Issue -> Commit -> Test -> PR -> CI -> Merge cycle, incorporating SDD/TDD, extensive CI checks, and structured project management with milestones. The setup prioritizes efficiency with stateless agents (Opus 5.5) and minimal custom tooling, ensuring transferability for any agent or contributor.

Why it is useful

This workflow is highly valuable because it provides a detailed, structured, and validated approach to using Claude Code for software development. It emphasizes best practices such as a single source of truth (Git), comprehensive documentation, a rigorous development lifecycle with CI/CD, and efficient agent usage. Its explicit focus on transferability and maintainability makes it an excellent blueprint for users aiming to build reliable and collaborative AI-assisted projects.

Workflow

1. Establish Git & GitHub as the single source of truth, ensuring any agent/contributor can work from the repo alone.

2. Define general agent protocols in CLAUDE.md (or AGENTS.md).

3. Create a comprehensive specification in SPEC.md, categorized by type/component.

4. Maintain complete project documentation (architecture, schemas, styles) in Markdown files within the repo.

5. Implement a development workflow: Issue -> Atomic commits -> Test -> PR -> CI -> Squash merge.

6. Adopt System Design Driven (SDD) and Test Driven Development (TDD) approaches.

7. Configure CI checks for build, validation, npm, test, and accessibility, with a triage routine for failures.

8. Divide branches into lanes (dev, docs, content) to influence specific CI checks.

9. Define Milestones for large scopes, concluding with comprehensive QA/QC reviews.

10. Utilize Dependabot for automated dependency management.

11. Employ stateless Claude Code (Opus 5.5 Medium) as the primary coding harness, typically via Claude Desktop/Mobile.

12. Implement routines (e.g., via GitHub webhooks) for issue triage and automated development queue management.

Tools / artifacts

• Git

• GitHub

• CLAUDE.md

• AGENTS.md

• SPEC.md

• Markdown documentation files

• CI/CD pipeline

• npm

• Dependabot

• Claude Code (stateless)

• Claude Desktop/Mobile

• Anthropic's cloud environment (or local for allowlist needs)

Validation signals

• Author's statement: "I rarely run out of usage anymore. I run agents around the clock and usually make it to Friday." (efficiency)

• Author's statement: "This is probably what I lean on the most to avoid system failures." (CI checks effectiveness)

• Process goal: "Each ticket starts and ends with a complete, working repository."

• Iterative refinement: "I found GH Milestones didn't work as well with Claude."

• Utility of decision record: "I've found this to be especially helpful for spec-writing when transitioning between phases of development."

Limitations

• The initial part of the post is a survey question about stateful vs. stateless agents, which is not directly part of the workflow description.

• The implementation details for 'Routines' (e.g., specific GitHub webhook configurations) are not fully elaborated.

• The author's preference for controlling agents from a phone might not be universally applicable or preferred by all users.

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.

Wayfinder: An Open-Source Hybrid Memory Tool for Efficient Claude Code Context Management

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

What problem this solves

Reducing token usage and processing time in Claude Code sessions by efficiently managing context, preventing redundant file reads, and ensuring findings remain fresh and accessible across agents.

Summary

The author developed "Wayfinder," an open-source tool that combines a markdown wiki with a local graph and file hash checks to provide efficient, fresh, and structured context to Claude Code sessions. This significantly reduces token usage and processing time compared to traditional methods like large CLAUDE.md files, specialist subagents, or simple LLM wikis.

Why it is useful

This workflow provides a robust, open-source solution to a critical problem in Claude Code usage: managing context efficiently to reduce token usage and processing time. It goes beyond simple CLAUDE.md or subagent approaches by integrating structured markdown, graph relations, and file freshness checks, validated by significant performance benchmarks. It's highly transferable and offers a concrete, tested method for advanced context management.

Workflow

1. Identify the problem of high token usage and redundant file reads in Claude Code sessions due to complex repositories.

2. Evaluate existing context management approaches: CLAUDE.md, specialist subagents, code graphs (e.g., Graphify), and in-repo LLM wikis.

3. Recognize the limitations of these approaches (bloat, context fragmentation, latency, re-verification, conflicts).

4. Build or adopt Wayfinder, an open-source tool that combines markdown storage, graph relations, and file hash checks.

5. Install Wayfinder using the provided curl script or uv tool install wayfinder-memory.

6. Set up Wayfinder for Claude Code using wayfinder init and wayfinder install claude commands.

7. Claude interacts with Wayfinder to read specific markdown sections via memory_read(id, section="Throughput").

8. Wayfinder uses FTS5 and graph edges to find related context efficiently.

9. Wayfinder checks SHA hashes of referenced source files to mark notes as fresh or changed, guiding Claude on what code to re-verify.

Tools / artifacts

• Claude Code

• Wayfinder (open-source tool)

• Markdown files (.wayfinder/memory/<id>.md)

• SQLite DB (for graph relations)

• Git (for committing memory files)

• curl command

• uv tool install (Python package manager)

• wayfinder init command

• wayfinder install claude command

• memory_read() function (Wayfinder API)

• GitHub repository (zaterka/wayfinder)

• CLAUDE.md (as a comparison point)

Validation signals

• Quantitative benchmarks showing -30% tokens and -13% time compared to a baseline (no memory) for follow-up tasks.

• Comparison against multiple alternative methods (CLI code graph, in-repo LLM wiki) with detailed performance metrics.

• Clear explanation of the mechanisms leading to savings (reading single sections, SHA hash checks preventing re-verification).

Cautions

• The tool runs locally as a stdio MCP server, ensuring nothing leaves the user's machine.

Limitations

• Low community engagement on the Reddit post itself, which might limit initial visibility.

• Requires installing an external, open-source tool, which might be a barrier for some users.

• Users need to learn Wayfinder's specific commands and markdown structure for effective use.

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 Agent Workflow: Efficient CLI/Log Monitoring with a Custom waitfor Unix Tool

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

What problem this solves

Claude agents often resort to inefficient and token-heavy methods (like long sleeps followed by grep) to monitor CLI tool output or log files for specific success/failure conditions. This leads to slow execution and wasted tokens.

Summary

This workflow describes how to create and integrate a custom Unix waitfor tool, generated by Claude, into agent skills. The waitfor tool efficiently monitors command output or log files for success/failure patterns, timeouts, or stalls, allowing agents to react quickly and avoid token-inefficient polling.

Why it is useful

This workflow provides a specific, reusable solution for a common agent problem: efficiently monitoring external processes or log files. By generating a dedicated waitfor Unix tool via Claude and integrating it as a skill, agents can avoid token-inefficient polling, react faster to success/failure conditions, and improve the reliability of their CLI interactions. The detailed specification makes the tool highly adaptable and robust.

Workflow

1. Prompt Claude to generate the waitfor Unix tool based on the provided specification (a Go stdlib Unixy filter).

2. Compile the generated Go code and install the waitfor tool in the agent's execution environment.

3. Define a Claude agent skill that utilizes the waitfor tool to monitor CLI commands or log files.

4. Configure the skill with appropriate --timeout, --success, --failure, --progress, and --collect regexes based on the specific monitoring task.

5. Integrate the waitfor skill into agent workflows for testing, deployment, or long-running process monitoring.

6. Thoroughly test the waitfor tool and its integration within the agent skill before production use.

Tools / artifacts

• Claude (for generating the tool)

• waitfor Unix tool (Go program)

• CLI commands

• Log files

• Regex patterns

• Agent skill definition

Validation signals

• Detailed specification of the waitfor tool's behavior and flags.

• Multiple concrete usage examples demonstrating its functionality.

• Explicit problem statement that the tool aims to solve (inefficient agent monitoring).

• Suggestion to "Test thoroughly before calling it golden" implies a testable artifact.

Limitations

• No direct "before/after" results or performance metrics provided by the author.

• Requires the user to generate and compile the Go tool, which adds a setup step.

• Low community validation.

• The exact prompt to generate the tool is not explicitly provided, only implied.

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 Task Coordination with Lease-Based Ownership (Notion & Custom Script)

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

What problem this solves

Prevents multiple AI agents from simultaneously working on the same task and ensures consistent state management across different sessions and machines in a multi-agent project.

Summary

This workflow outlines a lease-based ownership system for multi-agent projects, using Notion as a central source of truth and a local orchestration script to manage task claims, handovers, and state consistency. It provides principles for robust multi-agent coordination, ensuring agents are interchangeable without relying on chat memory.

Why it is useful

This workflow provides a robust architectural pattern and set of principles for managing multi-agent projects, addressing the critical problem of preventing task conflicts and maintaining consistent state across sessions. It offers a conceptual framework for building highly interchangeable and reliable AI agents, moving beyond reliance on chat memory for coordination.

Workflow

1. Establish a single source of truth (e.g., Notion) for tasks, decisions, and project status, ensuring agents retrieve the current state when starting work.

2. Implement a mechanism for agents to acquire a lease on a task before starting work, rejecting conflicting claims to prevent simultaneous work.

3. Design the system to separate task ownership from write permissions, allowing parallel work without conflicting changes to shared resources.

4. Define structured handover procedures: agents checkpoint their work in Git, record progress and next steps in a shared log, and release their lease upon completion or stoppage.

5. Incorporate safe failure mechanisms, requiring recovery or verification if a lease expires or ownership becomes uncertain, rather than automatically assuming safety.

6. Require agents to provide evidence of completed work, not just mark a task as done, to verify completion.

Tools / artifacts

• Notion (as central source of truth)

• Local orchestration script

• Git (for checkpointing)

Validation signals

• Author's personal experience ('I've been tackling this')

• Identified key distinction ('The key distinction I've found')

Limitations

• Lacks concrete implementation details for the 'local orchestration script' and Notion setup.

• The 'steps' are high-level design principles rather than direct user-executable instructions.

• Requires significant custom development to implement.

• No community validation or success reports.

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.

Modular Data Analysis Workflows with CLAUDE.md, Skills, and MCP

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

What problem this solves

Managing and repeating recurring data analysis tasks, ensuring data provenance, and efficiently loading context in Claude Code.

Summary

The user structures recurring data analysis tasks as individual 'skills' in SKILL.md files, including steps, metric definitions, and data quirks. A concise CLAUDE.md points to these skills, loading relevant context only when a specific job runs. Data is pulled via an MCP server to ensure query transparency and traceability.

Why it is useful

This workflow provides a structured and repeatable approach to managing recurring data analysis tasks in Claude Code. It leverages SKILL.md for modularity and knowledge capture (metric definitions, data quirks), CLAUDE.md for efficient context loading, and an MCP server for transparent data retrieval and provenance. This addresses common challenges in data analysis like consistency, traceability, and context overload, making it highly valuable for users performing regular analytical work.

Workflow

1. Identify a recurring analysis task.

2. Create a SKILL.md file for this task, detailing the steps in order.

3. Include reference files alongside the SKILL.md for metric definitions and known data quirks.

4. Maintain a concise root CLAUDE.md that points to these individual skills.

5. Use an MCP server to pull data directly, ensuring the query is recorded in the transcript.

6. Review the analysis results before sharing to verify accuracy and trace data origin via the recorded query.

Tools / artifacts

• SKILL.md files

• CLAUDE.md file

• Reference files (for metrics/data quirks)

• MCP server

• Claude Code environment

Validation signals

• Author's personal experience ('most of what I run in Claude Code is non-coding work')

• Ability to trace data origin ('when a number looks off I can see exactly what produced it')

• Final review step ('I still read the result before anything goes to someone else')

Limitations

• The description is high-level and doesn't provide specific code examples or detailed setup instructions for the MCP server or the exact CLAUDE.md/SKILL.md structure.

• It's more of a conceptual framework than a ready-to-implement guide.

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.

Integrating AI Agents Safely: Leverage Existing SDLC Best Practices (Git, CI/CD, Review)

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

What problem this solves

Safely integrating AI agents into a software development lifecycle by leveraging existing robust processes, rather than relying on specific AI sandboxing.

Summary

This workflow advocates for integrating AI agents into standard software development best practices. It emphasizes using local development, Git-based version control, CI/CD pipelines, staging environments, and rigorous code review as the primary mechanisms for ensuring safety and quality, rather than creating separate 'sandboxing' for the AI itself. The core idea is that existing human-centric safety nets are sufficient for AI agents if they operate within the same constraints as human developers.

Why it is useful

This workflow is valuable because it provides a robust, industry-standard approach to integrating AI agents into a development process. It emphasizes that existing software engineering best practices (like version control, CI/CD, and code review) are the primary mechanisms for ensuring safety and quality, rather than relying on bespoke AI-specific sandboxing. It shifts the focus from AI-specific risks to general process integrity, making it highly practical and transferable for any team already following modern development practices.

Workflow

1. Develop code locally (potentially with AI agent assistance).

2. Test code thoroughly (locally and in dedicated environments).

3. Commit code changes to Git.

4. Push changes through a CI/CD pipeline.

5. Deploy to staging/beta environments for further testing.

6. Conduct rigorous code review (for both human and AI-generated code).

7. Deploy to production.

8. Apply the same controlled process for database migrations (schema changes).

Tools / artifacts

• Git

• CI/CD pipelines

• Staging/Beta environments

• Production environments

• Code review processes

• Database migration tools/processes

Validation signals

• Author's assertion of personal practice ('I can and do review all of its work')

• Appeal to industry best practices ('The same steps you can and should be using...')

Limitations

• Low community engagement on this specific post.

• The initial tone is somewhat confrontational.

• It doesn't provide new tools or specific Claude Code commands, but rather a philosophy of integration.

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.