1. Project
One project per area of work (a client, a product, a recurring job).
Lesson 12
Put it all together: a setup where good output is the default, not luck.
One project per area of work (a client, a product, a recurring job).
Standing role, audience, voice and rules in the project instructions. Keep them short and specific.
The reference material Claude should always draw on: style guide, product facts, best past examples. Keep them current.
Saved prompt templates for your recurring tasks, built on the Role + Task + Context + Format formula. Fill in the blanks instead of starting cold.
Define exactly what you want back (sections, length, tables, file type) so outputs are consistent and easy to review.
Check the output, tell Claude specifically what to change, and fold the lessons back into the instructions so the next run is better. That loop is what makes it a system.
Help me set up a project for [area of work]. Ask me 8 questions, then write: (1) project instructions under 200 words, (2) a list of files I should add, (3) two reusable prompt templates.