菜单
Philosophy and practices for ensuring all infrastructure changes are codified, reproducible, and validated. Use when making infrastructure changes, deploying services, or reviewing operational procedures.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Core Elixir language guidelines covering common pitfalls like list access, immutability, module organization, struct access, date/time handling, and OTP patterns. Use when writing or reviewing Elixir code.
Ecto best practices covering preloading, schema types, changeset validation, field access, security, and migration conventions. Use when working with Ecto schemas, changesets, queries, or migrations.
Best practices for testing Elixir applications with Ecto.SQL.Sandbox, including background process handling, Oban testing, and test output quality. Use when writing or reviewing Elixir tests.
Phoenix HEEx template rules covering interpolation syntax, form building, class lists, conditional rendering, comments, and common anti-patterns. Use when writing or reviewing HEEx templates.
Phoenix LiveView patterns covering streams, JavaScript interop (hooks, colocated scripts, push events), testing, and form handling. Use when building or reviewing LiveView features.
Phoenix 1.8 framework conventions covering layouts, routing, components, icons, forms, HTTP clients, and design file handling. Use when building or reviewing Phoenix web applications.
| name | repeatable-deployments |
| description | Philosophy and practices for ensuring all infrastructure changes are codified, reproducible, and validated. Use when making infrastructure changes, deploying services, or reviewing operational procedures. |
All infrastructure changes MUST be codified in the repository. Manual changes to servers are temporary fixes that will be lost on redeployment. If you make a manual change to fix something, you MUST then codify it.
Configuration files - Any config files placed on servers (model configs, app configs, etc.)
Environment variables - All env vars in compose templates, secrets via secret management lookups
Directory structure - Any directories that must exist on target hosts
External dependencies - Backends, plugins, or binaries extracted from images
Permissions - File/directory permissions that differ from defaults
mode, owner, group in automation tasksdocker exec to modify container stateWork is NOT complete until it can be reproduced from scratch. Manual fixes during debugging are acceptable, but the final deliverable must be validated by:
This ensures:
Exception: Quick debugging sessions may skip validation, but must create a follow-up issue to codify and validate the fix properly.