Examples
AI loop examples
The best AI loop examples are repetitive work patterns with clear evidence and a stop condition: code repair, source QA, browser testing, support follow-up, and pre-publish checks.
Current library snapshot
68total loop patterns
10categories
21engineering loops
10operating domains
All examples
| Loop | Category | Difficulty | Cadence | Verification |
|---|---|---|---|---|
| Longform to Asset Pack | Content | Intermediate | After publishing or recording a substantial essay, talk, podcast, demo, or research note | Each drafted asset traces to the source, preserves the original claim, strips private details, and stays unpublished until approved. |
| One Post a Week Experiment | Content | Beginner | Weekly for six weeks | Winner is supported by comparable replies, saves, and questions, not just likes. |
| Pre-Publish Source Check | Content | Intermediate | Before publishing factual work | Every checkable claim is supported by a current source or visibly flagged for an editor. |
| Recurring Question to FAQ | Content | Beginner | Weekly, or whenever the same question appears three times across email, chat, calls, comments, or onboarding | The loop produces a source-backed answer, suggested placement, support macro, and measurement hook; nothing is published, sent, or promised externally without approval. |
| Release Notes Truth Sweep | Content | Intermediate | Before publishing release notes or changelog updates | Every public note maps to shipped user-visible behavior, and unverifiable or sensitive claims are cut, narrowed, or queued for approval. |
| Social Source to Insight | Content | Intermediate | After saving a high-signal source | Source captured, takeaways extracted, draft angles written, and no public post is published without approval. |
| Accessibility Repair | Design | Advanced | Before launch or when audits fail | No confirmed accessibility blocker remains in the agreed pages, components, or tasks. |
| Design Token Drift Loop | Design | Intermediate | Weekly scheduled pass on the primary product UI package; also trigger after a design-system release or a large UI feature merge | After each change, (1) token lint or grep count of banned hard-coded color/spacing values in the scoped paths drops or stays flat with zero new hits, (2) component story/example pages render without console token errors, and (3) before/after screenshots for the same viewport show the intended visual with no unintended layout shift. |
| Error Message Rewrite | Design | Intermediate | When users hit confusing errors | Every in-scope user-visible error is accounted for, rewritten or blocked, and verified in a reachable state. |
| Visual Feedback Repair | Design | Beginner | After AI-generated UI changes or visual bug reports | Before/after screenshots, console state, and responsive checks show the visual issue is fixed without breaking adjacent states. |
| API Contract Drift | Engineering | Intermediate | After API changes or SDK releases | Server behavior, client types, examples, and docs agree on request/response contracts. |
| Acceptance Scenario Lockstep | Engineering | Intermediate | Before and during ambiguous feature work | The same scenarios written before implementation pass after the change, and any scope expansion is explicitly approved. |
| Agent Instructions After-Action | Engineering | Beginner | After a successful or painful agent coding session | Repo instructions contain only reusable, source-grounded lessons and the next similar task can start without rediscovering the same trap. |
| Architecture Rubric Refactor | Engineering | Advanced | When architecture work has a defined scope | Scoped module meets the written rubric, tests pass, and unresolved objections are explicit. |
| Behavior Ladder TDD | Engineering | Intermediate | When implementing logic-heavy features | Each behavior test fails before implementation, passes after the smallest change, and remains green through final refactor. |
| Bug Report to Repro Kit | Engineering | Intermediate | Whenever a customer, teammate, or monitor surfaces a bug that is too vague to fix safely | The kit contains a minimal repro path, environment notes, expected versus actual behavior, captured evidence, and either a failing test/script or a clearly marked blocker; no customer reply, public issue, or production change is sent without approval. |
| CI Optimization | Engineering | Advanced | Monthly or when CI is painful | CI p50/p95 improves against the same workflow without weakening tests or hiding failures. |
| Claude Code Repo Readiness | Engineering | Beginner | Before major agent work | Repo has agent instructions, documented commands, architecture notes, risk areas, and a docs/loops scaffold. |
| Cold Load Trim | Engineering | Advanced | When first visit feels heavy | Initial screen downloads fewer bytes while screenshots and behavior remain unchanged. |
| Completion Promise Loop | Engineering | Intermediate | For scoped implementation tasks where half-finished output is the main risk | Every acceptance criterion is checked with tests, browser evidence, logs, screenshots, or a clear blocker report before the agent stops. |
| Feature Flag Retirement Sweep | Engineering | Intermediate | Monthly or after a rollout stabilizes | Each reviewed flag has an owner, purpose, current state, and retirement decision; removed flags pass tests and require approval before production config changes. |
| Fresh Clone Onboarding | Engineering | Intermediate | Before onboarding | A clean machine reaches the documented ready state using only the README. |
| Parallel Agent Worktree Sweep | Engineering | Advanced | When several independent repo improvements can run at once | Each agent branch has isolated scope, passing checks, a summary, and no conflicting files before integration review. |
| Project Docs Freshness | Engineering | Beginner | Nightly or after meaningful code changes | Changed behavior, APIs, CLI commands, config, and workflows are reflected in docs. Docs checks pass. |
| Reference Oracle Implementation | Engineering | Advanced | Before implementing tricky behavior with an external source of truth | Generated outputs match the reference oracle across the agreed fixture set, with tolerances documented for legitimate differences. |
| Schema Migration Dry Run | Engineering | Advanced | Before production database migrations or bulk data changes | Migration runs cleanly on a recent snapshot or staging clone, row counts and sample records match expectations, rollback is documented, and production execution remains approval-gated. |
| Spec to Task Shards | Engineering | Intermediate | Before multi-file feature work or migrations | A written spec, non-goals, acceptance checks, and ordered task shards exist before implementation begins. |
| Test Flake Stabilizer | Engineering | Intermediate | When tests are inconsistent | The repaired test and full suite pass for the required consecutive-run streak. |
| Test and Logging Coverage | Engineering | Intermediate | Weekly or before release | Critical flows have useful tests and structured logs for representative success and failure paths. |
| Trace-First Debugging | Engineering | Intermediate | When an agent is tempted to patch a bug from a hunch | The bug is reproduced, the root cause is evidenced by traces or tests, and the fix includes a regression check. |
| Webhook Replay Harness | Engineering | Intermediate | When webhook integrations fail, drift, or need safer changes | A captured or synthetic payload replays through a non-production handler, expected state changes match assertions, idempotency is proven, and live provider/customer side effects remain approval-gated. |
| Adversarial PR Review | Evaluation | Advanced | For meaningful PRs | An independent critic approves the unchanged version or only accepted findings remain. |
| Agent Merge Queue Review | Evaluation | Advanced | After multiple agent-generated PRs or branches accumulate | Only branches with passing checks, clear intent, non-conflicting scope, and human-readable evidence are merged or promoted. |
| Browser Quality Streak | Evaluation | Intermediate | Before release | N realistic scenarios pass consecutively, and earlier failures have regression coverage. |
| Model Output Drift Watch | Evaluation | Intermediate | Weekly or after model, prompt, retrieval, or tool changes | Representative outputs are compared against a baseline, regressions are classified with evidence, and risky changes are rolled back or queued for approval. |
| Prompt Regression Suite | Evaluation | Intermediate | Before changing a production prompt, agent instruction, or model setting | Must-pass cases stay green, known failure cases do not regress, and any changed behavior is documented with an accept or reject decision. |
| RAG Grounding Audit | Evaluation | Intermediate | Before shipping or refreshing a retrieval-backed assistant | Representative answers cite the right source chunks, abstain when retrieval is weak, and expose no private or stale material. |
| Customer Proof Packet | Growth | Intermediate | Before publishing a case study, testimonial, sales claim, or investor/customer proof point | Each public-safe claim maps to approved evidence, private details are redacted, and anything using a name, logo, metric, or quote is queued for explicit approval. |
| Paid Ads Copy Variant Loop | Growth | Intermediate | Every 2–3 days while spend is live; weekly when spend is low | Each active variant has enough spend or impressions for a decision rule, losers are paused, winners keep or increase budget share, and every copy/creative change is logged with the metric that justified it. |
| Product Feedback to Measure Loop | Growth | Advanced | Weekly product tick; bug/uptime work stays in a separate reliability loop | Top pain themes are ranked with evidence, one feature or UX change is prototyped or shipped behind a flag, a pre-chosen KPI (activation, retention, NPS, revenue proxy) is measured after the window, and bug/uptime work was not mixed into this cycle. |
| Promise to Proof | Growth | Intermediate | Before launch or campaign refresh | Every high-risk customer promise is supported, narrowed, or awaiting an explicit decision. |
| SEO Monthly Rank Experiment | Growth | Intermediate | Monthly (or every 2 weeks); not continuous thrash | One reversible change set is applied, Search Console (or equivalent) rank/click metrics for the target queries are recorded before and after the waiting window, the experiment log is updated, and if rank fell the change is queued for undo. |
| SEO/GEO Visibility | Growth | Intermediate | Monthly | Priority pages are indexable, answer-ready, internally linked, and no high-impact benchmark gaps remain. |
| Talk to Five Buyers | Growth | Intermediate | Before major landing-page rewrite | Proposed copy traces to repeated anonymized buyer objections across approved interviews. |
| Memory Bank Continuity | Knowledge | Beginner | At the start and end of multi-session agent work | Project brief, active context, decisions, tech constraints, and progress are current enough for a fresh agent to continue safely. |
| Open Loop and Stale Memory Cleanup | Knowledge | Beginner | Weekly | No current open loop is contradicted by recent daily or project notes. |
| Research to Artifact | Knowledge | Intermediate | Whenever research must support a decision | The artifact meets acceptance criteria, traces important claims to sources, and states uncertainty plainly. |
| Source Library Ingestion QA | Knowledge | Intermediate | After each source capture | Metadata complete, transcript/article state honest, useful takeaways present, and qmd retrieval verified or refreshed. |
| Agent Cost Budget Loop | Operations | Intermediate | Manual trial, then scheduled if it proves useful | Every high-cost run maps to an outcome, cap, and future adjustment. |
| Agent Handoff Continuity | Operations | Intermediate | Before pausing or switching agents | A new agent can state goal, current state, proof, blockers, and next action without reading the whole transcript. |
| Agent Toolchain Health Check | Operations | Beginner | Weekly or before a heavy agent run | Critical tools authenticate, return sane output, and have a known fallback or blocker owner. |
| CRM Hygiene Loop | Operations | Intermediate | Manual trial, then scheduled if it proves useful | No high-value account lacks owner, next action, stage, or stale-date flag. |
| Incident Timeline Reconstruction | Operations | Intermediate | During incidents, after outages, or before writing a postmortem | A timestamped timeline separates facts from guesses, names owners for open questions, and gates any customer-facing update for approval. |
| Living Story | Operations | Intermediate | Weekly or per project window | Every prior thread is carried forward, closed with evidence, or flagged stale/needs-review. |
| Notebook to Repeatable Pipeline | Operations | Intermediate | When an ad hoc analysis, spreadsheet, or notebook needs to run again | A clean run reproduces the expected output from named inputs, assumptions and owners are documented, and any scheduled sends or external updates are approval-gated. |
| Production Error Sweep | Operations | Advanced | Daily or after incident | Actionable errors are fixed with reproduction or tests, or explicitly classified as noise. |
| Side-Effect Dry Run Gate | Operations | Beginner | Before giving an agent tools that can change external state | Every side-effecting action has an exact preview, risk level, required approval, and rollback or fallback; no live action runs until authorized. |
| Support Macro Learning Loop | Operations | Intermediate | Manual trial, then scheduled if it proves useful | Top repeated issue has a macro/doc/product action with evidence. |
| Calendar Promise Proof | Personal Ops | Beginner | Daily or before week planning | Every calendar-derived promise has an owner, due date, evidence, or explicit drop decision. |
| Inbox Decision Triage | Personal Ops | Beginner | Daily or before deep work | Every sampled message is archived, labeled, delegated, converted to a task, or left with a drafted reply; no external message is sent without approval. |
| Meeting Transcript Action Miner | Personal Ops | Beginner | After recorded meetings or dense calls | Decisions, commitments, owners, due dates, and unresolved questions are captured with source evidence; no external follow-up is sent without approval. |
| Stakeholder Briefing Packet | Personal Ops | Beginner | Before high-leverage meetings, calls, or relationship-sensitive updates | The packet states objective, context, open asks, risks, likely questions, and recommended stance with source links; no message, agenda, or document is shared externally without approval. |
| Support Refund Follow-Up | Personal Ops | Beginner | Until terminal state | Refund is received, or no approved next step remains and a blocker is named. |
| Dependency CVE Burndown | Security | Advanced | After security scan | No exploitable high or critical CVE remains without an explicit risk decision. |
| Permission Scope Minimizer | Security | Intermediate | Before launching an integration, agent tool, or automation with account access | The workflow succeeds with the narrowest tested permissions, unused scopes are documented for removal, and any live credential changes remain approval-gated. |
| Sandboxed YOLO Probe | Security | Advanced | Before allowing autonomous shell-heavy agent runs | The agent can run needed commands inside the sandbox, cannot reach forbidden files/secrets, and produces a replayable diff or report before host-side changes. |
| Vendor Security Packet Builder | Security | Intermediate | Before answering vendor security questionnaires or procurement due diligence | Every answer maps to an approved source, uncertain claims are queued for review, and nothing is sent externally without approval. |
| Loop Hiring Manager | Strategy | Intermediate | When a project accumulates recurring chores | At most three candidates fill proven recurring gaps, with one recommended safe manual trial. |
How to choose
| If the work is… | Start with… |
|---|---|
| Code or repo maintenance | Coding agent loops |
| Fact checking or research | Pre-Publish Source Check or Research to Artifact |
| Quality assurance | Verification loops |
| Recurring personal follow-up | Calendar Promise Proof |