How real projects brief Claude Code: the commands, conventions and warnings they put in CLAUDE.md.
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
AnthropicCLAUDE.mdanthropics/claude-for-legal/employment-legal/CLAUDE.md
policy draft — suppress the internal narration. Specifically: - Work-product header: KEEP (it protects the document) - ⚠️ Reviewer note: KEEP (it's the one place the reviewer finds what they need before
Steady3 mentions in 2 weeks
No other project uses it yet
AnthropicCLAUDE.mdanthropics/claude-for-legal/ip-legal/CLAUDE.md
prior-art skills work from user-supplied references; no automated literature pull | | Document storage (Drive / SharePoint / Box) | [PLACEHOLDER ✓/✗] | User uploads agreements and exhibits directly for each review | | Slack | [PLACEHOLDER ✓/✗] | Alerts
Steady3 mentions in 2 weeks
No other project uses it yet
AnthropicCLAUDE.mdanthropics/claude-for-legal/law-student/CLAUDE.md
real client facts into a study tool. --- ## Available integrations | Integration | Status | Fallback if unavailable | |---|---|---| | Document storage (Google Drive / SharePoint / Box / Dropbox) | [✓ / ✗] | Outputs save to local files in plugin directory
Steady3 mentions in 2 weeks
No other project uses it yet
AnthropicCLAUDE.mdanthropics/claude-for-legal/legal-builder-hub/CLAUDE.md
does not exist in most other legal systems — asserting it on a document does not create it. In the EU, there is no general work-product protection for internal legal
Steady3 mentions in 2 weeks
No other project uses it yet
AnthropicCLAUDE.mdanthropics/claude-for-legal/legal-clinic/CLAUDE.md
Clio (case management) | [✓ / ✗] | Case metadata captured in local intake / status files; no auto-sync | | Document storage (Google Drive / SharePoint / Box) | [✓ / ✗] | Student outputs save to local filesystem; review stays in-plugin
Steady3 mentions in 2 weeks
No other project uses it yet
AnthropicCLAUDE.mdanthropics/claude-for-legal/litigation-legal/CLAUDE.md
unavailable | |---|---|---| | DMS (iManage / NetDocuments) | [✓ / ✗] | Matter docs read from local/cloud paths; no DMS-native profiling | | Document storage (Google Drive / SharePoint / Box) | [✓ / ✗] | Manual file paths; matter folders local only | | Gmail | [✓ / ✗] | Correspondence pulled
Steady3 mentions in 2 weeks
No other project uses it yet
AnthropicCLAUDE.mdanthropics/claude-for-legal/privacy-legal/CLAUDE.md
team / outside firm / N/A if a lawyer] --- ## Available integrations | Integration | Status | Fallback if unavailable | |---|---|---| | Document storage (Drive / SharePoint) | [PLACEHOLDER ✓/✗] | Outputs saved locally; policy-monitor sweep runs in direct-query mode
Steady3 mentions in 2 weeks
No other project uses it yet
AnthropicCLAUDE.mdanthropics/claude-for-legal/product-legal/CLAUDE.md
Launch tracker (Jira / Linear / Asana) | [PLACEHOLDER ✓/✗] | User pastes or links PRDs directly per review | | Document storage (Drive / SharePoint) | [PLACEHOLDER ✓/✗] | Review memos saved locally; seed-doc pulls done manually | | Slack | [PLACEHOLDER
Steady3 mentions in 2 weeks
No other project uses it yet
AnthropicCLAUDE.mdanthropics/claude-for-legal/regulatory-legal/CLAUDE.md
Regulatory feeds (paid subscription) | [✓ / ✗] | Free Federal Register API + user-pasted alerts; no enrichment layer | | Document storage (Google Drive, SharePoint, Box) | [✓ / ✗] | Policy library indexed from local paths | | Slack | [✓ / ✗] | Digests emitted
Steady3 mentions in 2 weeks
No other project uses it yet
saulpwCLAUDE.mdsaulpw/visidata/CLAUDE.md
apps/ # Standalone applications │ └── experimental/ # Experimental features (load/install with 'import visidata.experimental.foo') ├── tests/ # Test files ├── docs/ # Documentation └── dev/ # Development utilities and docs ``` ## Features Directory (`visidata/features/`) - All `.py` files in this directory
No other project uses it yet
TelegramMessengerDeletes or force-pushesCLAUDE.mdTelegramMessenger/Telegram-iOS/CLAUDE.md
Swift/Objective-C formatting and spacing - **Types**: Prefer strong typing and explicit type annotations where needed - **Documentation**: Document public APIs with comments ## Project Structure - Core launch and application extensions code
Steady3 mentions in 2 weeks
No other project uses it yet
nhostCLAUDE.mdnhost/nhost/CLAUDE.md
Hybrid Go + TypeScript monorepo containing Nhost's open-source services, SDK, CLI, dashboard, and documentation. Uses Nix for Go builds and pnpm + Turbo for JS/TS workspaces. **Important**: Each project
No other project uses it yet
nhostReads credentialsCLAUDE.mdnhost/nhost/dashboard/CLAUDE.md
Load that first. Only dashboard workflows (commands, navigation wiring, specific helpers and references) are documented below. This document covers commands, project layout, and dashboard-specific workflows not captured
No other project uses it yet
caorushiziCLAUDE.mdcaorushizi/mediago/CLAUDE.md
serves `/player/` but suppresses the embedded main UI because Electron owns the main renderer. ## Documentation Site Safety `docs/` is the production VitePress source directory. Everything placed there can be packaged
JetBrainsCLAUDE.mdJetBrains/Exposed/CLAUDE.md
critical - breaking changes require major version bump - Use `@InternalApi` annotation for internal implementation details - Document breaking changes in BREAKING_CHANGES.md under "Breaking changes" section ## Code Style and Conventions ### Style Configuration - **EditorConfig
Steady22 mentions in 2 weeks
No other project uses it yet
bigbluebuttonCLAUDE.mdbigbluebutton/bigbluebutton/docs/CLAUDE.md
interact, assert await browser.close(); ``` ## Source of truth When updating tables/values that document server behaviour (e.g. the "Other meeting configs available" table in `administration/customize.md`), cross-reference: - `bigbluebutton-web/grails-app/conf/bigbluebutton.properties` — authoritative
davidkimaiCLAUDE.mddavidkimai/Context-Engineering/CLAUDE.md
CLAUDE.md - Cognitive Operating System This document provides a comprehensive framework of cognitive tools, protocol shells, reasoning templates, and workflows for Claude Code. Load this file in your project root
HypothesisWorksCLAUDE.mdHypothesisWorks/hypothesis/.claude/CLAUDE.md
unnecessary verbosity - **Idiomatic** - follows Python and Hypothesis conventions - **Minimally commented** - code should be self-documenting; only add comments where truly needed - **Module-scope imports** - put imports
No other project uses it yet
anyprotoReads credentialsCLAUDE.mdanyproto/anytype-ts/CLAUDE.md
business logic - **gRPC Middleware** - Backend logic (separate anytype-heart repository) - **Block-based Editor** - Document editing with composable blocks ### Frontend Architecture (src/ts/) **Entry Points:** - `entry.tsx` - Application entry point - `app.tsx` - Main React
Steady2 mentions in 2 weeks
No other project uses it yet
CoreBunchDeletes or force-pushesCLAUDE.mdCoreBunch/Instatic/CLAUDE.md
src/ui/ Shared UI primitives (Button, Input, Tree, icons, cn) src/styles/ Global tokens (globals.css) docs/ Documentation (start at docs/README.md) examples/ Plugin templates vendor/ Vendored pixel-art-icons package ``` Source of truth
A file Claude Code reads at the start of every session. It holds the commands, conventions and warnings the agent needs for this project.
At the repository root. Claude Code also reads CLAUDE.md files in subdirectories when it works there.
Build and test commands, the project's layout, conventions that aren't obvious from the code, and mistakes to avoid. Short files tend to work better than long ones.
Claude Code reads CLAUDE.md; most other agents read AGENTS.md. Many projects keep one and point the other at it.
