jcodemunch-mcp
jgravelle/jcodemunch-mcp/CLAUDE.md
findings-row`), and a typed number is a review finding. ⚠⚠ **A competitor's README figure is never a measurement and competitor code runs only in the sandbox**; a release title
How real projects brief Claude Code: the commands, conventions and warnings they put in CLAUDE.md.
jgravelle/jcodemunch-mcp/CLAUDE.md
findings-row`), and a typed number is a review finding. ⚠⚠ **A competitor's README figure is never a measurement and competitor code runs only in the sandbox**; a release title
BytePioneer-AI/codex-host/CLAUDE.md
implicit cross-module coupling. ## Code Size & Structure - Keep handwritten production modules focused on one primary responsibility. - Treat 500 lines as a design-review signal, not a hard limit. When
huggingface/OpenEnv/CLAUDE.md
claude/skills/` and run inline: **Review & Validation Skills:** | Skill | Trigger | Definition | |-------|---------|------------| | [`alignment-review`](.claude/skills/alignment-review/SKILL.md) | "review this code" | Two-tier review (bugs + alignment flags) | | [`pre-submit-pr`](.claude/skills/pre-submit-pr/SKILL.md) | "ready for PR?" | Comprehensive
chrisryugj/korean-law-mcp/CLAUDE.md
v4.14.1: `law_system`·`amendment_track`·`ordinance_compare`·`procedure_detail` 추가, 공용 `withChainDeadline` 헬퍼). `document_review` 는 기반 법령 프리픽스가 없고 갈래 수가 고정이라 개별 fetch 한도(전체 45초)만 건다
Natively-AI-assistant/natively-cluely-ai-assistant/CLAUDE.md
change, and architectural decision must preserve correct behavior on both operating systems. --- ## MCP Tools: code-review-graph **IMPORTANT: This project has a knowledge graph. ALWAYS use the `code-review-graph
Nano-Collective/nanocoder/CLAUDE.md
ToolManager.initializeCustomTools()` registers them into the same registry as built-ins and MCP tools — downstream code (`/tools`, subagents, mode filtering) sees them through the unified registry. Mode policy for custom tools
antonbabenko/terraform-skill/CLAUDE.md
code block / table adds a fact not in surrounding prose - [ ] Subsection under 400 tokens - [ ] Anchors referenced from SKILL.md remain stable - [ ] For substantive new sections, get a second-opinion review from
jnMetaCode/agency-orchestrator/CLAUDE.md
repo `ai-shortfilm-prompts` (MIT, same author). The upstream `SKILL.md` is an **interactive** Claude Code skill (it asks via AskUserQuestion, `Read`s template files); AO steps have no tools
muxy-app/muxy/CLAUDE.md
demo extension at ~/.config/muxy/extensions to the user. - Prefix the demo extensions with `demo-*` ## Code Review - Review changes against the stated PR, issue, or task. Start with the diff, directly affected
tractorjuice/arc-kit/CLAUDE.md
plugins/arckit-claude/hooks/README.md).** [`plugins/arckit-claude/docs/ENFORCEMENT.md`](plugins/arckit-claude/docs/ENFORCEMENT.md) is the three-tier statement of what the hooks enforce in code, what is only asked of the model, and what the deploying organisation owns — a change
oh-my-mermaid/oh-my-mermaid/CLAUDE.md
translations in the same commit - Translations can be machine-generated but should be reviewed for obvious errors ## Versioning - Follow [Semantic Versioning](https://semver.org/) - Sync version across: `package.json`, `.claude-plugin
jhlee0409/claude-code-history-viewer/CLAUDE.md
CLAUDE.md This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository. If the user's prompt starts with “EP:”, then the user wants
777genius/agent-teams-ai/CLAUDE.md
work autonomously in parallel, communicate with each other, create and manage their own tasks, review code, and collaborate across teams. You manage everything through a kanban board — like
wondelai/skills/CLAUDE.md
grow-business, grow-website, grow-app, improve-code-quality, remove-technical-debt, design-code-architecture, conversion-optimization, architecture-optimization | | **UX/Design** | refactoring-ui, ios-hig-design, ux-heuristics, hooked-ux, improve
AgriciDaniel/claude-blog/CLAUDE.md
Creation & Optimization Skill ## Project Overview This repository contains **Claude Blog**, a Tier 4 Claude Code skill for blog content creation, optimization, and management. It follows the Agent Skills open standard
Lumiwealth/lumibot/CLAUDE.md
rules live in `docs/BACKTESTING_ARCHITECTURE.md` under "RULE #1". Read it before touching any data-fetching code. ## Quick Start **First, read these files:** 1. `docs/BACKTESTING_ARCHITECTURE.md` - Understand the backtesting data flow
digitalsamba/claude-code-video-toolkit/CLAUDE.md
FFmpeg ## Directory Structure ``` claude-code-video-toolkit/ ├── .claude/ │ ├── skills/ # Domain knowledge for Claude │ └── commands/ # Guided workflows ├── tools/ # Python CLI automation ├── templates/ # Video templates │ ├── sprint-review/ # Sprint review video template │ └── product
agentset-ai/agentset/docs/CLAUDE.md
existing pages - Include both basic and advanced use cases - Language tags on all code blocks - Alt text on all images - Relative paths for internal links ## Common mistakes to avoid - **Inconsistent
doobidoo/mcp-memory-service/CLAUDE.md
browsing. - Read graphify-out/GRAPH_REPORT.md only for broad architecture review or when query/path/explain do not surface enough context. - After modifying code, run `graphify update .` to keep the graph current
WorldFlowAI/everything-claude-code/examples/CLAUDE.md
DEBUG=false ``` ## Available Commands - `/tdd` - Test-driven development workflow - `/plan` - Create implementation plan - `/code-review` - Review code quality - `/build-fix` - Fix build errors ## Git Workflow - Conventional commits: `feat:`, `fix:`, `refactor:`, `docs:`, `test
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.