Skip to content

Add writing-style ground rules to agent instructions - #185

Merged
HamptonMakes merged 2 commits into
mainfrom
claude/style-instructions
Aug 19, 2026
Merged

Add writing-style ground rules to agent instructions#185
HamptonMakes merged 2 commits into
mainfrom
claude/style-instructions

Conversation

@HamptonMakes

Copy link
Copy Markdown
Collaborator

Live agent output shows two recurring problems the instructions never address:

  1. Metadata written into document bodies — date/"last updated" lines, invented status fields (CoPlan deliberately has no document status), author lines, version tables. The platform records all of this (version history, attribution, visibility/tags), so it's stale the moment it's written.
  2. Promotional prose in working documents — especially design docs padded with impressive-sounding language instead of plain statements.

New ## Writing Style section in /agent-instructions:

  • "The platform already records it" — bans body metadata, with one carve-out: dates that anchor facts ("verified at commit abc123") belong in content.
  • Plain-language rules (Simplified-Technical-English-inspired): short sentences, active voice, plain verbs, named banned filler words, "write like a runbook, not a keynote," length-is-a-cost.
  • Type-level override: a plan type's description or template may override any of these — so a persuasive type (marketing pitch) composes cleanly with the defaults.

🤖 Generated with Claude Code

Two rule sets observed missing from live agent output: agents write
document metadata into plan bodies (date lines, invented status fields,
author lines — all things the platform records), and they pad working
documents with promotional prose. New "Writing Style" section bans
body metadata (with a facts-anchor exception), sets Simplified-
Technical-English-style plain-language rules with named banned words,
and lets a plan type's description or template override the defaults
so persuasive types (e.g. a pitch) stay possible.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

- Short sentences. One idea per sentence. Active voice, present tense.
- Plain verbs: "use", not "leverage"; "check", not "perform validation of".
- No metaphors, no marketing adjectives, no drama. Words that signal padding — "robust", "seamless", "comprehensive", "cutting-edge", "elegant", "crucially", "delve" — are banned unless you are quoting someone.

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

and add "honest", "actually"

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🤖 Added both in b0547c2.

Review feedback from Hampton on the padding-words list.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
@HamptonMakes
HamptonMakes merged commit 21bf488 into main Aug 19, 2026
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant