type: user

role: user

content:
Create the file `/Users/steve.briggs/projects/operations/terraform/iac-library/aws/storage/database-tools-db/variables.tf` with this exact content:

```hcl
# ---------------------------------------------------------------------------------------------------------------------
# REQUIRED PARAMETERS
# ---------------------------------------------------------------------------------------------------------------------

variable "env" {
  description = "The environment (dev, staging, prod)"
  type        = string
  validation {
    condition     = var.env != null && var.env != ""
    error_message = "Env must be set"
  }
}

variable "vpc_id" {
  description = "The ID of the VPC the RDS instance will be deployed into"
  type        = string
}

variable "private_subnet_ids" {
  description = "List of private subnets in the VPC for the RDS Subnet Group"
  type        = list(string)
}

variable "trusted_cidr_blocks" {
  description = "CIDR blocks allowed to access the RDS instance on port 5432"
  type        = list(string)
}

variable "pg_version" {
  description = "Postgres database version prefix"
  type        = string
}

# ---------------------------------------------------------------------------------------------------------------------
# OPTIONAL PARAMETERS
# ---------------------------------------------------------------------------------------------------------------------

variable "name" {
  description = "The name of the RDS instance. Defaults to tools-database-<env>"
  type        = string
  default     = ""
}

variable "db_name" {
  description = "Database name to create when creating the DB instance"
  type        = string
  default     = ""
}

variable "admin_username" {
  description = "Database admin user"
  type        = string
  default     = "immuta_postgres"
}

variable "rds_instance_size" {
  description = "RDS instance size"
  type        = string
  default     = "db.t4g.small"
}

variable "allocated_storage" {
  description = "Initial storage allocated in GiB"
  type        = number
  default     = 20
}

variable "max_allocated_storage" {
  description = "Upper limit for storage autoscaling in GiB"
  type        = number
  default     = 50
}

variable "storage_encrypted" {
  description = "Whether to encrypt the RDS instance"
  type        = bool
  default     = true
}

variable "storage_type" {
  description = "Storage type of the RDS instance"
  type        = string
  default     = "gp3"
}

variable "encrypt_replicas" {
  description = "Whether to encrypt backup replicas"
  type        = bool
  default     = true
}

variable "multi_az" {
  description = "Deploy the RDS instance as multi-AZ"
  type        = bool
  default     = false
}

variable "final_snapshot" {
  description = "Take a final snapshot before destroying the DB instance"
  type        = bool
  default     = false
}

variable "backup_retention_period" {
  description = "Days to retain backups (0-35)"
  type        = number
  default     = 21
}

variable "replica_retention_period" {
  description = "Days to retain backup replicas (0-35)"
  type        = number
  default     = 21
}

variable "enhanced_monitoring_enabled" {
  description = "Enable enhanced monitoring"
  type        = bool
  default     = true
}

variable "performance_insights_enabled" {
  description = "Enable performance insights"
  type        = bool
  default     = true
}

variable "kms_key_deletion_window_in_days" {
  description = "Days to retain KMS key after deletion"
  type        = number
  default     = 30
}

variable "subnet_group_name_override" {
  description = "Override for subnet group name"
  type        = string
  default     = ""
}

variable "dba_security_group_name_override" {
  description = "Override for external access SG name"
  type        = string
  default     = ""
}

variable "security_group_name_override" {
  description = "Override for local access SG name"
  type        = string
  default     = ""
}

variable "ca_cert_identifier" {
  description = "RDS CA cert identifier"
  type        = string
  default     = "rds-ca-rsa2048-g1"
}

variable "parameters" {
  description = "A map of DB parameters to apply via a parameter group. If empty, the default parameter group is used"
  type        = set(map(string))
  default     = []
}

variable "vault_secret_path" {
  description = "Vault KV path to store admin credentials"
  type        = string
  default     = "platform/tools-database"
}

variable "tags" {
  description = "Tags to apply to created resources"
  type        = map(string)
  default     = {}
}
```

Then verify formatting:
```bash
cd /Users/steve.briggs/projects/operations/terraform/iac-library/aws/storage/database-tools-db
terraform fmt -check variables.tf
```

Run `terraform fmt variables.tf` to fix any diffs, then re-check.

End with `STATUS: DONE` or `STATUS: BLOCKED`.

userType: external

entrypoint: cli


content:
- obsidian-load: Load context from Obsidian notes in the `Claude/` directory into the current conversation.
- obsidian-save: Save current conversation context to an Obsidian note under the `Claude/` directory.
- mind:search: Search memories for specific content or patterns
- mind:stats: Show memory statistics and storage information
- mind:ask: Ask questions about memories and get context-aware answers
- mind:recent: Show recent memories and activity timeline
- mind:memory: Claude Mind - Search and manage Claude's persistent memory stored in a single portable .mv2 file
- mind:mind: Claude Mind - Search and manage Claude's persistent memory stored in a single portable .mv2 file
- superpowers:dispatching-parallel-agents: Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies
- superpowers:test-driven-development: Use when implementing any feature or bugfix, before writing implementation code
- superpowers:systematic-debugging: Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
- superpowers:executing-plans: Use when you have a written implementation plan to execute in a separate session with review checkpoints
- superpowers:using-superpowers: Use when starting any conversation - establishes how to find and use skills, requiring Skill tool invocation before ANY response including clarifying questions
- superpowers:using-git-worktrees: Use when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback
- superpowers:requesting-code-review: Use when completing tasks, implementing major features, or before merging to verify work meets requirements
- superpowers:finishing-a-development-branch: Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for merge, PR, or cleanup
- superpowers:brainstorming: You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
- superpowers:writing-plans: Use when you have a spec or requirements for a multi-step task, before touching code
- superpowers:receiving-code-review: Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation
- superpowers:verification-before-completion: Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always
- superpowers:writing-skills: Use when creating new skills, editing existing skills, or verifying skills work before deployment
- superpowers:subagent-driven-development: Use when executing implementation plans with independent tasks in the current session
- update-config: Use this skill to configure the Claude Code harness via settings.json. Automated behaviors ("from now on when X", "each time X", "whenever X", "before/after X") require hooks configured in settings.json - the harness executes these, not Claude, so memory/preferences cannot fulfill them. Also use for: permissions ("allow X", "add permission", "move permission to"), env vars ("set X=Y"), hook troubleshooting, or any changes to settings.json/settings.local.json files. Examples: "allow npm commands", "add bq permission to global settings", "move permission to user settings", "set DEBUG=true", "when claude stops show X". For simple settings like theme/model, suggest the /config command.
- keybindings-help: Use when the user wants to customize keyboard shortcuts, rebind keys, add chord bindings, or modify ~/.claude/keybindings.json. Examples: "rebind ctrl+s", "add a chord shortcut", "change the submit key", "customize keybindings".
- verify: Verify that a code change actually does what it's supposed to by running the app and observing behavior. Use when asked to verify a PR, confirm a fix works, test a change manually, check that a feature works, or validate local changes before pushing.
- simplify: Review changed code for reuse, quality, and efficiency, then fix any issues found.
- fewer-permission-prompts: Scan your transcripts for common read-only Bash and MCP tool calls, then add a prioritized allowlist to project .claude/settings.json to reduce permission prompts.
- loop: Run a prompt or slash command on a recurring interval (e.g. /loop 5m /foo). Omit the interval to let the model self-pace. - When the user wants to set up a recurring task, poll for status, or run something repeatedly on an interval (e.g. "check the deploy every 5 minutes", "keep running /babysit-prs"). Do NOT invoke for one-off tasks.
- schedule: Create, update, list, or run scheduled remote agents (routines) that execute on a cron schedule. - When the user wants to schedule a recurring remote agent, set up automated tasks, create a cron job for Claude Code, or manage their scheduled agents/routines. Also use when the user wants a one-time scheduled run ("run this once at 3pm", "remind me to check X tomorrow").
- claude-api: Build, debug, and optimize Claude API / Anthropic SDK apps. Apps built with this skill should include prompt caching. Also handles migrating existing Claude API code between Claude model versions (4.5 → 4.6, 4.6 → 4.7, retired-model replacements).
TRIGGER when: code imports `anthropic`/`@anthropic-ai/sdk`; user asks for the Claude API, Anthropic SDK, or Managed Agents; user adds/modifies/tunes a Claude feature (caching, thinking, compaction, tool use, batch, files, citations, memory) or model (Opus/Sonnet/Haiku) in a file; questions about prompt caching / cache hit rate in an Anthropic SDK project.
SKIP: file imports `openai`/other-provider SDK, filename like `*-openai.py`/`*-generic.py`, provider-neutral code, general programming/ML.
- run: Launch and drive this project's app to see a change working. Use when asked to run, start, or screenshot the app, or to confirm a change works in the real app (not just tests). First looks for a project skill that already covers launching the app; otherwise falls back to built-in patterns per project type (CLI, server, TUI, Electron, browser-driven, library).
- init: Initialize a new CLAUDE.md file with codebase documentation
- review: Review a pull request
- security-review: Complete a security review of the pending changes on the current branch

type: attachment


type: message

role: assistant

type: text

text: I'll create the file and verify its formatting.

service_tier: standard

attributionAgent: general-purpose

attributionPlugin: superpowers

type: assistant


Write

content:
# ---------------------------------------------------------------------------------------------------------------------
# REQUIRED PARAMETERS
# ---------------------------------------------------------------------------------------------------------------------

variable "env" {
  description = "The environment (dev, staging, prod)"
  type        = string
  validation {
    condition     = var.env != null && var.env != ""
    error_message = "Env must be set"
  }
}

variable "vpc_id" {
  description = "The ID of the VPC the RDS instance will be deployed into"
  type        = string
}

variable "private_subnet_ids" {
  description = "List of private subnets in the VPC for the RDS Subnet Group"
  type        = list(string)
}

variable "trusted_cidr_blocks" {
  description = "CIDR blocks allowed to access the RDS instance on port 5432"
  type        = list(string)
}

variable "pg_version" {
  description = "Postgres database version prefix"
  type        = string
}

# ---------------------------------------------------------------------------------------------------------------------
# OPTIONAL PARAMETERS
# ---------------------------------------------------------------------------------------------------------------------

variable "name" {
  description = "The name of the RDS instance. Defaults to tools-database-<env>"
  type        = string
  default     = ""
}

variable "db_name" {
  description = "Database name to create when creating the DB instance"
  type        = string
  default     = ""
}

variable "admin_username" {
  description = "Database admin user"
  type        = string
  default     = "immuta_postgres"
}

variable "rds_instance_size" {
  description = "RDS instance size"
  type        = string
  default     = "db.t4g.small"
}

variable "allocated_storage" {
  description = "Initial storage allocated in GiB"
  type        = number
  default     = 20
}

variable "max_allocated_storage" {
  description = "Upper limit for storage autoscaling in GiB"
  type        = number
  default     = 50
}

variable "storage_encrypted" {
  description = "Whether to encrypt the RDS instance"
  type        = bool
  default     = true
}

variable "storage_type" {
  description = "Storage type of the RDS instance"
  type        = string
  default     = "gp3"
}

variable "encrypt_replicas" {
  description = "Whether to encrypt backup replicas"
  type        = bool
  default     = true
}

variable "multi_az" {
  description = "Deploy the RDS instance as multi-AZ"
  type        = bool
  default     = false
}

variable "final_snapshot" {
  description = "Take a final snapshot before destroying the DB instance"
  type        = bool
  default     = false
}

variable "backup_retention_period" {
  description = "Days to retain backups (0-35)"
  type        = number
  default     = 21
}

variable "replica_retention_period" {
  description = "Days to retain backup replicas (0-35)"
  type        = number
  default     = 21
}

variable "enhanced_monitoring_enabled" {
  description = "Enable enhanced monitoring"
  type        = bool
  default     = true
}

variable "performance_insights_enabled" {
  description = "Enable performance insights"
  type        = bool
  default     = true
}

variable "kms_key_deletion_window_in_days" {
  description = "Days to retain KMS key after deletion"
  type        = number
  default     = 30
}

variable "subnet_group_name_override" {
  description = "Override for subnet group name"
  type        = string
  default     = ""
}

variable "dba_security_group_name_override" {
  description = "Override for external access SG name"
  type        = string
  default     = ""
}

variable "security_group_name_override" {
  description = "Override for local access SG name"
  type        = string
  default     = ""
}

variable "ca_cert_identifier" {
  description = "RDS CA cert identifier"
  type        = string
  default     = "rds-ca-rsa2048-g1"
}

variable "parameters" {
  description = "A map of DB parameters to apply via a parameter group. If empty, the default parameter group is used"
  type        = set(map(string))
  default     = []
}

variable "vault_secret_path" {
  description = "Vault KV path to store admin credentials"
  type        = string
  default     = "platform/tools-database"
}

variable "tags" {
  description = "Tags to apply to created resources"
  type        = map(string)
  default     = {}
}

type: direct


content: File created successfully at: /Users/steve.briggs/projects/operations/terraform/iac-library/aws/storage/database-tools-db/variables.tf (file state is current in your context — no need to Read it back)


text: Now let me verify the formatting:


Bash

command: cd /Users/steve.briggs/projects/operations/terraform/iac-library/aws/storage/database-tools-db && terraform fmt -check variables.tf

speed: standard


content: (Bash completed with no output)


text:
Perfect! The file is already properly formatted according to terraform fmt standards.

STATUS: DONE

The variables.tf file has been created at `/Users/steve.briggs/projects/operations/terraform/iac-library/aws/storage/database-tools-db/variables.tf` with all the specified content. The terraform fmt check passed with no formatting issues.