26 prompts with receipts
-
Fresh
sha 71a49ff7Explore, don’t decide: widen the field before the model converges
A role-boundary prompt you paste at the moment before you ask AI to recommend – it separates supported facts from inferences, returns three materially different framings (each with its key assumption and failure mode), runs a divergence check against fake variety, and refuses to pick a path, so the first plausible answer can't quietly anchor the decision.
-
Fresh
sha 3fae3fb2Sign-off gate: prove the claim or label it NOT RUN
Before an agent says "tests pass", "done", or "safe to deploy", forces it to grade the claim by how it was actually obtained and lead with a one-line proof tied to visible evidence (command + exit + output) – or downgrade to NOT RUN – so it can't claim a check it never made.
-
Fresh
sha a2230c76Audit your governance, then level it up (enforced, not theatre)
A read-only audit of a project's rules, configs, gates, and agent contracts that runs the gates rather than reading them, grades each as enforced-or-aspirational, fail-closed-or-open, and load-bearing-or-theatre, hunts the high-leverage governance most projects lack, and returns a ranked, reuse-first plan to make it hold.
-
Fresh
sha fb142765Brief a sub-agent like a colleague, not a warrant
A fixed skeleton for the prompt you hand DOWN to a sub-agent – goal and trust instead of a recipe and a wall of prohibitions, with a strict-mode gate up front, a bounded license to adapt, and a recover-before-you-escalate failure rule.
-
Fresh
sha ee4afbb0Abstain when the data is stale: suppress, do not guess
Thread one can_emit(state) check through every interpretive output site, run-level AND per-line, so a recommendation, risk read, or "act now" is suppressed – replaced by a single honest reason – whenever the inputs behind it are too stale, too sparse, missing, or failed this run.
-
Fresh
sha 78cdcaf4Map an unfamiliar repo from evidence, not guesses
Build a navigational map of a repo you have never seen – read-only, governance docs first, real entry points from the build files, layers and dependency direction verified by import edges, ONE real journey traced end-to-end with a quoted file:line snippet at every hop, then a "to change X, start at Y" index and a danger-zone list with a fan-in threshold. Every claim is phrased no stronger than the line you quoted proves; anything not directly read is marked INFERENCE, never asserted as fact.
-
Fresh
sha 3d7b5900Plan, then apply – a two-phase gate for irreversible actions
Splits any irreversible action into a read-only PLAN phase that must show the context-pinned command, blast radius, real rollback, and a verified pre-existing backup the action cannot reach – then a separately-approved APPLY phase, gated on a literal approval token, that re-checks the facts and runs only what was shown.
-
Fresh
sha f4d8caf3Measure first – find the real bottleneck, keep only proven wins
A performance contract that bans guessing. Declare the metric and a guardrail, profile the real path, change one thing at the hotspot, re-measure against pasted command output, and keep the change only if the number actually moved and nothing else regressed.
-
Fresh
sha 756ca8a5Refactor under a net – pin the behaviour, then change it
Before refactoring untested code, write tests that lock in what it ACTUALLY does now (bugs included), prove them green against the unchanged code, then change structure one mechanical move at a time, snapshotting and re-running the pinned suite after each move.
-
Fresh
sha 660c93f9Turn a vague request into a spec, with every assumption tagged
Before any code, the model emits SPEC, PLAN, TASKS, and a GATE, with every decision the request did not specify tagged inline and ranked by what it costs to undo, and every destructive action inventoried and blocked by default – so you correct the expensive guesses and approve the dangerous steps before either is written into code.
-
Fresh
sha deb44f54No fix until the bug reproduces
Forces an agent to stand up a deterministic, captured-failing reproduction before it is allowed to propose, write, or apply any fix – and to stop and report instead of patching when it cannot reproduce.
-
Fresh
sha b2cf3f6aUnattended Autonomous Work Orchestrator (validate-then-implement, fail-closed)
An operator contract for a long, unattended agent session: it asks for every permission up front (then waits), pulls the next task from a plan file (and only hardens existing work when idle, never inventing scope to look busy), and runs a strict per-task loop — pre-flight baseline, reproduce/write a failing check first, implement the smallest fix inside a hard scope cap, verify with pasted command output, hand the diff to a second-model critic, and gate on green-plus-no-unrefuted-objection or else revert. Parallel agents are allowed only for read-only investigation; mutations stay serial. It halts on clear conditions (time/iteration budget, repeated gate failures, out-of-scope or irreversible mutation, broken toolchain) and ends with an evidence-first report of commits, command output, and critic verdicts — so you wake up to proven progress, not a wall of optimistic prose.
-
Fresh
sha cbb5f9c2Two adversarial critics, you stay the judge (dedupe + keep uniques)
Runs two independent critics over a draft, dedupes their agreements as high-signal, keeps each one's unique catches, and refuses to blind-apply anything.
-
Fresh
sha 88e51979Sharp Engineering Writer: 4-Draft Self-Critique That Kills AI-Tells
A writing-operator contract that produces one sharp, human engineering piece on {{topic}} in {{voice}}. It forces four internal drafts with a brutal self-critique between each (cut filler, vague AI wording, overclaims, and the em-dash / rule-of-three / antithesis tics), grounds every load-bearing fact with fresh live research instead of memory, refuses to invent specifics, and reverts to the strongest prior draft if a revision gets worse. Output is the final piece plus a short evidence block: sources checked, claims cut, and tics removed. Built for engineers who want copy that reads human and survives a fact-check, not generic thought-leadership.
-
Fresh
sha 2c975663Session Handoff + Durable Maintenance, Double-Audited
An operator-grade end-of-session prompt: the agent persists session-only state to disk, syncs drifted docs, does scoped git hygiene, runs the project's validation gate as a fail-closed line, then audits the resulting handoff TWICE from a cold-start reader's view and validates every claim against disk/git/command output. Output demands evidence (paths, real command output, git log) and a hard GO/NO-GO instead of a tidy summary. Built so a fresh session with zero memory can take over from the handoff doc alone.
-
Fresh
sha cc036359Audit Guard: Stop Agents From “Fixing” Deliberately Deferred Work
Prepend to any quick-wins / tech-debt audit so the agent reads the plan docs first and treats documented deferrals as out of scope, not bugs.
-
Fresh
sha e779cd80Multi-Lens QA Fan-Out: Blind Self-Review Across 5 Lenses, Then Triage
Reviews your diff five separate times through blind, non-overlapping lenses, then dedupes and ranks so one pass cannot rationalize away another's catch.
-
Fresh
sha 7137afdbModule-by-Module Product/UX Review (Operator Contract)
A systematic, evidence-first product/UX review that walks every module, page, and tab of a product from the real user's perspective against the documented product principles. Obvious fixes get applied inline (with pre-flight, verify-after, and revert-on-red rails); non-obvious changes are queued for the owner with options and a recommendation. A second model runs as a devil's-advocate critic on each batch. Output is receipts (paths, diffs, command output, screenshots/repro), not vibes. Built as an operator contract with a scope cap so it cannot run away.
-
Fresh
sha 2ce8e035Long-Run Context Hygiene Operator
A meta-prompt that keeps a long autonomous agent run from degrading. Reach for this when a run is long enough that the agent's OWN context degrades – not as a general agent contract (use the unattended-autonomous-orchestrator for that), but as a context-hygiene layer you stack on top to fight context rot across many hours or a multi-day session. It forces the agent to compress its own language, write periodic self-TLDR checkpoints with hard evidence, offload bounded sub-tasks to sub-agents so the main context spends its budget on synthesis (not raw reading), and actively detect and counter that rot. It is an operator contract: every checkpoint must cite real artifacts (paths, commits, command output), every mutation is preceded by a pre-flight snapshot and followed by a verify step, and the run fails closed (reverts) on a red verify. Built for unattended multi-step work where the failure mode is silent drift, not a loud crash. It deliberately does NOT carry task-selection or critic machinery – that is the orchestrator's job, and this layer assumes it sits on top of one.
-
Fresh
sha 08880b9cGit Hygiene and Work-Recovery Sweep (Operator Contract)
Find engineering work that exists only in this session, on stale branches, in stashes, or in orphaned worktrees; decide what is worth keeping; integrate it properly (a real cherry-pick or rebase, not a throwaway patch); validate it with the project's own checks; and leave the tree clean. Built as an operator contract: every mutation is preceded by a pre-flight snapshot, followed by a verify step, fails closed on a red check, and is capped so it cannot run away. Output is evidence (paths, SHAs, command output), not a tidy summary.
-
Fresh
sha 3bec85d6Fail-Open vs Fail-Closed Audit for Any Gate or Notification Path
Forces a reviewer to classify every guard as fail-open or fail-closed and name the worst silent-failure case before approving.
-
Fresh
sha 100edf9bClaim-ladder gate: verify against the live source before you encode it
Forces the agent to drop to the running source and cite file:line or a command run before it writes any load-bearing config, guardrail, or claim.
-
Freshexperimental
sha bccaa64aAudit a “byte-exact / copy-paste-safe” claim end to end
A narrow, specialist audit for proving a delivery pipeline does not silently mangle bytes; trace every transform from source to what the user pastes and name the one that corrupts.
-
Fresh
sha cf798743Adversarial Code Reviewer That Refuses to Rubber-Stamp
A code-review prompt that can't approve until it names one concrete issue (or proves the diff clean line-by-line).
-
Fresh
sha dccc8986Adversarial Fix Verification: Prove the Bug Is Gone, Not Just Green CI
Forces an agent to prove a claimed fix actually closes the bug, hunt the regressions it introduced, and probe the changed lines before signing off.
-
Fresh
sha 76711bdbCherry-pick the value from every PR (never merge dirty)
Review each open PR against main, extract its best parts cleanly, capture the lesson from the rest, close the worthless with a real reason – leave the repo cleaner than you found it.
Nothing matches that. Refine the search, or read the index at /prompts.json.
Workflows These prompts chain. Run them in order as a pipeline, not a pile. Vague request to a verified, shipped change Safe refactor and performance loop Destructive-action and safety-gate pipeline Unattended overnight run with an evidence gate Repo cleanup and work recovery A human-sounding piece that survives a fact-check