Skip to main content
CLAUDE CODE FREE

Best practices

Master Claude Code with proven workflows, tips, and techniques from the community.

Foundation

Core Concepts

Understanding these three building blocks will help you use Claude Code more effectively.

🤖

Agents

Autonomous actors in fresh isolated context with custom tools, permissions, model, memory, and persistent identity

Use for: Use for parallel work, isolated experiments, or long-running tasks

⌨️

Commands

Knowledge injected into existing context - simple user-invoked prompt templates for workflow orchestration

Use for: Use for quick workflows, repeating patterns, or team-standardized tasks

🎯

Skills

Configurable, preloadable, auto-discoverable workflows with context forking and progressive disclosure

Use for: Use for complex multi-step processes, team playbooks, or reusable patterns

Workflows

Recommended Workflows

Follow these proven patterns for reliable results.

Research → Plan → Execute → Review → Ship

The standard workflow pattern for reliable results

1.Gather context2.Draft plan3.Implement changes4.Review quality5.Ship confidently

Browser-based Plan Review

Use /ultraplan for browser-based plan review with inline comments

1.Run /ultraplan <prompt>2.Review in browser3.Add comments4.Execute remotely or return to terminal

Auto Mode for Safety

Enable Auto Mode to replace manual permission prompts with AI safety classification

1.Auto Mode enabled2.Claude decides what's safe3.Risks blocked automatically4.Focus on coding

Power User

Pro Tips

Advanced techniques to boost your productivity.

⭐

Terminal Setup

Configure terminal for Option as Meta (Mac users) to unlock Alt/Option key shortcuts

iTerm2: Preferences → Profiles → Keys → Left/Right Option key = Esc+
⭐

Bash Commands

Use ! prefix for direct bash commands without going through Claude interpretation

! npm test && ! git status
⭐

Permissions

Set up permission rules proactively using /permissions to manage allow/ask/deny rules

/permissions
⭐

Side Questions

Use /btw for quick questions without cluttering the main context

/btw what was that config file name?
⭐

Context Management

Leverage /compact to free context space on long sessions

/compact focus on the bug fix approach
⭐

Flicker-Free Sessions

Set CLAUDE_CODE_NO_FLICKER=1 for stable, flicker-free terminal sessions

export CLAUDE_CODE_NO_FLICKER=1
⭐

Scheduled Tasks

Use /schedule for cloud-based prompts that run even when offline

/schedule check deploy status every 10m

Context

Memory Files

Persistent context that survives across sessions.

CLAUDE.md

Persistent low-level project context

Run /init at project start to auto-generate

.claude/

Configuration for skills, hooks, and memory files

Store team playbooks and custom workflows here

Quick Command Reference

/initCreate CLAUDE.md
/compactFree context
/btwSide question
/ultraplanBrowser planning
!Bash mode
/permissionsManage rules