- 2 space indents
- One logical change per commit
- Commit subjects: one line, under 50 characters (GitHub's display limit), sentence case
- Commit each change
- Use present tense in commits and CHANGELOG.md
- Use sentence case for headings (not Title Case)
- Never use bold text as headings, use proper heading levels instead
- Always add an empty line after headings
- No formatting in CHANGELOG.md except
inline codeand when absolute necessary - Use
*as bullets in CHANGELOG.md - CHANGELOG.md bullets: 2-10 words
- Rationale belongs in code comments or docs, never in commits or CHANGELOG.md
- Real semver: patch = fix/tweak, minor = new capability, major = breaking change. Default to patch
- One version bump per work session, not per commit or per fix. Consolidate same-day changes into it
- Never use Claude watermark in commits (FORBIDDEN: "Co-Authored-By")
- No emojis in commits or code
- Keep CHANGELOG.md date up to date when adding entries
- Never use "====" separators or underlines with "=", if you must use them, prefer dash or single line separators or headings that match the text width
Files that contain version numbers and must be updated on each release:
README.md- badge in line 3 (version-X.Y.Z)CHANGELOG.md- new entry at the top
- Always add tasks to the Claude Code to-do list and keep it up to date.
- Review your to-do list and prioritize before starting.
- If new tasks come in, don't jump to them right away—add them to the list in order of urgency and finish your current work first.
- Do not ever guess features, always proof them via looking up official docs, GitHub code, issues, if possible.
- When looking things up, do not use years in search terms like 2024 or 2025.