CLAUDE.md examples from real projects

FujiwaraChokiReads credentialsCLAUDE.md

MoneyPrinter

FujiwaraChoki/MoneyPrinter/CLAUDE.md

python -m compileall Backend # syntax check curl http://localhost:8080/api/models # API smoke test ``` ### Tests No test suite exists yet. If added, use pytest: ```bash uv run pytest -q # all tests

qazbnm456Reads credentialsCLAUDE.md

awesome-web-security

qazbnm456/awesome-web-security/CLAUDE.md

skills/awesome-web-security/` so AI agents can query the list at runtime. No build, no test suite, no application runtime. Every change is either YAML data, Python tooling, or Markdown docs. ## Files

No other project uses it yet

Open-LLM-VTuberCLAUDE.md

Open-LLM-VTuber

Open-LLM-VTuber/Open-LLM-VTuber/CLAUDE.md

upgrade system for breaking changes - Validate configurations in respective config manager classes ## Testing and Quality Assurance The project uses: - **Ruff** for linting and formatting (configured in `pyproject.toml`) - **Pre-commit hooks

No other project uses it yet

formkitReads credentialsCLAUDE.md

auto-animate

formkit/auto-animate/.dmux-hooks/CLAUDE.md

with `#!/bin/bash` 4. **Use environment variables**: Access `$DMUX_ROOT`, `$DMUX_WORKTREE_PATH`, etc. 5. **Test it**: Set env vars manually and run the script ## Hook Execution Model - **Non-blocking**: Hooks

OpenNHPReads credentialsCLAUDE.md

opennhp

OpenNHP/opennhp/CLAUDE.md

support (requires clang) make ebpf # Build plugins make plugins # Initialize/tidy modules make init ``` ## Running Tests ```bash # Run tests in the nhp module cd nhp && go test ./... # Run tests

EverMind-AICLAUDE.md

EverOS

EverMind-AI/EverOS/CLAUDE.md

make lint # ruff (check + format-check) + import-linter make format # auto-fix formatting make test # pytest tests/unit make integration # pytest tests/integration make ci # full CI: lint + test + integration ``` ## Architecture

browserlessReads credentialsCLAUDE.md

browserless

browserless/browserless/CLAUDE.md

then starts with .env config) npm run dev # Start without rebuilding npm start # Run tests (builds test artifacts first) npm run test # Run single test file npx mocha build/path/to/file.spec.js # Lint

No other project uses it yet

borgbackupCLAUDE.md

borg

borgbackup/borg/.claude/CLAUDE.md

Python), a pyinstaller-made binary is meant: - POSIX: `pyinstaller --clean --distpath=dist/binary/ scripts/borg.exe.spec` ## Writing tests Always write pytest-style tests unless unittest-style is explicitly required. ## Writing docstrings, comments, documentation

No other project uses it yet

glideappsDeletes or force-pushesCLAUDE.md

quicktype

glideapps/quicktype/CLAUDE.md

node dist/index.js --help ``` For live rebuild/re-run while developing renderer output, use: ```bash npm start -- " " ``` ## Testing ### Test strategy quicktype's primary testing method is end-to-end fixture tests driven

No other project uses it yet

EverMind-AICLAUDE.md

EverMemOS

EverMind-AI/EverMemOS/CLAUDE.md

make lint # ruff (check + format-check) + import-linter make format # auto-fix formatting make test # pytest tests/unit make integration # pytest tests/integration make ci # full CI: lint + test + integration ``` ## Architecture

coleam00Pipes a download into a shellCLAUDE.md

context-engineering-intro / claude-code-full-guide

coleam00/context-engineering-intro/claude-code-full-guide/CLAUDE.md

pyproject.toml - **Use venv_linux** (the virtual environment) whenever executing Python commands, including for unit tests. ### Project Architecture Follow strict vertical slice architecture with tests living next to the code they

coleam00CLAUDE.md

context-engineering-intro

coleam00/context-engineering-intro/CLAUDE.md

PLANNING.md`. - **Use venv_linux** (the virtual environment) whenever executing Python commands, including for unit tests. ### 🧱 Code Structure & Modularity - **Never create a file longer than 500 lines of code

StarTrail-orgPipes a download into a shellCLAUDE.md

LEANN

StarTrail-org/LEANN/CLAUDE.md

README) uv sync --extra diskann # Install lint tools uv sync --group lint # Install test tools uv sync --group test ``` ## Code Quality ```bash # Format code ruff format # Lint with auto

Model Context ProtocolCLAUDE.md

typescript-sdk

modelcontextprotocol/typescript-sdk/CLAUDE.md

words are true** — Changesets, docs and comments say what the code does. 7. **Test what users see** — Prefer tests that cover the end-to-end usage a user would actually

No other project uses it yet

Model Context ProtocolCLAUDE.md

typescript-sdk / e2e

modelcontextprotocol/typescript-sdk/test/e2e/CLAUDE.md

test suite Conformance-style tests for the SDK's public surface. `requirements.ts` is a pure-data manifest: every behavior the SDK must satisfy, with its spec/source link. Test files

No other project uses it yet

plasma-umassReads credentialsCLAUDE.md

scalene

plasma-umass/scalene/CLAUDE.md

native/C time **Platform support:** Linux, macOS, WSL 2 (full support); Windows (partial support) ## Build & Test Commands ```bash # Install in development mode pip install -e . # Run all tests python3 -m pytest

No other project uses it yet

ccfosCLAUDE.md

nightingale

ccfos/nightingale/CLAUDE.md

build ./...` works without running `fe.sh`. ## Commands ```bash go build ./... # ~1 min cold; also verifies tests compile go test ./... # in-memory sqlite (github.com/glebarez/sqlite), no external services ./n9e --configs etc.local # etc.local

mrexodiaCLAUDE.md

ida-pro-mcp

mrexodia/ida-pro-mcp/CLAUDE.md

signature creation, scanning, xref signatures (uses sigmaker.py) - `api_debug.py`: debugger control, unsafe / low priority for tests - `api_python.py`: execute Python in IDA context - `api_resources.py`: `ida://` MCP resources ## Core implementation rules ### IDA thread

cheatCLAUDE.md

cheat

cheat/cheat/CLAUDE.md

binaries for all platforms make build-release # Install cheat to your PATH make install ``` ### Testing and Quality Checks ```bash # Run all tests make test go test ./... # Run a single test

maxrave-devReads credentialsCLAUDE.md

SimpMusic

maxrave-dev/SimpMusic/CLAUDE.md

Gradle build when explicitly requested by the user or for final release verification. ### Testing - Unit tests for Domain layer (Use cases) - Repository tests with fake data sources - UI tests with