Source instructions onlyA profile for configuring CLAUDE.md so Claude Code starts with the right project memory.

Install or setup path

Install Claude Code first, then use /init and the official memory docs to create and refine the CLAUDE.md files that should persist across sessions.

No verified install command on this page

This profile is useful for evaluation and workflow context, but WhichAITools did not verify one direct install command for it. Use the linked source instructions instead of guessing.

Use this profile for

Developers and teams who want Claude Code to boot into a repo with the correct context, constraints, and workflow expectations already loaded.

Primary categorySkill Authoring
Source count3
OpenClaw relevantNo

What it does

This profile explains CLAUDE.md as Claude Code's persistent project memory layer and shows how to split instructions between global `~/.claude/CLAUDE.md` and a project-level `CLAUDE.md`. It helps teams decide what belongs in shared repository context, what belongs in personal defaults, and how `/init` fits into the setup flow.

Best for

Developers and teams who want Claude Code to boot into a repo with the correct context, constraints, and workflow expectations already loaded.

Why it stands out

Instead of treating CLAUDE.md like a random notes file, it frames it as a scoped memory system with clear hierarchy and maintenance rules.

Adopt this skill carefully

Return to the parent path

Move back to the category or hub instead of jumping to the homepage and losing context.

Cross-check the method

Review methodology and manuals before treating a public profile or copied command like production-ready guidance.

Use the surrounding workflow hub

When the profile belongs to OpenClaw operations, continue inside the OpenClaw cluster instead of starting over.

Safety notes

  • Do not put API keys, passwords, or other secrets in any CLAUDE.md file.
  • Keep personal preferences in `~/.claude/CLAUDE.md` and repo-specific rules in the project file so unrelated projects do not inherit the wrong context.
  • Review CLAUDE.md after major workflow or architecture changes so stale instructions do not mislead future sessions.

Source context

This profile is based on Anthropic's first-party Claude Code docs for memory, setup, and best practices. Those pages define where CLAUDE.md files live, how they load, and how /init scaffolds a starter file, so the guidance is anchored in the product's native behavior rather than community folklore.

Claude Code overviewHow Claude remembers your projectBest Practices for Claude Code

Related profiles

Claude Code Skills Packages

Use this profile when you are comparing Claude Code skill collections and need a clear mental model for what a package is, how SKILL.md-based bundles work, and how to evaluate them before installation.

Subagents Workflow

Use this profile when one Claude Code session is becoming a bottleneck and the work can be split into parallel, scoped subtasks with cleaner context boundaries.

Skill Authoring Blueprint

Use this profile when the goal is to turn repeated prompts into stable, reviewable skills rather than one-off automation sprawl.