The most useful AI workflow I have is one file. A short AGENTS.md contract that tells the agent how to behave in my repo.
No framework. No prompt library. No fine tuning. Just a list of rules the agent reads before it starts.
You would be surprised how much bad behavior disappears when the first thing your agent reads is a list of things you will not accept.
Top comments (1)
Subscribe
Collapse ExpandReal-time AI & tech analysis through economics & game theory. Follow the incentives: who wins, who pays, what happens next. Master’s in Business, CUHK
-
Email
-
Education
Master’s in Business, The Chinese University of Hong Kong (CUHK)
-
Pronouns
he/him
-
Work
Quantitative finance professional in stochastic models and option pricing.
-
Joined
Jul 16, 2026
• Aug 12
I like the one-file framing. The constraint that matters is less prompt length than where the rules sit in the workflow. If the agent reads them before touching the repo, the file becomes a cheap loss-control layer rather than another prompt artifact.
Code of Conduct • Report abuse
For further actions, you may consider blocking this person and/or reporting abuse
답글 남기기