ImageGlass / source
d2phap/ImageGlass/source/CLAUDE.md
# ImageGlass v10 ## Project Overview ImageGlass v10 is a complete rewrite in **C# with .NET
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.
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
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
No other project uses it yet
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
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
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
semaphoreui/semaphore/.claude/CLAUDE.md
Claude Code Instructions # Documentation The documentation stored in /docs directory. It is a submodule with official Semaphore UI documentation in on Docusaurus engine. You should actualize the documentation
No other project uses it yet
phpstan/phpstan/CLAUDE.md
infrastructure. The actual source code lives at [phpstan/phpstan-src](https://github.com/phpstan/phpstan-src). - **Website:** https://phpstan.org/ - **Documentation:** https://phpstan.org/user-guide/getting-started - **API Reference:** https://apiref.phpstan.org/ ## Repository Structure ``` ├── phpstan # CLI entry point (shell script
phpstan/phpstan/website/CLAUDE.md
global data files - `src/_posts/` — Blog posts (Markdown) - `src/js/` — TypeScript source files - `src/user-guide/` — User guide documentation (Markdown) - `src/developing-extensions/` — Extension development docs - `src/writing-php-code/` — PHP writing guide - `src/app.pcss` — Main stylesheet (Tailwind + custom
567-labs/instructor/CLAUDE.md
coverage run -m pytest tests/ -k "not docs"` then `uv run coverage report` - Build documentation: `uv run mkdocs serve` (for local preview) or `./build_mkdocs.sh` (for production) - Waiting: use `sleep
Steady5 mentions in 2 weeks
No other project uses it yet
formkit/auto-animate/.dmux-hooks/CLAUDE.md
dmux Hooks System - Agent Reference **Auto-generated documentation for AI agents** This document contains everything an AI agent needs to create, modify, and understand dmux hooks. It is automatically generated
Steady38 mentions in 2 weeks
1 project uses a version of this
OpenNHP/opennhp/CLAUDE.md
HTML for readers without JS, without that CSP, or with reduced motion. **One documented exception to self-containment.** The homepage ` ` carries a meta description, a canonical URL and the Open
browserless/browserless/CLAUDE.md
interfaces (`BodySchema`, `QuerySchema`, `ResponseSchema`) that are automatically converted to: - Runtime JSON Schema validation - OpenAPI documentation (served at `/docs`) ### Docker Images Located in `docker/` with browser-specific Dockerfiles: - `base/` - Base image
Steady25 mentions in 2 weeks
No other project uses it yet
borgbackup/borg/.claude/CLAUDE.md
Always write pytest-style tests unless unittest-style is explicitly required. ## Writing docstrings, comments, documentation The docs shall always be in sync with the current code, algorithms and data structures
No other project uses it yet
coleam00/context-engineering-intro/claude-code-full-guide/CLAUDE.md
ready code - `develop` - Integration branch for features - `feature/*` - New features - `fix/*` - Bug fixes - `docs/*` - Documentation updates - `refactor/*` - Code refactoring - `test/*` - Test additions or fixes ### Commit Message Format Never include claude
coleam00/context-engineering-intro/CLAUDE.md
Google style: ```python def example(): """ Brief summary. Args: param1 (type): Description. Returns: type: Description. """ ``` ### 📚 Documentation & Explainability - **Update `README.md`** when new features are added, dependencies change, or setup steps are modified
StarTrail-org/LEANN/CLAUDE.md
enables semantic search across various data sources (emails, browser history, chat history, code, documents) on a single laptop without cloud dependencies. ## Build & Development Commands ### Quick install (pip) ```bash pip install
Steady4 mentions in 2 weeks
1 project uses a version of this
maxrave-dev/SimpMusic/CLAUDE.md
questions, the AI agent **MUST** follow this research workflow: #### Step 1: Look up official documentation - Use **MCP Context7** (`resolve-library-id` → `query-docs`) to fetch up-to-date documentation
Orchestra-Research/AI-research-SKILLs/CLAUDE.md
format: ``` skill-name/ ├── SKILL.md # Main guidance (200-600 lines with YAML frontmatter) ├── references/ # Deep documentation (300KB+ target) │ ├── README.md # From official docs │ ├── api.md # API reference │ ├── tutorials.md # Step-by-step guides │ ├── issues.md
rybbit-io/rybbit/docs/CLAUDE.md
rules in `content/partials/guides/README.md`; copy `TEMPLATE.mdx` for a new guide) ## Project Overview This is the documentation and marketing website for Rybbit, built with Next.js 16 and Fumadocs. The site includes: - Documentation
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.