# CLAUDE.md

This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.

## Project overview

### Repository structure

- `main.tf`: Main Terraform configuration file.
- `variables.tf`: File containing all Terraform variables.
- `outputs.tf`: File containing all Terraform outputs.
- `modules/`: Directory containing reusable Terraform modules.

### Code conventions

Resources must be named using the following convention: `<resource_type>_<resource_name>`. 
Commits must follow the conventional commit format: `<type>(<scope>): <description>`.

## Forbidden actions

* Never push directly to the main branch. Always create a feature branch and submit a pull request for review./
* Never use hardcoded values in Terraform files. Always use variables or data sources.
* Never store sensitive information in the repository. Use a secure secrets management solution instead./

---
name: create-module
description: Create a new Terraform module. Use this skill when user asks to create a new Terraform module with a standard file structure.
---

Create a new Terraform module scaffold. The module name comes from `$ARGUMENTS` (kebab-case). If empty, ask the user for the name before proceeding.

Create the directory `modules/<name>/` with exactly these five files:

**`modules/<name>/main.tf`**

**`modules/<name>/variables.tf`**

**`modules/<name>/outputs.tf`**

**`modules/<name>/README.md`**

Check https://registry.terraform.io/ to fill those files with the appropriate content for a Terraform module.

You must use the latest version for the given provider if appropriate, pin the exact version (wildcard versions are not allowed). 
Enrich the `README.md` with a description of the module, usage instructions, and examples.

Do not add any other files or directories beyond these five.

After creating the files, list them with their relative paths, then remind the user to:
- Ensure every variable in `variables.tf` has both `description` and `type` set.

---
name: create-pr
description: Create a new Github Pull Request. Use this skill when user asks to create a new Github Pull Request.
---

Pre-requisites before creating a PR :
* Ensure no sensitive information is present in the code changes (e.g., passwords, API keys, secrets).
* Run terraform fmt, terraform validate to ensure the code is properly formatted and valid.
* Ensure each commit message follows the conventional commit format (e.g., feat: add new feature, fix: fix bug, docs: update documentation).

1. Create a new Github Pull Request for the current branch. The title of the PR comes from `$ARGUMENTS`. If empty, ask the user for the title before proceeding.

2. The PR description should be generated based on the changes in the current branch. If `$ARGUMENTS` contains a description, use it instead.

3. The PR should be created against the default branch of the repository (usually `main` or `master`).

4. After creating the PR, output the URL of the newly created PR.