CLAUDE.md · git:20260918.c7659b2 · 2026-09-18 · sha256 d41f6e1893048ca2

CLAUDE.md git:20260918.c7659b2A

Immutable. This exact content is served forever at /api/v1/blob/d41f6e1893048ca2.

# Shell

always use ripgrep instead of grep
always use fd instead of find
always use git commit --no-gpg-sign when commiting
always prefer brew over npm for system tools

# Coding
prefer python and use uv

# Markdown
adhere to DavidAnson markdownlint

# Writing preference
- never use em dash or en dash
- never use "this isn't just..., it's..." trope
- NO METASPEAK: every deliverable (report, email, doc, Jira/Slack post) reads as a standalone artifact by a fresh author. Never reference prior drafts, revisions, review feedback, the writing process, or what changed ("as discussed", "updated to reflect", "per your feedback", "in this revision"). Before presenting any deliverable, self-check for these and strip them.

# Repository content

This repository is public. Write every file so a stranger can use it:

- Refer to the person as "User", never by name, and use they/them.
- Use generic paths: `~/...`, `$HOME`, or a configurable variable. Never
  hardcode `/Users/<name>/...`.
- Never name an employer, an internal host, or an internal repository path.

# Research & Verification
Before guessing how a third-party service behaves, verify first. In priority order:
1. Live state (account/instance-specific): query the actual API, run the CLI, read the real config/source. Never assume runtime state.
2. Documented behavior of libraries/SDKs/APIs/CLIs (WorkOS, Slack, Homebrew, etc.): use Context7.
3. Niche/self-hosted tools Context7 won't have (go2rtc, HA integrations): WebSearch/WebFetch, or read the tool's own source.
4. Provide links when posting, e.g. Jira Service Management, so Users can see the data, logs, code, documentation, etc.

Show the source you verified against before proposing a fix.