Reddit user shares Claude Code setup for portfolio projects

✍️ OpenClawRadar📅 Published: April 15, 2026🔗 Source
Reddit user shares Claude Code setup for portfolio projects
Ad

From manual workflow to structured Claude Code

A developer on r/ClaudeAI shared their experience moving from a cumbersome manual workflow to a more organized Claude Code setup. They previously used Claude.ai for personal projects with what they described as a "pretty janky system" involving constant copy-pasting between chats.

The old workflow

Their previous approach involved:

  • One permanent "main chat" for planning architecture, phases, and build order
  • Creating new chats for each feature implementation
  • Manually copying implementation prompts between chats
  • Pushing to GitHub and adding repo + summary as Project Knowledge
  • Returning to main chat to repeat the process

They noted this was "exhausting" due to constant copy-pasting, re-explaining context, and manually maintaining summary files.

The new Claude Code structure

After exploring Claude Code, they developed this file structure:

~/.claude/CLAUDE.md # personal prefs, use plan mode for new features
project/
├── .claude/CLAUDE.md # router — what to read on startup, when to write what
├── architecture.md # decisions, patterns, system design
├── roadmap.md # phases and status
└── phases/
    └── phase1/
        ├── phase_plan.md # before work starts
        └── phase_summary.md # when phase is done

The project CLAUDE.md file tells Claude to:

  • Load architecture and roadmap first
  • Use plan mode before touching any new feature
  • Write the phase plan before starting
  • Write the summary when done
Ad

Motivation and approach

The developer is building portfolio projects they want to "actually understand and be able to talk about in interviews, not just ship and forget." They emphasize that plan mode forces them to think through decisions before Claude writes anything, and the phase documentation ensures they always know what was built and why.

Questions raised

The post asks several practical questions for the community:

  • Whether others are using similar file-based memory approaches or completely different systems
  • If the Frontend plugin and Superpowers plugin are actually useful or overhyped
  • Which MCP servers have actually changed how people work day to day
  • How to ensure actual learning rather than just watching Claude code when building portfolio projects
  • Requests to see other people's setups, especially CLAUDE.md snippets

📖 Read the full source: r/ClaudeAI

Ad

👀 See Also

User Reports $868 AUD OpenClaw Bill, Duplicate Sessions, and Breakage After Updates
Use Cases

User Reports $868 AUD OpenClaw Bill, Duplicate Sessions, and Breakage After Updates

A user spent $868 AUD on OpenClaw + Claude Sonnet in a month. They discovered duplicated Telegram polling sessions causing double agent runs, duplicate tool calls, and 2x token billing. Two major updates broke their setup, requiring manual config edits.

OpenClawRadar
Claude Code Agent Orchestrator Architecture for Multi-Agent Systems
Use Cases

Claude Code Agent Orchestrator Architecture for Multi-Agent Systems

The Ultrathink team runs an AI-operated store where 6 Claude Code agents handle design, code, marketing, and operations. Their orchestrator agent coordinates work across specialized agents, handles failures, and ships code to production automatically.

OpenClawRadar
User Deploys AI Assistant 'Elvis' on VPS for Project Management Tasks
Use Cases

User Deploys AI Assistant 'Elvis' on VPS for Project Management Tasks

A developer spent three days setting up an AI assistant called 'Elvis' on a Linux VPS, integrating it with Microsoft Teams, JIRA, Asana, and email systems. The assistant successfully handled project management tasks including reading emails, extracting requirements, updating change requests, and coordinating with team members.

OpenClawRadar
How a React useEffect Bug Caused Random Haptic Feedback and Tanked App Retention
Use Cases

How a React useEffect Bug Caused Random Haptic Feedback and Tanked App Retention

A developer ignored user reports of random app vibrations for months, only to discover a React useEffect dependency issue was causing constant haptic feedback on mid-range devices, dropping 7-day retention from 35% benchmark to 18%.

OpenClawRadar