Merge pull request #124 from ssumanbiswas/feat/aws-iac-skills

feat: add AWS Infrastructure as Code skills
This commit is contained in:
sickn33
2026-02-24 13:38:00 +01:00
committed by GitHub
8 changed files with 352 additions and 9 deletions

View File

@@ -2,9 +2,9 @@
Generated at: 2026-02-08T00:00:00.000Z
Total skills: 927
Total skills: 930
## architecture (63)
## architecture (64)
| Skill | Description | Tags | Triggers |
| --- | --- | --- | --- |
@@ -24,6 +24,7 @@ Total skills: 927
| `c4-container` | Expert C4 Container-level documentation specialist. Synthesizes | c4, container | c4, container, level, documentation, synthesizes |
| `c4-context` | Expert C4 Context-level documentation specialist. Creates | c4 | c4, context, level, documentation, creates |
| `calendly-automation` | Automate Calendly scheduling, event management, invitee tracking, availability checks, and organization administration via Rube MCP (Composio). Always search... | calendly | calendly, automation, automate, scheduling, event, invitee, tracking, availability, checks, organization, administration, via |
| `cloudformation-best-practices` | CloudFormation template optimization, nested stacks, drift detection, and production-ready patterns. Use when writing or reviewing CF templates. | cloudformation, best, practices | cloudformation, best, practices, optimization, nested, stacks, drift, detection, writing, reviewing, cf |
| `code-refactoring-refactor-clean` | You are a code refactoring expert specializing in clean code principles, SOLID design patterns, and modern software engineering best practices. Analyze and r... | code, refactoring, refactor, clean | code, refactoring, refactor, clean, specializing, principles, solid, software, engineering, analyze, provided, improve |
| `codebase-cleanup-refactor-clean` | You are a code refactoring expert specializing in clean code principles, SOLID design patterns, and modern software engineering best practices. Analyze and r... | codebase, cleanup, refactor, clean | codebase, cleanup, refactor, clean, code, refactoring, specializing, principles, solid, software, engineering, analyze |
| `context-degradation` | Recognize patterns of context failure: lost-in-middle, poisoning, distraction, and clash | degradation | degradation, context, recognize, failure, lost, middle, poisoning, distraction, clash |
@@ -648,7 +649,7 @@ Total skills: 927
| `x-article-publisher-skill` | Publish articles to X/Twitter | x, article, publisher, skill | x, article, publisher, skill, publish, articles, twitter |
| `youtube-summarizer` | Extract transcripts from YouTube videos and generate comprehensive, detailed summaries using intelligent analysis frameworks | video, summarization, transcription, youtube, content-analysis | video, summarization, transcription, youtube, content-analysis, summarizer, extract, transcripts, videos, generate, detailed, summaries |
## infrastructure (90)
## infrastructure (92)
| Skill | Description | Tags | Triggers |
| --- | --- | --- | --- |
@@ -670,6 +671,7 @@ Total skills: 927
| `bash-pro` | Master of defensive Bash scripting for production automation, CI/CD | bash | bash, pro, defensive, scripting, automation, ci, cd |
| `bats-testing-patterns` | Master Bash Automated Testing System (Bats) for comprehensive shell script testing. Use when writing tests for shell scripts, CI/CD pipelines, or requiring t... | bats | bats, testing, bash, automated, shell, script, writing, tests, scripts, ci, cd, pipelines |
| `box-automation` | Automate Box cloud storage operations including file upload/download, search, folder management, sharing, collaborations, and metadata queries via Rube MCP (... | box | box, automation, automate, cloud, storage, operations, including, file, upload, download, search, folder |
| `cdk-patterns` | Common AWS CDK patterns and constructs for building cloud infrastructure with TypeScript, Python, or Java. Use when designing reusable CDK stacks and L3 cons... | cdk | cdk, common, aws, constructs, building, cloud, infrastructure, typescript, python, java, designing, reusable |
| `cicd-automation-workflow-automate` | You are a workflow automation expert specializing in creating efficient CI/CD pipelines, GitHub Actions workflows, and automated development processes. Desig... | cicd, automate | cicd, automate, automation, specializing, creating, efficient, ci, cd, pipelines, github, actions, automated |
| `claude-d3js-skill` | Creating interactive data visualisations using d3.js. This skill should be used when creating custom charts, graphs, network diagrams, geographic visualisati... | claude, d3js, skill | claude, d3js, skill, creating, interactive, data, visualisations, d3, js, should, used, custom |
| `cloud-architect` | Expert cloud architect specializing in AWS/Azure/GCP multi-cloud | cloud | cloud, architect, specializing, aws, azure, gcp, multi |
@@ -734,6 +736,7 @@ Total skills: 927
| `service-mesh-observability` | Implement comprehensive observability for service meshes including distributed tracing, metrics, and visualization. Use when setting up mesh monitoring, debu... | service, mesh, observability | service, mesh, observability, meshes, including, distributed, tracing, metrics, visualization, setting, up, monitoring |
| `slo-implementation` | Define and implement Service Level Indicators (SLIs) and Service Level Objectives (SLOs) with error budgets and alerting. Use when establishing reliability t... | slo | slo, define, level, indicators, slis, objectives, slos, error, budgets, alerting, establishing, reliability |
| `sql-pro` | Master modern SQL with cloud-native databases, OLTP/OLAP | sql | sql, pro, cloud, native, databases, oltp, olap |
| `terraform-aws-modules` | Terraform module creation for AWS — reusable modules, state management, and HCL best practices. Use when building or reviewing Terraform AWS infrastructure. | terraform, aws, modules | terraform, aws, modules, module, creation, reusable, state, hcl, building, reviewing, infrastructure |
| `terraform-infrastructure` | Terraform infrastructure as code workflow for provisioning cloud resources, creating reusable modules, and managing infrastructure at scale. | terraform, infrastructure | terraform, infrastructure, code, provisioning, cloud, resources, creating, reusable, modules, managing, scale |
| `terraform-module-library` | Build reusable Terraform modules for AWS, Azure, and GCP infrastructure following infrastructure-as-code best practices. Use when creating infrastructure mod... | terraform, module, library | terraform, module, library, reusable, modules, aws, azure, gcp, infrastructure, following, code, creating |
| `terraform-skill` | Terraform infrastructure as code best practices | terraform, skill | terraform, skill, infrastructure, code |

View File

@@ -1,6 +1,6 @@
# 🌌 Antigravity Awesome Skills: 927+ Agentic Skills for Claude Code, Gemini CLI, Cursor, Copilot & More
# 🌌 Antigravity Awesome Skills: 930+ Agentic Skills for Claude Code, Gemini CLI, Cursor, Copilot & More
> **The Ultimate Collection of 927+ Universal Agentic Skills for AI Coding Assistants — Claude Code, Gemini CLI, Codex CLI, Antigravity IDE, GitHub Copilot, Cursor, OpenCode, AdaL**
> **The Ultimate Collection of 930+ Universal Agentic Skills for AI Coding Assistants — Claude Code, Gemini CLI, Codex CLI, Antigravity IDE, GitHub Copilot, Cursor, OpenCode, AdaL**
[![License: MIT](https://img.shields.io/badge/License-MIT-yellow.svg)](https://opensource.org/licenses/MIT)
[![Claude Code](https://img.shields.io/badge/Claude%20Code-Anthropic-purple)](https://claude.ai)
@@ -17,7 +17,7 @@
If this project helps you, you can [support it here](https://buymeacoffee.com/sickn33) or simply ⭐ the repo.
**Antigravity Awesome Skills** is a curated, battle-tested library of **927 high-performance agentic skills** designed to work seamlessly across all major AI coding assistants:
**Antigravity Awesome Skills** is a curated, battle-tested library of **930 high-performance agentic skills** designed to work seamlessly across all major AI coding assistants:
- 🟣 **Claude Code** (Anthropic CLI)
- 🔵 **Gemini CLI** (Google DeepMind)
@@ -42,7 +42,7 @@ This repository provides essential skills to transform your AI assistant into a
- [🎁 Curated Collections (Bundles)](#curated-collections)
- [🧭 Antigravity Workflows](#antigravity-workflows)
- [📦 Features & Categories](#features--categories)
- [📚 Browse 927+ Skills](#browse-927-skills)
- [📚 Browse 930+ Skills](#browse-930-skills)
- [🤝 How to Contribute](#how-to-contribute)
- [🤝 Community](#community)
- [☕ Support the Project](#support-the-project)
@@ -343,7 +343,7 @@ The repository is organized into specialized domains to transform your AI into a
Counts change as new skills are added. For the current full registry, see [CATALOG.md](CATALOG.md).
## Browse 927+ Skills
## Browse 930+ Skills
We have moved the full skill registry to a dedicated catalog to keep this README clean.

View File

@@ -81,6 +81,7 @@
"cc-skill-coding-standards",
"cc-skill-frontend-patterns",
"cc-skill-security-review",
"cdk-patterns",
"code-documentation-doc-generate",
"context7-auto-research",
"copilot-sdk",

View File

@@ -1,6 +1,6 @@
{
"generatedAt": "2026-02-08T00:00:00.000Z",
"total": 927,
"total": 930,
"skills": [
{
"id": "3d-web-experience",
@@ -5393,6 +5393,30 @@
],
"path": "skills/cc-skill-strategic-compact/SKILL.md"
},
{
"id": "cdk-patterns",
"name": "cdk-patterns",
"description": "Common AWS CDK patterns and constructs for building cloud infrastructure with TypeScript, Python, or Java. Use when designing reusable CDK stacks and L3 constructs.",
"category": "infrastructure",
"tags": [
"cdk"
],
"triggers": [
"cdk",
"common",
"aws",
"constructs",
"building",
"cloud",
"infrastructure",
"typescript",
"python",
"java",
"designing",
"reusable"
],
"path": "skills/cdk-patterns/SKILL.md"
},
{
"id": "changelog-automation",
"name": "changelog-automation",
@@ -5802,6 +5826,31 @@
],
"path": "skills/cloud-penetration-testing/SKILL.md"
},
{
"id": "cloudformation-best-practices",
"name": "cloudformation-best-practices",
"description": "CloudFormation template optimization, nested stacks, drift detection, and production-ready patterns. Use when writing or reviewing CF templates.",
"category": "architecture",
"tags": [
"cloudformation",
"best",
"practices"
],
"triggers": [
"cloudformation",
"best",
"practices",
"optimization",
"nested",
"stacks",
"drift",
"detection",
"writing",
"reviewing",
"cf"
],
"path": "skills/cloudformation-best-practices/SKILL.md"
},
{
"id": "coda-automation",
"name": "coda-automation",
@@ -19247,6 +19296,31 @@
],
"path": "skills/temporal-python-testing/SKILL.md"
},
{
"id": "terraform-aws-modules",
"name": "terraform-aws-modules",
"description": "Terraform module creation for AWS — reusable modules, state management, and HCL best practices. Use when building or reviewing Terraform AWS infrastructure.",
"category": "infrastructure",
"tags": [
"terraform",
"aws",
"modules"
],
"triggers": [
"terraform",
"aws",
"modules",
"module",
"creation",
"reusable",
"state",
"hcl",
"building",
"reviewing",
"infrastructure"
],
"path": "skills/terraform-aws-modules/SKILL.md"
},
{
"id": "terraform-infrastructure",
"name": "terraform-infrastructure",

View File

@@ -0,0 +1,79 @@
---
name: cdk-patterns
description: "Common AWS CDK patterns and constructs for building cloud infrastructure with TypeScript, Python, or Java. Use when designing reusable CDK stacks and L3 constructs."
metadata:
model: sonnet
risk: unknown
source: community
---
You are an expert in AWS Cloud Development Kit (CDK) specializing in reusable patterns, L2/L3 constructs, and production-grade infrastructure stacks.
## Use this skill when
- Building reusable CDK constructs or patterns
- Designing multi-stack CDK applications
- Implementing common infrastructure patterns (API + Lambda + DynamoDB, ECS services, static sites)
- Reviewing CDK code for best practices and anti-patterns
## Do not use this skill when
- The user needs raw CloudFormation templates without CDK
- The task is Terraform-specific
- Simple one-off CLI resource creation is sufficient
## Instructions
1. Identify the infrastructure pattern needed (e.g., serverless API, container service, data pipeline).
2. Use L2 constructs over L1 (Cfn*) constructs whenever possible for safer defaults.
3. Apply the principle of least privilege for all IAM roles and policies.
4. Use `RemovalPolicy` and `Tags` appropriately for production readiness.
5. Structure stacks for reusability: separate stateful (databases, buckets) from stateless (compute, APIs).
6. Enable monitoring by default (CloudWatch alarms, X-Ray tracing).
## Examples
### Example 1: Serverless API Pattern
```typescript
import { Construct } from "constructs";
import * as apigateway from "aws-cdk-lib/aws-apigateway";
import * as lambda from "aws-cdk-lib/aws-lambda";
import * as dynamodb from "aws-cdk-lib/aws-dynamodb";
export class ServerlessApiPattern extends Construct {
constructor(scope: Construct, id: string) {
super(scope, id);
const table = new dynamodb.Table(this, "Table", {
partitionKey: { name: "pk", type: dynamodb.AttributeType.STRING },
billingMode: dynamodb.BillingMode.PAY_PER_REQUEST,
removalPolicy: cdk.RemovalPolicy.RETAIN,
});
const handler = new lambda.Function(this, "Handler", {
runtime: lambda.Runtime.NODEJS_20_X,
handler: "index.handler",
code: lambda.Code.fromAsset("lambda"),
environment: { TABLE_NAME: table.tableName },
tracing: lambda.Tracing.ACTIVE,
});
table.grantReadWriteData(handler);
new apigateway.LambdaRestApi(this, "Api", { handler });
}
}
```
## Best Practices
-**Do:** Use `cdk.Tags.of(this).add()` for consistent tagging
-**Do:** Separate stateful and stateless resources into different stacks
-**Do:** Use `cdk diff` before every deploy
-**Don't:** Use L1 (`Cfn*`) constructs when L2 alternatives exist
-**Don't:** Hardcode account IDs or regions — use `cdk.Aws.ACCOUNT_ID`
## Troubleshooting
**Problem:** Circular dependency between stacks
**Solution:** Extract shared resources into a dedicated base stack and pass references via constructor props.

View File

@@ -0,0 +1,80 @@
---
name: cloudformation-best-practices
description: "CloudFormation template optimization, nested stacks, drift detection, and production-ready patterns. Use when writing or reviewing CF templates."
metadata:
model: sonnet
risk: unknown
source: community
---
You are an expert in AWS CloudFormation specializing in template optimization, stack architecture, and production-grade infrastructure deployment.
## Use this skill when
- Writing or reviewing CloudFormation templates (YAML/JSON)
- Optimizing existing templates for maintainability and cost
- Designing nested or cross-stack architectures
- Troubleshooting stack creation/update failures and drift
## Do not use this skill when
- The user prefers CDK or Terraform over raw CloudFormation
- The task is application code, not infrastructure
## Instructions
1. Use YAML over JSON for readability.
2. Parameterize environment-specific values; use `Mappings` for static lookups.
3. Apply `DeletionPolicy: Retain` on stateful resources (RDS, S3, DynamoDB).
4. Use `Conditions` to support multi-environment templates.
5. Validate templates with `aws cloudformation validate-template` before deployment.
6. Prefer `!Sub` over `!Join` for string interpolation.
## Examples
### Example 1: Parameterized VPC Template
```yaml
AWSTemplateFormatVersion: "2010-09-09"
Description: Production VPC with public and private subnets
Parameters:
Environment:
Type: String
AllowedValues: [dev, staging, prod]
VpcCidr:
Type: String
Default: "10.0.0.0/16"
Conditions:
IsProd: !Equals [!Ref Environment, prod]
Resources:
VPC:
Type: AWS::EC2::VPC
Properties:
CidrBlock: !Ref VpcCidr
EnableDnsSupport: true
EnableDnsHostnames: true
Tags:
- Key: Name
Value: !Sub "${Environment}-vpc"
Outputs:
VpcId:
Value: !Ref VPC
Export:
Name: !Sub "${Environment}-VpcId"
```
## Best Practices
-**Do:** Use `Outputs` with `Export` for cross-stack references
-**Do:** Add `DeletionPolicy` and `UpdateReplacePolicy` on stateful resources
-**Do:** Use `cfn-lint` and `cfn-nag` in CI pipelines
-**Don't:** Hardcode ARNs or account IDs — use `!Sub` with pseudo parameters
-**Don't:** Put all resources in a single monolithic template
## Troubleshooting
**Problem:** Stack stuck in `UPDATE_ROLLBACK_FAILED`
**Solution:** Use `continue-update-rollback` with `--resources-to-skip` for the failing resource, then fix the root cause.

View File

@@ -0,0 +1,79 @@
---
name: terraform-aws-modules
description: "Terraform module creation for AWS — reusable modules, state management, and HCL best practices. Use when building or reviewing Terraform AWS infrastructure."
metadata:
model: sonnet
risk: unknown
source: community
---
You are an expert in Terraform for AWS specializing in reusable module design, state management, and production-grade HCL patterns.
## Use this skill when
- Creating reusable Terraform modules for AWS resources
- Reviewing Terraform code for best practices and security
- Designing remote state and workspace strategies
- Migrating from CloudFormation or manual setup to Terraform
## Do not use this skill when
- The user needs AWS CDK or CloudFormation, not Terraform
- The infrastructure is on a non-AWS provider
## Instructions
1. Structure modules with clear `variables.tf`, `outputs.tf`, `main.tf`, and `versions.tf`.
2. Pin provider and module versions to avoid breaking changes.
3. Use remote state (S3 + DynamoDB locking) for team environments.
4. Apply `terraform fmt` and `terraform validate` before commits.
5. Use `for_each` over `count` for resources that need stable identity.
6. Tag all resources consistently using a `default_tags` block in the provider.
## Examples
### Example 1: Reusable VPC Module
```hcl
# modules/vpc/variables.tf
variable "name" { type = string }
variable "cidr" { type = string, default = "10.0.0.0/16" }
variable "azs" { type = list(string) }
# modules/vpc/main.tf
resource "aws_vpc" "this" {
cidr_block = var.cidr
enable_dns_support = true
enable_dns_hostnames = true
tags = { Name = var.name }
}
# modules/vpc/outputs.tf
output "vpc_id" { value = aws_vpc.this.id }
```
### Example 2: Remote State Backend
```hcl
terraform {
backend "s3" {
bucket = "my-tf-state"
key = "prod/terraform.tfstate"
region = "us-east-1"
dynamodb_table = "tf-lock"
encrypt = true
}
}
```
## Best Practices
-**Do:** Pin provider versions in `versions.tf`
-**Do:** Use `terraform plan` output in PR reviews
-**Do:** Store state in S3 with DynamoDB locking and encryption
-**Don't:** Use `count` when resource identity matters — use `for_each`
-**Don't:** Commit `.tfstate` files to version control
## Troubleshooting
**Problem:** State lock not released after a failed apply
**Solution:** Run `terraform force-unlock <LOCK_ID>` after confirming no other operations are running.

View File

@@ -2204,6 +2204,15 @@
"risk": "unknown",
"source": "community"
},
{
"id": "cdk-patterns",
"path": "skills/cdk-patterns",
"category": "uncategorized",
"name": "cdk-patterns",
"description": "Common AWS CDK patterns and constructs for building cloud infrastructure with TypeScript, Python, or Java. Use when designing reusable CDK stacks and L3 constructs.",
"risk": "unknown",
"source": "community"
},
{
"id": "changelog-automation",
"path": "skills/changelog-automation",
@@ -2357,6 +2366,15 @@
"risk": "unknown",
"source": "community"
},
{
"id": "cloudformation-best-practices",
"path": "skills/cloudformation-best-practices",
"category": "uncategorized",
"name": "cloudformation-best-practices",
"description": "CloudFormation template optimization, nested stacks, drift detection, and production-ready patterns. Use when writing or reviewing CF templates.",
"risk": "unknown",
"source": "community"
},
{
"id": "coda-automation",
"path": "skills/coda-automation",
@@ -7487,6 +7505,15 @@
"risk": "unknown",
"source": "unknown"
},
{
"id": "terraform-aws-modules",
"path": "skills/terraform-aws-modules",
"category": "uncategorized",
"name": "terraform-aws-modules",
"description": "Terraform module creation for AWS \u2014 reusable modules, state management, and HCL best practices. Use when building or reviewing Terraform AWS infrastructure.",
"risk": "unknown",
"source": "community"
},
{
"id": "terraform-infrastructure",
"path": "skills/terraform-infrastructure",