원클릭으로
ci-templates
Use when setting up CI/CD pipelines. Teaches pipeline design principles and references platform-specific templates.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
메뉴
Use when setting up CI/CD pipelines. Teaches pipeline design principles and references platform-specific templates.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
Build immersive, scroll-driven websites with GSAP ScrollTrigger, Lenis smooth scroll, parallax effects, and cinematic page transitions. Use when building premium corporate sites, landing pages, or marketing microsites that need motion and polish beyond static designs.
Use when adding docstrings, creating API documentation, or building documentation sites. Invoke for OpenAPI/Swagger specs, JSDoc, doc portals, tutorials, user guides.
Use when reviewing pull requests, conducting code quality audits, or identifying security vulnerabilities. Invoke for PR reviews, code quality checks, refactoring suggestions.
Use when investigating slow queries, analyzing execution plans, or optimizing database performance. Invoke for index design, query rewrites, configuration tuning, partitioning strategies, lock contention resolution.
Use when investigating errors, analyzing stack traces, or finding root causes of unexpected behavior. Invoke for error investigation, troubleshooting, log analysis, root cause analysis.
Use when setting up CI/CD pipelines, containerizing applications, or managing infrastructure as code. Invoke for pipelines, Docker, Kubernetes, cloud platforms, GitOps.
SOC 직업 분류 기준
| name | ci-templates |
| description | Use when setting up CI/CD pipelines. Teaches pipeline design principles and references platform-specific templates. |
Principles for designing fast, reliable CI/CD pipelines. Platform-specific templates in docs/ci-templates/.
Run quick checks first. Don't waste 10 minutes building if linting fails in 10 seconds.
Stage Order:
1. Lint/Format (seconds)
2. Type Check (seconds)
3. Unit Tests (minutes)
4. Integration Tests (minutes)
5. Build (minutes)
6. E2E Tests (minutes)
7. Deploy (varies)
Never re-download what you already have.
| Framework | Cache Path |
|---|---|
| PHP/Composer | vendor/ |
| Node.js | node_modules/ |
| Python | .venv/ or ~/.cache/pip |
Jobs that don't depend on each other should run simultaneously.
✓ Good: lint + unit-tests + type-check (parallel)
✗ Bad: lint → unit-tests → type-check (sequential)
Don't rebuild between stages. Pass build artifacts.
Use Docker Hub, GitHub Container Registry, or official images by default. Custom registries are an optimization, not a requirement.
| Platform | Template Location | Config File |
|---|---|---|
| GitLab CI | docs/ci-templates/gitlab/ | .gitlab-ci.yml |
| GitHub Actions | docs/ci-templates/github/ | .github/workflows/*.yml |
No setup required. Works everywhere.
| Framework | Image | Notes |
|---|---|---|
| PHP | php:8.3-cli | Add extensions in before_script |
| Python | python:3.12 | Add deps in before_script |
| Node | node:20 | Works out of the box |
| Playwright | mcr.microsoft.com/playwright:latest | All browsers included |
| Security | aquasec/trivy:latest | Multi-language scanner |
For faster builds, pre-bake dependencies into custom images.
Configure in .claude/registry.json:
{
"registry": "your-registry.example.com/images",
"images": {
"php": { "testing": "php:8.3-testing" },
"node": { "base": "node:20-base" }
}
}
See docs/registry-config.md for building custom images.
Always include security scanning. Use allow_failure: true initially to avoid blocking deploys while you fix issues.
| Scanner | What It Checks | Image |
|---|---|---|
composer audit | PHP dependencies | php:* |
npm audit | Node dependencies | node:* |
pip-audit | Python dependencies | python:* |
| Trivy | Everything + containers | aquasec/trivy |
| Gitleaks | Secrets in code | zricethezav/gitleaks |
# .gitlab-ci.yml - minimal working example
stages: [test]
test:
image: node:20
script:
- npm ci
- npm test
cache:
paths: [node_modules/]
# .github/workflows/test.yml - minimal working example
name: Test
on: [push, pull_request]
jobs:
test:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v4
- uses: actions/setup-node@v4
with: { node-version: '20' }
- run: npm ci
- run: npm test
Full templates for common stacks:
| Stack | GitLab | GitHub |
|---|---|---|
| Laravel/PHP | docs/ci-templates/gitlab/laravel.yml | docs/ci-templates/github/laravel.yml |
| Django/Python | docs/ci-templates/gitlab/django.yml | docs/ci-templates/github/django.yml |
| React/Node | docs/ci-templates/gitlab/react.yml | docs/ci-templates/github/react.yml |
| Full-Stack | docs/ci-templates/gitlab/fullstack.yml | docs/ci-templates/github/fullstack.yml |
When setting up a pipeline:
These templates work with:
/laravel, /python, /react commands/architect security for security scanningsystem-architect skill for infrastructure audits