home / skills / shaul1991 / shaul-agents-plugin / frontend-build

frontend-build skill

/skills/frontend-build

This skill optimizes frontend build settings and deployment pipelines by managing environment variables, Docker configuration, and CI/CD workflows.

npx playbooks add skill shaul1991/shaul-agents-plugin --skill frontend-build

Review the files below or copy the command above to add this skill to your agents.

Files (1)
SKILL.md
537 B
---
name: frontend-build
description: 빌드/배포 에이전트. 빌드 설정과 배포 파이프라인을 관리합니다.
allowed-tools: Read, Write, Edit, Glob, Grep, Bash
---

# Frontend Build Agent

## 역할
빌드 설정과 배포 파이프라인을 관리합니다.

## 담당 업무
- 빌드 설정 최적화
- 환경 변수 관리
- Docker 설정
- CI/CD 파이프라인

## 트리거 키워드
빌드, build, 배포, deploy, docker

## 산출물 위치
- 설정: `next.config.js`, `Dockerfile`
- CI/CD: `.github/workflows/`

Overview

This skill is a frontend build and deploy agent that manages build configuration and deployment pipelines. It centralizes build settings, Docker integration, environment variable handling, and CI/CD workflow maintenance. The skill is aimed at streamlining consistent, reproducible frontend releases across environments.

How this skill works

The agent inspects project configuration files and deployment artifacts (notably next.config.js and Dockerfile) and updates or validates build settings. It also prepares and maintains CI/CD definitions under .github/workflows/, ensuring environment variables and Docker images are built and deployed reliably. Triggers include keywords like build, deploy, docker to initiate tasks or generate pipeline changes.

When to use it

  • Setting up a new frontend repo for predictable builds and containerized deployment
  • Standardizing environment variable management across dev, staging, and production
  • Creating or repairing Dockerfile and image build steps for the frontend
  • Adding or optimizing GitHub Actions workflows for automated builds and deployments
  • Auditing build configuration (next.config.js) for performance and correctness

Best practices

  • Keep sensitive values out of config files; use secrets in CI/CD and environment stores
  • Version Dockerfile and workflow templates to enable reproducible builds
  • Validate next.config.js and build outputs locally before pushing workflow changes
  • Use deterministic build steps and lock dependency versions to reduce flakes
  • Test pipeline changes in a feature branch and use a staging environment before production

Example use cases

  • Add a Dockerfile that builds the Next.js app and produces a minimal production image
  • Generate GitHub Actions workflow to run tests, build artifacts, and push Docker images
  • Migrate environment variables from checked-in files to encrypted CI secrets
  • Optimize next.config.js for server-side rendering and static export performance
  • Fix intermittent CI failures by pinning Node and dependency versions in the build

FAQ

Which files does the agent modify or produce?

It focuses on next.config.js, Dockerfile, and workflow files under .github/workflows/.

How are secrets handled?

The agent recommends and configures use of CI secrets and environment stores; it avoids writing sensitive values into repo files.