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.
tsinghua-fib-labReads credentialsCLAUDE.mdtsinghua-fib-lab/AgentSociety/CLAUDE.md
development package - `packages/agentsociety/` - Legacy city simulation package - `packages/agentsociety-community/` - Community contributions - `packages/agentsociety-benchmark/` - Benchmarking utilities The frontend is a separate React application in `frontend/`. VSCode extension is in `extension/`. ## Development Commands ### Python
chili-chips-baCLAUDE.mdchili-chips-ba/wireguard-fpga/CLAUDE.md
build_artifacts.slang/top.bit (~10 min, 3 GB) ``` openXC7 needs the software built first for `imem.INIT.vh`. `FRONTEND=sv2v` converts with sv2v instead of `read_slang`; `TOOLCHAIN=old` is the legacy nextpnr-xilinx
Team-CommonlyReads credentialsCLAUDE.mdTeam-Commonly/commonly/CLAUDE.md
Agent Hub UX, install confirmation, first-message coaching | The 60-second value prop | | 🟢 **Marketplace frontend** | Mid-queue (backend already shipped: PR #215 + #230, `/api/marketplace/*` 9 endpoints) | Browse page, manifest detail
giuseppe99barchettaCLAUDE.mdgiuseppe99barchetta/SuggestArr/CLAUDE.md
Build & Run Commands - Backend Docker: `docker build . -f ./docker/Dockerfile --target dev --tag suggestarr:nightly` - Frontend serve (dev): `cd client && npm run serve` - Frontend build: `cd client && npm run build` - Frontend
nanobot-aiCLAUDE.mdnanobot-ai/nanobot/CLAUDE.md
isolation. The `pkg/mcp/sandbox/` handles containerization and port mapping. Nanobot does not bundle a frontend. External UIs communicate through MCP endpoints, `/api/events`, and the browser proxy routes. ## Configuration Configuration is YAML
first-flukeCLAUDE.mdfirst-fluke/oh-my-ag/CLAUDE.md
prisma} | | debug | `.agents/rules/debug.md` | on request | | design | `.agents/rules/design.md` | on request | | dev-workflow | `.agents/rules/dev-workflow.md` | on request | | frontend | `.agents/rules/frontend.md` | **/*.{tsx,jsx,css,scss} | | i18n-arb | `.agents/rules/i18n-arb.md` | **/*.arb | | i18n-guide | `.agents/rules/i18n-guide.md` | always | | infrastructure | `.agents/rules/infrastructure.md
ruzinCLAUDE.mdruzin/stenoai/CLAUDE.md
backend code for security issues, error handling gaps, edge cases, and best practices - Review frontend code for layout bugs, CSS consistency, accessibility, and polish - Put UI changes through a design
hhyqhhReads credentialsCLAUDE.mdhhyqhh/inno-agent/CLAUDE.md
apps/inno-agent/` — backend (CLI + HTTP server), TypeScript, compiles to `dist/`. - `apps/inno-agent/web/` — frontend (React 19 + Lit + Tailwind 4 + Vite), workspace `inno-agent-web`. - `electron/` — Electron main process (`main.js` + `loading.html`) for desktop builds
chernistryCLAUDE.mdchernistry/bernstein/CLAUDE.md
write to them manually. - `adversary` - `analyst` - `architect` - `backend` - `ci-fixer` - `devops` - `docs` - `frontend` - `manager` - `ml-engineer` - `prompt-engineer` - `qa` - `resolver` - `retrieval` - `reviewer` - `security` - `visionary` - `vp` ## Documentation duty Every PR that
Surging3 mentions in 2 weeks
1 project uses a version of this
kgoedeckeCLAUDE.mdkgoedecke/doop/CLAUDE.md
host via Docker: `docker compose up` (real Postgres, port 4400). ## Project layout ``` src/ - React frontend (Vite entry: index.html) src/components/ui/ - shadcn-generated UI primitives src/pages/ - route-level pages src/hooks/ - React hooks
first-flukeCLAUDE.mdfirst-fluke/oh-my-agent/CLAUDE.md
prisma} | | debug | `.agents/rules/debug.md` | on request | | design | `.agents/rules/design.md` | on request | | dev-workflow | `.agents/rules/dev-workflow.md` | on request | | frontend | `.agents/rules/frontend.md` | **/*.{tsx,jsx,css,scss} | | i18n-arb | `.agents/rules/i18n-arb.md` | **/*.arb | | i18n-guide | `.agents/rules/i18n-guide.md` | always | | infrastructure | `.agents/rules/infrastructure.md
kunkunshCLAUDE.mdkunkunsh/kunkun/CLAUDE.md
Kunkun is a cross-platform desktop application built with Tauri (Rust backend) and SvelteKit (frontend). It's an extensible launcher/utility app that supports custom extensions developed in various web frameworks
dohoooCLAUDE.mddohooo/helmor/CLAUDE.md
with perf HUD (VITE_HELMOR_PERF_HUD=1) bun run build # tsc + vite build (frontend bundle to dist/) bun run typecheck # tsc --noEmit for frontend AND sidecar bun run lint
dromaraCLAUDE.mddromara/tianai-captcha/CLAUDE.md
binding 3. **tianai-captcha-solon-plugin** - Solon framework integration 4. **tianai-captcha-web-sdk** - Frontend JavaScript SDK ## Core Architecture ### Key Components **ImageCaptchaApplication** (cloud.tianai.captcha.application.ImageCaptchaApplication) - Main entry point for captcha operations - Handles
d-kimusonCLAUDE.mdd-kimuson/claude-code-viewer/CLAUDE.md
based client built as a CLI tool serving a Vite application. **Core Architecture**: - Frontend: Vite + TanStack Router + React 19 + TanStack Query - Backend: Hono (standalone server) + Effect-TS (all business logic
MiniMax-AICLAUDE.mdMiniMax-AI/OpenRoom/CLAUDE.md
VibeApp Development Guide An iframe-based micro-frontend VibeApp system (React + Cloud NAS). ## Quick Start Create a new app: `/vibe {AppName} {Description}` Modify an existing app: `/vibe {AppName} {ChangeDescription}` Resume
zwave-jsCLAUDE.mdzwave-js/zwave-js-ui/CLAUDE.md
environment setup ### Domain-specific instructions - [`.github/instructions/general-istructions.md`](.github/instructions/general-istructions.md) — Commit conventions and PR standards - [`.github/instructions/frontend-instructions.md`](.github/instructions/frontend-instructions.md) — Frontend folder structure, Vue 3 + Vuetify 3 patterns, Pinia, Socket.IO - [`.github/instructions/backend-instructions.md`](.github/instructions/backend-instructions.md) — Backend folder structure, Express
Steady4 mentions in 2 weeks
No other project uses it yet
HemmeligOrgReads credentialsCLAUDE.mdHemmeligOrg/Hemmelig.app/CLAUDE.md
powers Hemmelig: | Layer | Technology | Notes | | -------------- | ---------------------------- | ------------------------------------------ | | **Runtime** | Node.js 25 | JavaScript runtime for dev and production | | **Frontend** | React 19 + Vite + TypeScript | All components use `.tsx` | | **Backend** | Hono (RPC mode) | Type-safe
distr-shCLAUDE.mddistr-sh/distr/CLAUDE.md
backend on chi/v5 serving the REST API on `/api/v1` and the compiled frontend on `/`. - `cmd/controller/docker/`, `cmd/controller/kubernetes/`: the controllers that run Docker Compose and Helm deployments in customer environments and report
ArcadeDataCLAUDE.mdArcadeData/arcadedb/studio/CLAUDE.md
CLAUDE.md This file provides guidance to Claude Code when working with the ArcadeDB Studio frontend. ## Overview ArcadeDB Studio is the web-based administration interface for ArcadeDB. It is a **traditional
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.
