This file provides guidance to Claude Code for working in this repository.
Use this section for durable repo-specific facts that agents repeatedly need. Prefer facts stored here over re-deriving them with shell commands on every task.
Keep only stable, reviewable metadata here. Do not store secrets, credentials, or ephemeral runtime state.
Suggested facts to record:
- Canonical GitHub repo:
<OWNER/REPO> - Default branch:
<main> - Primary package manager:
<pnpm | npm | yarn | uv | go> - Version-file locations agents should check first:
<.nvmrc, packageManager, pyproject.toml, go.mod, etc.> - Canonical config files:
<paths agents should read before falling back to discovery> - Primary CI workflows:
<workflow filenames> - Primary release/publish workflows:
<workflow filenames> - Preferred build/test/lint/format/coverage commands:
<commands> - Coverage threshold:
<value> - Generated or protected paths agents should avoid editing directly:
<paths>
Update this section when those facts change. If live runtime state is required, discover it separately instead of treating it as a durable repo fact.
Created by Ballast. Do not edit this section.
Read and follow these rule files in .claude/rules/ when they apply:
.claude/rules/common/local-dev-badges.md— Rules for common/local-dev-badges.claude/rules/common/local-dev-env.md— Rules for common/local-dev-env.claude/rules/common/local-dev-license.md— Rules for common/local-dev-license.claude/rules/common/local-dev-mcp.md— Rules for common/local-dev-mcp.claude/rules/common/docs.md— Rules for common/docs.claude/rules/common/cicd.md— Rules for common/cicd.claude/rules/common/observability.md— Rules for common/observability.claude/rules/common/publishing-libraries.md— Rules for common/publishing-libraries.claude/rules/common/publishing-sdks.md— Rules for common/publishing-sdks.claude/rules/common/publishing-apps.md— Rules for common/publishing-apps.claude/rules/common/git-hooks.md— Rules for common/git-hooks.claude/rules/typescript/typescript-linting.md— Rules for typescript/linting.claude/rules/typescript/typescript-logging.md— Rules for typescript/logging.claude/rules/typescript/typescript-testing.md— Rules for typescript/testing.claude/rules/python/python-linting.md— Rules for python/linting.claude/rules/python/python-logging.md— Rules for python/logging.claude/rules/python/python-testing.md— Rules for python/testing.claude/rules/go/go-linting.md— Rules for go/linting.claude/rules/go/go-logging.md— Rules for go/logging.claude/rules/go/go-testing.md— Rules for go/testing.claude/rules/ansible/ansible-linting.md— Rules for ansible/linting.claude/rules/ansible/ansible-logging.md— Rules for ansible/logging.claude/rules/ansible/ansible-testing.md— Rules for ansible/testing.claude/rules/terraform/terraform-linting.md— Rules for terraform/linting.claude/rules/terraform/terraform-logging.md— Rules for terraform/logging.claude/rules/terraform/terraform-testing.md— Rules for terraform/testing
Created by Ballast. Do not edit this section.
Read and use these skill files in .claude/skills/ when they are relevant:
.claude/skills/owasp-security-scan.skill— run an OWASP-aligned security audit across Go, TypeScript, and Python projects.claude/skills/github-health-check.skill— run a comprehensive GitHub repository health check covering CI status, branch hygiene, and repo configuration