Reddit user shares Claude Code setup for portfolio projects

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 doneThe 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
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
👀 See Also

Claude Code Agents Orchestrator Pipeline: Work Queues, Agent Spawning, Verification Gates
A Reddit post from r/clawdbot details how Claude Code agents operate an AI-run store, handling design, marketing, QA, and ops 30 times daily. It links to Episode 9 of a blog series that explains the orchestrator pipeline in production, including issues not shown in demos.

Using Claude as a Learning Mentor with Documentation Context
A developer shares a method for using Claude as a learning tool by feeding tool documentation into its context and using a specific prompt to create a task-based mentor. The approach skips traditional courses and tutorials in favor of hands-on learning with immediate feedback.

OpenClaw user builds 10-automation operations stack with sports picks, lead generation, and digital fulfillment
A developer spent two months building an AI operations stack on OpenClaw that includes a daily sports picks pipeline with ESPN data and Twilio delivery, a nightly pick grader, business lead scraping from Google Maps, Stripe pollers for digital products, session briefing emails, and daily ops reports.

Developer builds YouTube news multistream viewer with Claude Code
A developer used Claude Code to build Beholder, a real-time news monitoring dashboard that displays dozens of live YouTube news streams simultaneously with media bias ratings. The tool includes 200+ channels, live news tickers, and works across mobile, tablet, and desktop.