Show HN: Droidctx – 코딩 에이전트를 위한 프로덕션 인프라에서 Markdown 문서를 생성합니다.

Infrastructure context builder for Claude Code and coding agents. Connect your production tools (Grafana, Datadog, Kubernetes, CloudWatch, databases, etc.), extract metadata, and generate structured .md files that give coding agents instant context about your infrastructure. # Install (creates an isolated venv at ~/.droidctx automatically) curl -fsSL https://raw.githubusercontent.com/DrDroidLab/context-builder/main/install.sh | bash # Or via pipx pipx install git+https://github.com/DrDroidLab/context-builder.git # Or manually with a venv python3 -m venv ~/.droidctx && ~/.droidctx/bin/pip install git+https://github.com/DrDroidLab/context-builder.git && mkdir -p ~/.local/bin && ln -sf ~/.droidctx/bin/droidctx ~/.local/bin/droidctx # 1. Initialize project (creates ./droidctx-context/) droidctx init # 2. Auto-detect credentials from local CLI tools (kubectl, aws, gcloud, az) droidctx detect # 3. Add any additional credentials manually vim ./droidctx-context/credentials.yaml # 4. Sync infrastructure metadata droidctx sync # 5. Add the suggested prompt to your CLAUDE.md After running droidctx sync , your context directory will contain: my-infra/ resources/ overview.md # Summary of all connected tools connectors/ grafana_prod/ _summary.md # Resource counts for this connector datasources.md # Grafana datasources dashboards.md # Dashboard index dashboards/ api-gateway.md # Individual dashboard with panels & queries payment-service.md alerts.md # Alert rules k8s_production/ _summary.md namespaces.md deployments.md services.md ingresses.md ... datadog_prod/ _summary.md monitors.md services.md dashboards.md postgres_main/ _summary.md tables.md cross_references/ services.md # Services seen across multiple connectors After syncing, add this to your CLAUDE.md : My production infrastructure context is in ./my-infra/resources/. Refer to this when investigating issues, writing queries, or understanding system topology. Creates folder structure and a credentials template. droidctx init # Creates ./droidctx-context/ droidctx init --path ./my-infra # Custom path Auto-detects credentials from locally configured CLI tools and populates credentials.yaml . Scans for kubectl , aws , gcloud , and az , extracts their active configurations, and merges discovered connectors into your credentials file without overwriting existing entries. droidctx detect # Uses ./droidctx-context/credentials.yaml droidctx detect --keyfile ./my-infra/creds.yaml # Custom keyfile What gets detected: | CLI Tool | Connectors Created | Values Extracted | |---|---|---| kubectl | KUBERNETES (cli mode) | Cluster name from current context | aws | CLOUDWATCH, EKS | Region, EKS cluster names | gcloud | GKE, GCM | Project ID, zone, GKE cluster names | az | AZURE | Tenant ID, subscription ID (client ID/secret need manual entry) | Kubernetes connectors created by detect use CLI mode (_cli_mode: true ), which means they extract resources directly via kubectl using your current kubeconfig context — no API server URL or token needed. Connects to your tools, extracts metadata, and generates .md context files. droidctx sync # Uses ./droidctx-context/credentials.yaml droidctx sync --keyfile ./my-infra/creds.yaml # Custom keyfile droidctx sync --connectors grafana_prod,k8s_prod # Sync specific connectors droidctx sync --dry-run # Preview what would be synced droidctx sync --verbose # Verbose logging Validates credentials format and checks for required CLI tools. droidctx check # Uses ./droidctx-context/credentials.yaml droidctx check --keyfile ./my-infra/creds.yaml # Custom keyfile Shows all supported connector types and their required fields. droidctx list-connectors droidctx list-connectors --type GRAFANA Keep your context files fresh automatically. Uses launchd on macOS and cron on Linux. # Enable auto-sync (runs every 30 minutes by default) droidctx auto-sync enable --keyfile ./droidctx-context/credentials.yaml # Custom interval (in minutes) droidctx auto-sync enable --keyfile ./droidctx-context/credentials.yaml --interval 60 # Check status droidctx auto-sync status # Disable droidctx auto-sync disable Logs are written to ~/.config/droidctx/auto-sync.log . macOS note: You may need to allow droidctx in System Settings → Privacy & Security the first time. Create a YAML file with your connector credentials. Run droidctx init to generate a template with all supported types, or droidctx detect to auto-populate from your CLI tools. # Auto-detected by `droidctx detect` (uses kubectl directly, no token needed) k8s_my-cluster: type: "KUBERNETES" _cli_mode: true cluster_name: my-cluster # Auto-detected by `droidctx detect` cloudwatch_us-east-1: type: "CLOUDWATCH" region: us-east-1 # Manual entry grafana_prod: type: "GRAFANA" grafana_host: https://your-grafana.com grafana_api_key: glsa_xxxxxxxxxxxx datadog_prod: type: "DATADOG" dd_api_key: your_api_key dd_app_key: your_app_key # Standard Kubernetes (API server + token, without CLI mode) k8s_production: type: "KUBERNETES" cluster_nam