When setting up frontend deployment automation that runs quality checks before anything reaches production.
You are a senior {{role}} brought in to help a developer or tech professional complete a {{use_case}} task. # Context - Pack: Developers & Tech Professionals - Category: Mobile & Frontend Development - Use case: Frontend CI/CD Pipeline - Source task: - Build a CI/CD pipeline for a {{framework}} frontend application hosted on {{vercel_netlify_aws_s3_cloudfront_custom}}. - Step 1: CI: lint, type-check, unit tests, component tests, bundle size budget check : write the full GitHub Actions YAML. - Step 2: Preview Deployments: how to deploy branch previews for every PR. - Step 3: Production Deployment: deployment strategy (atomic, with rollback), environment variable promotion, and CDN cache invalidation. - Step 4: Post-deploy: Lighthouse CI score enforcement and E2E smoke tests. # Goal CI YAML with lint, types, tests, and bundle checks; preview deployment config; production deployment strategy; and Lighthouse CI enforcement. # Constraints - Treat this as a sequential workflow where each step builds on the previous step. - Keep every step clearly labeled and easy to run separately if needed. - Avoid generic filler, vague advice, and unsupported claims. - Make the output specific, practical, and ready to use. # Output CI YAML with lint, types, tests, and bundle checks; preview deployment config; production deployment strategy; and Lighthouse CI enforcement.
{{double-curly}} with your real context.When setting up frontend deployment automation that runs quality checks before anything reaches production.
A bundle size budget check in CI prevents accidental performance regressions — add a threshold that breaks the build if exceeded.
Debug this problem systematically. Identify the root cause, explain why it is happening, provide the fix, and explain how to prevent it in future.
Design the high-level architecture for this system. Cover components, data flow, scaling strategy, and key design decisions.
Recommend the best no-code or low-code tool stack for the stated goal, with implementation guidance.
Design the complete analysis approach for the stated question. Include the analytical method, the steps to execute it, and the format for presenting findings.