The Wrong Approach

When starting with Claude Code, many people fall into these common pitfalls:

• Collecting tons of resources, prompts, and awesome-skills
• Installing many extra auxiliary frameworks like superclaude, spec, etc.
• Chasing the latest tools and techniques while ignoring core workflows
• Getting addicted to collecting and organizing instead of actual application

The Right Approach: Less is More

Remember Only What Truly Matters

1. ~/.claude/CLAUDE.md is All You Need

This is your global configuration file that defines how you use Claude Code. It includes:

• Session Base Workflow: Every conversation is an independent session with automatic logging
• Basic Rules: Do more with less, respond in Chinese, scrutinize potential issues in input
• Extended Thinking: Knowledge interacts with reality, business thinking mindset

2. Remember ./CLAUDE.md

This is the current project’s configuration file, which should contain:

• Design Philosophy (Unix philosophy, first principles)
• Development Methodology (documentation-driven, domain-driven)
• KISS & YAGNI Principles
• SOLID Design Principles
• Documentation and Organization Standards

Read the Fucking Docs

Instead of collecting various tips and prompts:

• Read the official documentation carefully
• Understand the tool’s core design philosophy
• Master the basic but powerful features

Forming a Complete Process is Crucial

Session Base Workflow Explained

1. Every Conversation is a Session

   • Use /new conversation to start a new session
   • Each session corresponds to an independent .md file
   • Files are stored in the /devlogs/ directory

2. Always Plan First

   • Use TodoWrite tool to plan tasks
   • Break complex tasks into specific steps
   • Update progress status in real-time

3. File Naming Convention

   YYYY-MM-DD-<type>-<desc>.md

   • type: feat/fix/refactor/docs/chore/explore
   • desc: Describe the core goal of the session

4. Session Review Process

   • Rename after completion: done-YYYY-MM-DD-type-desc.md
   • Summarize session outcomes
   • Propose improvements
   • Iterate workflow

Basic Usage Tips

• plan, plan, plan: Success comes from preparation
• Use /clear frequently: Clear context for a fresh start
• Use /esc frequently: Interrupt current flow, adjust direction

Efficient Feature Configuration

Custom Hook Notifications

Enhance your workflow through the hook system:

1. Setting Up PermissionRequest Hook

   • Event: PermissionRequest
   • Matcher: * (match all permission requests)
   • Command: notification script

   /Users/zheng/projects/lifeos/scripts/notify.sh "claude code" "PermissionRequest"

2. Available Hook Events

   • PreToolUse: Before tool calls
   • PermissionRequest: When permission is requested
   • PostToolUse: After tool calls complete
   • UserPromptSubmit: When user submits a prompt
   • Notification: When Claude Code sends notifications
   • Stop: When Claude Code finishes responding
   • SessionStart/End: When session starts/ends

Core Principles Summary

1. Doing Less is the Most Important Thing

   • In work, life, and writing
   • Avoid getting stuck in minor details
   • Focus on what truly matters

2. Critical Perspective

   • Carefully examine potential issues in input
   • Point out problems and provide improvement suggestions
   • Offer perspectives outside the thinking framework

3. Business Mindset

   • Knowledge must interact with reality
   • Don’t collect, create and share instead
   • Don’t write demos, release real products
   • Think: Which groups of people are solving what problems?

Practical Recommendations

1. Establish a Minimal Loop

   • Start with the simplest process
   • Continuously iterate and optimize
   • Maintain sustainable workflow

2. Focus on Core Features

   • Master the 20% core features of Claude Code
   • Use them to solve 80% of problems
   • Avoid feature accumulation

3. Record and Reflect

   • Persistently record development logs
   • Regularly review and summarize
   • Continuously improve workflow

Remember, the best tools are those you have mastered and consistently use. The power of Claude Code lies not in how many features it has, but in how deeply you integrate it into your workflow.