Style and Conventions

Markdown and text formatting

Write one sentence per line in markdown, text, and documentation files.
Prefer prose over bullet lists when explaining concepts or providing narrative flow. Reserve bulleted lists for genuinely discrete items or enumerations, not for breaking up what should be continuous explanation.
Keep section header nesting shallow. Avoid deeply nested subsections (###, ####) when flatter structure with clear prose transitions would be more readable. Most documents should rarely need headers beyond three levels.
Use bold text (**) sparingly, primarily for critical emphasis within sentences. Avoid bolding section labels, definitions, or key terms when plain text suffices. Prefer italic (*) for subtle emphasis.
Avoid using emojis in code, comments, documentation, markdown files, etc unless explicitly requested to do so.
For documentation-specific markdown conventions (frontmatter titles, header levels), see "Markdown formatting conventions" in ~/.claude/skills/preferences-documentation/SKILL.md.

Prefer lowercase except when replicating code conventions like PascalCase or camelCase, in acronyms, or in proper nouns.
Do prefer to capitalize the first letter of the first word and use Chicago Manual sentence-style capitalization for
- complete sentences that end with punctuation marks
- markdown file title frontmatter, section headings, and any level of subsection heading
Do not use uppercase words for emphasis or notification purposes like "IMPORTANT", "URGENT", "WARNING", etc except in relevant situations like error handling, logging, or quoting usage by other sources.
Do not name files with all uppercase letters. Use lowercase kebab-case specifically for markdown filenames or if there is no specific convention for the programming language or filetype (e.g. python uses snake_case).