Claude Code Workflow Visual: Memory Hierarchy, Skills, Hooks, and Loop
A Reddit user shared a workflow visual that maps out how Claude Code's components fit together: CLAUDE.md, memory hierarchy, skills, hooks, project structure, and the workflow loop.
Memory Layering
The visual clarifies context loading order:
~/.claude/CLAUDE.md→ global memory/CLAUDE.md→ repo context./subfolder/CLAUDE.md→ scoped context
Subfolders append context, not replace it. This explains why sessions can feel overloaded when those files grow large.
Skills
Instead of repeating prompts, define reusable patterns in .claude/skills/. Examples:
.claude/skills/testing/SKILL.md .claude/skills/code-review/SKILL.md
Claude auto-invokes skills when the description matches.
Workflow Loop
The recommended loop:
cd project && claude Plan mode Describe feature Auto accept /compact commit frequently
No single element is groundbreaking, but seeing it all together helps organize Claude Code usage.
The ecosystem is still evolving, and workflows remain personal.
📖 Read the full source: r/ClaudeAI
👀 See Also
OpenClaw installation hurdles on Windows 11 for non-developers
A recreational tinkerer details three specific obstacles when installing OpenClaw on a $200 Mini PC running Windows 11, including PowerShell execution policies, Windows Defender blocks, and missing dependencies like Node.js and Git.
OpenClaw setup tips from a user's experience: Gmail MCP, profile flags, and networking issues
A user running OpenClaw on a Mac via UTM with Ubuntu VM shares specific configuration issues encountered: the Gmail MCP server requires html_body instead of body parameter, the --profile prod flag is needed to avoid a hardcoded dev identity, and API keys must be placed in auth-profiles.json via paste-token command.
End-to-End LLM Stack Trace: From Keystroke to Streamed Token
A software engineer has created a comprehensive document tracing every layer of the stack when sending a prompt to an LLM, covering client-side token counting, network protocols, API gateways, safety classifiers, tokenization, KV cache, sampling pipeline, and streaming mechanics.
Documentation for Writing MCP Tools in C# .NET Framework for Claude Desktop/Code
Complete documentation and C# coding examples for creating custom MCP tools using .NET Framework 4.8, enabling Claude Desktop/Code to automate interactions with external processes, software, APIs, and IoT devices.