artifact-swap
block/artifact-swap/CLAUDE.md
@ai-rules/.generated-ai-rules/ai-rules-generated-AGENTS.md
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.
block/artifact-swap/CLAUDE.md
@ai-rules/.generated-ai-rules/ai-rules-generated-AGENTS.md
block/qrgo/.agents/CLAUDE.md
.agents/AGENTS.md
aws/n8n-nodes-agentcore/CLAUDE.md
This project keeps all agent instructions in AGENTS.md. Always follow the rules in ./AGENTS.md, and when working in subdirectories, also check for a closer AGENTS.md in that directory tree.
NVIDIA/dl-lowlat-infer/CLAUDE.md
Do not duplicate AGENTS.md content here. For workflows, see README.md.
pydantic/claude-code-logfire-plugin/CLAUDE.md
A Claude Code plugin that captures sessions and exports pydantic-ai compatible OTel traces to Pydantic Logfire, with local JSONL fallback. The plugin is a single Python 3 script (stdlib only, no external dependencies). The entire plugin is a single Python script (scripts/log-event.py) invoked by every hook event defined in hooks/hooks.json. The plugin manifest lives at .claude-plugin/plugin.json. Data flow: Claude Code hook fires -> stdin JSON piped to log-event.py -> appends JSONL locally -> if LOGFIRE_TOKEN set and event is SessionStart/Stop/SubagentStop/SessionEnd,…
vercel-labs/oss-gtm-feedback/apps/www/CLAUDE.md
This is a Next.js 16 application for GTM feedback collection and reporting. It uses: This project uses next-safe-action v8 for type-safe server actions with a sophisticated middleware pipeline. Located in src/lib/actions/clients/, we have three main action clients:
microsoft/cates/examples/ecosystem/CLAUDE.md
No summary in the file. Open it to read it.
microsoft/cates/fixtures/ecosystem/CLAUDE.md
No summary in the file. Open it to read it.
microsoft/ppteval/claude-workspace/CLAUDE.md
You are running inside a single-task workspace for the PowerPoint Computer Use benchmark. Each invocation handles exactly one task. The harness has prepared this directory with everything you need. 1. Read TASK.md and OUTPUT_INSTRUCTIONS.md first. They define the goal and the exact path you must write your output to. Follow the output path literally — the grader looks for that path and nothing else. 2. Treat inputs/ as read-only. Copy the file before modifying it. 3. Write your result to…
Azure/sap-automation-qa/CLAUDE.md
No summary in the file. Open it to read it.
block/chalkline/CLAUDE.md
Read AGENTS.md and follow it for every task in this repository.
block/model-ledger/CLAUDE.md
Open-source model inventory and governance framework. Apache-2.0. This is an Apache-2.0 open-source project. All code must be generic and useful to any organization. Organization-specific connectors, auth, and backends go in separate packages. Examples in code, tests, and docstrings must be generic — use names like "Credit Scorecard", "feature_pipeline", "risk-team", "scoring_model". Never use organization-specific system names, team names, queue names, or person names in OSS code. The project is designed to be wrapped by downstream packages that add organization-specific connectors, auth,…
google/lightflow/CLAUDE.md
When orchestrating multi-step workflows with side effects (e.g., database migrations, API batch modifications, code deployments, or multi-stage reports), use Lightflow to guarantee topological execution order, atomic state checkpoints, and human-in-the-loop approval gates. When working via the bash tool in Claude Code (python3 -m lightflow is equivalent to lightflow whenever the console script is not on PATH): - Scaffolding new workflows (create_lightflow): When asked to build a new Lightflow workflow, run the create_lightflow meta-workflow that ships in the Lightflow repository to…
microsoft/agent-resources/CLAUDE.md
When the user's request matches an available skill, ALWAYS invoke it using the Skill tool as your FIRST action. Do NOT answer directly, do NOT use other tools first. The skill has specialized workflows that produce better results than ad-hoc answers. Key routing rules: - Product ideas, "is this worth building", brainstorming → invoke office-hours - Bugs, errors, "why is this broken", 500 errors → invoke investigate - Ship, deploy, push, create PR → invoke ship - QA, test the…
getsentry/launchpad/CLAUDE.md
Launchpad is a Python-based microservice for analyzing iOS and Android app bundle sizes. It provides detailed analysis of app binaries, generates optimization insights, and offers size breakdowns with visualization. This…
microsoft/cat/CLAUDE.md
When the user's request matches an available skill, invoke it via the Skill tool. When in doubt, invoke the skill. Key routing rules: - Product ideas/brainstorming → invoke /office-hours - Strategy/scope → invoke /plan-ceo-review - Architecture → invoke /plan-eng-review - Design system/plan review → invoke /design-consultation or /plan-design-review - Full review pipeline → invoke /autoplan - Bugs/errors → invoke /investigate - QA/testing site behavior → invoke /qa or /qa-only - Code review/diff check → invoke /review - Visual polish →…
langchain-ai/macaw-design-system/CLAUDE.md
No summary in the file. Open it to read it.
microsoft/AgentPlatformAdvisor/CLAUDE.md
When the user's request matches an available skill, invoke it via the Skill tool. When in doubt, invoke the skill. Key routing rules: - Product ideas/brainstorming -> invoke /office-hours - Strategy/scope -> invoke /plan-ceo-review - Architecture -> invoke /plan-eng-review - Design system/plan review -> invoke /design-consultation or /plan-design-review - Full review pipeline -> invoke /autoplan - Bugs/errors -> invoke /investigate - QA/testing site behavior -> invoke /qa or /qa-only - Code review/diff check -> invoke /review - Visual polish ->…
NVIDIA/structured-data-models-client/CLAUDE.md
See AGENTS.md.
pydantic/connect4/CLAUDE.md
Connect Four game demo showcasing PydanticAI and Pydantic Logfire capabilities. Features human vs AI and AI vs AI gameplay with multiple LLM model support. Live at https://logfire.run. IMPORTANT: ALWAYS USE…
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.