Skip to content

Docs: Writing rules (no em-dash, uv/ppp/tcl, tone) #137

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
b-re-w merged 1 commit into from
Oct 3, 2026
Merged

Docs: Writing rules (no em-dash, uv/ppp/tcl, tone) #137

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 9 additions & 0 deletions AGENTS.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -143,6 +143,15 @@ Report by category, and never put them in one column:
A rising test count is not progress when the tests assert an absence. Before writing "nothing left
to implement", say what you counted against.

### Writing docs and code text

- **No em-dash.** Do not write the em-dash character (U+2014) anywhere: docs, guides, README,
comments, docstrings, strings, commit messages, PR and issue text. Use a comma, colon,
parentheses, or two sentences.
- **Install and run examples use `uv`, `ppp` (pypackpack) or `tcl` (toolchain-lite).** Never write
a `pip install` example in a guide, README or doc.
- **Tone:** the pythonx-compose guide is the reference for how docs read; align with it.

## 10. Agents

- A headless agent (`claude -p`, `agy -p`) has **no next turn**. Tell it to run long commands in the
Expand Down
Loading