corsair
corsairdev/corsair/CLAUDE.md
docs.corsair.dev/llm-gateway. ## Product note The hosted product moved from `corsairdev/hosted` to `corsairdev/hub`. `hosted` receives documentation updates only
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.
corsairdev/corsair/CLAUDE.md
docs.corsair.dev/llm-gateway. ## Product note The hosted product moved from `corsairdev/hosted` to `corsairdev/hub`. `hosted` receives documentation updates only
No other project uses it yet
mauriceboe/TREK/CLAUDE.md
layout) · `server/src/app-config/README.md` (env parsing quirks) · `plugin-sdk/README.md` (plugin author guide). - `wiki/` — end-user documentation. `Dockerfile` / `docker-compose*.yml` — the deployment path and the local S3 test stack
mauriceboe/TREK/plugin-sdk/CLAUDE.md
parity gates fail closed; version/compat checks fail **closed** on unknown host versions. A subtlety documented in `src/permissions.ts`: ctx methods fail loudly at call time, but hooks/events/jobs are gated *before
mauriceboe/TREK/server/CLAUDE.md
# CLAUDE.md Scope: the **`@trek/server`** workspace. See the repo-root `CLAUDE.md` for the monorepo picture
mauriceboe/TREK/shared/CLAUDE.md
schema. Don't "tidy up" a schema to be stricter than the contract it documents. **Response schemas** (` ResponseSchema`, with the row schemas they are built from) describe what a route
Bash-it/bash-it/CLAUDE.md
ensures scripts work regardless of user's shell options ## Project Planning & Roadmaps Strategic planning documents are maintained in `docs/plans/`: - **[Quick Reference](docs/plans/bash-it-quick-reference.md)** - TL;DR summary of current issues and action
storytold/lightcraft/CLAUDE.md
fallback (`unwrap_or…`) only where it can't silently corrupt a document. An unfinished feature returns an "unsupported" error or is disabled. Sole exception: a provably infallible literal, as `#[allow
grokability/snipe-it/CLAUDE.md
build`, `npm run dev`, or `composer run dev`. Ask them. ## Documentation Files - You must only create documentation files if explicitly requested by the user. ## Replies - Be concise in your explanations
Steady15 mentions in 2 weeks
No other project uses it yet
yusufkaraaslan/Skill_Seekers/CLAUDE.md
claude.ai/code) when working with code in this repository. ## Project Overview **Skill Seekers** converts documentation from 18 source types into production-ready formats for 21+ AI platforms (LLM platforms
d2phap/ImageGlass/source/CLAUDE.md
# ImageGlass v10 ## Project Overview ImageGlass v10 is a complete rewrite in **C# with .NET
electron-userland/electron-builder/CLAUDE.md
tokens, cloud credentials, code-signing certs, update-manifest keys) must come from explicit configuration. Documented env-var inputs such as `CSC_LINK`, `GH_TOKEN` and `KEYGEN_TOKEN` count as explicit
mauriceboe/NOMAD/CLAUDE.md
layout) · `server/src/app-config/README.md` (env parsing quirks) · `plugin-sdk/README.md` (plugin author guide). - `wiki/` — end-user documentation. `Dockerfile` / `docker-compose*.yml` — the deployment path and the local S3 test stack
Steady6 mentions in 2 weeks
2 projects use a version of this
mauriceboe/NOMAD/plugin-sdk/CLAUDE.md
parity gates fail closed; version/compat checks fail **closed** on unknown host versions. A subtlety documented in `src/permissions.ts`: ctx methods fail loudly at call time, but hooks/events/jobs are gated *before
Steady6 mentions in 2 weeks
2 projects use a version of this
mauriceboe/NOMAD/shared/CLAUDE.md
schema. Don't "tidy up" a schema to be stricter than the contract it documents. ## Rules for new contracts The parity rule governs **existing** routes; it is not a license
Steady6 mentions in 2 weeks
2 projects use a version of this
e2b-dev/E2B/CLAUDE.md
changeset text. When changing user-facing behavior of the SDKs or CLI, document it in e2b-dev/docs where applicable by updating or adding the relevant guide pages
moonD4rk/HackBrowserData/CLAUDE.md
t.TempDir()` for filesystem tests, `go-sqlmock` for database tests - **Architecture**: see `rfcs/` for design documents ## Key Constraints - `modernc.org/sqlite` pinned at v1.31.1 (v1.32+ requires Go 1.21) - `golang.org/x/text` will
AndyMik90/Aperant/CLAUDE.md
definition files │ │ └── utils/ # ANSI sanitizer, shell escape, provider detection │ └── types/ # TypeScript type definitions ├── guides/ # Documentation └── scripts/ # Build and utility scripts ``` ## Commands Quick Reference ### Setup ```bash npm run install:all # Install
benbjohnson/litestream/CLAUDE.md
CLAUDE.md - Claude Code Configuration Claude-specific optimizations for Litestream. See [AGENTS.md](AGENTS.md) for project documentation. ## Critical Coding Rules - **Always return errors, never log and continue.** The only exception is DEBUG
Steady7 mentions in 2 weeks
No other project uses it yet
apache/dolphinscheduler/dolphinscheduler-master/CLAUDE.md
Adding a new coordination primitive → put the key scheme in `server.master.cluster` and document it. - **Failover is the highest-risk code path**. Any change in `server.master.failover` must be exercised against `AbstractMasterIntegrationTestCase
No other project uses it yet
fathah/hermes-desktop/CLAUDE.md
essence is always captured. ```markdown # Good Section Brief overview of what this section documents and why it matters. More detail can go in subsequent paragraphs, code blocks, or lists. ## Child
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.