skilld
All skills
google avatar

/application-design-center-design-deploy

@becc4b8
by googlegoogle/skills21k stars
1,698

Processes GCP infrastructure design and deployment workflows within Application Design Center (ADC). Use when: - Designing GCP infrastructure with Terraform. - Validating local HCL. - Performing best-practice plan scans. - Importing templates to Application Design Center (ADC). - Deploying templates. - Troubleshooting deployment failures. Boundaries: - Only use for GCP-specific cloud infrastructure. - Only use for Terraform coding within the ADC context.

Ask your Agent

Use this Skill: https://skilld.dev/gh/google/skills/application-design-center-design-deploy

This session only. Nothing lands on disk.

referencesterraform_validator_instructions.md

≈638 tokens on demand. Your agent reads this file only when SKILL.md points to it.

Terraform Validation Guidelines

You act as a semantic validator to review module configurations and verify they are fully production-ready.

1. Key Validator Assertions

During validation, verify these parameters:

  • Enforce Module Preference (CRITICAL): Verify that the configuration prioritizes modules over direct resource blocks. Resource blocks are allowed only if no suitable approved module is available from the registry or templates. Flag any resource block that maps to an available approved module.
  • Match Input Code Style: If the input has user-provided Terraform/HCL code, relax the module-preference check. The validated code should match the user's coding style (e.g., resources vs. modules) and not be rewritten in a module-centric way.
  • Static Configuration Checks: Verify that no locals, for_each, or count statements are declared.
  • Encourage Configurable Variables: Verify that configurable parameters (like project ID, region, resource names) are parameterized using variable blocks in variables.tf, with default values defined in terraform.tfvars. Avoid hardcoding environment-specific values.
  • Inspect Inter-Module Output Bindings:
    • Enforce that database connection strings, network identifiers (subnets, VPC names), and keys/endpoints are set via output bindings from other modules, except for pre-existing default configurations (like the network or subnet named "default").
    • Flag manual text assignments that should be structured module-output linkages, unless they are intentionally referencing default pre-existing GCP project resources like "default".
  • Enforce Pinned GitHub Source Format: Ensure that every module's source uses the GitHub repository source path (e.g., github.com/...) instead of the registry format.
  • Assert Mandatory Version Pinning (CRITICAL): Verify that every single module block containing a Git/GitHub source has a ?ref=... parameter appended, and that the tag matches the registry's refTag of the corresponding component revision exactly. Flag any version-less Git source as a critical validation failure.

2. Handover

If all validations are successfully cleared and the setup matches the design CUJs, output exactly: LGTM.

Source: SKILL.md on GitHub

Third-party checks

No alerts10d3 checks · Risk SAFE
  • Gen Agent Trust Hub10d

    This skill facilitates the design and deployment of GCP infrastructure using Terraform and Google Application Design Center. It incorporates security best practices such as mandatory secret management and local state isolation. External operations are restricted to trusted official repositories and Google Cloud services.

  • Socket10d

    No alerts

  • Snyk10d

    Risk: LOW · No issues

Provenance

Signed by skilld at becc4b8. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub yesterday.

Activeupdated 2 weeks ago

Capability

Other metadata
metadata
{
  "version": "1.0.0",
  "publisher": "google",
  "category": "CloudInfrastructure"
}

README badge

README badge for google/skills/application-design-center-design-deploy