Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
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
17 changes: 17 additions & 0 deletions users/profiles/claude/base.md
Original file line number Diff line number Diff line change
Expand Up @@ -4,6 +4,23 @@
- No preamble/postamble ("Here's what I'll do...").
- Batch tool calls and run commands in parallel when possible.

## Tone

- Conversational - like talking to a colleague, not writing a textbook
- Direct - get to the point, no throat-clearing
- Honest - don't oversell, say what it does
- No emdashes (use normal -), no marketing buzzwords, no "revolutionary"
- Never use "load-bearing" or "load bearing"

## Formatting

- **Bold**: sparingly, for genuine emphasis only. Never bold every other word.
- **Italics**: avoid entirely - hard to read, rarely adds value. Use `code` for
technical terms and bold for emphasis instead.
- **Emojis**: fine in moderation (section headings). Never in code examples or
as bullet substitutes.
- **Code blocks**: always specify the language.

## Code Comments

Comments are good when they add value. Do NOT add comments on obvious code - that
Expand Down
14 changes: 2 additions & 12 deletions users/profiles/claude/rules/writing.md
Original file line number Diff line number Diff line change
@@ -1,21 +1,11 @@
These rules apply to all written content: READMEs, docs, walkthroughs, blog posts.

## Tone

- Conversational - like talking to a colleague, not writing a textbook
- Direct - get to the point, no throat-clearing
- Honest - don't oversell, say what it does
- No emdashes (use normal -), no marketing buzzwords, no "revolutionary"
General tone and formatting rules live in `base.md` and apply universally; this
file covers prose-specific concerns.

## Formatting

- **Bold**: sparingly, for genuine emphasis only. Never bold every other word.
- **Italics**: avoid entirely - hard to read, rarely adds value. Use `code` for
technical terms and bold for emphasis instead.
- **Emojis**: fine in moderation (section headings). Never in code examples or
as bullet substitutes.
- **Line length**: 80-100 chars (except URLs and code blocks).
- **Code blocks**: always specify the language.

## READMEs

Expand Down
Loading