containerization-rules
Rules for creating and maintaining Dockerfiles.
Best use case
containerization-rules is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Rules for creating and maintaining Dockerfiles.
Teams using containerization-rules should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/containerization-rules/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How containerization-rules Compares
| Feature / Agent | containerization-rules | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Rules for creating and maintaining Dockerfiles.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Containerization Rules Skill <identity> You are a coding standards expert specializing in containerization rules. You help developers write better code by applying established guidelines and best practices. </identity> <capabilities> - Review code for guideline compliance - Suggest improvements based on best practices - Explain why certain patterns are preferred - Help refactor code to meet standards </capabilities> <instructions> When reviewing or writing code, apply these guidelines: - You are an expert in containerization technologies. - Follow best practices for creating efficient and secure Dockerfiles. </instructions> <examples> Example usage: ``` User: "Review this code for containerization rules compliance" Agent: [Analyzes code against guidelines and provides specific feedback] ``` </examples> ## Memory Protocol (MANDATORY) **Before starting:** ```bash cat .claude/context/memory/learnings.md ``` **After completing:** Record any new patterns or exceptions discovered. > ASSUME INTERRUPTION: Your context may reset. If it's not in memory, it didn't happen.
Related Skills
common-rules
Tüm skill'ler için ortak kurallar ve standartlar. Git workflow, code style, documentation ve performance best practices içerir.
checkstyle-rules
Use when applying Checkstyle built-in checks for Java code including naming conventions, code metrics, and suppressions.
assistant-behavior-rules
AI assistant behavior rules including response formatting and interaction patterns
ameba-custom-rules
Use when creating custom Ameba rules for Crystal code analysis including rule development, AST traversal, issue reporting, and rule testing.
alpine-js-usage-rules
Guidelines for using Alpine.js for declarative JavaScript functionality.
agp-router-rules
Rules for using the Agp Router.
admin-interface-rules
Rules for the Admin interface functionalities
pyqt6-ui-development-rules
Specific rules for PyQt6 based UI development focusing on UI/UX excellence and performance.
mobile-first-design-rules
Focuses on rules and best practices for mobile-first design and responsive typography using tailwind.
create-design-system-rules
Generates custom design system rules for the user's codebase. Use when user says "create design system rules", "generate rules for my project", "set up design rules", "customize design system guidelines", or wants to establish project-specific conventions for Figma-to-code workflows. Requires Figma MCP server connection.
accessibility-rules
Concise accessibility checklist and practices for components in the repository. Use when implementing UI to ensure keyboard, screen reader, and focus semantics.
rules-vs-skills
Explain when to use always-on Rules vs on-demand Skills. Use when the team is confused about where to encode guidance, deciding between rules and skills, or understanding the difference between invariants and procedures.