glances
nicolargo/glances/CLAUDE.md
YOUR changes made unused. - Don't remove pre-existing dead code unless asked. The test: Every changed line should trace directly to the user's request. ## 4. Goal-Driven Execution
No other project uses it yet
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.
nicolargo/glances/CLAUDE.md
YOUR changes made unused. - Don't remove pre-existing dead code unless asked. The test: Every changed line should trace directly to the user's request. ## 4. Goal-Driven Execution
No other project uses it yet
davila7/claude-code-templates/CLAUDE.md
Rust port of the install core) is **in the backlog**: do not plan, change, test parity with or mention it unless Daniel resumes it. ## Essential Commands ```bash # Development npm install
davila7/claude-code-templates/docs/CLAUDE.md
docs/components.json` 3. Commit changes: ```bash git add docs/components.json git commit -m "Update component catalog" ``` ### Testing Locally Before committing: 1. Serve site locally: `python -m http.server 8000` 2. Test component loading
Steady15 mentions in 2 weeks
No other project uses it yet
k1tbyte/Wemod-Patcher/CLAUDE.md
Vite, bridge bundle, `verify:dist` - `cd web-panel; pnpm exec vitest run ` - one web test - `build.cmd -EnableUpdateNotifications` - the opt-in update-check variant ## Rules `.claude/rules/` holds the working rules. Claude
1 project uses a version of this
topoteretes/cognee/CLAUDE.md
GLiNER client and `EMBEDDING_PROVIDER=embedding_worker` alike (`docs/embedding-worker.md`) - **evals** - Evaluation tools - **deepeval** - DeepEval testing framework - **posthog** - PostHog analytics - **tracing** - OpenTelemetry tracing - **dev** - All development tools (pytest, ty, ruff
surrealdb/surrealdb/CLAUDE.md
code (REQUIRED before commits) cargo make fmt # Run clippy lints cargo make ci-clippy ``` ## Testing Conventions Language tests, upgrade tests, and benchmarks: `language-tests/CLAUDE.md`. Parser tests: `surrealdb/parser-next/CLAUDE.md`. ### Keep
Steady2 mentions in 2 weeks
No other project uses it yet
surrealdb/surrealdb/language-tests/CLAUDE.md
CLAUDE.md Conventions for the SurrealQL test suite in `language-tests/`. ## Commands ```bash # Run language tests cd language-tests && cargo run run # Run specific language test # Note: all paths are relative
No other project uses it yet
surrealdb/surrealdb/surrealism/CLAUDE.md
wasm32. Accepts Sigstore bundle v0.3 (Rekor v2 + RFC 3161 timestamp) and SSH signatures. | ## Build / Test / Deploy Workflow - **Build:** `surreal ext build` — compiles the Rust project to `wasm32-wasip2`, optimizes with
No other project uses it yet
labstack/echo/CLAUDE.md
Makefile for common development tasks: - `make check` - Run linting, vetting, and race condition tests (default target) - `make init` - Install required linting tools (golint, staticcheck) - `make lint` - Run staticcheck and golint
No other project uses it yet
tirth8205/code-review-graph/CLAUDE.md
code-review-graph/graph.db` (SQLite, WAL mode). ## Key Commands ```bash # Development uv run pytest tests/ --tb=short -q uv run ruff check code_review_graph/ uv run mypy code_review
projectdiscovery/nuclei/CLAUDE.md
designed for zero false positives through real-world condition simulation. ## Development Commands ### Building and Testing - `make build` - Build the main nuclei binary to ./bin/nuclei - `make test` - Run unit tests with
No other project uses it yet
ankitects/anki/CLAUDE.md
Claude Code Configuration > **Note:** Every command you need — building, running, testing, linting, > formatting — is defined as a recipe in the project `justfile`. Run > `just --list` to see them
No other project uses it yet
getzep/graphiti/CLAUDE.md
import sorting + formatting) make format # Lint code (ruff + pyright type checking) make lint # Run tests make test # Run all checks (format, lint, test) make check ``` ### Server Development (run from server
No other project uses it yet
cockroachdb/cockroach/CLAUDE.md
wrapped through the `./dev` tool, which should be preferred to direct `go (build|test)` or `bazel` invocations. ### Essential Commands #### Building a package / package tests This is useful as a compilation
No other project uses it yet
Zackriya-Solutions/meetily/CLAUDE.md
Full Tauri development mode pnpm run tauri:build # Production build # GPU-Specific Builds (for testing acceleration) pnpm run tauri:dev:metal # macOS Metal GPU pnpm run tauri:dev:cuda # NVIDIA
Steady3 mentions in 2 weeks
1 project uses a version of this
decolua/9router/CLAUDE.md
dashboard/compat APIs), `open-sse/` (the provider-agnostic routing/translation engine), `cli/` (the launcher package), and `tests/`. ## Commands Dashboard/gateway (run from repo root): ```bash cp .env.example .env npm install PORT=20128 NEXT
1 project uses a version of this
conductor-oss/conductor/CLAUDE.md
documenting. 2. Read the method signature and required parameters. 3. If a working test exists for that method, use it as the starting point. 4. Write from the signature
No other project uses it yet
vxcontrol/pentagi/CLAUDE.md
overgeneralisation". Keep the invariant the story was there to protect. This applies to test *names* as well as test comments. 6. **No meta-commentary** about why the enum has five
Steady5 mentions in 2 weeks
No other project uses it yet
facebook/rocksdb/CLAUDE.md
lossless_cast from cast_util.h are preferred. * Avoid declared type `auto` (`auto&`, `auto*` OK). ### Testing Philosophy **Comprehensive Coverage:** Every change should include appropriate test coverage. This includes unit tests
No other project uses it yet
hasura/graphql-engine/v3/CLAUDE.md
just to run the tests please ## Aisura / Remote Dev For development on Aisura or shared remote machines, use `compose.isolated.yaml` which supports multiple parallel sessions without port or container conflicts. ### Start
Steady6 mentions in 2 weeks
No other project uses it yet
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.