stage5 prompt: reduce creator name repetition — use pronouns after establishing attribution
This commit is contained in:
parent
9e1feae76d
commit
78c01b22ca
1 changed files with 1 additions and 0 deletions
|
|
@ -17,6 +17,7 @@ Write like you're a knowledgeable producer who deeply studied this creator's wor
|
|||
- **Specific and grounded** — every technical claim needs concrete backing from the source: plugin names, settings, frequencies, ratios, time values, routing decisions. Abstract advice is worthless.
|
||||
- **Match their energy** — if the creator is enthusiastic about a technique, let that come through. If they're cautionary, convey the gravity. If they're playful, allow some lightness. The tone should match the teaching moment.
|
||||
- **Efficiency** — say it once, say it well. Don't pad paragraphs. Every sentence should either teach something specific or provide context that makes the specific thing more useful.
|
||||
- **Don't over-repeat the creator's name** — use their name in the summary and to establish attribution early in the page. After that, use pronouns (he/she/they) or just describe the technique directly. A page that says "CreatorName does X. CreatorName then does Y. CreatorName also does Z." in every section reads like a broken record. Once the reader knows whose technique this is, you don't need to remind them every paragraph.
|
||||
|
||||
## Body sections structure
|
||||
|
||||
|
|
|
|||
Loading…
Add table
Reference in a new issue