aws-samples

@aws-samples source repo

848 skills
0 followers
last month last updated

▌
Modernization Strategy · aws-samples
Decide the 6R modernization pattern — Rehost / Replatform / Refactor / Repurchase / Retire / Retain — using a decision tree and cost/time/risk matrix. Produces a defensible strategy-decision.md that justifies the selected pattern with quantitative evidence. Use after workload-assessment and before to-be-architecture.

6 installs
▌
Requirements Analysis · aws-samples
Adaptive-depth requirements analysis for AIDLC Inception. Simple features produce a 1-paragraph brief; complex features produce structured REQ-001/REQ-002 functional and non-functional requirements with acceptance criteria and traceability to user stories.

5 installs
▌
Aidlc Incident Response · aws-samples
Run the AI-DLC `incident-response` stage (operation phase) in isolation, without advancing the main workflow. Packages `/aidlc --stage incident-response --single`: the engine emits one run-stage directive for incident-response and its gate, the conductor runs it, then the single-stage run commits a synthetic-id pair and stops. The main workflow's Current Stage is never touched.

5 installs
▌
Aidlc Application Design · aws-samples
Run the AI-DLC `application-design` stage (inception phase) in isolation, without advancing the main workflow. Packages `/aidlc --stage application-design --single`: the engine emits one run-stage directive for application-design and its gate, the conductor runs it, then the single-stage run commits a synthetic-id pair and stops. The main workflow's Current Stage is never touched.

6 installs
▌
Aidlc Deployment Pipeline · aws-samples
Run the AI-DLC `deployment-pipeline` stage (operation phase) in isolation, without advancing the main workflow. Packages `/aidlc --stage deployment-pipeline --single`: the engine emits one run-stage directive for deployment-pipeline and its gate, the conductor runs it, then the single-stage run commits a synthetic-id pair and stops. The main workflow's Current Stage is never touched.

6 installs
▌
Aidlc Observability Setup · aws-samples
Run the AI-DLC `observability-setup` stage (operation phase) in isolation, without advancing the main workflow. Packages `/aidlc --stage observability-setup --single`: the engine emits one run-stage directive for observability-setup and its gate, the conductor runs it, then the single-stage run commits a synthetic-id pair and stops. The main workflow's Current Stage is never touched.

7 installs
▌
Aidlc Practices Discovery · aws-samples
Run the AI-DLC `practices-discovery` stage (inception phase) in isolation, without advancing the main workflow. Packages `/aidlc --stage practices-discovery --single`: the engine emits one run-stage directive for practices-discovery and its gate, the conductor runs it, then the single-stage run commits a synthetic-id pair and stops. The main workflow's Current Stage is never touched.

4 installs
▌
Aidlc Reverse Engineering · aws-samples
Run the AI-DLC `reverse-engineering` stage (inception phase) in isolation, without advancing the main workflow. Packages `/aidlc --stage reverse-engineering --single`: the engine emits one run-stage directive for reverse-engineering and its gate, the conductor runs it, then the single-stage run commits a synthetic-id pair and stops. The main workflow's Current Stage is never touched.

5 installs
▌
Aidlc Deployment Execution · aws-samples
Run the AI-DLC `deployment-execution` stage (operation phase) in isolation, without advancing the main workflow. Packages `/aidlc --stage deployment-execution --single`: the engine emits one run-stage directive for deployment-execution and its gate, the conductor runs it, then the single-stage run commits a synthetic-id pair and stops. The main workflow's Current Stage is never touched.

4 installs
▌
Aidlc Feedback Optimization · aws-samples
Run the AI-DLC `feedback-optimization` stage (operation phase) in isolation, without advancing the main workflow. Packages `/aidlc --stage feedback-optimization --single`: the engine emits one run-stage directive for feedback-optimization and its gate, the conductor runs it, then the single-stage run commits a synthetic-id pair and stops. The main workflow's Current Stage is never touched.

6 installs
▌
Aidlc Infrastructure Design · aws-samples
Run the AI-DLC `infrastructure-design` stage (construction phase) in isolation, without advancing the main workflow. Packages `/aidlc --stage infrastructure-design --single`: the engine emits one run-stage directive for infrastructure-design and its gate, the conductor runs it, then the single-stage run commits a synthetic-id pair and stops. The main workflow's Current Stage is never touched.

7 installs
▌
Aidlc Requirements Analysis · aws-samples
Run the AI-DLC `requirements-analysis` stage (inception phase) in isolation, without advancing the main workflow. Packages `/aidlc --stage requirements-analysis --single`: the engine emits one run-stage directive for requirements-analysis and its gate, the conductor runs it, then the single-stage run commits a synthetic-id pair and stops. The main workflow's Current Stage is never touched.

6 installs
▌
Aidlc Performance Validation · aws-samples
Run the AI-DLC `performance-validation` stage (operation phase) in isolation, without advancing the main workflow. Packages `/aidlc --stage performance-validation --single`: the engine emits one run-stage directive for performance-validation and its gate, the conductor runs it, then the single-stage run commits a synthetic-id pair and stops. The main workflow's Current Stage is never touched.

5 installs
▌
Aidlc Environment Provisioning · aws-samples
Run the AI-DLC `environment-provisioning` stage (operation phase) in isolation, without advancing the main workflow. Packages `/aidlc --stage environment-provisioning --single`: the engine emits one run-stage directive for environment-provisioning and its gate, the conductor runs it, then the single-stage run commits a synthetic-id pair and stops. The main workflow's Current Stage is never touched.

5 installs
▌
Aidlc · aws-samples bundle
AI-DLC workflow orchestrator. Start, resume, or manage an AI-driven development lifecycle. Scopes are defined one file per scope under `.kiro/scopes/`; run `bun .kiro/tools/aidlc-utility.ts help` for the authoritative list and descriptions. Utilities: --status, --init, --doctor, --stage, --phase, --scope, --depth, --test-strategy, --test-run, --version, --help. Or describe what you want to build and the scope will be auto-detected.

7 installs
▌
Aidlc Mvp · aws-samples
Run the AI-DLC workflow with the mvp scope baked in — no scope detection. Skip operations, ship the core. Packaging over `/aidlc --scope mvp`, which works without this skill.

5 installs
▌
Aidlc Init · aws-samples
Scaffold an AI-DLC workspace — run the whole Initialization phase (scaffold the aidlc-docs/ tree, detect the workspace, initialise state) in one step, without starting a stage workflow. Packaging over `/aidlc --init`, which works without this skill. Pass `--force` to reinitialise an existing workspace; `--scope <name>` to seed the initial scope (defaults to poc).

6 installs
▌
Aidlc Bugfix · aws-samples
Run the AI-DLC workflow with the bugfix scope baked in — no scope detection. Fix a specific bug. Packaging over `/aidlc --scope bugfix`, which works without this skill.

6 installs
▌
Aidlc Replay · aws-samples
Print a structured session narrative for stakeholders who weren't in the room. Numbers (stage counts, phase rollup, duration) come from `aidlc-runtime.ts summary`; prose comes from the audit trail and artefacts. Renders to the terminal only — writes no file, never mutates workflow state, never emits audit events.

3 installs
▌
Aidlc Feature · aws-samples
Run the AI-DLC workflow with the feature scope baked in — no scope detection. Default for new features, practical depth. Packaging over `/aidlc --scope feature`, which works without this skill.

4 installs
▌
Aidlc Nfr Design · aws-samples
Run the AI-DLC `nfr-design` stage (construction phase) in isolation, without advancing the main workflow. Packages `/aidlc --stage nfr-design --single`: the engine emits one run-stage directive for nfr-design and its gate, the conductor runs it, then the single-stage run commits a synthetic-id pair and stops. The main workflow's Current Stage is never touched.

5 installs
▌
Aidlc CI Pipeline · aws-samples
Run the AI-DLC `ci-pipeline` stage (construction phase) in isolation, without advancing the main workflow. Packages `/aidlc --stage ci-pipeline --single`: the engine emits one run-stage directive for ci-pipeline and its gate, the conductor runs it, then the single-stage run commits a synthetic-id pair and stops. The main workflow's Current Stage is never touched.

7 installs
▌
Aidlc Feasibility · aws-samples
Run the AI-DLC `feasibility` stage (ideation phase) in isolation, without advancing the main workflow. Packages `/aidlc --stage feasibility --single`: the engine emits one run-stage directive for feasibility and its gate, the conductor runs it, then the single-stage run commits a synthetic-id pair and stops. The main workflow's Current Stage is never touched.

5 installs
▌
Aidlc Session Cost · aws-samples
Read-only session cost view. Prints deterministic aggregates for the current workflow — duration, stage outcomes, memory entries, sensor firings, learnings captured — sourced entirely from `aidlc-runtime.ts summary`. Never mutates workflow state, never emits audit events, never writes files.

6 installs
▌
Aidlc User Stories · aws-samples
Run the AI-DLC `user-stories` stage (inception phase) in isolation, without advancing the main workflow. Packages `/aidlc --stage user-stories --single`: the engine emits one run-stage directive for user-stories and its gate, the conductor runs it, then the single-stage run commits a synthetic-id pair and stops. The main workflow's Current Stage is never touched.

7 installs
▌
Aidlc Outcomes Pack · aws-samples
Generate a comprehensive handover document at workflow close so the team can own, operate, and continue the system without re-running the workflow. Stage/phase/learning counts come from `aidlc-runtime.ts summary`; prose comes from the artefacts. Writes OUTCOMES.md but never mutates workflow state or emits audit events.

7 installs
▌
Aidlc Rough Mockups · aws-samples
Run the AI-DLC `rough-mockups` stage (ideation phase) in isolation, without advancing the main workflow. Packages `/aidlc --stage rough-mockups --single`: the engine emits one run-stage directive for rough-mockups and its gate, the conductor runs it, then the single-stage run commits a synthetic-id pair and stops. The main workflow's Current Stage is never touched.

6 installs
▌
Aidlc Build And Test · aws-samples
Run the AI-DLC `build-and-test` stage (construction phase) in isolation, without advancing the main workflow. Packages `/aidlc --stage build-and-test --single`: the engine emits one run-stage directive for build-and-test and its gate, the conductor runs it, then the single-stage run commits a synthetic-id pair and stops. The main workflow's Current Stage is never touched.

4 installs
▌
Aidlc Intent Capture · aws-samples
Run the AI-DLC `intent-capture` stage (ideation phase) in isolation, without advancing the main workflow. Packages `/aidlc --stage intent-capture --single`: the engine emits one run-stage directive for intent-capture and its gate, the conductor runs it, then the single-stage run commits a synthetic-id pair and stops. The main workflow's Current Stage is never touched.

6 installs
▌
Aidlc Security Patch · aws-samples
Run the AI-DLC workflow with the security-patch scope baked in — no scope detection. CVE response. Packaging over `/aidlc --scope security-patch`, which works without this skill.

6 installs
▌
Aidlc Team Formation · aws-samples
Run the AI-DLC `team-formation` stage (ideation phase) in isolation, without advancing the main workflow. Packages `/aidlc --stage team-formation --single`: the engine emits one run-stage directive for team-formation and its gate, the conductor runs it, then the single-stage run commits a synthetic-id pair and stops. The main workflow's Current Stage is never touched.

5 installs
▌
Aidlc Code Generation · aws-samples
Run the AI-DLC `code-generation` stage (construction phase) in isolation, without advancing the main workflow. Packages `/aidlc --stage code-generation --single`: the engine emits one run-stage directive for code-generation and its gate, the conductor runs it, then the single-stage run commits a synthetic-id pair and stops. The main workflow's Current Stage is never touched.

6 installs
▌
Aidlc Market Research · aws-samples
Run the AI-DLC `market-research` stage (ideation phase) in isolation, without advancing the main workflow. Packages `/aidlc --stage market-research --single`: the engine emits one run-stage directive for market-research and its gate, the conductor runs it, then the single-stage run commits a synthetic-id pair and stops. The main workflow's Current Stage is never touched.

2 installs
▌
Aidlc Refined Mockups · aws-samples
Run the AI-DLC `refined-mockups` stage (inception phase) in isolation, without advancing the main workflow. Packages `/aidlc --stage refined-mockups --single`: the engine emits one run-stage directive for refined-mockups and its gate, the conductor runs it, then the single-stage run commits a synthetic-id pair and stops. The main workflow's Current Stage is never touched.

5 installs
▌
Aidlc Approval Handoff · aws-samples
Run the AI-DLC `approval-handoff` stage (ideation phase) in isolation, without advancing the main workflow. Packages `/aidlc --stage approval-handoff --single`: the engine emits one run-stage directive for approval-handoff and its gate, the conductor runs it, then the single-stage run commits a synthetic-id pair and stops. The main workflow's Current Stage is never touched.

6 installs
▌
Aidlc Nfr Requirements · aws-samples
Run the AI-DLC `nfr-requirements` stage (construction phase) in isolation, without advancing the main workflow. Packages `/aidlc --stage nfr-requirements --single`: the engine emits one run-stage directive for nfr-requirements and its gate, the conductor runs it, then the single-stage run commits a synthetic-id pair and stops. The main workflow's Current Stage is never touched.

6 installs
▌
Aidlc Scope Definition · aws-samples
Run the AI-DLC `scope-definition` stage (ideation phase) in isolation, without advancing the main workflow. Packages `/aidlc --stage scope-definition --single`: the engine emits one run-stage directive for scope-definition and its gate, the conductor runs it, then the single-stage run commits a synthetic-id pair and stops. The main workflow's Current Stage is never touched.

6 installs
▌
Aidlc Units Generation · aws-samples
Run the AI-DLC `units-generation` stage (inception phase) in isolation, without advancing the main workflow. Packages `/aidlc --stage units-generation --single`: the engine emits one run-stage directive for units-generation and its gate, the conductor runs it, then the single-stage run commits a synthetic-id pair and stops. The main workflow's Current Stage is never touched.

7 installs
▌
Aidlc Delivery Planning · aws-samples
Run the AI-DLC `delivery-planning` stage (inception phase) in isolation, without advancing the main workflow. Packages `/aidlc --stage delivery-planning --single`: the engine emits one run-stage directive for delivery-planning and its gate, the conductor runs it, then the single-stage run commits a synthetic-id pair and stops. The main workflow's Current Stage is never touched.

4 installs
▌
Aidlc Functional Design · aws-samples
Run the AI-DLC `functional-design` stage (construction phase) in isolation, without advancing the main workflow. Packages `/aidlc --stage functional-design --single`: the engine emits one run-stage directive for functional-design and its gate, the conductor runs it, then the single-stage run commits a synthetic-id pair and stops. The main workflow's Current Stage is never touched.

5 installs
▌
AI Adr · aws-samples
Keep a project's architecture decision log — stand it up on first run, then write records and move them through propose, accept, and decline. Invoke ONLY via the /ai-adr slash command. Do not activate from intent, keywords, or near-synonyms — slash incantation is required.

5 installs
▌
AI Init · aws-samples
Initialize or refine unified project context (.context/README.md). Invoke ONLY via the /ai-init slash command. Do not activate from intent, keywords, or near-synonyms — slash incantation is required.

6 installs
▌
AI Plan · aws-samples
Create a comprehensive implementation plan for a feature, with phases, code samples, and testing strategy. Invoke ONLY via the /ai-plan slash command. Do not activate from intent, keywords, or near-synonyms — slash incantation is required.

7 installs
▌
AI Draft · aws-samples
Write a full document draft, incorporating research and outline if available. Invoke ONLY via the /ai-draft slash command. Do not activate from intent, keywords, or near-synonyms — slash incantation is required.

5 installs
▌
Ipa Help · aws-samples
Report IPA project state and suggest the next lifecycle skill to run.

4 installs
▌
Ipa Init · aws-samples
Initialize IPA project configuration

5 installs
▌
AI Create · aws-samples
Create a new working folder with a README.md identity document for a feature or a document. Invoke ONLY via the /ai-create slash command. Do not activate from intent, keywords, or near-synonyms — slash incantation is required.

5 installs
▌
AI Archive · aws-samples
Retire one finished work folder by moving it into the working root's .archive/ directory and transferring its manifest row. Invoke ONLY via the /ai-archive slash command. Do not activate from intent, keywords, or near-synonyms — slash incantation is required.

4 installs
▌
AI Context · aws-samples
Write agent context documentation (CLAUDE.md + README.md) for a source code directory. Invoke ONLY via the /ai-context slash command. Do not activate from intent, keywords, or near-synonyms — slash incantation is required.

4 installs
▌
AI Outline · aws-samples
Create a structured document outline with heading hierarchy, section guidance, and constitution-validated coverage. Invoke ONLY via the /ai-outline slash command. Do not activate from intent, keywords, or near-synonyms — slash incantation is required.

7 installs
▌
Ipa Deploy · aws-samples bundle
Deploy composed infrastructure patterns by executing generated Makefiles. Use when the user says 'deploy', 'stand up', 'create stacks', or invokes /ipa-deploy. For teardown, use /ipa-destroy.

3 installs
▌
AI As Built · aws-samples
Document how a feature, subsystem, or module was actually built. Invoke ONLY via the /ai-as-built slash command. Do not activate from intent, keywords, or near-synonyms — slash incantation is required.

6 installs
▌
AI Diataxis · aws-samples bundle
Create, assess, or survey documentation against the Diátaxis compass. Invoke ONLY via the /ai-diataxis slash command. Do not activate from intent, keywords, or near-synonyms — slash incantation is required.

6 installs
▌
AI Research · aws-samples
Research a codebase or a topic, producing structured findings; emits SDD phase suggestions only when asked. Invoke ONLY via the /ai-research slash command. Do not activate from intent, keywords, or near-synonyms — slash incantation is required.

1 install
▌
Ipa Compose · aws-samples bundle
Compose a deployment from stack skills and generate executable artifacts (Makefiles, security disposition). Use when the user says 'compose', 'generate deployment', or invokes /ipa-compose.

5 installs
▌
Ipa Destroy · aws-samples
Destroy composed infrastructure patterns by executing teardown targets in generated Makefiles. Use when the user says 'destroy', 'tear down', 'delete stacks', 'remove infrastructure', 'clean up stacks', or invokes /ipa-destroy.

4 installs
▌
Ipa Prepare · aws-samples
Deploy one-time prerequisite infrastructure from scripts/prepare.mk. Use when the user says 'prepare', 'deploy prerequisites', 'create ECR', or invokes /ipa-prepare.

5 installs
▌
AI Architect · aws-samples bundle
Design software architecture for a feature before planning implementation. Invoke ONLY via the /ai-architect slash command. Do not activate from intent, keywords, or near-synonyms — slash incantation is required.

5 installs
▌
AI Implement · aws-samples
Execute an implementation plan for a feature by building all code specified in it. Invoke ONLY via the /ai-implement slash command. Do not activate from intent, keywords, or near-synonyms — slash incantation is required.

4 installs
▌
Ipa K8S Help · aws-samples
Guide and troubleshoot the local Kubernetes (k3d + Helm + Tilt) inner-dev loop, and guide a manual EKS deploy of the app-lib chart. Use when the user says 'set up local k8s', 'tilt won't start', 'pod can't reach DynamoDB', 'my local cluster is broken', 'deploy this chart to EKS', or invokes /ipa-k8s-help. NOT for IPA lifecycle state — that is /ipa-help.

6 installs
▌
Ipa Security · aws-samples
Provision or update centralized security infrastructure (IAM roles) for an IPA project. Use when the user says 'security', 'set up security', 'IAM roles', or invokes /ipa-security.

5 installs
▌
Ipa Stack Ecr · aws-samples bundle
Deploy an ECR repository for container image storage.

6 installs
▌
Ipa Stack Logs · aws-samples bundle
Deploy a centralized S3 log bucket for CloudFront, S3 access, and VPC flow logs.

7 installs
▌
AI Util Jupyter · aws-samples
Create simple, focused Jupyter notebooks that demonstrate a single concept or technique. Invoke ONLY via the /ai-util-jupyter slash command. Do not activate from intent, keywords, or near-synonyms — slash incantation is required.

5 installs
▌
Ipa Stack Queue · aws-samples
Deploy a queue tier stack: SQS + DLQ + worker Lambda + ESM + DynamoDB (feature-flagged).

8 installs
▌
Ipa Author Guide · aws-samples
Write a complete IPA documentation guide conforming to the Guide Format Standard. Use when the user says 'write a guide', 'author a guide', 'new guide', 'create a guide', 'draft a guide', 'add a guide', or invokes /ipa-author-guide. Also trigger when the user references writing documentation for the guides/ section or asks to document a workflow as a how-to. Do NOT use for stack reference docs (those go in stacks/), skill docs (developer-docs/skills/), or general page authoring.

9 installs
▌
Ipa Author Stack · aws-samples bundle
Create or update an IPA stack skill — from single-service prepare stacks to multi-service tier stacks. Use when the user says 'create a stack', 'new stack', 'add [service] to IPA', 'create a tier', 'create a feature stack', 'write a stack skill', 'update the [service] stack', or wants to add infrastructure to the IPA system. Do NOT use for composing/deploying existing stacks (that is ipa-compose/ipa-deploy).

7 installs
▌
Ipa Codepipeline · aws-samples
[DEPRECATED] Use /ipa-compose codepipeline + /ipa-prepare instead.

5 installs
▌
Ipa Stack Backend · aws-samples
Deploy a backend tier stack: Lambda + API Gateway v2 + DynamoDB (feature-flagged).

8 installs
▌
Ipa Stack Cognito · aws-samples bundle
Deploy a Cognito User Pool stack with OAuth 2.0 Hosted UI and OIDC endpoints.

5 installs
▌
Ipa Stack Tfstate · aws-samples bundle
Deploy a Terraform state backend (S3 + DynamoDB) via CloudFormation.

6 installs
▌
AI Util Export PDF · aws-samples bundle
Export a markdown file to a branded PDF. Invoke ONLY via the /ai-util-export-pdf slash command. Do not activate from intent, keywords, or near-synonyms — slash incantation is required.

6 installs
▌
AI Util Kiro Skill · aws-samples
Migrate Claude Code skills (.claude/skills/*/SKILL.md) to Kiro skills (.kiro/skills/*/SKILL.md). Invoke ONLY via the /ai-util-kiro-skill slash command. Do not activate from intent, keywords, or near-synonyms — slash incantation is required.

6 installs
▌
Ipa Stack Frontend · aws-samples
Deploy a frontend tier stack: S3 static hosting + CloudFront distribution + OAC.

6 installs
▌
AI Util Export DOCX · aws-samples
Export a markdown file to Microsoft Word (.docx) format. Invoke ONLY via the /ai-util-export-docx slash command. Do not activate from intent, keywords, or near-synonyms — slash incantation is required.

5 installs
▌
AI Diataxis Scaffold · aws-samples bundle
Stand up the four Diátaxis mode directories, each seeded with an index page, in a project that has no documentation tree. Invoke ONLY via the /ai-diataxis-scaffold slash command. Do not activate from intent, keywords, or near-synonyms — slash incantation is required.

5 installs
▌
AI Util Claude Skill · aws-samples
Write new Claude Code skills from scratch given a description of what the skill should do. Invoke ONLY via the /ai-util-claude-skill slash command. Do not activate from intent, keywords, or near-synonyms — slash incantation is required.

6 installs
▌
AI Util Git Worktree · aws-samples bundle
Manage git worktrees for parallel feature work. Invoke ONLY via the /ai-util-git-worktree slash command. Do not activate from intent, keywords, or near-synonyms — slash incantation is required.

5 installs
▌
Ipa Stack Codecommit · aws-samples bundle
Deploy a CodeCommit repository for source code management.

5 installs
▌
Ipa Stack Codepipeline · aws-samples bundle
Deploy a CodePipeline CI/CD pipeline with CodeBuild for automated build/test/deploy.

4 installs
▌
Web Test Automation · aws-samples bundle
Use when designing, choosing tools for, or writing automated tests for web applications — E2E and UI tests, visual regression, web accessibility (axe-core), API testing inside browser flows, flaky-test debugging, page object model, and CI integration. Playwright-first, with Cypress and Selenium guidance and migration paths. Triggers on web testing, browser test, E2E, Playwright, Cypress, Selenium, page object, locator, flaky test, visual regression, accessibility testing, network mocking, CI sharding. For native iOS/Android/React Native/Flutter app tests, use the mobile-test-automation skill instead.

5 installs
▌
AWS Observability · aws-samples bundle
Builds, configures, debugs, and optimizes AWS observability with CloudWatch (Log Insights, Metrics, Alarms, Dashboards, EMF), X-Ray, CloudTrail, and ADOT (AWS Distro for OpenTelemetry), AND enables/onboards services to Application Signals using ADOT auto-instrumentation SDKs. Covers Log Insights queries, alarms (metric, composite, anomaly), dashboards, custom metrics/EMF, X-Ray tracing and sampling, ADOT collector config, CloudTrail auditing, and end-to-end Application Signals enablement via ADOT SDKs (CloudWatch Observability EKS add-on, CloudWatch Agent IAM, OTLP endpoints, ServiceEvents, Dynamic Instrumentation) on EC2, ECS, EKS, and Lambda in Python, Node.js, Java, and .NET. Applies to CloudWatch, alarms, dashboards, EMF, X-Ray, traces, CloudTrail, ADOT, monitoring, synthetics/canaries, OR enabling/onboarding/instrumenting a service for Application Signals using ADOT, ServiceEvents, auto-instrumentation, or making a service show up in Application Signals. Not for app logging or security threat detection.

6 installs
▌
Incident Triage · aws-samples bundle
Interpret production incident tickets and monitoring alerts, identify the affected application or business flow, retrieve and correlate evidence (logs, telemetry, source code context, configuration, deployment history, known issues), and produce an evidence-backed incident analysis: summary, probable root-cause hypotheses with confidence indicators, impacted components, recommended diagnostic/remediation steps, and routing or escalation guidance. Triggers on phrases like: production incident, incident ticket, triage this alert, root cause, RCA, correlate logs, what broke, error spike, latency spike, transaction failed, timeout, outage, sev1/P1, escalate, on-call, anomaly detection, alert threshold, known issue, postmortem. Use whenever a production issue, alert, or incident report is being analyzed — even if the user just pastes an error message, a stack trace, a screenshot description, or asks 'why are customers seeing this error?'

3 installs
▌
Terraform Skill · aws-samples bundle
Use when writing, reviewing, or debugging Terraform/OpenTofu modules, tests, CI, scans, or state ops - diagnoses failure mode (identity churn, secrets, blast radius, CI drift, state corruption) with version-aware guards.

5 installs
▌
Ecs Security · aws-samples bundle
Security and compliance guidance for Amazon ECS — "ECS was unable to assume the role", task role vs execution role, iam:PassRole, confused-deputy aws:SourceArn trust, Fargate vs EC2 shared responsibility, injecting Secrets Manager/SSM secrets (trailing-colon JSON-key gotcha), readonlyRootFilesystem / non-root / drop capabilities, ECS Exec governance, security-group-per-task, VPC endpoint policies, GuardDuty ECS Runtime Monitoring, ECR Inspector scanning, image signing, Fargate FIPS, or PCI/HIPAA/FedRAMP. Walks a discovery-driven 7-layer stack plus the AWS-canonical baseline and a 30/60/90 roadmap. Trigger even if "compliance" is never said — any ECS hardening, task-trust fix, or secrets-injection qualifies. Skip for EKS/Kubernetes (eks-security), GenAI/GPU security (ecs-genai), App Runner/Lambda, auditing a live estate's operational posture (ecs-operation-review — "audit my ECS security posture" matches both), or account-level security with no ECS angle.

6 installs
▌
AWS Cloudformation · aws-samples bundle
Author, validate, and troubleshoot AWS CloudFormation templates. Covers template authoring with secure defaults, pre-deployment validation (cfn-lint, cfn-guard, change sets), and root-cause diagnosis of failed stacks using CloudFormation events and CloudTrail correlation.

5 installs
▌
Java Upgrade · aws-samples bundle
Use when upgrading a Java service to the latest Java LTS (target newest — e.g. Java 25; fall back to 21/17 only if a dependency blocks it), performing the associated framework upgrade (Spring Boot 2→3, javax→jakarta), and containerising the result for ECS/EKS. Covers upgrade tooling (OpenRewrite, jdeps, jdeprscan, Maven/Gradle toolchain), the common Java 8→17/21/25 breakages, the containerisation arc, and — when a managed transformation service (e.g. AWS Transform) is NOT permitted — the prescriptive, group-by-group, build-verified language-native upgrade path (see references/prescriptive-language-native-upgrade.md). Triggers on Java upgrade, JDK upgrade, LTS upgrade, Spring Boot upgrade, jakarta migration, OpenRewrite, jdeps, jdeprscan, containerise Java, Dockerfile for Java, Corretto.

6 installs
▌
Mobile Test Automation · aws-samples bundle
Use when designing, choosing tools for, or writing automated tests for mobile apps — native iOS, native Android, React Native, and Flutter. Covers Appium, Maestro, Detox, Espresso, XCUITest, emulator/simulator vs real device strategy, device farms (AWS Device Farm, BrowserStack, Sauce Labs), gestures, deep links, permissions, app lifecycle, mobile flakiness, and CI. Triggers on mobile testing, app test, iOS test, Android test, Appium, Maestro, Detox, Espresso, XCUITest, emulator, real device, device farm, deep link, app permissions. For web browser tests, use the web-test-automation skill instead.

4 installs
▌
Gitlab Mr · aws-samples bundle
Locate GitLab vulnerability reports and deliver remediations back to GitLab — branch/commit strategy, raising merge requests via glab CLI, the GitLab REST API, or a GitLab MCP, MR descriptions that carry the triage rationale, and optional write-back of dispositions (dismiss/comment findings). Triggers on phrases like: raise MR, merge request, glab, GitLab API, create branch, commit the fix, where is the vulnerability report, CI artifacts, security dashboard, dismiss finding, write back to GitLab, MR description, one MR per group vs batched. Use whenever fetching a GitLab security report or delivering a fix/disposition to GitLab, even if the user just says 'open the MR' or 'where's the report'.

3 installs
▌
Dotnet Testing · aws-samples bundle
Use when authoring automated tests for .NET / C# code — unit tests, integration tests, mocking collaborators, and code coverage. Covers choosing a framework, structuring test projects, writing focused tests that map to requirements, and gating merges to keep trunk green. Triggers on .NET test, C# test, xUnit, NUnit, MSTest, coverlet, Moq, unit test .NET, dotnet test, test coverage C#, mocking C#. For web/browser E2E tests use web-test-automation; for mobile app tests use mobile-test-automation.

4 installs
▌
Nova Sonic Optimization · aws-samples
Optimize a Nova Sonic voice agent for low latency, cost, and reliability on AWS. Covers (1) measuring end-to-end and per-segment latency, (2) same-region deployment and network path tuning, (3) streaming inference and tool-call patterns that hide latency, (4) cost levers (provisioned vs on-demand, voice pricing), and (5) reliability across multiple regions. TRIGGER when: user wants to reduce voice latency; user mentions Groq-class responsiveness; user asks about same-region deployment, streaming, or cold start; user wants to control Nova Sonic cost. SKIP when: user is designing a new agent for the first time (use nova-sonic-best-practices); user is migrating from text (use text-agent-to-nova-sonic-voice).

5 installs
▌
Dotnet AWS Ecs · aws-samples bundle
Generates IaC (CloudFormation or CDK) and a deployment guide to deploy a .NET workload to Amazon ECS Fargate on Linux containers with an Application Load Balancer. Produces a VPC, ECS cluster, task definition, ALB, and auto-scaling. NOT for Windows containers, EC2 launch type, or Kubernetes/EKS deployments.

8 installs
▌
Nova Sonic Best Practices · aws-samples
Best practices for building a Nova Sonic speech-to-speech voice agent on AWS. Covers (1) when to choose Nova Sonic over a STT→LLM→TTS pipeline, (2) voice-first system prompt design, (3) tool calling for voice, (4) conversation UX patterns (barge-in, confirmation, disfluencies), and (5) common pitfalls. TRIGGER when: user is designing a new Nova Sonic voice agent; user asks how to write a voice prompt; user asks about speech-to-speech vs STT→LLM→TTS; user asks about tool calling, barge-in, or voice UX with Nova Sonic. SKIP when: user is migrating an existing text agent (use text-agent-to-nova-sonic-voice instead); user is debugging latency or cost (use nova-sonic-optimization instead).

5 installs
▌
Regression Testing · aws-samples bundle
Use when planning or writing a behaviour-first regression safety net BEFORE a major change — a Java/JDK version upgrade, a framework migration (e.g. Spring Boot 2→3, AngularJS→React), a runtime change, or a large refactor. Prioritises tests that validate observable external behaviour (API contracts, E2E flows, pure business logic) so the suite survives the change boundary, and provides a decision-gated, per-unit test-generation workflow. Triggers on regression test, pre-upgrade test, test strategy, safety net, behaviour parity, API contract test, test prioritisation, what to test before upgrade. For the mechanics of writing web/UI E2E tests, also use the web-test-automation skill.

4 installs
▌
AWS Event Driven Patterns · aws-samples bundle
Domain architecture guidance for event-driven financial-services systems on AWS — real-time market-data pipelines, stream processing, alert/subscription matching, multi-channel notification delivery, idempotency, and event-driven CDK stack design. Triggers on phrases like: event-driven architecture for FSI, market data stream processing, MSK topic and partition design, Flink vs Lambda vs ECS for streaming, subscription matching engine, push notification delivery, effectively-once processing, idempotency key, event-driven observability. For generic Lambda/EventBridge how-to unrelated to FSI event pipelines, use the aws-lambda skill instead; for MSK/Kafka service mechanics use the aws-messaging-and-streaming skill instead.

3 installs
▌
AWS Serverless Deployment · aws-samples bundle
AWS SAM and AWS CDK deployment for serverless applications. Triggers on phrases like: use SAM, SAM template, SAM init, SAM deploy, CDK serverless, CDK Lambda construct, NodejsFunction, PythonFunction, SAM and CDK together, serverless CI/CD pipeline. For general app deployment with service selection, use deploy-on-aws plugin instead.

8 installs
▌
Dotnet Adot Sidecar · aws-samples bundle
Adds OpenTelemetry instrumentation to a containerized .NET application and configures AWS Distro for OpenTelemetry (ADOT) as an ECS sidecar container. Updates existing IaC to include the ADOT collector in the task definition with proper IAM permissions. NOT for non-containerized apps or apps without existing ECS infrastructure.

7 installs
▌
Kotlin Coding Standards · aws-samples
Conventions for clean, idiomatic, safe Kotlin. Use when writing or reviewing Kotlin code.

6 installs
▌
Dotnet Post Transform · aws-samples bundle
Fixes build errors, wires dependency injection, and resolves static file serving issues in ASP.NET Framework apps transformed to ASP.NET Core by AWS Transform for .NET. Use after running AWS Transform to get a transformed project from compiling to running correctly. Works through five sequential phases automatically. ALSO USE for missing DI registrations, broken images/CSS/JS after migration, middleware pipeline ordering, Content folder vs wwwroot mismatch, and ConfigurationManager shim creation. NOT for greenfield ASP.NET Core apps, EF Core migration authoring, or production deployment hardening.

5 installs
▌
Terraform Best Practices · aws-samples
Guidance for writing clean, maintainable, secure Terraform (HCL). Use when authoring or reviewing Infrastructure as Code with Terraform.

4 installs

848 published skills · page 6 of 9