Skip to content

Commit 5a9eda4

Browse files
chore: add proper claude code guidelines
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
1 parent 521ecd4 commit 5a9eda4

1 file changed

Lines changed: 19 additions & 2 deletions

File tree

CLAUDE.md

Lines changed: 19 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,23 @@
11
# Claude Code Guidelines
22

3-
## Git Commits
3+
## Linting
44

5-
When committing changes, do not include a `Co-Authored-By` line for Claude in commit messages.
5+
- Use **pickier** for linting — never use eslint directly
6+
- Run `bunx --bun pickier .` to lint, `bunx --bun pickier . --fix` to auto-fix
7+
- When fixing unused variable warnings, prefer `// eslint-disable-next-line` comments over prefixing with `_`
68

9+
## Frontend
10+
11+
- Use **stx** for templating — never write vanilla JS (`var`, `document.*`, `window.*`) in stx templates
12+
- Use **crosswind** as the default CSS framework
13+
- stx `<script>` tags should only contain stx-compatible code (signals, composables, directives)
14+
15+
## Dependencies
16+
17+
- **buddy-bot** handles dependency updates — not renovatebot
18+
- **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`
19+
- If `better-dx` is in `package.json`, ensure `bunfig.toml` includes `linker = "hoisted"`
20+
21+
## Commits
22+
23+
- Use conventional commit messages (e.g., `fix:`, `feat:`, `chore:`)

0 commit comments

Comments
 (0)