poml
microsoft/poml/CLAUDE.md
watch-extension # Watch mode for extension npm run watch # Watch mode for TypeScript compilation ``` ### Testing Commands ```bash npm test # Run all Jest tests npm run test-vscode # Run VS Code
How real projects brief Claude Code: the commands, conventions and warnings they put in CLAUDE.md.
microsoft/poml/CLAUDE.md
watch-extension # Watch mode for extension npm run watch # Watch mode for TypeScript compilation ``` ### Testing Commands ```bash npm test # Run all Jest tests npm run test-vscode # Run VS Code
microsoft/poml/packages/poml-browser/CLAUDE.md
builds npm run build:prod # Build for production npm run zip # Alias for package # Testing npm run build:test # Build for testing npm run test:vitest # Run unit tests with
microsoft/FluidFramework/server/gitrest/CLAUDE.md
whole-summary read/write - `src/runner.ts` / `src/runnerFactory.ts` — Service runner - `src/app.ts` — Express app setup - `src/test/` — Mocha tests ## Build & Dev ```shell # Install dependencies pnpm install # Build all packages pnpm run build # Build without linting
microsoft/FluidFramework/server/historian/CLAUDE.md
historian-base. - **`@fluidframework/historian-base`** (`packages/historian-base`) — Core logic: routes, services, runner, and customizations (`src/`). Contains tests under `src/test/`. ## Build & Dev - **Package manager:** pnpm (v11.27.0). Do not use npm install. - **Node:** >=22.22.2 - **Build
aipotheosis-labs/aci/CLAUDE.md
head # Apply migrations docker compose exec runner alembic revision --autogenerate -m "description" # Create migration # Testing and quality docker compose exec test-runner pytest # Run tests ruff format . # Format code ruff
formkit/formkit/CLAUDE.md
exports CLI binary - **dev**: Internal dev utilities ## Commands ```bash pnpm build # Build packages pnpm test # Run vitest (interactive/watch mode) npx vitest run # Run tests once (non-interactive) pnpm
formkit/formkit/.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
conorbronsdon/avoid-ai-writing/CLAUDE.md
coding assistants; the repository also includes a dependency-free deterministic detector and test suite. ## Repository structure - `SKILL.md` — entry instructions, severity tiers, preservation rules, and output formats. - `references/patterns.md` — canonical word tiers
eugeniughelbur/obsidian-second-brain/CLAUDE.md
section + command list) and `README.md` (commands table). 6. Add a `CHANGELOG.md` entry under "Unreleased". ## Testing locally Symlink the local checkout into Claude Code so slash commands run from this repo
JetBrains/koog/a2a/CLAUDE.md
protocol messages - **ktor3**: HTTP client/server for transport implementations - **oshai-kotlin-logging**: Structured logging ### Testing Libraries - **kotlin-test**: Multiplatform test framework - **kotest-assertions**: Rich assertion library for complex objects - **kotlinx-coroutines
JetBrains/koog/examples/simple-examples/CLAUDE.md
example ./gradlew runExampleCalculator ./gradlew runExampleStreamingWithTools ./gradlew runExampleRoutingViaGraph # Build the project ./gradlew assemble # Run tests ./gradlew test ``` All available tasks follow the pattern `runExample*`. See `build.gradle.kts` for the complete list. ## Project
supabase/supabase-js/.claude/CLAUDE.md
detailed information: > > - **[CONTRIBUTING.md](../CONTRIBUTING.md)** - Development guidelines, commit format, PR process > - **[TESTING.md](../docs/TESTING.md)** - Complete testing guide with Docker requirements > - **[RELEASE.md](../docs/RELEASE.md)** - Release workflows and versioning strategy > - **[MIGRATION.md](../docs/MIGRATION.md)** - Cross-cutting migration
0xNyk/council-of-high-intelligence/CLAUDE.md
Reference tables (triads, profiles, polarity pairs) are above the execution sequence, not mixed in ### Testing - Always run `./scripts/council-simulation-checklist.sh` after changes - Always run `./install.sh --dry-run` to verify installation - When changing
stripe/stripe-node/.claude/CLAUDE.md
stripe-node ## Testing - Run all tests: `just test` (builds first) - Run a specific test: `just test --grep "test name pattern"` - Run type tests: `just types-test` (builds first, then type
pydantic/logfire/CLAUDE.md
config file handling │ ├── tracer.py # ProxyTracerProvider, tracer wrapping │ ├── metrics.py # ProxyMeterProvider, metrics handling │ ├── exporters/ # OTLP, console, test exporters and processors │ ├── integrations/ # Framework-specific instrumentation │ ├── auto_trace/ # AST rewriting for auto-instrumentation │ └── ... ├── integrations
pydantic/logfire/docs/integrations/agent-frameworks/CLAUDE.md
conversation data unless the example emitted it in a real run. ## Verification before publishing - Test the sample against current package releases using the exact installation and run commands
embabel/embabel-agent/CLAUDE.md
push. You may use git tools for history, diffing or staging only. ALWAYS work test first. When making an enhancement or fixing a bug, write failing tests first, then implement
macro-inc/macro/CLAUDE.md
develop the repository. | ## Read when relevant | Task | Guide | | --- | --- | | Rust code, builds, or tests | [Rust development](docs/RUST_DEVELOPMENT.md) | | SQLx queries, migrations, DB tests, or cache errors | [Database development](docs/DATABASE_DEVELOPMENT.md) | | Web frontend
vijaythecoder/awesome-claude-agents/CLAUDE.md
Information" - Specify what context next specialist needs - Main agent will parse and coordinate 3. **Testing Agents**: - Test invocation patterns - Verify delegation works correctly - Ensure quality of output ## Important Files
IvanMurzak/Unity-MCP/CLAUDE.md
modelcontextprotocol.io/). Sub-projects: `Unity-MCP-Plugin/` (Unity Editor/Runtime plugin), `cli/`, `Installer/`, `Unity-Tests/`. The MCP server is NOT in this repo — the plugin consumes the shared [GameDev-MCP-Server
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.