Carousel Studio

Tech with Mak

@techNmak

Someone finally documented how to actually use Claude Code. 22K+ stars. claude-code-best-practice. Direct from Boris Cherny and team: → Always use plan mode, give Claude a way to verify → Ask Claude to interview you using AskUserQuestion tool → Use Git Worktrees for parallel development → /loop - schedule recurring tasks for up to 3 days → Code Review - fresh context windows catch bugs the original agent missed → /btw - side chain conversations while Claude works → Make phase-wise gated plans with tests for each phase → Use cross-model (Claude Code + Codex) to review your plan → CLAUDE[.]md should target under 200 lines per file → Use commands for workflows instead of sub-agents → Have feature-specific sub-agents with skills instead of general QA or backend engineer → Vanilla Claude Code is better than complex workflows for smaller tasks → Take screenshots and share with Claude when stuck → Use MCP to let Claude see Chrome console logs → Ask Claude to run terminal as background task for better debugging → Use cross-model for QA - e.g. Codex for plan and implementation review The community workflows included: → Cross-Model (Claude Code + Codex) Workflow → RPI (Research Plan Implement) → Ralph Wiggum Loop for autonomous tasks → Github Speckit (74K stars) → obra/superpowers (72K stars) → OpenSpec OPSX (28K stars) The billion-dollar questions it addresses: → What should you put inside CLAUDE[.]md? → When should you use command vs agent vs skill? → Why does Claude ignore CLAUDE[.]md instructions? → Can we convert a codebase into specs and regenerate code from those specs alone? The daily habits: → Update Claude Code daily → Start your day by reading the changelog → Follow r/ClaudeAI, r/ClaudeCode on Reddit Repost it. Bookmark it.

Apply Image

Tech with Mak

@techNmak

GitHub Repo: <a target="_blank" href="https://github.com/shanraisshan/claude-code-best-practice" color="blue">github.com/shanraisshan/c…</a>