Yaccp Claude Plugin Aws Docusaurus
yaccp-claude-plugin-aws-docusaurus is a Claude Code plugin for the Operate phase that deploys Docusaurus and other static sites to AWS using S3, CloudFront, and Lambda@Edge.
by yaccp · github.com/yaccp/claude-plugin-aws-docusaurus
Install when you ship a Docusaurus or other static site and want Claude Code-guided deploys to AWS S3, CloudFront, and optional Lambda@Edge and Route53.
Add it to Claude Code
Install the plugin in Claude Code. One command, paste-ready.
/plugin install yaccp-claude-plugin-aws-docusaurus@yaccp/claude-plugin-aws-docusaurusBuilt to be called by your agent
Skillselion is itself an MCP server. Your agent can pull this entry and a paste-ready install config straight from the API - no copy-paste.
Retrieve this entry with skillselion.get_details("plugin:yaccp/claude-plugin-aws-docusaurus") and the paste-ready config with skillselion.get_install_config("plugin:yaccp/claude-plugin-aws-docusaurus").
What it does
yaccp-claude-plugin-aws-docusaurus is a single-plugin Claude Code package for solo builders who treat documentation and marketing sites as static artifacts on AWS. The marketplace entry describes deploying with S3, CloudFront, and Lambda@Edge, with Route53 called out as optional—typical for Docusaurus output after you run a local or CI build. Instead of memorizing console clicks or one-off Terraform, you register the plugin and let Claude Code walk through bucket policies, distribution settings, and edge functions in a repeatable script. It fits indie hackers publishing docs-heavy SaaS, open-source handbooks, or changelog sites who already chose AWS over Vercel or Netlify. Complexity is intermediate: you need AWS credentials, understanding of static hosting, and comfort invalidating CloudFront when content changes. This is deploy automation via Claude Code plugin, not a frontend generator or SEO skill.
Highlights
- 1 focused Claude Code plugin for AWS static-site deployment
- S3 origin plus CloudFront CDN wiring for Docusaurus builds
- Lambda@Edge hooks for edge behavior on the CDN path
- Optional Route53 DNS steps for custom domains
- Documented yaccp workflow aimed at static-site operators
Why builders use it
Solo builders stall after `docusaurus build` because wiring S3, CloudFront, edge functions, and DNS on AWS is tedious and easy to misconfigure.
After installing the plugin, you can drive a guided AWS static-site deployment from Claude Code with CDN and optional custom-domain steps documented in the repo.
At a glance
- Type - Plugin in DevOps.
- Adoption - 0 installs, 0 stars, 0 votes.
FAQ
Who is yaccp-claude-plugin-aws-docusaurus for?
It is for Claude Code users shipping static sites—especially Docusaurus—who host on AWS and want plugin-guided S3 and CloudFront setup.
When should I use yaccp-claude-plugin-aws-docusaurus?
Use it when you have a production-ready static build and need to push or refresh hosting on S3 behind CloudFront, including optional Lambda@Edge and Route53.
How do I add yaccp-claude-plugin-aws-docusaurus to my agent?
Add the yaccp/claude-plugin-aws-docusaurus repo to your Claude Code plugin sources, install the single deployment plugin, and configure AWS credentials per the plugin README before running deploy commands.
Comments
Share how you use yaccp-claude-plugin-aws-docusaurus, gotchas, or tips for other indie builders.
No comments yet - be the first to share how you use it.