Ad-hoc AI prompting creates inconsistency across engineering teams — different engineers get different results, and hard-won prompting knowledge disappears when people leave. The solution is reusable workflow templates that standardize how teams interact with AI coding agents. A good template includes a clear task definition, context inputs, ordered spec steps, guardrails, and validation criteria. Three ready-to-use templates are provided: migrating React class components to hooks, adding test coverage to untested modules, and generating structured PR descriptions. The post also introduces Aviator Runbooks as a platform for storing and iterating on these templates, with context files that improve over time as teams use them.

8m read timeFrom aviator.co
Post cover image
Table of contents
Why Ad-Hoc Prompting Is Not So GreatThe Structure of an AI Workflow Template3 Templates for Common Engineering TasksTemplates Get Smarter Over TimeBuilding Your Own TemplateNext StepsFrequently Asked Questions

Sort: