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.
Microsoft AzureCLAUDE.mdAzure/LogicAppsUX/libs/vscode-extension/CLAUDE.md
Shared utilities and services for the Logic Apps VS Code extension. Provides common functionality used by both the extension host and webviews. Package: @microsoft/vscode-extension-logic-apps Read libs/vscode-extension/src/graphify-out/GRAPH_REPORT.md for structural context (god nodes, communities, surprising connections).
Microsoft AzureCLAUDE.mdAzure/aks-app-routing-operator/CLAUDE.md
The AKS Web Application Routing Operator is a Kubernetes operator that manages resources for AKS Application Routing functionality. It's built using the Kubebuilder framework and manages several Custom Resource Definitions (CRDs) for routing, DNS, and certificate management. Some test packages (e.g. pkg/controller/dns/) use controller-runtime's envtest and require Kubernetes API server binaries. Use setup-envtest to install them and set KUBEBUILDER_ASSETS: If setup-envtest use -p path doesn't expand correctly in your shell, run setup-envtest use first to see the path, then set…
Microsoft AzureCLAUDE.mdAzure/aks-app-routing-operator/pkg/manifests/CLAUDE.md
This package stores Kubernetes manifests that are served to customers. These manifests are used to deploy various components of the App Routing Operator. The test fixtures in this package are generated from the Helm charts. To regenerate the fixtures, run the tests with the GENERATE_FIXTURES environment variable set to true:
Microsoft AzureCLAUDE.mdAzure/ARO-HCP/CLAUDE.md
This is the main repository for Red Hat OpenShift on Azure (ARO) using the Hosted Control Planes (HCP) architecture. It contains some of the code for the required microservices along with most of the configuration and pipeline definition necessary to deploy it. For integration tests (require Cosmos emulator): Rendered config changes under config/rendered/ must be committed with your PR. Run make verify-materialize to check. Note: make test runs envtest-setup automatically, but if you run go test directly in a module…
Microsoft AzureCLAUDE.mdAzure/ARO-HCP/config/CLAUDE.md
Docs on how these configs work: - docs/configuration.md - docs/bicep.md if you're editing bicep files When making changes to configs/config*.yaml you might need to update the appropriate schema files. After updating configs, verify and render new config by running: - cd config; make materialize These might result in changes to rendered configs which must be attached to any PRs. Examples: - Commit 4a276befedc7f8a33692c6d8d6746e22344f195c adds a new bool parameter set to True by default, but False in 'dev' cloud envs. Commit…
Microsoft AzureCLAUDE.mdAzure/ARO-HCP/test/CLAUDE.md
Load AGENTS.md for context The metrics/alert pages shown inline on a Prow job's Spyglass page (and browsable under gcsweb at .../artifacts/e2e-parallel/aro-hcp-gather-observability/artifacts/) are produced by the gather-observability subcommand, not by a Grafana dashboard. Source lives in test/cmd/aro-hcp-tests/gather-observability/. The CI step aro-hcp-gather-observability runs aro-hcp-tests gather-observability (cmd.go, Use: "gather-observability") and writes every artifact into the --output dir, which Prow uploads to that GCS path. Each tab's HTML is a full, self-contained page (the existing alerts and metrics panel templates, unchanged) embedded into its…
Microsoft AzureCLAUDE.mdAzure/ARO-HCP/test-integration/claude.md
Artifact-driven integration tests for frontend, backend, and admin services. Tests run against a mock Cosmos DB by default. Tests are declarative: you define a sequence of numbered step directories under an artifacts tree. The framework discovers them automatically via //go:embed artifacts and fs.ReadDir().
Microsoft AzureCLAUDE.mdAzure/ai-infrastructure-on-azure/CLAUDE.md
This repo contains infrastructure validation tests and operational knowledge for Azure CycleCloud Workspace for Slurm and AKS clusters with NVIDIA GPU nodes. A single skill, skills/ai-infra/, contains all operational knowledge as a SKILL.md index plus reference files in references/. When answering questions about cluster operations, hardware validation, or troubleshooting GPU/network issues, read skills/ai-infra/SKILL.md first to find the relevant reference files, then read those. The skill covers:
Microsoft AzureCLAUDE.mdAzure/telescope/CLAUDE.md
See the design.md for an overview of telescope's architecture and components. See the contribute.md and test-scenario-implementation-guide.md for detailed walkthroughs on implementing new test scenarios or modifying existing ones. See the verify.md for instructions to verify test scenarios locally and end-to-end.
Microsoft AzureCLAUDE.mdAzure/kperf/CLAUDE.md
See the design.md for an overview of kperf's architecture and components. See the build.md for build instructions to compile and install kperf and runkperf. See setup.md for setup instructions on how to prepare your environment for running kperf and runkperf. See the kperf.md for instructions on how to test kperf end-to-end. See the runkperf.md for instructions how to test runkperf end-to-end.
Microsoft AzureCLAUDE.mdAzure/sap-automation-qa/CLAUDE.md
No summary in the file. Open it to read it.
Microsoft AzureCLAUDE.mdAzure/sap-automation-bootstrap/CLAUDE.md
@.github/copilot-instructions.md
Microsoft AzureCLAUDE.mdAzure/azure-cleanroom/CLAUDE.md
Read .github/copilot-instructions.md for repo conventions, architecture, and development patterns.
Microsoft AzureCLAUDE.mdAzure/operation-cache-controller/CLAUDE.md
The Operation Cache Controller is a Kubernetes operator built with kubebuilder v4 framework that manages operations and caches the outcome of those operations. It provisions resources, pre-provisions resources for future use (caching), and manages the lifecycle of resources and cache. The controller manages four main Custom Resource Definitions (CRDs) in the controller.azure.github.com API group: The project follows a handler-based reconciliation pattern with clear separation of concerns: The main reconcilers are located in internal/controller/: - RequirementReconciler - Creates Cache and Operation…
Microsoft AzureCLAUDE.mdAzure/kcl-azure-pipelines/CLAUDE.md
This document describes the coding conventions and patterns used in this repository for implementing Azure Pipelines schemas in KCL. Don't use relative imports: For file-level documentation (especially for types): Pattern: type Name = SimpleForm | ComplexForm | ... Don't create separate schemas for identical structures:
Microsoft AzureCLAUDE.mdAzure/sap-automation-gh-bootstrap/CLAUDE.md
@.github/copilot-instructions.md
Microsoft AzureCLAUDE.mdAzure/aks-traffic-ingress-competitive-testing/CLAUDE.md
This is a load-testing framework for comparing Kubernetes ingress controllers (nginx via Ingress, Istio via Gateway API). It orchestrates: spin up a Kind cluster → install a traffic controller → deploy a backend server via Helm → run vegeta load tests → collect JSON results → tear down. master.sh handles everything including cleanup (via EXIT trap). Requires kubectl, helm, jq, and curl on the host. scripts/master.sh is the single entry point that orchestrates these steps in order: Each module under…
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.
