terradart: Skill for Claude Code

Tighten example topology

Use after terradart-backfill-examples when a quickstart gained coverage-only resources that synth + validate but are not linked into the stack.

When to use

• Reviewer or agent notices factories that "exist only to appear in synth output."
• dart tool/check_example_topology.dart reports unwired must-reference types on a strict quickstart.
• Before merging a large example extension (especially compute_lb_quickstart).

Workflow

• 1. Identify orphans — resources with no incoming TfArg.ref / dependsOn from siblings. Natural leaf nodes (forwarding rules, IAM members, one-shot jobs, firewalls) do not need incoming refs.

• 2. Wire must-reference types (common cases):

  Factory type	Wire into
  GoogleComputeSslCertificate	sslCertificates on GoogleComputeTargetSslProxy / GoogleComputeTargetHttpsProxy
  GoogleComputeRegionSslCertificate	sslCertificates on GoogleComputeRegionTargetHttpsProxy
  GoogleComputeRegionHealthCheck	healthChecks on GoogleComputeRegionBackendService
  GoogleComputeTargetHttpProxy	target on GoogleComputeGlobalForwardingRule (port 80)
  GoogleComputeRegionTargetHttpProxy	target on GoogleComputeForwardingRule (regional ILB)

• 3. Reorder add(...) blocks so referenced resources are created before consumers; capture final x = add(...) when later siblings need TfArg.ref(x.*).

• 4. Sensitive fields — keep TfArg.variable + variables.tf.json (see backfill skill).

• 5. Register strict quickstarts — add slug to strict: in tool/example_topology_allowlist.yaml when the example should enforce must-reference rules in CI.

• 6. Verify:

  dart tool/check_example_topology.dart
  dart tool/check_docs_consistency.dart
  tool/agent_verify.sh
  

Automation

tool/check_example_topology.dart scans synth JSON for Terraform types listed under must_be_referenced in tool/example_topology_allowlist.yaml. If the resource address appears only once, the quickstart is unwired.