Claude Code STHLM - Meetup #1: Project Structure & Sustainable Memory

Join us for the first Claude Code Stockholm meetup! We're bringing together developers who are exploring agentic coding to share practical knowledge and learn from each other.

What We'll Cover
This session focuses on building a sustainable project structure for Claude Code that scales beyond quick demos. We'll explore how to organize your workspace so that both you and Claude maintain context across sessions, weeks, and even months of development.

The .claude Directory
We'll set up the foundations: the commands/ folder for reusable workflows, the agents/ folder for specialized task handlers, and how these integrate with your CLAUDE,md file to create a consistent development environment.

The docs/ Strategy
Here's where it gets interesting. We'll introduce a docs/ structure with two key components:

• docs/api-docs/ - A place to cache SDK documentation and code examples. Instead of letting Claude fetch the same information repeatedly, we'll show you how to build a local knowledge base that Claude can reference instantly. Think of it as your project's technical library.
• docs/hist/ - Your project diary. This is where you document what happened in each session: decisions made, approaches tried, problems solved. When you return to a project after days or weeks, this becomes invaluable. We'll discuss when to rotate old entries and how to keep this sustainable as your project grows.

MCP Integration with .mcp,json
We'll look at how Model Context Protocol fits into this structure, with practical examples of fetching documentation and extending Claude's capabilities at the project level.

Why This Matters
We have all been there in the beginning. When you start a project, context is easy. Three months in, with multiple features built and dozens of sessions behind you, maintaining that context becomes the challenge. Knowledge dept builds when we develop more than we can manage to keep in our own memory. This session gives you patterns that work for real projects, so you can focus on delivering value without losing context.

Who Should Come

• Beginners wanting to get started with Claude Code
• Developers working with Claude Code who want to level up their workflow
• Teams looking to standardize their agentic coding approach
• Anyone curious about practical patterns for long-term projects

No preparation needed. We'll build examples together and discuss what works in different scenarios.

Beyond Claude Code
While we focus on Claude Code, the principles we'll cover—the docs/ structure, project memory strategies, and cached knowledge—transfer directly to other agentic coding tools like Gemini CLI and Codex CLI. Build these patterns once, use them anywhere.