Aperant
AndyMik90/Aperant/CLAUDE.md
debug # Debug mode with verbose output npm run dev:mcp # Electron MCP server for AI debugging # Project data: .auto-claude/specs/ (gitignored
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.
AndyMik90/Aperant/CLAUDE.md
debug # Debug mode with verbose output npm run dev:mcp # Electron MCP server for AI debugging # Project data: .auto-claude/specs/ (gitignored
semaphoreui/semaphore/.claude/CLAUDE.md
consider any solution that introduces security risks. ## How to do research Use MCP server `research` if your asks you to research something. ## Writing Tests Use `github.com/stretchr/testify/assert` (and `require` when
No other project uses it yet
Open-LLM-VTuber/Open-LLM-VTuber/CLAUDE.md
src/open_llm_vtuber/mcpp/`): - Tool execution and server registry - JSON detection and parameter extraction - Integration with various MCP servers for extended functionality ## Key Development Patterns ### Error Handling The codebase uses the missing `_cleanup
No other project uses it yet
StarTrail-org/LEANN/CLAUDE.md
without rebuild - `leann-backend-diskann/`: DiskANN backend for larger-than-memory datasets - `leann-mcp/`: MCP server for Claude Code integration Backends are auto-discovered via `leann-backend-*` naming convention
Steady4 mentions in 2 weeks
1 project uses a version of this
mrexodia/ida-pro-mcp/CLAUDE.md
CLAUDE.md Guidance for working in this repository. ## What this project is IDA Pro MCP Server: exposes IDA Pro / idalib functionality to MCP clients. Main pieces: - `src/ida_pro_mcp/server.py`: MCP server entrypoint - `src/ida_pro_mcp/idalib_server.py
nearai/ironclaw/CLAUDE.md
CLAUDE.md`, runtime `skills/`) are governed by `.claude/rules/guidance-maintenance.md`. ## Codebase knowledge graph (MCP) The `codebase-memory` MCP server indexes `crates/` into a knowledge graph; prefer it over `Grep` for *code structure* (cross
anthropics/claude-code-action/CLAUDE.md
imports don't need `.js` extensions. - GitHub API calls should use retry logic (`src/utils/retry.ts`). - MCP servers are auto-installed at runtime to `~/.claude/mcp/github-{type}-server/`. ## Security hardening for GitHub Actions
rehan-remade/universal-modder/CLAUDE.md
Installed as a plugin, the skills are namespaced (`/universal-modder:mod-any-game`), the fal MCP server comes from `.mcp.json` (needs `FAL_KEY` in the environment), and a SessionStart hook puts
Steady7 mentions in 2 weeks
1 project uses a version of this
anthropics/claude-for-legal/CLAUDE.md
commercial-legal, privacy-legal, ...) .claude-plugin/plugin.json # plugin manifest (name, version, description, author) .mcp.json # MCP servers the plugin connects to CLAUDE.md # practice-profile TEMPLATE (see "Plugin CLAUDE.md" below) README.md
Steady3 mentions in 2 weeks
No other project uses it yet
nhost/nhost/CLAUDE.md
based CLI for local development (`nhost dev`), project management, deployments, secrets, and MCP server ### Shared Libraries (`internal/lib/`) - `internal/lib/oapi` - shared OpenAPI middleware and utilities - `internal/lib/clidocs` - CLI documentation generation - `internal/lib/pgmigrate` - target-oriented
No other project uses it yet
tsparticles/tsparticles/CLAUDE.md
exec nx test`) - avoids using globally installed CLI - You have access to the Nx MCP server and its tools, use them to help the user - For Nx plugin best practices
Steady24 mentions in 2 weeks
1 project uses a version of this
redpanda-data/connect/CLAUDE.md
Public API wrappers. Thin `import _` wrappers for selective compilation. `internal/cli/` - Enterprise CLI (license management, MCP server, agent mode). `internal/license/` - RCL validation and enforcement. `internal/rpcplugin/` - RPC plugin system (Python/Go templates). `public/schema
No other project uses it yet
meshtastic/firmware/CLAUDE.md
layout, coding conventions, the build system, CI/CD, the native C++ test suite, and the MCP Server & Hardware Test Harness. Read it top-to-bottom before starting any non-trivial change
opengeos/GeoLibre/CLAUDE.md
ROOTS` (default `/data`). Local MBTiles use a custom MapLibre protocol backed by Tauri commands. **MCP server** (`python/src/geolibre/mcp/`, the `geolibre-mcp` console script): a headless stdio MCP server that authors `.geolibre.json
ntop/ntopng/CLAUDE.md
Dual-Graph Context Policy This project uses a local dual-graph MCP server for efficient context retrieval. ## MANDATORY: Always follow this order 1. **Call `graph_continue` first** — before any file
Steady2 mentions in 2 weeks
No other project uses it yet
nullclaw/nullclaw/CLAUDE.md
Networking**: `gateway`, `channels` 4. **Extensions**: `security`, `cron`, `health`, `tools`, `identity`, `cost`, `observability`, `heartbeat`, `runtime`, `mcp`, `subagent`, `auth`, `multimodal`, `agent_routing` 5. **Hardware/Integrations**: `hardware`, `peripherals`, `rag`, `skillforge`, `tunnel`, `voice` ### Key Entry
webiny/webiny-js/CLAUDE.md
titles:** Mirror the commit style ## Webiny This project uses the Webiny framework. A `webiny` MCP server is available. When helping with Webiny-related tasks, call `get_started()` first
EricLBuehler/mistral.rs/CLAUDE.md
image generation, and speech models with Rust and Python SDKs, plus OpenAI HTTP and MCP APIs. ## Essential Commands ### Building ```bash # Basic release build cargo build --release # With CUDA support (Linux
Steady2 mentions in 2 weeks
No other project uses it yet
gaozhangmin/aliyunpan/CLAUDE.md
keys, UA) scripts/ Build scripts, CLI entry points (clouddrive-cli.mjs, clouddrive-mcp.mjs) clouddrive-cli/ Standalone CLI + MCP server package (npm: clouddrive-cli) core/ Command implementations, MCP server, upload planning providers/ 8 cloud
Tencent/AI-Infra-Guard/CLAUDE.md
Teaming Platform** by Tencent Zhuque Lab. It scans AI infrastructure for fingerprints, CVE vulnerabilities, MCP server risks, agent workflow issues, and jailbreak susceptibility. It uses a **distributed server-agent architecture
Steady2 mentions in 2 weeks
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.