{
  "instructions": [
    {
      "instruction": "Read references/best_practices.md BEFORE starting any validation. This is a mandatory first step.",
      "relevant_when": "Any Terragrunt validation request.",
      "why_given": "Step 0 of the Validation Workflow is explicitly labelled 'MANDATORY FIRST STEP' and states 'You MUST read the best practices reference file BEFORE starting validation. This is not optional.'"
    },
    {
      "instruction": "After running detect_custom_resources.py, look up documentation for EVERY detected custom provider and module using context7 MCP (preferred) or WebSearch fallback. Do not skip any.",
      "relevant_when": "detect_custom_resources.py output lists any non-HashiCorp provider or remote module.",
      "why_given": "The Documentation Lookup section is labelled CRITICAL and states 'you MUST look up documentation for EACH ONE. Do not skip any.'"
    },
    {
      "instruction": "Verify each item in all four checklists (Configuration Pattern, Dependency Management, Security, DRY Principle) and document each result as pass or fail. Incomplete verification is not acceptable.",
      "relevant_when": "Best Practices Check section of validation workflow.",
      "why_given": "The Best Practices Check section is labelled REQUIRED and states 'You MUST verify each checklist item below and document the result. Incomplete verification is not acceptable.'"
    },
    {
      "instruction": "Use 'terragrunt run --all validate' (not 'terragrunt validate' in a single unit) to validate the entire dependency graph.",
      "relevant_when": "Validating a project with multiple Terragrunt units.",
      "why_given": "Anti-Patterns section states 'NEVER validate only the current unit in isolation' because dependency chains may fail even when individual units pass."
    },
    {
      "instruction": "Use 'terragrunt dag graph' (not 'graph-dependencies') to visualise the dependency graph. The graph-dependencies command is deprecated in Terragrunt 0.93+.",
      "relevant_when": "Validating dependency relationships between Terragrunt units.",
      "why_given": "The Dependency Graph Validation section notes 'graph-dependencies command replaced with dag graph in Terragrunt 0.93+' and the skill targets 0.93+."
    },
    {
      "instruction": "When diagnosing HCL function errors, use --terragrunt-log-level debug (or TG_LOG=debug) to get the full HCL evaluation trace.",
      "relevant_when": "HCL function errors such as path_relative_to_include() or find_in_parent_folders() produce cryptic messages.",
      "why_given": "Anti-Patterns section states 'NEVER skip --terragrunt-log-level debug when diagnosing HCL function errors' because debug mode shows evaluated function calls."
    },
    {
      "instruction": "Flag root configuration files named 'terragrunt.hcl' as an anti-pattern in Terragrunt 0.93+. The root file should be named 'root.hcl'.",
      "relevant_when": "Finding a file named terragrunt.hcl at the root of the infrastructure directory.",
      "why_given": "The Troubleshooting section documents the 'Root terragrunt.hcl anti-pattern warning' and states root configs should be named root.hcl in 0.93+."
    }
  ]
}