Skip to content

CLAUDE MD Solo

rUv edited this page Jul 30, 2025 · 2 revisions

Claude Code Configuration for Solo Developers

🚀 CRITICAL: Personal Productivity Parallel Execution

MANDATORY RULE: As a solo developer, ALL development activities MUST be self-coordinated and efficient:

  1. Project Planning → Initialize swarm with personal scope in ONE call
  2. Feature Development → Batch ALL related tasks together
  3. Testing & QA → Parallel execution of all quality checks
  4. Deployment → Batch ALL release activities together

👤 SOLO DEVELOPER SWARM ORCHESTRATION PATTERN

Personal Project Initialization (Single Message)

[BatchTool - Solo Project Setup]:
  // Initialize personal productivity swarm
  - mcp__claude-flow__swarm_init { 
      topology: "star", 
      maxAgents: 4, 
      strategy: "solo_developer" 
    }
  
  // Spawn productivity-focused agents
  - mcp__claude-flow__agent_spawn { type: "coordinator", name: "Project Manager Self" }
  - mcp__claude-flow__agent_spawn { type: "coder", name: "Full-Stack Developer" }
  - mcp__claude-flow__agent_spawn { type: "tester", name: "QA Self" }
  - mcp__claude-flow__agent_spawn { type: "analyst", name: "Product Owner Self" }

  // Solo developer todos - ALL project aspects at once
  - TodoWrite { todos: [
      { id: "project-planning", content: "Define project scope and requirements", status: "completed", priority: "high" },
      { id: "tech-stack", content: "Choose technology stack and architecture", status: "in_progress", priority: "high" },
      { id: "mvp-features", content: "Identify MVP features and user stories", status: "pending", priority: "high" },
      { id: "development-setup", content: "Set up development environment and tools", status: "pending", priority: "high" },
      { id: "frontend-development", content: "Build user interface and components", status: "pending", priority: "high" },
      { id: "backend-development", content: "Implement API and business logic", status: "pending", priority: "high" },
      { id: "database-design", content: "Design and implement data layer", status: "pending", priority: "medium" },
      { id: "testing-suite", content: "Write comprehensive tests", status: "pending", priority: "medium" },
      { id: "deployment-setup", content: "Configure deployment and hosting", status: "pending", priority: "medium" },
      { id: "documentation", content: "Create project documentation", status: "pending", priority: "low" }
    ]}

  // Initialize solo developer memory context
  - mcp__claude-flow__memory_usage { 
      action: "store", 
      key: "solo/project_context", 
      value: { 
        developer: "solo",
        project_type: "full_stack_web_app",
        time_commitment: "evenings_weekends",
        tech_stack: "react_node_postgres",
        deployment_target: "vercel_heroku"
      } 
    }

🎯 SELF-MANAGEMENT COORDINATION

Daily Development Routine

MANDATORY: As a solo developer, maintain consistent daily coordination:

# Daily development check-in (run each coding session)
npx claude-flow@alpha hooks pre-task --description "Daily coding session start" --auto-spawn-agents false
npx claude-flow@alpha hooks notify --message "Today's focus: [feature/bug/refactor], Time available: [hours], Goals: [specific targets]" --telemetry true

Solo Developer Agent Template

You are the [Development Role] for a solo developer project.

MANDATORY SOLO COORDINATION:
1. SELF-ACCOUNTABILITY: Set clear daily and weekly goals
2. TIME MANAGEMENT: Focus on high-impact features first
3. QUALITY BALANCE: Balance speed with maintainable code
4. LEARNING INTEGRATION: Document discoveries and learnings

Your development focus: [specific area of responsibility]
Time constraints: [available hours/schedule]
Learning goals: [new technologies/patterns to explore]

REMEMBER: You are the entire development team - plan, code, test, and deploy efficiently!

💻 FULL-STACK DEVELOPMENT WORKFLOW

Complete Feature Implementation

// ✅ CORRECT: Full-stack feature development in parallel
[BatchTool - Feature Development]:
  // All layers of the feature developed together
  - Task("Full-Stack Developer: Implement user authentication with frontend, backend, and database")
  - Task("QA Self: Write unit, integration, and end-to-end tests for auth feature")
  - Task("Project Manager Self: Update project roadmap and document decisions")

  // Frontend components
  - Write("src/components/LoginForm.tsx", loginFormCode)
  - Write("src/components/SignupForm.tsx", signupFormCode)
  - Write("src/components/UserProfile.tsx", userProfileCode)
  - Write("src/hooks/useAuth.ts", authHookCode)

  // Backend API endpoints
  - Write("api/auth/login.js", loginEndpointCode)
  - Write("api/auth/signup.js", signupEndpointCode)
  - Write("api/auth/profile.js", profileEndpointCode)
  - Write("middleware/auth.js", authMiddlewareCode)

  // Database schema and migrations
  - Write("database/migrations/001_create_users_table.sql", createUsersTableCode)
  - Write("database/models/User.js", userModelCode)
  - Write("database/seeds/users.js", userSeedCode)

  // Testing suite
  - Write("tests/auth.test.js", authTestCode)
  - Write("tests/integration/auth-flow.test.js", authFlowTestCode)
  - Write("cypress/e2e/authentication.cy.js", authE2ETestCode)

  // Documentation
  - Write("docs/authentication.md", authDocumentationCode)
  - Write("README.md", updatedReadmeCode)

  // Store feature completion
  - mcp__claude-flow__memory_usage { 
      action: "store", 
      key: "solo/features/authentication", 
      value: { 
        status: "completed",
        implementation_time: "8_hours",
        tech_used: ["bcrypt", "jwt", "react_hook_form"],
        lessons_learned: ["JWT security considerations", "Form validation patterns"]
      } 
    }

🔄 RAPID PROTOTYPING PATTERN

Quick MVP Development

[BatchTool - MVP Development]:
  // Minimal viable product setup
  - Bash("npx create-react-app my-project --template typescript")
  - Bash("cd my-project && npm install express cors dotenv bcryptjs jsonwebtoken")
  - Bash("mkdir -p server/{routes,models,middleware} && mkdir -p src/{components,hooks,pages,services}")

  // Essential project files
  - Write("server/index.js", expressServerCode)
  - Write("server/routes/api.js", apiRoutesCode)
  - Write("src/App.tsx", reactAppCode)
  - Write("src/components/Layout.tsx", layoutComponentCode)
  - Write("package.json", updatedPackageJsonCode)

  // Basic deployment configuration
  - Write("Dockerfile", dockerfileCode)
  - Write("docker-compose.yml", dockerComposeCode)
  - Write("vercel.json", vercelConfigCode)

  // Quick testing setup
  - Write("jest.config.js", jestConfigCode)
  - Write("src/App.test.tsx", appTestCode)

🛠️ DEVELOPMENT ENVIRONMENT OPTIMIZATION

Personal Productivity Setup

[BatchTool - Dev Environment]:
  // IDE and tooling configuration
  - Write(".vscode/settings.json", vscodeSettingsCode)
  - Write(".vscode/extensions.json", vscodeExtensionsCode)
  - Write(".vscode/launch.json", vscodeDebugConfigCode)
  - Write(".vscode/tasks.json", vscodeTasksCode)

  // Development workflow automation
  - Write("scripts/dev-setup.sh", devSetupScript)
  - Write("scripts/test-watch.sh", testWatchScript)
  - Write("scripts/build-and-deploy.sh", buildDeployScript)

  // Code quality tools
  - Write(".eslintrc.js", eslintConfigCode)
  - Write(".prettier.config.js", prettierConfigCode)
  - Write("husky.config.js", huskyConfigCode)
  - Write(".gitignore", gitignoreCode)

  // Personal development notes
  - Write("DEVELOPMENT_LOG.md", developmentLogCode)
  - Write("LEARNING_NOTES.md", learningNotesCode)
  - Write("ARCHITECTURE_DECISIONS.md", architectureDecisionsCode)

📚 CONTINUOUS LEARNING INTEGRATION

Knowledge Management System

# Learning session coordination
npx claude-flow@alpha hooks pre-task --description "Learning new technology/pattern"
npx claude-flow@alpha hooks notify --message "Learning: [technology], Application: [how it helps project], Time spent: [duration]" --telemetry true
npx claude-flow@alpha hooks post-task --task-id "learning_session" --analyze-performance true

Personal Knowledge Base

[BatchTool - Knowledge Management]:
  // Learning documentation
  - Write("docs/LEARNING_PATH.md", learningPathCode)
  - Write("docs/TECH_RESEARCH.md", techResearchCode)
  - Write("docs/CODE_PATTERNS.md", codePatternsCode)
  - Write("docs/TROUBLESHOOTING.md", troubleshootingGuideCode)

  // Code templates and snippets
  - Write("templates/react-component.tsx", reactComponentTemplateCode)
  - Write("templates/express-route.js", expressRouteTemplateCode)
  - Write("templates/test-template.js", testTemplateCode)

  // Personal utilities
  - Write("utils/dev-helpers.js", devHelpersCode)
  - Write("utils/common-functions.js", commonFunctionsCode)
  - Write("utils/api-client.js", apiClientCode)

  // Store learning progress
  - mcp__claude-flow__memory_usage { 
      action: "store", 
      key: "solo/learning_progress", 
      value: { 
        current_focus: "typescript_advanced_patterns",
        completed_topics: ["react_hooks", "node_express", "postgresql"],
        next_goals: ["docker", "kubernetes", "graphql"],
        skill_level: "intermediate_advancing_to_advanced"
      } 
    }

⚡ TIME MANAGEMENT AND FOCUS

Pomodoro Integration with Development

# Focused coding session (25-minute Pomodoro)
npx claude-flow@alpha hooks pre-task --description "Pomodoro coding session: [specific task]"
# ... 25 minutes of focused coding ...
npx claude-flow@alpha hooks post-task --task-id "pomodoro_session" --analyze-performance true

Priority-Based Task Management

// Task prioritization for solo developers
- TodoWrite { todos: [
    // High Priority: Core functionality that blocks other features
    { id: "auth-system", content: "Complete user authentication system", status: "in_progress", priority: "high" },
    { id: "data-layer", content: "Set up database and core models", status: "pending", priority: "high" },
    
    // Medium Priority: Important features that enhance user experience
    { id: "ui-polish", content: "Improve user interface and responsiveness", status: "pending", priority: "medium" },
    { id: "error-handling", content: "Add comprehensive error handling", status: "pending", priority: "medium" },
    
    // Low Priority: Nice-to-have features and optimizations
    { id: "performance-optimization", content: "Optimize app performance and loading", status: "pending", priority: "low" },
    { id: "advanced-features", content: "Add advanced user features", status: "pending", priority: "low" }
  ]}

🚀 SOLO DEVELOPER BEST PRACTICES

✅ DO:

  • Start Small: Begin with MVP and iterate based on feedback
  • Document Everything: Maintain clear documentation for future you
  • Automate Repetitive Tasks: Use scripts and tools to reduce manual work
  • Regular Backups: Implement version control and backup strategies
  • Time Boxing: Use focused time blocks for different types of work
  • Learning Integration: Incorporate new technologies gradually
  • Testing Early: Write tests as you develop, not after

❌ DON'T:

  • Don't over-engineer solutions - keep it simple and working
  • Avoid perfectionism paralysis - ship and iterate
  • Don't skip version control or proper git practices
  • Never work without backups and deployment safety nets
  • Don't ignore security basics even in personal projects
  • Avoid feature creep - stick to your defined scope
  • Don't work in isolation - seek feedback from users or peers

📱 PROJECT TYPES FOR SOLO DEVELOPERS

Personal Portfolio Website

[BatchTool - Portfolio Setup]:
  // Portfolio project structure
  - Write("src/components/Hero.tsx", heroComponentCode)
  - Write("src/components/Projects.tsx", projectsComponentCode)
  - Write("src/components/Skills.tsx", skillsComponentCode)
  - Write("src/components/Contact.tsx", contactComponentCode)

  // Content management
  - Write("content/projects.json", projectsDataCode)
  - Write("content/skills.json", skillsDataCode)
  - Write("content/experience.json", experienceDataCode)

  // Deployment configuration
  - Write("netlify.toml", netlifyConfigCode)
  - Write("public/_redirects", netlifyRedirectsCode)

SaaS Side Project

[BatchTool - SaaS Project]:
  // SaaS application structure
  - Write("src/components/Landing.tsx", landingPageCode)
  - Write("src/components/Dashboard.tsx", dashboardCode)
  - Write("src/components/Pricing.tsx", pricingComponentCode)
  - Write("src/components/Settings.tsx", settingsComponentCode)

  // Business logic
  - Write("server/services/subscription.js", subscriptionServiceCode)
  - Write("server/services/payment.js", paymentServiceCode)
  - Write("server/services/analytics.js", analyticsServiceCode)

  // Third-party integrations
  - Write("server/integrations/stripe.js", stripeIntegrationCode)
  - Write("server/integrations/sendgrid.js", emailIntegrationCode)

Open Source Tool

[BatchTool - Open Source Project]:
  // Open source project setup
  - Write("README.md", openSourceReadmeCode)
  - Write("CONTRIBUTING.md", contributingGuideCode)
  - Write("LICENSE", mitLicenseCode)
  - Write("CODE_OF_CONDUCT.md", codeOfConductCode)

  // Package configuration
  - Write("package.json", openSourcePackageJsonCode)
  - Write(".npmignore", npmIgnoreCode)
  - Write("rollup.config.js", rollupConfigCode)

  // Documentation
  - Write("docs/API.md", apiDocumentationCode)
  - Write("docs/EXAMPLES.md", examplesDocumentationCode)
  - Write("examples/basic-usage.js", basicExampleCode)

🔧 DEPLOYMENT AND MAINTENANCE

Solo Developer Deployment Strategy

[BatchTool - Deployment Setup]:
  // Simple deployment pipeline
  - Write(".github/workflows/deploy.yml", deployWorkflowCode)
  - Write("scripts/deploy.sh", deployScriptCode)
  - Write("scripts/backup.sh", backupScriptCode)

  // Monitoring for solo projects
  - Write("monitoring/uptime-check.js", uptimeCheckCode)
  - Write("monitoring/error-tracking.js", errorTrackingCode)
  - Write("monitoring/performance-monitor.js", performanceMonitorCode)

  // Maintenance automation
  - Write("scripts/update-dependencies.sh", updateDependenciesScript)
  - Write("scripts/security-audit.sh", securityAuditScript)
  - Write("scripts/cleanup.sh", cleanupScript)

Cost-Effective Infrastructure

[BatchTool - Budget Infrastructure]:
  // Free tier deployments
  - Write("vercel.json", vercelDeploymentConfig)
  - Write("netlify.toml", netlifyDeploymentConfig)
  - Write("railway.json", railwayDeploymentConfig)

  // Database setup
  - Write("database/setup-postgres.sh", postgresSetupScript)
  - Write("database/setup-mongodb.sh", mongodbSetupScript)
  - Write("database/migrate.js", migrationScript)

  // Environment configuration
  - Write(".env.example", envExampleCode)
  - Write("config/database.js", databaseConfigCode)
  - Write("config/app.js", appConfigCode)

💡 SOLO DEVELOPER SUCCESS PATTERNS

Minimum Viable Product (MVP) Focus

Week 1: Core functionality (authentication, basic CRUD)
Week 2: User interface and basic user experience
Week 3: Testing, bug fixes, and performance optimization
Week 4: Deployment, monitoring, and documentation

Feature Development Cycle

1. Research and spike (understand the problem)
2. Design and plan (create simple architecture)
3. Implement core functionality (make it work)
4. Add tests (ensure reliability)
5. Refactor and optimize (make it maintainable)
6. Document and deploy (share the solution)

Personal Development Metrics

// Track personal productivity metrics
- mcp__claude-flow__memory_usage { 
    action: "store", 
    key: "solo/productivity_metrics", 
    value: { 
      coding_hours_per_week: 20,
      features_completed_per_month: 8,
      bugs_found_per_feature: 2,
      learning_hours_per_week: 5,
      satisfaction_score: 8.5
    } 
  }

Remember: As a solo developer, you are the entire team. Claude Flow helps you coordinate all aspects of development efficiently, from planning to deployment, while maintaining high quality and continuous learning!

Clone this wiki locally