From aws-docusaurus
Deploy and manage static sites on AWS infrastructure (S3, CloudFront, ACM, Route53).
How this skill is triggered — by the user, by Claude, or both
Slash command
/aws-docusaurus:aws-docusaurusThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Deploy and manage static sites on AWS infrastructure (S3, CloudFront, ACM, Route53).
Deploy and manage static sites on AWS infrastructure (S3, CloudFront, ACM, Route53).
ALWAYS start by reading the configuration:
cat .claude/yaccp/aws-docusaurus/config.json 2>/dev/null || echo '{}'
This determines the current state and available options.
Les buckets S3 doivent suivre cette convention :
${SITE_NAME}-${AWS_ACCOUNT_ID}-${AWS_REGION}
Exemple : my-docs-123456789012-eu-west-3
AWS_ACCOUNT_ID=$(aws sts get-caller-identity --query Account --output text)
S3_BUCKET="${SITE_NAME}-${AWS_ACCOUNT_ID}-${AWS_REGION}"
Avant de créer un nouveau certificat, vérifier les certificats existants :
# Lister les certificats dans us-east-1 (requis pour CloudFront)
aws acm list-certificates --region us-east-1 --output table
# Chercher un wildcard pour le domaine parent
PARENT_DOMAIN=$(echo $DOMAIN | sed 's/^[^.]*\.//')
aws acm list-certificates --region us-east-1 \
--query "CertificateSummaryList[?DomainName=='*.${PARENT_DOMAIN}'].CertificateArn" \
--output text
Règles :
*.example.com couvre tous les sous-domainesBased on config.json content:
| State | Condition | Action |
|---|---|---|
NO_CONFIG | File missing or empty | → First time setup |
CONFIGURED | Valid config exists | → Show main menu |
Use AskUserQuestion:
SITE_NAME, DOMAIN, AWS_REGIONAWS_ACCOUNT_ID automatiquementS3_BUCKET avec la conventionAfter configuration, save to:
mkdir -p .claude/yaccp/aws-docusaurus
# Write config.json with collected parameters
Use AskUserQuestion:
Always offer:
Guides completion of development work by verifying tests, detecting environment, and presenting structured options for merge, PR, or cleanup.
Guides creation and editing of skills using test-driven development with pressure scenarios and subagents to verify agent compliance.
Dispatches multiple subagents concurrently for independent tasks without shared state. Use when facing 2+ unrelated failures or subsystems that can be investigated in parallel.
npx claudepluginhub joshuarweaver/cascade-code-devops-misc-1 --plugin yaccp-claude-plugin-aws-docusaurus