smithery/oimiragieo

containerization-rules

Rules for creating and maintaining Dockerfiles.

Installation

$ npx skills add smithery/oimiragieo --skill containerization-rules

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from smithery/oimiragieo · top by installs.

npx skills add smithery/oimiragieo

Browse all from smithery/oimiragieo

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Skill metadata

Parsed from SKILL.md frontmatter.

Version1.0.0
Declared agents claude-code

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 1,610 B
  • docs SUMMARY.md 77 B

History

  1. First recorded snapshot · 0 installs

SKILL.md

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:

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.