cicd-pipeline-design

Included with Lifetime

$97 forever

Design CI/CD pipeline from source to prod. Tool selection, stages, quality gates, artifact management, deployment strategy (blue-green / canary / rolling / progressive), observability, secrets via OIDC.

Design

What this skill does


# CI/CD Pipeline Design

You design a CI/CD pipeline: stages, quality gates, deployment strategy.

## Tool selection

| Tool | Best for |
|---|---|
| **GitHub Actions** | Repo on GitHub; rich ecosystem |
| **GitLab CI** | Repo on GitLab; integrated |
| **Jenkins** | Legacy / on-prem / highly customizable |
| **CircleCI** | Cloud-native, fast |
| **Buildkite** | Self-hosted agents with cloud UI |
| **Azure Pipelines** | Azure-ecosystem |
| **Tekton** | K8s-native pipelines |
| **Argo Workflows / Argo CD** | K8s-native; GitOps |
| **Dagger** | Portable pipelines in code |

## Pipeline stages

```
Source → Build → Test → Security → Artifact → Deploy → Verify → Notify
```

### Source

- Trigger on push / PR / merge / tag
- Branch protection rules
- Commit signing (optional but recommended)

### Build

- Deterministic / reproducible
- Cache dependencies (`node_modules`, container layers, language caches)
- Build artifact versioned (semver + commit SHA)

### Test

| Layer | When | Gate |
|---|---|---|
| Unit | Every PR | Must pass |
| Integration | Every PR (slower) | Must pass |
| E2E critical path | Pre-merge or post-deploy to staging | Must pass |
| Performance | Nightly / pre-release | Regression detection |
| Security (SAST) | Every PR | Fail on critical/high |
| SCA (dependencies) | Every PR | Fail on critical vuln |
| Container scan | On image build | Fail on critical |
| License check | On dependency change | Fail on non-allow-listed |

### Security scans

- **SAST**: Semgrep / SonarQube / CodeQL / Snyk Code
- **SCA**: Dependabot / Snyk / Renovate
- **Container scan**: Trivy / Grype / Snyk Container
- **Secret scan**: Gitleaks / TruffleHog / built-in
- **License**: license-checker / FOSSA / Snyk License

### Artifact

- Semver-tagged
- Immutable
- Signed (Sigstore / Cosign)
- Provenance (SLSA attestations)

### Deploy strategies

| Strategy | How | Risk profile |
|---|---|---|
| **Rolling** | Replace instances gradually | Simple; downtime-free for stateless |
| **Blue-green** | Deploy to parallel env, switch | Fast rollback; 2× capacity momentarily |
| **Canary** | Route small % to new, watch, scale | Risk-controlled; needs traffic-split capability |
| **Progressive delivery** | Canary + automated metrics gating | Highest safety; requires observability depth |
| **Feature flags** | Deploy dark, enable per cohort | Decouples deploy from release |
| **Shadow / dark launch** | Run new alongside, compare | Validate before full cutover |

### Verify

- Smoke tests post-deploy
- Health checks
- Metrics from observability
- Error-rate + latency delta vs baseline
- Auto-rollback on regression

### Notify

- Slack / Teams / email on success + failure
- PagerDuty on prod failure

## Environment flow

```
Dev (auto) → Staging (auto on merge) → Production (manual approval or auto with all gates green)
```

## Secrets

- OIDC federation (GitHub Actions → AWS IAM via OIDC; GitLab → GCP Workload Identity)
- No long-lived keys in pipeline secrets
- Runtime secrets via vault at deploy (not baked into artifacts)

## Cache + speed

- Dependency caches
- Parallel test runs
- Selective CI (only run tests for changed components)
- Incremental builds

## Observability of pipeline itself

- Pipeline duration trend
- Flaky test tracking
- Build-success rate per branch
- Bottleneck stage identification

## Report

```markdown
# CI/CD Pipeline: [Product]

## Tool Selection
[Chosen + rationale]

## Pipeline Stages
[Each stage with gates]

## Quality Gates
[Unit / integration / E2E / SAST / SCA / container / license]

## Artifact Management
[Versioning + signing + provenance]

## Deployment Strategy
[Rolling / blue-green / canary / progressive / feature-flags]

## Environment Flow
[Dev → staging → prod with approvals]

## Secrets
[OIDC federation + no long-lived keys]

## Observability
[Pipeline + deployment]

## Rollback Procedure
[Automated + manual triggers]

## Diagram
```

## Failure behavior
- No test gates → require
- Secrets in pipeline env → migrate to OIDC
- No rollback → require
- mmdc failure → see mixin

Files: 1

Size: 4.3 KB

Complexity: 13/100

Category: Design

Source: https://github.com/ssiertsema/claude-code-plugins/tree/main/cicd-pipeline-design/skills/cicd-pipeline-design

Related in Design

contribute

Included

Local-only OSS contribution command center. Auto-refreshes the user's in-flight PR and issue state on invoke so conversations start with full context — no need to brief Claude on what's in flight. Helps the user find issues to contribute to on GitHub, builds per-repo dossiers of what each upstream expects (CLA, DCO, branch convention, AI policy, draft-first, review bots, issue templates), runs deterministic gates before any external action so AI-assisted contributions don't reach maintainers as slop. State is markdown-only: candidate files at ~/.contribute-system/candidates/, repo dossiers at ~/.contribute-system/research/, append-only event log at ~/.contribute-system/log.jsonl. No database, no cloud calls. Use when the user asks about their PRs / issues / contributions, wants to find new work to take on, claim an issue, build/refresh a repo's dossier, or draft a Design Issue or PR. Trigger with "/contribute", "what's my PR status", "find a contribution", "claim issue X", "draft a Design Issue for Y", "refresh dossier for Z".

Designscripts

architectural-analysis

Included

User-triggered deep architectural analysis of a codebase or scoped subtree across eight modes — information architecture, data flow, integration points, UI surfaces, interaction patterns, data model, control flow, and failure modes. This skill should be used when the user asks to "diagram this codebase," "map the architecture," "show the data flow," "give me an ERD," "trace control flow," "find the integration points," "verify the layout pattern," "audit the UX architecture," or any similar request whose primary deliverable is mermaid diagrams plus cited reports under docs/architecture/. Dispatches haiku/sonnet sub-agents in parallel for per-mode exploration, then verifies every citation mechanically before any node lands in a diagram. Not for one-off prose explanations of code (use code-explanation) or for high-level system design from scratch (use system-design).

Designscripts

mcp

Included

Model Context Protocol (MCP) server development and tool management. Languages: Python, TypeScript. Capabilities: build MCP servers, integrate external APIs, discover/execute MCP tools, manage multi-server configs, design agent-centric tools. Actions: create, build, integrate, discover, execute, configure MCP servers/tools. Keywords: MCP, Model Context Protocol, MCP server, MCP tool, stdio transport, SSE transport, tool discovery, resource provider, prompt template, external API integration, Gemini CLI MCP, Claude MCP, agent tools, tool execution, server config. Use when: building MCP servers, integrating external APIs as MCP tools, discovering available MCP tools, executing MCP capabilities, configuring multi-server setups, designing tools for AI agents.

Designscripts

react-native-skia

Included

Design, build, debug, and optimise high-polish animated graphics in React Native or Expo using @shopify/react-native-skia, Reanimated, and Gesture Handler. Use when the user wants canvas-driven UI, shaders, paths, rich text, image filters, sprite fields, Skottie, video frames, snapshots, web CanvasKit setup, or performance tuning for custom motion-heavy elements such as loaders, hero art, cards, charts, progress indicators, particle systems, or gesture-driven surfaces. Also use when the user asks for fluid, glow, glass, blob, parallax, 60fps/120fps, or GPU-friendly animated effects in React Native, even if they do not explicitly say "Skia". Do not use for ordinary form/layout work with standard views.

Designscripts

plaid

Included

Product Led AI Development — guides founders from idea to launched product. Six capabilities: Idea (discover a product idea), Validate (pressure-test the idea against fatal flaws, problem reality, competition, and 2-week MVP feasibility), Plan (vision intake + document generation), Design (translate image references into a design.md spec), Launch (go-to-market strategy), and Build (roadmap execution). Use when someone says "PLAID", "plaid idea", "help me find an idea", "product idea", "idea from my business", "idea from my expertise", "plaid validate", "validate my idea", "pressure-test", "is this idea good", "find fatal flaws", "validate the problem", "plan a product", "define my vision", "generate a PRD", "product strategy", "plaid design", "design from image", "translate image to design", "create design.md", "extract design tokens", "plaid launch", "go-to-market", "launch plan", "GTM strategy", "launch playbook", "plaid build", "build the app", "start building", or "execute the roadmap".

Designscripts

nextjs-framer-motion-animations

Included

Adds production-safe Motion for React or Framer Motion animations to Next.js apps, including reveal, hover and tap micro-interactions, whileInView, stagger, AnimatePresence, layout and layoutId transitions, reorder, scroll-linked UI, and lightweight route-content transitions. Use when the user asks to add, refactor, or debug Motion or Framer Motion in App Router or Pages Router codebases, especially around server/client boundaries, reduced motion, LazyMotion, bundle size, hydration, or route transitions. Avoid for GSAP-style timelines, WebGL or 3D scenes, heavy scroll storytelling, or CSS-only effects unless Motion is explicitly requested.

Designscripts