Mark mvandermeulen

5 Must-Know Error Handling Techniques for Production n8n Workflows

TL;DR This video outlines five essential error handling techniques for building robust, production-ready n8n workflows. Production readiness implies workflows that notify errors, log failures, implement retry/fallback logic, and fail safely without unintended consequences. Failures are inevitable, necessitating proactive planning and the use of "guardrails" built by identifying error patterns through logging. The techniques covered include using dedicated error workflows for centralized notification and logging, configuring nodes to retry on temporary failures, setting up fallback LLMs for AI-driven processes, enabling nodes to continue processing even if individual items error (preventing full workflow stoppage), and implementing polling for asynchronous operations to ensure completion before proceeding. Ultimately, understanding error patterns allows for the creation of preventative "guardrails" to enhance workflow predictability and

SPARC Framework Prompt Template

Introduction

You are an AI language model assisting in the development of a project using the SPARC framework, which consists of the following steps:

Specification
Pseudocode
Architecture
Refinement

Claude-SPARC Automated Development System For Claude Code

This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.

Overview

The SPARC Automated Development System (claude-sparc.sh) is a comprehensive, agentic workflow for automated software development using the SPARC methodology (Specification, Pseudocode, Architecture, Refinement, Completion). This system leverages Claude Code's built-in tools for parallel task orchestration, comprehensive research, and Test-Driven Development.

Features

CLAUDE.md - Universal Development Principles

This document contains universal development principles and practices for AI assistants working on any project. These principles are derived from battle-tested practices and represent a philosophy of clear, honest, and systematic development.

Required Tools and Research Methods

1. Mandatory MCP Tool Usage

BEFORE ANY ACTION, you MUST use these tools. Tool names use double underscores between segments.

Claude Code Hooks for working with `uv`

by Glenn Matlin / glennmatlin on all socials

Installation

Download and copy all files in this gist to ~/.claude/
Move the .py files to ~/.claude/hooks
Restart Claude Code.

System Prompt: Architectural Principles to Code By

Use rg tool to search for files efficiently

Core Principles

Clean, Simple, Maintainable Code
- Favor readability over cleverness
- Prioritize simplicity in design

Write code that future developers can easily understand

Claude Code + Serena MCP Auto-Wrapper

Zero-configuration automatic Serena MCP server management for Claude Code

Transparently starts exactly one Serena instance per project with unique ports. No per-project setup required!

✨ Features

Zero Configuration: Just run claude - Serena starts automatically
Per-Project Isolation: Each project gets its own Serena instance on unique ports (9000+)

	#!/usr/bin/env swift
	// Required parameters:
	// @raycast.schemaVersion 1
	// @raycast.title Copy UUID
	// @raycast.mode silent
	// @raycast.packageName Developer Tools

	// Optional parameters:
	// @raycast.icon ./copy-uuid.png
	// @raycast.author Rix1

	#!/usr/bin/env zsh
	# Multi-project worktree manager with Claude support
	#
	# ASSUMPTIONS & SETUP:
	# - Your git projects live in: ~/projects/
	# - Worktrees will be created in: ~/projects/worktrees/<project>/<branch>
	# - New branches will be named: <your-username>/<feature-name>
	#
	# DIRECTORY STRUCTURE EXAMPLE:
	# ~/projects/

	#!/usr/bin/env bash

	set -euo pipefail

	issue=$1

	~/.claude/local/claude \
	"Start working on issue #$issue
	- Keep an open mind. Feel free to reconsider the proposed approach
	- Use context7 for updated docs