sagemaker-python-sdk
aws/sagemaker-python-sdk/CLAUDE.md
replacements, the SDK-first interface map, the contributing workflow, and a canonical v3 train + deploy example — read [`AGENTS.md`](./AGENTS.md) directly
How real projects brief Claude Code: the commands, conventions and warnings they put in CLAUDE.md.
aws/sagemaker-python-sdk/CLAUDE.md
replacements, the SDK-first interface map, the contributing workflow, and a canonical v3 train + deploy example — read [`AGENTS.md`](./AGENTS.md) directly
AmoyLab/Unla/CLAUDE.md
race detection go test ./pkg/utils/... # test specific packages ``` ### Configuration Validation ```bash # Test configuration before deployment go run cmd/mcp-gateway/main.go test -c configs/mcp-gateway.yaml ``` ### Operational Commands ```bash # Live reload configuration go run cmd/mcp-gateway/main.go
carlvellotti/free-ai-courses/CLAUDE.md
course content (distributed via GitHub Releases as a zip) 2. **website/** - Next.js documentation site (deployed to Vercel at ccforpms.com) Students download course-materials/ as a zip, extract it, run `claude
AgriciDaniel/claude-blog/CLAUDE.md
handles cover image generation, SEO metadata, FAQ schema, internal linking, sitemap/llms.txt updates, and Vercel deployment
Shopify/hydrogen/e2e/CLAUDE.md
TEST_EMAIL="hydrogen-e2e-test@example.com" \ pnpm exec playwright test --project=skeleton e2e/specs/skeleton/customerAccount.spec.ts # Against an existing Oxygen deployment (skips tunnel): CUSTOMER_ACCOUNT_URL=https://your-oxygen-deployment.oxygen.myshopify.com \ OXYGEN_AUTH_BYPASS_TOKEN=your-token \ pnpm exec
cloudflare/templates/CLAUDE.md
lockfiles # Validate live demo links pnpm run validate-live-demo-links # Validate Deploy to Cloudflare buttons pnpm run validate-d2c-buttons ``` ### Deployment Commands ```bash # Deploy all templates pnpm run deploy
omnimind-ai/OmniBot/CLAUDE.md
Configuration Optional/required properties in `gradle.properties` or `~/.gradle/gradle.properties`: ```properties # Optional backend endpoint for self-hosted deployments OMNIBOT_BASE_URL= # Required only for release signing OMNI_RELEASE_STORE_FILE=/abs/path/release.jks OMNI_RELEASE
microsoft/PowerApps-Samples/CLAUDE.md
driven app samples - **portals/**: Power Apps Portals samples (OAuth, Web API) - **powershell/** & **build-tools/**: Deployment automation ## Building and Testing ### Power Apps Component Framework (PCF) Each PCF control is a self
BayramAnnakov/claude-reflect/CLAUDE.md
file is updated in the appropriate section (steps, guardrails, etc.) **Example:** ``` User: /deploy Claude: [deploys without running tests] User: "no, always run tests before deploying" → /reflect detects this relates
lst97/claude-code-sub-agents/CLAUDE.md
agent-organizer`):** - New requirements spanning multiple domains ("Now add authentication and deploy to AWS"). - Significant scope changes ("Actually, let's make this a mobile app instead"). - Tasks requiring different expertise
aws/aws-lambda-dotnet/Libraries/src/Amazon.Lambda.DurableExecution/CLAUDE.md
real `SourceGeneratorLambdaJsonSerializer` — set `TestLambdaContext.Serializer` so `LambdaSerializerHelper.GetRequired` finds one. ### Integration tests (expensive, real AWS) `Libraries/test/Amazon.Lambda.DurableExecution.IntegrationTests` deploys real Lambdas. Each test builds a `TestFunctions/ /` project with **`dotnet publish` (framework-dependent, linux
pedrohcgs/claude-code-my-workflow/CLAUDE.md
TEXINPUTS=../Preambles:$TEXINPUTS xelatex -interaction=nonstopmode file.tex TEXINPUTS=../Preambles:$TEXINPUTS xelatex -interaction=nonstopmode file.tex # Deploy Quarto to GitHub Pages ./scripts/sync_to_docs.sh LectureN # Quality score python3 scripts/quality_score.py Quarto/file.qmd # Palette sync (LaTeX ↔ SCSS
fynnfluegge/agtx/CLAUDE.md
worktree at `{worktree_dir}/{slug}` (default `.agtx/worktrees/{slug}`), copies files, runs init script, deploys skills, starts agent. - **Running**: Agent implementing. **Review**: optionally create PR; tmux window stays open; can resume
silverstein/minutes/CLAUDE.md
version of `minutes-sdk`, not `file:../sdk`), verify the Cloudflare Pages site deploy after the validated `site/` changes reach `main`, and update the Homebrew tap if CLI changed. ## Design System
Open-Source-Legal/OpenContracts/CLAUDE.md
styles # Build for production yarn build # Preview production build locally yarn serve ``` ### Production Deployment ```bash # CRITICAL: Always run migrations FIRST in production docker compose -f production.yml --profile migrate up migrate
daymade/claude-code-skills/CLAUDE.md
treat a merged source change as proof that this runtime advanced. For recorder deployment, follow that workflow's ordinary-copy migration and link readback; retaining a LaunchAgent wrapper does
CloudAI-X/claude-workflow-v2/CLAUDE.md
update README with new feature chore: bump version to X.Y.Z ``` ### Branching - `main` is always deployable - Feature branches: `feature/description` - Bug fixes: `fix/description` ## Available Agents (Use These!) When working on this repo
peterkrueck/Claude-Code-Development-Kit/templates/CLAUDE.md
available skills proactively**: `/review-work` for code review, `/update-docs` after significant changes, `/deploy` for deployments. - **Context7 first**: When working with external libraries, check Context7 for current documentation before relying on training
jayminwest/overstory/CLAUDE.md
load + query capabilities) overlay.ts # Dynamic CLAUDE.md overlay generator identity.ts # Persistent agent identity (CVs) hooks-deployer.ts # Deploy hooks config to worktree copilot-hooks-deployer.ts # Deploy hooks config to Copilot worktrees guard-rules.ts # Shared guard constants
sceneview/sceneview/CLAUDE.md
holds a live API key.** Never print it, never commit it. - **Merging to `main` deploys.** Play Store rollout is automatic. The App Store submission is automated but Apple's review
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.