aws-docusaurus
# Aws Docusaurus
What this skill does
# Aws Docusaurus
Deploy and manage static sites on AWS infrastructure (S3, CloudFront, ACM, Route53).
## IMPORTANT: Environment Discovery
**ALWAYS start by reading the configuration:**
```bash
cat .claude/yaccp/aws-docusaurus/config.json 2>/dev/null || echo '{}'
```
This determines the current state and available options.
## Naming Conventions
### S3 Bucket Naming (OBLIGATOIRE)
Les buckets S3 **doivent** suivre cette convention :
```
${SITE_NAME}-${AWS_ACCOUNT_ID}-${AWS_REGION}
```
Exemple : `my-docs-123456789012-eu-west-3`
```bash
AWS_ACCOUNT_ID=$(aws sts get-caller-identity --query Account --output text)
S3_BUCKET="${SITE_NAME}-${AWS_ACCOUNT_ID}-${AWS_REGION}"
```
### ACM Certificate Reuse (RECOMMANDÉ)
**Avant de créer un nouveau certificat**, vérifier les certificats existants :
```bash
# 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-domaines
- Réutiliser évite les limites ACM (2500 certs/compte)
- Proposer à l'utilisateur le choix : réutiliser ou créer
## State Machine
Based on config.json content:
| State | Condition | Action |
|-------|-----------|--------|
| `NO_CONFIG` | File missing or empty | → First time setup |
| `CONFIGURED` | Valid config exists | → Show main menu |
## State: NO_CONFIG
Use AskUserQuestion:
- **"Commencer la configuration"** → Collect required parameters
- **"Voir la documentation"** → Show plugin help
### Configuration Steps
1. Collecter `SITE_NAME`, `DOMAIN`, `AWS_REGION`
2. Récupérer `AWS_ACCOUNT_ID` automatiquement
3. Construire `S3_BUCKET` avec la convention
4. **Vérifier les certificats ACM existants**
5. Proposer réutilisation ou création
After configuration, save to:
```bash
mkdir -p .claude/yaccp/aws-docusaurus
# Write config.json with collected parameters
```
## State: CONFIGURED
Use AskUserQuestion:
- **"▶️ Exécuter"** → Run main action
- **"⚙️ Configuration"** → Modify settings
- **"📊 Statut"** → Show current state
- **"❓ Aide"** → Documentation
## After Each Action
Always offer:
- **"Retour au menu"** → Back to main menu
- **"Quitter"** → End session
Related in Cloud & DevOps
appbuilder-action-scaffolder
IncludedCreate, implement, deploy, and debug Adobe Runtime actions with consistent layout, validation, and error handling. Use this skill whenever the user needs to add actions to an App Builder project, understand action structure (params, response format, web/raw actions), configure actions in the manifest, use App Builder SDKs (State, Files, Events, database), deploy and invoke actions via CLI, debug action issues, or implement patterns such as webhook receivers, custom event providers, journaling consumers, large payload redirects, action sequence pipelines, and Asset Compute workers. Also trigger when users mention serverless functions in Adobe context, action logging, IMS authentication for actions, or cron-style scheduled actions.
orchestrating-datacloud
IncludedSalesforce Data Cloud product orchestrator for connect→prepare→harmonize→segment→act workflows. Use this skill when the user needs a multi-step Data Cloud pipeline, cross-phase troubleshooting, or data space and data kit management. TRIGGER when: user needs a multi-step Data Cloud pipeline, asks to set up or troubleshoot Data Cloud across phases, manages data spaces or data kits, or wants a cross-phase sf data360 workflow. DO NOT TRIGGER when: work is isolated to a single phase (use the matching phase-specific skill), the task is STDM/session tracing/parquet telemetry (use observing-agentforce), standard CRM SOQL (use querying-soql), or Apex implementation (use generating-apex).
github-project-automation
IncludedAutomate GitHub repository setup with CI/CD workflows, issue templates, Dependabot, and CodeQL security scanning. Includes 12 production-tested workflows and prevents 18 errors: YAML syntax, action pinning, and configuration. Use when: setting up GitHub Actions CI/CD, creating issue/PR templates, enabling Dependabot or CodeQL scanning, deploying to Cloudflare Workers, implementing matrix testing, or troubleshooting YAML indentation, action version pinning, secrets syntax, runner versions, or CodeQL configuration. Keywords: github actions, github workflow, ci/cd, issue templates, pull request templates, dependabot, codeql, security scanning, yaml syntax, github automation, repository setup, workflow templates, github actions matrix, secrets management, branch protection, codeowners, github projects, continuous integration, continuous deployment, workflow syntax error, action version pinning, runner version, github context, yaml indentation error
sf-datacloud
IncludedSalesforce Data Cloud product orchestrator for connect→prepare→harmonize→segment→act workflows. TRIGGER when: user needs a multi-step Data Cloud pipeline, asks to set up or troubleshoot Data Cloud across phases, manages data spaces or data kits, or wants a cross-phase `sf data360` workflow. DO NOT TRIGGER when: work is isolated to a single phase (use the matching sf-datacloud-* skill), the task is STDM/session tracing/parquet telemetry (use sf-ai-agentforce-observability), standard CRM SOQL (use sf-soql), or Apex implementation (use sf-apex).
fabric-cli
IncludedUse this skill for Fabric.so CLI workflows with the `fabric` terminal command: diagnose/install/login, search or browse a Fabric library, save notes/links/files, create folders, ask the Fabric AI assistant, manage tasks/workspaces, generate shell completion, check subscription usage, produce JSON output, and use Fabric as persistent agent memory. Do not use for Microsoft Fabric/Azure/Power BI `fab`, Daniel Miessler's Fabric framework, Python Fabric SSH, Fabric.js, or textile/fashion fabric.
lark
IncludedLark/Feishu CLI skills: lark-cli operations for docs, markdown, sheets, base, calendar, im, mail, task, okr, drive, wiki, slides, whiteboard, apps, approval, attendance, contact, vc, minutes, event. Use when the user needs to operate Lark/Feishu resources via lark-cli, send messages, manage documents, spreadsheets, calendars, tasks, OKRs, deploy web pages, or any Feishu/Lark workspace operations.