suwappubot CLAUDE.md

CLAUDE.md

This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.

Workflow

• IMPLEMENT, don't plan. When asked to fix or build something, DO the work. If you need to explore first, limit exploration to 5 minutes then start building. Only produce a plan document if explicitly asked for one.
• If blocked, say so explicitly — don't fill the response with exploration as a substitute for implementation.

Response Length

• Keep each assistant turn under ~400 output tokens. Prefer many short turns over one long turn.
• For long reports, audits, or plans: Write them to a file and reply with the path + a 3-bullet summary. Never inline a whole document in a turn.
• Write deliverables to disk as they are produced, not at the end. An interrupted session should cost a turn, not the whole run.

Git Conventions

• IMPORTANT: Do NOT add "Co-Authored-By" lines to commit messages.
• Journal-only commits (harness(journal): ...) must end the subject with [skip ci]. The test workflow has no path filters and cancels superseded PR runs, so a plain journal push cancels the in-flight CI run you're waiting on. Never put [skip ci] on a commit that touches code.

Git Operations

Before any git push, rebase, or merge, run this mandatory pre-flight sequence. Do NOT skip steps. Only proceed after reporting all findings. If any issue is found, fix it first and re-run.

Pre-flight checklist (run every time):

1. Build artifacts: Check for .next/, node_modules/, dist/ in tracked files. If found, add to .gitignore and unstage before proceeding.
2. Lock files: Run ls .git/*.lock 2>/dev/null — if stale lock files exist, investigate what holds them (don't just delete).
3. Worktree check: Run git rev-parse --git-common-dir — if in a worktree, NEVER rebase. Always use git merge or git pull --no-rebase.
4. Divergence check: Compare git rev-parse HEAD vs git rev-parse @{u} to detect local/remote divergence. Recommend merge (not force-push) unless user explicitly approves.
5. Uncommitted work: Run git status and git stash list to surface any uncommitted changes or stashed work. Report before proceeding.