Prompting.

Your Prompting reading path

A prompt should name the reader task, trusted sources, allowed changes, and expected output. The articles here connect a well-written build brief to permission boundaries and repeatable evaluation. Pair the guidance with a downloadable template, then adapt it to your actual repository rather than treating it as a universal command.

Read the relevant guide below, then apply one bounded change in your own project. Keep the source, expected result, and verification step together. A small task that you can inspect is a more useful starting point than a broad instruction with no stopping rule.