Thomas Hartmann thomashartm

name	description
orchestrating-swarms	Master multi-agent orchestration using Claude Code's TeammateTool and Task system. Use when coordinating multiple agents, running parallel code reviews, creating pipeline workflows with dependencies, building self-organizing task queues, or any task benefiting from divide-and-conquer patterns.

Claude Code Swarm Orchestration

Master multi-agent orchestration using Claude Code's TeammateTool and Task system.

Superconductor App Development Guide for AI SWE Agents

This is a Rails 8 app, using Tailwind for CSS (with DaisyUI), Slim for HTML templates, Phlex for view components, Stimulus for JavaScript, and Turbo for streaming updates. It runs using docker-compose, which we manage with dip.

Read more about the purpose and business logic of the app in @README.md

Initial Setup (already done)

Before you started, the following two commands were already run for you: bin/setup set everything up, and bin/dev started the web app.

🧠 How to Save Context Tokens When Using Claude Code

This is a personal reference workflow for minimizing token usage while maintaining project continuity across Claude Code (Sonnet 4 with file access).

✅ Setup: Populate `CLAUDE.md`

Claude loads CLAUDE.md automatically at session start.

This is how I quickly got an Apache Zepplin notebook running against the AWS Glue Dev endpoint. None of the guides out there seemed concise, and I found some custom Docker containers doing what you can do easily. This gives you the power - it sets up port forwarding & runs the official Docker image.

Create your Glue Dev endpoint (this involves creating a keypair, I just used ssh-keygen)
Once READY, select it and copy the "SSH tunnel to remote interpreter"

eg: ssh -i <private-key.pem> -vnNT -L :9007:169.254.76.1:9007 glue@..compute.amazonaws.com

Connect to the endpoint in a terminal session, modifying the above to match: ssh -i ~/.ssh/glue-dev -vnNT -L :9007:*127.0.0.1*:9007 glue@<ec2-endpoint>.<region>.compute.amazonaws.com
Run the Apache Zepplin Docker container `docker run -p 8080:8080 --rm -v $PWD/logs:/logs -v $PWD/notebook:/notebook -e ZEPPELIN_LOG_DIR='/l

Story: Writing Scripts with Go

This is a story about how I tried to use Go for scripting. In this story, I’ll discuss the need for a Go script, how we would expect it to behave and the possible implementations; During the discussion I’ll deep dive to scripts, shells, and shebangs. Finally, we’ll discuss solutions that will make Go scripts work.

Why Go is good for scripting?

While python and bash are popular scripting languages, C, C++ and Java are not used for scripts at all, and some languages are somewhere in between.

Code is clean if it can be understood easily – by everyone on the team. Clean code can be read and enhanced by a developer other than its original author. With understandability comes readability, changeability, extensibility and maintainability.

General rules

Follow standard conventions.
Keep it simple stupid. Simpler is always better. Reduce complexity as much as possible.
Boy scout rule. Leave the campground cleaner than you found it.
Always find root cause. Always look for the root cause of a problem.

Design rules

Docker - How to cleanup (unused) resources

Once in a while, you may need to cleanup resources (containers, volumes, images, networks) ...

delete volumes

// see: https://github.com/chadoe/docker-cleanup-volumes

$ docker volume rm $(docker volume ls -qf dangling=true)

$ docker volume ls -qf dangling=true | xargs -r docker volume rm

	package com.nateyolles.aem.osgiannotationdemo.core.services.impl;

	import org.apache.commons.lang3.StringUtils;
	import org.osgi.service.metatype.annotations.AttributeDefinition;
	import org.osgi.service.metatype.annotations.AttributeType;
	import org.osgi.service.metatype.annotations.ObjectClassDefinition;
	import org.osgi.service.metatype.annotations.Option;

	@ObjectClassDefinition(name = "Annotation Demo Service - OSGi")
	public @interface Configuration {

	// applications/kinesis_streamer/lib/handler.js

	import AWS from 'aws-sdk';
	const kinesis = new AWS.Kinesis();

	export function receiveEvent(event, context, callback) {
	console.log('demoHandler');
	console.log(`Event: ${JSON.stringify(event, null, 2)}`);
	console.log(`Context: ${JSON.stringify(context, null, 2)}`);
	const base64Data = event.Records[0].kinesis.data;

	console.log(location.hash);
	var tabValue = document.URL;
	window.location = tabValue.substring(0, tabValue.lastIndexOf("#"));
	console.log(location.hash);
	window.location.hash = `#<noscript><script>confirm(1)&k7="><svg/t='&k8='onload='/&k9=/+eval(t)'`
	location.reload();
	console.log(location.hash);