Skip to content

CLAUDE.md

Latest commit

 

History

History
27 lines (17 loc) · 1.43 KB

CLAUDE.md

File metadata and controls

27 lines (17 loc) · 1.43 KB

Claude Code Guidelines

About

GitLint is a tool for enforcing consistent Git commit message conventions based on the Conventional Commits specification. It provides configurable rules (conventional-commits, header-max-length, body-max-line-length, etc.) with error/warning severity levels, Git hooks integration (install/uninstall via CLI or use with husky), and a programmatic API for linting and parsing commit messages.

Linting

  • Use pickier for linting — never use eslint directly
  • Run bunx --bun pickier . to lint, bunx --bun pickier . --fix to auto-fix
  • When fixing unused variable warnings, prefer // eslint-disable-next-line comments over prefixing with _

Frontend

  • Use stx for templating — never write vanilla JS (var, document.*, window.*) in stx templates
  • Use crosswind as the default CSS framework which enables standard Tailwind-like utility classes
  • stx <script> tags should only contain stx-compatible code (signals, composables, directives)

Dependencies

  • buddy-bot handles dependency updates — not renovatebot
  • better-dx provides shared dev tooling as peer dependencies — do not install its peers (e.g., typescript, pickier, bun-plugin-dtsx) separately if better-dx is already in package.json
  • If better-dx is in package.json, ensure bunfig.toml includes linker = "hoisted"

Commits

  • Use conventional commit messages (e.g., fix:, feat:, chore:)