claude-code-tips/GLOBAL-CLAUDE.md at main · ebcode/claude-code-tips · GitHub
Skip to content

GLOBAL-CLAUDE.md

Latest commit

 

History

History
76 lines (46 loc) · 3.73 KB

GLOBAL-CLAUDE.md

File metadata and controls

76 lines (46 loc) · 3.73 KB
Raw

Writing Style

  • Use sentence case for headers, not title case
  • Never use em dashes (—). Use spaced hyphens - (space, hyphen, space) instead.
  • Don't make up or add content I didn't say. Stick to what I've said. Rephrasing is okay, but don't embellish.

About Me

  • Name: YK
  • GitHub: ykdojo
  • Current year: 2026 (focus your research on the past three months)

Behavior

Respond concisely. Lead with the answer or a recommendation, not a menu of options. Don't restate my question, recap work I can already see, append "one note" asides, or raise topics I didn't ask about. Aim for under ~100 words by default: lead with the key facts, then use short bullet points instead of a paragraph per point. Expand only when I ask for depth or the task genuinely needs it.

Double-check before claiming something as fact. Don't state things confidently without a source - if you can't verify it, say so or go verify it first. Trust verified evidence over a single conflicting source.

When I paste large content with no instructions, just summarize it.

Git

  • Run commit and push as separate commands, never chained (git commit && git push). Auto mode may reject the push, and a chained command makes the rejection kill the commit too. Commit first so it always lands, then push as its own step (which I can approve separately).

Publishing to npm

My npm account has 2FA set to auth-and-writes, so npm publish requires 2FA. The web login (npm login --auth-type=web) signs in but does NOT satisfy publish-time 2FA, and npm publish then fails with a 403.

Reliable path - use a Classic Automation token (they bypass 2FA):

  1. npmjs.com - Access Tokens - Generate New Token - Classic Token - type Automation - Generate.
  2. Publish from the package dir: npm publish --//registry.npmjs.org/:_authToken=npm_...
  3. Revoke the token afterward.

Avoid Granular Access Tokens for this - they are fiddly: they error if org permissions are set without selecting an org (I have no orgs), and a brand-new unscoped package can't be individually selected, so it needs "All packages".

Before publishing: npm publish --dry-run to confirm the file list, and gitignore generated artifacts so they don't ship.

Containers

Use safeclaw containers (local: /Users/yk/Desktop/projects/safeclaw). Containers are named safeclaw-<session-name> (e.g., safeclaw-work, safeclaw-research).

To list running safeclaw containers: docker ps --filter "name=safeclaw-"

To create a new container: cd /Users/yk/Desktop/projects/safeclaw && ./scripts/run.sh -s <name> -n

For read-only gh API calls on public repos, use a running safeclaw container: docker exec safeclaw-<name> bash -c 'gh api <endpoint>'. If container gh lacks permissions, fall back to host gh.

URL Fetching

Always fetch individual URLs through a safeclaw container: docker exec safeclaw-<name> curl -sL <url>

If the page is JavaScript-heavy (curl returns minimal or empty content), use Playwright instead (safeclaw containers have Playwright installed).

Tmux

For interactive Claude Code sessions:

tmux new-session -d -s <name> '<command>'
tmux send-keys -t <name> '<input>' Enter  # don't forget Enter!
tmux capture-pane -t <name> -p

Note: For Claude Code sessions, you may need to send Enter again after a short delay to ensure the prompt is submitted.

Long-running Jobs

If you need to wait for a long-running job, use sleep commands with manual exponential backoff: wait 1 minute, then 2 minutes, then 4 minutes, and so on.

Claude for Chrome

  • Use read_page to get element refs from the accessibility tree
  • Use find to locate elements by description
  • Click/interact using ref, not coordinates
  • NEVER take screenshots unless explicitly requested by the user