deploy-frontend

Build and deploy a frontend to S3 and CloudFront from a local machine.

18|6|Updated Apr 1, 2026
One-click install
npx skills add https://github.com/minh2004pd/chatbotfullpipeline --skill deploy-frontend
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: deploy-frontend
Source: https://github.com/minh2004pd/chatbotfullpipeline/tree/main/.claude/skills/deploy-frontend
Command: npx skills add https://github.com/minh2004pd/chatbotfullpipeline --skill deploy-frontend

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Build locally deploy frontend to S3 and CloudFront to bypass CI bottlenecks and speed up release cycles.

Core Features & Use Cases

  • Build frontend locally and verify the bundle.
  • Sync dist to S3 with proper cache settings and invalidate CloudFront to reflect changes.
  • Use case: developers can deploy hotfixes or feature previews without waiting for CI pipelines.

Quick Start

Run the local deployment workflow to build the frontend and publish it to S3 and CloudFront.

Frequently Asked Questions about deploy-frontend

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I manually deploy a frontend to AWS S3 and CloudFront without waiting for CI?

You can manually deploy a frontend to S3 and CloudFront by building locally and syncing the dist folder to S3 while invalidating the cache, bypassing CI pipelines to speed up release cycles.

What AWS permissions do I need to deploy to S3 and invalidate CloudFront?

To deploy to S3 and invalidate CloudFront, your AWS CLI credentials must have s3:PutObject and cloudfront:CreateInvalidation permissions, plus an active CF_DISTRIBUTION_ID configured in your environment.

Can I sync local frontend builds to S3 with proper cache settings?

Yes, you can sync local frontend builds to S3 with proper cache settings and trigger CloudFront invalidation to ensure viewers immediately see the latest changes.

What is the best way to release frontend hotfixes without a full CI pipeline?

The best way to release frontend hotfixes without CI is to build locally, verify the bundle, and publish directly to S3 and CloudFront for immediate feature previews or fixes.

Why deploy frontend from a local machine instead of using a CI pipeline?

Deploying frontend from a local machine bypasses CI bottlenecks, allowing developers to quickly verify local builds and push hotfixes or feature previews without waiting for pipeline execution.