Skills
Split high-value generation into separate generate / critique / synthesize model calls
Rather than asking one model to draft, self-check, and finalize in a single pass, route the work through distinct calls in defined roles — one generates, a second critiques against explicit criteria, a third synthesizes the revision. It costs more and adds architectural complexity, but on high-stakes outputs the quality lift is substantial because each role gets a clean context and a single objective instead of competing instructions. The same structure also separates static context (who you are, the project) from dynamic context (this specific task) so heavy docs can be cached and pinned.
Source
↳ Follow the thread