Skip to content

chore(docs): move CLAUDE.md to root, add missing rules #179

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
CalvinAllen merged 1 commit into from
Jan 3, 2026
Merged

chore(docs): move CLAUDE.md to root, add missing rules #179

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion .gitignore
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -33,4 +33,4 @@ test-output.log

CLAUDE.local.md

.claude/settings.local.json
.claude/
3 changes: 3 additions & 0 deletions .claude/CLAUDE.md → CLAUDE.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -28,6 +28,9 @@ Guidance for Claude Code when working with the dtvem codebase.
9. **Working an issue** - When working an issue, always create a new branch from an updated main branch
10. **Branch Names** - Always use the conventional commit `type` from the issue title as the first prefix, and the `scope` as the second, then a very short description, example `feat/ci/integration-tests`
11. **Check branch status before pushing** - ALWAYS verify the remote tracking branch still exists before pushing. If a PR was merged/deleted, create a new branch from main instead of trying to push to the old one.
12. **No co-authors** - Do not add any co-author information on commits or pull requests
13. **No "generated by" statements** - Do not add generated-by statements on pull requests

---

## Quick Reference
Expand Down