Skip to content

michtio/craftcms-claude-skills / skills/craft-plugins

craft-plugins

Verified

Index and router for plugin-specific Craft CMS 5 guidance — configuration, Twig API, PHP API, migrations, deployment, and pitfalls for the plugins this pack documents. Load whenever a task names a plugin this pack documents, and for passwordless or magic-link auth with no plugin named; read references/<plugin>.md first.

references/amazon-ses.md

View on GitHub
# Amazon SES

Mail transport adapter by PutYourLightsOn. Replaces Craft's default Sendmail/SMTP transport with Amazon Simple Email Service via the Symfony Amazon Mailer. Zero configuration beyond AWS credentials — no Twig API, no CP section, just a transport swap. Used in 5/6 projects.

`putyourlightson/craft-amazon-ses` — Free (MIT)

## Documentation

- Docs: https://putyourlightson.com/plugins/amazon-ses
- GitHub: https://github.com/putyourlightson/craft-amazon-ses

## Setup

1. Install via Plugin Store or Composer
2. CP → Settings → Email → Transport Type → "Amazon SES"
3. Enter AWS region and credentials

Credentials can be left blank to use the default AWS credential provider chain (environment variables, IAM roles, etc.).

## Configuration

All settings are configured via the CP email settings UI. Environment variables are supported:

| Setting | Env Example | Description |
|---------|-------------|-------------|
| Region | `$AWS_REGION` | AWS region (e.g., `eu-west-1`) |
| API Key | `$AWS_ACCESS_KEY_ID` | AWS access key (blank for credential chain) |
| Secret | `$AWS_SECRET_ACCESS_KEY` | AWS secret key (blank for credential chain) |
| Configuration Set | `$SES_CONFIGURATION_SET` | Optional — for bounce/complaint tracking via SNS |

### Environment-Based Config

Use `.env` for credentials:

```env
# .env
AWS_REGION=eu-west-1
AWS_ACCESS_KEY_ID=AKIAXXXXXXXXXX
AWS_SECRET_ACCESS_KEY=your-secret-key
SES_CONFIGURATION_SET=my-config-set
```

Then reference `$AWS_REGION` etc. in the CP email settings.

## Common Pitfalls

- Not verifying sender domain/email in SES — AWS requires domain verification (DKIM + SPF via Route 53 or manual DNS) before sending. Without it, emails fail silently or bounce.
- Using SES in sandbox mode — new SES accounts are sandboxed (can only send to verified addresses). Request production access before launch.
- Missing SNS configuration for bounces — if using a Configuration Set, configure SNS topics for bounces and complaints. This is especially important with Campaign plugin.
- Hardcoding credentials — use environment variables or IAM roles, never hardcode keys in the CP.
- Not setting the right region — SES endpoints are regional. Use the same region as your verified domain.

## No Twig/PHP API

This plugin has no Twig API, no console commands, and no config file. It registers a mail transport adapter — that's it. All email sending goes through Craft's standard `Craft::$app->mailer->compose()` API.

For the full AWS SES setup pattern including DKIM, SPF, and DMARC configuration, see the `craft-site` skill's `references/third-party-integration.md`.

## Pair With

- **Campaign** — Campaign sends email campaigns through Craft's mailer, so Amazon SES handles delivery. Campaign has webhook support for SES bounce/complaint notifications via SNS.
- **Formie** — form notification emails route through SES when configured as the transport
- **Sherlock** — monitoring alerts go through Craft's mailer → SES
writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deploymentStars: 322kUpdated Claude CodeCodexVerifiedInstall
xlsxanthropics/skillsUse this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .xltx, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved.Stars: 198kUpdated Claude CodeCodexVerifiedInstall
shipping-and-launchaddyosmani/agent-skillsPrepares production launches. Use when preparing to deploy to production, or when asking what needs to be in place before shipping. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy.Stars: 119kUpdated Claude CodeCodexVerifiedInstall
childhoodthedotmack/claude-memBabysit a shipped release after merge, publication, or deployment. Verify published packages, production behavior, installed plugins, and late CI or user reports until the observation window is clean; use babysit for PR readiness before release.Stars: 118kUpdated Claude CodeCodexVerifiedInstall