nix-config

Shape answers so they are immediately actionable instead of long. Use on any response that would otherwise run long — multi-step tasks, explanations, plans, reviews with many findings, or answers that hand back commands, paths, or snippets to run. Leads with the next action, numbers steps, restates progress, caps lists, and gives concrete time estimates. Complements caveman (which handles tone); this handles shape.

Senior software architect for system design, ADRs, microservices evaluation, technology trade-off analysis. Use when designing system architecture, evaluating patterns, creating ADRs, analyzing technology choices, or planning migrations.

Go CLI development with Cobra command hierarchy, Bubbletea interactive TUI, Lipgloss terminal styling, Charmbracelet ecosystem (Bubbles, Huh forms, Glamour markdown rendering), and shell completions. Use when building CLI tools, adding subcommands, creating interactive TUI, styling terminal output, or implementing shell completions.

Cloud architecture design, migration, optimization, and disaster recovery across AWS and Azure. Use when designing VPCs/VNets, IAM/RBAC, compute/storage architectures, cost optimization, multi-cloud patterns, or planning migrations. Both Terraform and CLI approaches.

Datadog monitoring strategy, alert design, tagging governance, dashboard patterns, SLO strategy, log management, cost optimization, and cross-pillar correlation workflows. Use when making architectural decisions about what to monitor, how to alert, how to tag, or how to structure Datadog for a service or platform. Delegates execution to pup CLI and infrastructure-as-code to sre-engineer.

Kubernetes workload management, Helm chart development, cluster troubleshooting, custom operators, configuration management, and multi-cluster administration. Use when deploying workloads, writing Helm charts, debugging pods, creating operators, managing ConfigMaps/Secrets/RBAC, or working with multi-cluster setups.

Implements application observability in Go: structured logging with slog, Prometheus metrics instrumentation, OpenTelemetry distributed tracing, Datadog APM with dd-trace-go, application profiling with pprof, and load testing with k6. Use when instrumenting Go services, adding structured logging, emitting Prometheus metrics, setting up distributed tracing, profiling CPU/memory, running load tests, or deploying monitoring infrastructure with Terraform.

Secure secrets management using Azure Key Vault, HashiCorp Vault, AWS Secrets Manager, or platform-native solutions. Use when storing credentials, managing API keys, handling certificates, configuring secret access in applications, infrastructure (Terraform/Ansible), Kubernetes, or CI/CD pipelines. Also covers secret rotation, scanning, ADO variable groups, workload identity, and least-privilege access patterns.

Use at the start or end of a work session tied to the Obsidian vault. Triggers for loading context — "resume", "catch me up", "what was I working on". Triggers for saving a session — "compress", "save session", "wrap up", "I'm done for today". Works from any project directory.

Defines service level objectives, creates error budget policies, designs incident response procedures, develops capacity models, and produces monitoring configurations and automation scripts for production systems. Use when defining SLIs/SLOs, managing error budgets, building reliable systems at scale, incident management, chaos engineering, toil reduction, capacity planning, Datadog monitors, Datadog SLOs, Terraform reliability patterns, or observability-as-code.

Read, search, create, and update GitLab merge requests, pipelines, issues, and releases via the glab CLI. Use when viewing or creating an MR, checking CI pipeline status, reading or filing issues, or managing releases on GitLab.

Azure DevOps pull request workflows and pipeline design standards. Use when creating or reviewing ADO pull requests, writing azure-pipelines.yml, designing build/release pipelines, or setting branch policies.

Engineers Vector (vector.dev) observability pipelines: VRL authoring, source/transform/sink topology design, Kubernetes agent+aggregator deployment, production hardening (buffers, backpressure, acknowledgements, self-monitoring), and Datadog integration. Use when writing or debugging VRL, wiring Vector sources/transforms/sinks, deploying the Vector agent or aggregator on Kubernetes, tuning buffers or backpressure, or shipping logs and metrics to Datadog.

Read, search, create, and update Jira issues via browser automation. Use when viewing a Jira ticket, running a JQL or natural-language issue search, creating an issue, or transitioning/commenting/reassigning an existing issue.

Temporal workflow orchestration — durable execution, worker development, testing, versioning, and operations. Use when writing or reviewing Temporal workflows/activities, configuring workers, debugging non-determinism errors, setting up replay testing, versioning with patches, tuning worker performance, operating Temporal clusters, designing entity workflows, platform control planes, multi-tenant patterns, Nexus cross-namespace communication, or saga compensation.

Apache Airflow DAG development, testing, performance tuning, security, and operations. Use when writing or reviewing DAGs, configuring Airflow, optimizing scheduler performance, setting up CI/CD for DAGs, managing secrets backends, or migrating to Airflow 3.x.

Sync Obsidian documents to Confluence wiki pages via browser automation. Use when pushing docs to Confluence, pulling or replying to comments, incorporating comment feedback, checking page status, or creating new wiki pages.

Use when asked to audit configs, check config freshness, verify tool configs are up to date, or after upgrading nix flake inputs.

Documentation code of conduct. Use when writing, reviewing, or editing documentation for the wiki, ADRs, specs, or any team-facing documents.

Designs and builds Internal Developer Platforms (IDPs) with self-service golden paths, developer experience as product, and measurable outcomes. Use when building IDPs, designing golden paths, creating self-service workflows, platform team structure, developer portals, platform contracts, or evaluating build-vs-adopt decisions for platform capabilities.

Use when writing, reviewing, or editing strategy documents, concept papers, or decision documents scoped to 'what and why' rather than 'how'. Triggers: strategy, concept, SRE strategy, architecture strategy, platform strategy, decision document, strategy review, strategy trimming.

Use when reviewing a pull request or your current branch before merging. Triggers: PR URL (GitHub or Azure DevOps), 'review my branch', 'review this PR', local branch review, pre-merge check. Auto-detects platform from URL or git remote.