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 Time Travel Game Evolves from Prompt to Full Deployed System
A Reddit user describes evolving a time travel RPG prompt in Claude into a complex system over 40 days, adding YAML state files, 50+ NPCs, event triggers, and eventually deploying it on Fly with a database and custom MCP server for cross-platform access.

Multi-agent setup triggers $3,400 in charges due to hallucination loop
A developer hardcoded a corporate virtual card into environment variables for testing a multi-agent MCP setup, resulting in $3,400 in charges when a primary agent got stuck in a hallucination loop that spun up new paid proxy instances every 45 seconds for 14 hours.

OpenClaw on Synology NAS: Telegram Media Requests and Container Management
A user reports running OpenClaw on a Synology NAS alongside media stack containers like Plex, Sonarr, Radarr, and SABnzbd. They use it for Telegram-based movie requests and automated NAS troubleshooting tasks.

Using MCP Servers to Connect Claude to Live Databases for On-Demand Analysis
A developer built an MCP server for CybersecTools, connecting Claude to a database of 10,000+ cybersecurity products, enabling live data analysis instead of traditional dashboards. The server provides 40 tools for comparing vendors, analyzing market categories, and checking NIST CSF 2.0 coverage.