aws-manifest

To generate an AWS infrastructure manifest, use this skill to automate creating the `docs/aws-manifest.md` file. It gathers project context, infers the application type, and collects deployment details to declare your infrastructure needs for Terraform provisioning.

Creating an AWS manifest supports static-site, api, fullstack, worker, and data-pipeline application types. The skill automatically infers your project's application type from project files and git remotes to structure the infrastructure declaration accurately.

Yes, this skill works with Terragrunt and bismuth-aws-org by generating the specific AWS manifest file they consume. It enforces naming and tagging conventions, ensuring the output is validated against the AWS Manifest Spec v1 for seamless downstream provisioning.

To ensure your AWS manifest follows naming and tagging conventions, this skill automatically enforces them during generation. It prompts for project name, tag, environments, and region, then validates the final output against the AWS Manifest Spec v1 requirements.

Before generating an AWS manifest file, you need standard project files and git remotes configured. The skill reads this context to infer the application type and prompts you for specific infrastructure details like deployment methods and target AWS regions.