touchHLE
touchHLE/touchHLE/CLAUDE.md
contributors o= ften fail to read, the project absolutely cannot accept AI-generated code= for legal reasons. Contributors choosing to use AI agents anyway create = problems for us, and this
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.
touchHLE/touchHLE/CLAUDE.md
contributors o= ften fail to read, the project absolutely cannot accept AI-generated code= for legal reasons. Contributors choosing to use AI agents anyway create = problems for us, and this
atopile/atopile/CLAUDE.md
read the correspondig skill. Skills are located in `.claude/skills/`. ``` .claude/skills ├── ato-language │ ├── EXTENSION.md │ └── SKILL.md ├── code-review │ └── SKILL.md ├── compiler │ └── SKILL.md ├── dev │ └── SKILL.md ├── domain-layer │ └── SKILL.md ├── fabll │ └── SKILL.md ├── faebryk │ └── SKILL.md ├── frontend │ └── SKILL.md
openrewrite/rewrite/CLAUDE.md
pass before submitting - Address review comments promptly ## Important Conventions ### Nullability Annotations The project uses JSpecify nullability annotations. ## Conclusion Following these guidelines will help maintain code quality and consistency across
pyvista/pyvista/CLAUDE.md
before writing code, `pyvista-vtk` before wrapping a VTK class or touching a filter, `pyvista-testing` before touching a plotting test or a baseline image, `pyvista-review` before reviewing
samber/cc-skills-golang/CLAUDE.md
concern itself. ```yaml # Bad — triggers on all Go work description: Use when writing code, reviewing style, or writing comments in Golang. # Good — triggers only when style is the actual concern
No other project uses it yet
fern-api/fern/CLAUDE.md
Check container logs - **IR compilation**: `pnpm fern check` → Check circular refs → Review migrations - **Test failures**: Unit (check generated code) | E2E (`pnpm fern:build`) | Lint (`pnpm format:fix`) - **Performance**: Use Turbo
Steady2 mentions in 2 weeks
No other project uses it yet
robusta-dev/holmesgpt/CLAUDE.md
# CLAUDE.md This file provides guidance to Claude Code (claude.ai/code) when working with code
dathere/qsv/CLAUDE.md
clippy` before committing. For feature-gated code, test with the relevant feature flag enabled. ## Code Review Response For Copilot/code review responses: apply the fix, run tests, commit, and reply
Steady7 mentions in 2 weeks
No other project uses it yet
brave/brave-core/.claude/CLAUDE.md
that you need from docs/ using the list at docs/README.md When working directly on code, consult with only relevant best practices listed at docs/best_practices.md ## Design System (Leo / Nala
sozu-proxy/sozu/CLAUDE.md
chunked` (CL.TE smuggling guard in `on_request_headers`, CWE-444). Whitespace around a coding is not ambiguity: kawa >= 0.7.1 excludes OWS from field values (RFC 9112 §5), so `chunked
httpcats/http.cat/CLAUDE.md
with a cat image for each HTTP status code. There's no server-side code: the "API" (e.g. `/404` returning the 404 cat image) is implemented in the Nginx config
Screenly/Anthias/CLAUDE.md
reason (http-to-localhost is a safe `python:S5332` FP). Never contort working code to dodge a rule. - **Run BOTH `ruff check` AND `ruff format --check`** before any Python push
eracle/OpenOutreach/CLAUDE.md
cannot share a label; a namespaced label changes every **table name**, so never hard-code one — ask the model (`Lead._meta.db_table`). This host's own app is namespaced for the same
nextlevelbuilder/goclaw/CLAUDE.md
asks → scout → planner writes → audit-verify → report. **Red-team practice:** After planner completes, run `code-reviewer`/`brainstormer` in audit mode: "spot-check 15+ claims vs live codebase". Past catches: fabricated
p-org/P/CLAUDE.md
workflow with user guidance - `peasy-ai-list-workflows`: List available and active workflows ### PeasyAI Code Review / Validation Pipeline Every MCP generation tool (`peasy-ai-gen-types-events`, `peasy
edtechre/pybroker/CLAUDE.md
NUMBA_DISABLE_JIT=1` environment variable to get a readable Python traceback, fix the code, then remove the variable — never leave JIT disabled in a final script. Debug indicator failures
dustinlyons/nixos-config/CLAUDE.md
specific build command to test 3. Review changes before switching ## CI/CD GitHub Actions automatically: - Tests starter template builds - Runs statix linting on Nix code - Updates flake.lock weekly - Manages dependencies
pytorch/rl/CLAUDE.md
bespoke loop, container or helper that re-implements what the library already does. A reviewer who has to read a hand-rolled stepping loop or a list of dataclasses
zts212653/clowder-ai/CLAUDE.md
check - `request-review` — Cross-cat review requests - `merge-gate` — Merge approval process ## Code Standards - File size: review responsibilities at 200 lines; split at 350 by default or explain the structural
No other project uses it yet
erigontech/erigon/cl/CLAUDE.md
Caplin Consensus Layer This directory contains consensus-critical Caplin code. Review all changes against the upstream Ethereum consensus specifications, not only local tests. Primary spec reference: https://github.com/ethereum/consensus-specs
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.