Skip to content

Latest commit

 

History

5 Commits

Folders and files

NameName
Last commit message
Last commit date
 
 
 
 

Repository files navigation

Gauntlet Prompts

Versioned prompts for running a Gauntlet Loop inside an agentic harness (Claude Code, Cursor, Codex, and similar).

This repo is a living collection: base prompts, stronger variants, and task-specific adaptations. Use it to track what worked, what failed, and how the wording evolved.


Credit

The Gauntlet Loop concept and method come from Matt Shumer (@mattshumer_).

  • Original write-up: How to Run a Gauntlet Loop
  • Original demo context: Claude-built game from a single long-running agent prompt ("Claude of Duty")

Core idea (paraphrased from Shumer):

The agent breaks the goal into parts, gives each part a specialist builder and a ruthless blind critic sub-agent, with a mandate to only pass if the artifact is better than a real-world equivalent. The human is the brake.

This repository does not claim ownership of that method. It only stores prompt text and variants derived for repeated use.


What a Gauntlet needs

These prompts are meant for agentic environments, not plain chat:

  • Claude Code
  • Cursor (Agent mode)
  • Codex / similar harnesses that can spawn sub-agents, edit files, and run for a long time

In normal chat, you only get a simulation of the loop. In a real harness, the loop can keep going until you stop it.


Prompt index

File Purpose
prompts/00-classic-shape.md Minimal classic shape closest to Shumer’s original style
prompts/01-strong-generic.md Strong general-purpose Gauntlet (high bar, aggressive wording)
prompts/02-research-system.md Tuned for a production multi-agent research system

How to use

  1. Open your project in Claude Code or Cursor Agent mode.
  2. Paste the chosen prompt from prompts/.
  3. Let it run. Watch any live progress file it creates.
  4. You decide when to stop.

Optional: after session limits or kills, keep a STEERING.md in the target project with concurrency caps (e.g. ≤3 agents) so the next session resumes cleanly.


Versioning convention

  • Bump filenames or add prompts/vN-... when the wording changes in a meaningful way.
  • Note the date and what changed in the commit message.
  • Prefer stricter bars over softer ones; do not weaken a bar just to make a run “pass.”

License

Prompt text in this repo is provided for practical reuse. Credit Matt Shumer for the Gauntlet Loop method when you write about or share derived prompts.

About

Versioned Gauntlet Loop prompts for agentic harnesses (Claude Code, Cursor, etc.). Inspired by Matt Shumer's Gauntlet Loop.

Resources

Stars

0 stars

Watchers

0 watching

Forks

Releases

Packages

Used by

Contributors