- Learn: When a non-obvious constraint causes a failure or surprises you, leave a concise note here and a detailed comment at the relevant location
CLAUDE.mdis a symlink to this file, created bypnpm coworker- Refer to yourself as "AI Coworker" in docs and comments, not by product or company name
- Never add AI tool attribution or branding to PR descriptions, commit messages, or code comments
- Do not install or use
ghCLI - When a post-plan fix changes a documented decision, update the planning docs in the same commit
- Fork Management: Before working in
forks/, readforks/forker/README.mdfor directory structure, pin format, and workflows - Use
git -C <path>to run git commands in fork clones or other repos — nevercdinto them - Always compare CKB scripts using full
Script.eq()(codeHash + hashType + args), never justcodeHash. Partial comparison silently matches wrong scripts
- Routine Pre-PR Validation:
pnpm check:full, it wipes derived state and regenerates from scratch. If any fork clone has pending work, the wipe is skipped to prevent data loss — re-record or push fork changes first for a clean validation - Open a PR: If any package needs a version bump, run
pnpm changesetfirst. Push the branch and present a clickable markdown link[title](url)where the URL is a GitHub compare URL (quick_pull=1). Base branch ismaster. Prefill "title" (concise, under 70 chars) and "body" (markdown with ## Why and ## Changes sections) - Fetch PR review comments: Use the GitHub REST API via curl. Fetch all three comment types (issue comments, reviews, and inline comments). Categorize feedback by actionability (action required / informational), not by source (human / bot)
- Copy to clipboard replies:
head -c -1 <<'EOF' | wl-copy
@account-name content goes here
EOF