CLAUDE.md Example

cc-fleet — AGENTS.md as a Pointer + Essentials

Demonstrates the pointer pattern done well: AGENTS.md declares CLAUDE.md the single source of truth and links the…

Type: CLAUDE.md Example
Repository: ethanhq/cc-fleet
GitHub stars: 213
License: Apache-2.0
Repo last updated: Aug 19, 2026
Source file: AGENTS.md

What cc-fleet — AGENTS.md as a Pointer + Essentials is

cc-fleet — AGENTS.md as a Pointer + Essentials is a claude.md example published in the ethanhq/cc-fleet repository on GitHub, which has about 213 stars. The repository describes itself as: “🚢 Run Claude Code's ⚙️ Dynamic Workflows, 👥 Agent Teams & ⚡ Subagents on any third-party model — DeepSeek · GLM · Kimi · Qwen … or your Codex subscription. No Anthropic subscription needed. ｜ 🚢 让 Claude Code 的 ⚙️ Dynamic Workflow、👥 Agent Team、⚡ Subagent 用上任意第三方模型 — DeepSeek · GLM · Kimi · Qwen…… 或你的 Codex 订阅,无需 Claude 订阅”

A CLAUDE.md file holds standing instructions that Claude Code reads at the start of every session in a project, such as conventions, commands, and rules. Examples like cc-fleet — AGENTS.md as a Pointer + Essentials show how other teams structure theirs.

In Claude Cowork, the equivalent places for this kind of guidance are your global instructions, project instructions, and folder instructions.

How to install cc-fleet — AGENTS.md as a Pointer + Essentials

Claude Code

Copy the parts that fit your project into CLAUDE.md at the project root, or into ~/.claude/CLAUDE.md for rules that apply everywhere.
Keep it short and specific; remove anything that doesn't match how your team works.

Claude Cowork

Put personal rules in Settings → Instructions for Claude (global instructions).
Put project or folder rules in the project's instructions or the folder instructions for that directory.

New to extending Cowork? Our plugins guide and Customize guide explain how skills, plugins, and connectors fit together.

Inside the source file

An excerpt from AGENTS.md, shared under the repository's Apache-2.0 license. Read the full file on GitHub.

This repo's agent/AI guidance lives in CLAUDE.md — it is the single source of truth for any coding agent (Claude Code, Codex, Cursor, etc.). Read it before editing: what cc-fleet is, the four execution lanes, the load-bearing invariants, and the build/test commands. The system design lives in docs/architecture.md; the skills' canonical source is skills/ (edit there, then make skill-sync — see CLAUDE.md); the user-facing references to keep in sync are docs/cli.md and docs/workflows.md.

The contribution standard (required checks, commit/PR rules, screenshots, AI attribution) is CONTRIBUTING.md.

Coding standards (the essentials)

Minimal intrusion. Change the fewest lines that solve the task. No out-of-scope refactor, rename, or reformat. Match the surrounding style.
Simplest correct implementation. No speculative abstraction, dependency, or config surface (YAGNI). Reuse an existing helper before adding one.
Concise comments. Explain why, not what; no narration or ticket/changelog notes. Fix comments your change makes stale.
Respect the invariants documented in CLAUDE.md: keys never in env/argv/history; classified Result envelopes from spawn/subagent; validate names before use; honor the lock order.
Verify before done: go test -race ./..., gofmt -l ., go vet ./... clean; plus claude plugin validate . --strict if you touched the plugin/skill.

AI attribution

AI-assisted (a human authored/reviewed the diff) → Co-Authored-By: trailer naming the tool/model in the commit message.
Fully AI-authored PR → add the autonomous-PR marker as the last line of the PR body (see CONTRIBUTING.md).

Before you install

Read the whole file first. Skills, commands, and subagents are instructions Claude will follow, so make sure they match what you want.
Check which tools, scripts, or MCP servers it uses. Local servers and scripts run with your permissions.
Try it in a test project or a copy of your files before pointing it at real work.
Pin the version you tested, and review changes before updating.
Watch for instructions that fetch web content or run shell commands; those are where prompt injection risks start. See our prompt injection guide.

FAQ

What is cc-fleet — AGENTS.md as a Pointer + Essentials?

cc-fleet — AGENTS.md as a Pointer + Essentials is a claude.md example for Claude Code and Claude Cowork from the ethanhq/cc-fleet repository on GitHub. Demonstrates the pointer pattern done well: AGENTS.md declares CLAUDE.md the single source of truth and links the…

How do I install cc-fleet — AGENTS.md as a Pointer + Essentials in Claude Code?

Copy the parts that fit your project into CLAUDE.md at the project root, or into ~/.claude/CLAUDE.md for rules that apply everywhere. Keep it short and specific; remove anything that doesn't match how your team works.

Can I use cc-fleet — AGENTS.md as a Pointer + Essentials in Claude Cowork?

Put personal rules in Settings → Instructions for Claude (global instructions). Put project or folder rules in the project's instructions or the folder instructions for that directory.

Is cc-fleet — AGENTS.md as a Pointer + Essentials safe to install?

It is a third-party community resource, not reviewed by Anthropic or this site. Read the source file first, check which tools and connectors it uses, and install only from sources you trust.

Similar resources

Browse all skills, subagents, and plugins →

Listing data comes from the public GitHub repository and was last checked in September 2026. Excerpts are © their authors and shared under Apache-2.0. This directory is independent and not affiliated with Anthropic or the resource's authors.