Requirements

Start with an analogy: Compare the code to something from everyday life
Draw a diagram: Use ASCII art to show the flow, structure, or relationships
Walk through the code: Explain step-by-step what happens
Highlight a gotcha: What&#39;s a common mistake or misconception?

Always create a directory in the skills directory.
Making the name in the md file the same as the directory name
The file name is always SKILL.md
Try to write an example of applying the skill like below
The words of names should be connected with "-"
The naming should follows verb-then-norm format unless it's too short to represent the meaning. for example, create-skill.

Example

When explaining code, always include:

Keep explanations conversational. For complex concepts, use multiple analogies.

Always create a directory in the skills directory.
Making the name in the md file the same as the directory name
The file name is always SKILL.md
Try to write an example of applying the skill like below
The words of names should be connected with "-"
The naming should follows verb-then-norm format unless it's too short to represent the meaning. for example, create-skill.

When explaining code, always include:

Keep explanations conversational. For complex concepts, use multiple analogies.