Retro to Rules: Learn from Repeated Agent Corrections
by Auny H
Turn recurring feedback into evidenced proposals, then save the changes you approve.
by Auny H
Turn recurring feedback into evidenced proposals, then save the changes you approve.
by Auny H
Give your agent a clear method for tool-calculated numbers, exact results, and explained rounding.
by Auny H
Keep full command logs retrievable while showing a small head or tail view and preserving the command's exit status.
by Auny H
Give your agent a clear path from documentation indexes to readable source pages, with a note showing how each page was fetched.
by Auny H
Turn a complex request into checkable units, dependency waves, and a plan your agent can review.
by Auny H
Turn an X Article, Markdown file, Google Doc export, web page or pasted text into the site post, newsletter draft, cross-posts and social teasers you need. Use your tools or take ready-to-paste files.
by Auny H
Turn findings into startable, deduplicated issues and verify the evidence before closing them.
by Auny H
Map a rename across code, docs, configuration, tests, and project notes, then check the old name in the same scope.
by Auny H
Help your agent preserve the difference between a passing idea, a preference, a working habit, and a firm rule.
by Auny H
Turn completed client work into a reusable method and blank template, with an explicit scan for identifying details.
by Auny H
Give agents a clear way to verify missing results, pending jobs, and skipped checks before reporting a conclusion.
by Auny H
One main agent routes work across Claude Code, Codex, Grok and other CLIs you pay for, with scoped briefs, a bundled runner that checks every answer, and independent review.