| name | [object Object] |
| description | [TODO: Write comprehensive description in third-person. Start with "This skill provides..." or "This skill should be used when..."] [TODO: Add "Use when" scenarios - specific situations where Claude should use this skill] [TODO: Add keywords - technologies, use cases, error messages that should trigger this skill] |
| license | MIT |
[TODO: Skill Display Name]
Status: [TODO: Production Ready / Beta / Experimental] Last Updated: [TODO: YYYY-MM-DD]
Quick Start ([TODO: X] Minutes)
1. [TODO: First Major Step]
[TODO: Provide clear, actionable instructions]
# [TODO: Example command]
Why this matters:
- [TODO: Explain the reasoning]
- [TODO: Key benefits]
2. [TODO: Second Major Step]
[TODO: Continue with step-by-step instructions]
// [TODO: Code example with comments]
CRITICAL:
- [TODO: Important notes that prevent common mistakes]
Critical Rules
Always Do
✅ [TODO: Best practice #1] ✅ [TODO: Best practice #2] ✅ [TODO: Best practice #3]
Never Do
❌ [TODO: Anti-pattern #1] ❌ [TODO: Anti-pattern #2] ❌ [TODO: Anti-pattern #3]
Common Patterns
Pattern 1: [TODO: Pattern Name]
// [TODO: Code example]
When to use: [TODO: Specific scenarios]
Pattern 2: [TODO: Pattern Name]
[TODO: More examples]
Official Documentation
- [TODO: Technology Name]: [TODO: Official docs URL]
- [TODO: Related Tool]: [TODO: Official docs URL]
Key Reminders:
- Use third-person for description: "This skill provides..." not "This skill helps you..."
- Write in imperative form: "To do X, run Y" not "You should run Y to do X"
- Include actual error messages and GitHub issue links
- Remove all [TODO:] markers before committing