claude-desktop-debian
aaddrick/claude-desktop-debian/CLAUDE.md
Claude Desktop Debian - Development Notes ## Required reading These documents are the source of truth. If anything in this file conflicts with them, they win. Read them before opening
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.
aaddrick/claude-desktop-debian/CLAUDE.md
Claude Desktop Debian - Development Notes ## Required reading These documents are the source of truth. If anything in this file conflicts with them, they win. Read them before opening
SaladDay/cc-switch-cli/CLAUDE.md
this gate after any code change, before declaring the work complete. Changes limited to documentation, comments, formatting or translated text skip it. 1. Freeze a review range the reviewer
Live-Charts/LiveCharts2/CLAUDE.md
same file (only when related by inheritance). This is required for automatic documentation generation. ## Key Constraints - **Never add platform-specific code to `LiveChartsCore`** — it must remain platform-agnostic - **.NET Framework
Steady2 mentions in 2 weeks
No other project uses it yet
hey-api/openapi-ts/CLAUDE.md
code: - **Preserve all JSDoc comments** - Read the original file first and keep all existing documentation - **Match existing code patterns** - Look at similar files in the codebase for conventions - **Prefer `edit
chakra-ui/ark/CLAUDE.md
Built on top of Zag.js state machines, it provides unstyled, accessible UI components. ## Documentation Structure This guide is split into focused documents for better navigation: - **[Overview](@.claude/docs/overview.md)** - Project overview, architecture
Steady19 mentions in 2 weeks
No other project uses it yet
trustwallet/assets/CLAUDE.md
Knowledge Scope This repo's `knowledge/` covers: **ci, code-conventions, patterns, specs** Topics NOT documented locally: architecture, build, conventions, core-libs, decisions, design, features, git-conventions, guides, observability, product, quality
leits/MeetingBar/CLAUDE.md
docs/ARCHITECTURE.md](docs/ARCHITECTURE.md) and [docs/TESTING.md](docs/TESTING.md) for implementation and verification details. Do not duplicate these documents here
unicity-sphere/sphere-sdk/CLAUDE.md
# CLAUDE.md - Sphere SDK Project Context This file provides context for Claude Code when working
digitallyinduced/ihp/CLAUDE.md
ihp.url = .*|ihp.url = \"path://$(pwd)\";|" ../flake.nix direnv allow cd .. nix flake update ``` ## Documentation The `/Guide/` directory contains comprehensive documentation in markdown. Run `devenv up` from the Guide directory to preview changes
kasmtech/KasmVNC/CLAUDE.md
spec compliance** — divergence is intended. (A detailed list of the deviations is not yet documented here; see `PLAN.md`. When in doubt, ask rather than reverting to standard VNC behavior.) - **Modern
tagspaces/tagspaces/CLAUDE.md
leading `/` (e.g., `/Users/username/Documents/`) - **Windows local**: Drive-letter paths with `\` separators (e.g., `C:\Users\username\Documents\`). Java `.properties` files treat `\` as escape characters — always convert to `/` when writing paths to config
breaking-brake/cc-wf-studio/CLAUDE.md
patch version bump) - `improvement:` - Minor enhancement to existing feature (patch version bump) - `docs:` - Documentation only - `refactor:` - Code refactoring - `chore:` - Build/tooling changes #### What to Avoid ❌ Long explanations (Problem/Solution/Impact sections) ❌ Multiple paragraphs
lukevella/rallly/CLAUDE.md
with dev scripts) ``` ## Architecture ### Monorepo Structure - `apps/web/` - Main Next.js application - `apps/landing/` - Marketing/landing page - `apps/docs/` - Documentation site - `packages/` - Shared packages: - `database/` - Prisma schema and client - `ui/` - Shared UI components - `emails/` - Email
No other project uses it yet
streamyfin/streamyfin/CLAUDE.md
file is an index, not a manual. When a topic below points at a document, read that document before relying on assumptions: most of these rules exist because their absence
entireio/cli/CLAUDE.md
reporting. - Existing exceptions (explicit user paths, global git config, transcript-read protocol gaps) are documented in the references; do not generalize them. ## Git and subprocess safety - Open repositories only through
gluestack/gluestack-ui/CLAUDE.md
mappers sync. ``` src/ ├── components/ui/ # All UI components (Button, Input, Modal, etc.) ├── docs-components/ # Documentation-specific components (website only) ├── docs/ # Component docs/examples (website only) └── sidebar.json # Documentation sidebar config (website only) apps
No other project uses it yet
fallow-rs/fallow/CLAUDE.md
imported: the universal repository contract for Claude, Codex, and contributors, and the central documentation index. Read `docs/development/task-context-map.md` next to load only the references the current task needs. ## Knowledge layers - `.agents/skills
Steady21 mentions in 2 weeks
No other project uses it yet
umbraco/Umbraco-CMS/CLAUDE.md
framework - **Entity Framework Core** - Modern ORM - **OpenIddict** - OAuth 2.0/OpenID Connect authentication - **Microsoft.AspNetCore.OpenApi** - OpenAPI document generation - **Swashbuckle.AspNetCore.SwaggerUI** - Swagger UI for API documentation - **Lucene.NET** - Full-text search via Examine - **ImageSharp** - Image
Hufe921/canvas-editor/CLAUDE.md
cypress:run` - Run Cypress tests headlessly - `npm run docs:dev` - Start VitePress documentation server - `npm run docs:build` - Build VitePress documentation - `npm run release` - Run release script
chakra-ui/zag/CLAUDE.md
Zag.js AI Agent Instructions ## Documentation For detailed information on specific topics, see: - `@.claude/docs/commands.md` - All available commands and workflows - `@.claude/docs/architecture.md` - Code organization and structure - `@.claude/docs/guidelines.md` - Development guidelines and best practices - `@.claude/docs/common-tasks.md
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.