Create doc
Skill CodelyTV/agentic_programming-course/05-mcps/3-mcp_vs_cli/4-multiple_cli/.agents/skills/create-doc
Create or improve documentation based on the current conversation. Use this when a plan has been created and changes were requested because it didn’t follow the repository’s conventions.From its SKILL.md
npx -y skills add CodelyTV/agentic_programming-course --skill create-docAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
SKILL.md
1.5 KB, 287 tokens by cl100k_base, as published. Nobody here has run it
Based on the current conversation, create new or improve existing documentation files inside the docs/ folder.
Steps
- Identify conventions, patterns, or decisions discussed in the conversation that should be documented.
- Check if a relevant doc already exists in
docs/(organized by area:backend/,frontend/,database/, etc.).- If it exists, improve it while preserving the required structure.
- If it does not exist, create a new file in the appropriate subfolder.
- Read
docs/documentation-guidelines.mdand follow its structure exactly. Every document MUST include these sections in order:
# 🎯 Name of the convention
## 💡 Convention
## 🏆 Benefits
## 👀 Examples (with ✅ Good and ❌ Bad subsections)
## 🧐 Real world examples
## 🔗 Related agreements
- Ask the user to confirm the target file path before writing.
Rules
- Each convention goes in its own standalone Markdown file — never bundle multiple conventions into one doc.
- Place files in the correct area subfolder (
backend/,frontend/,database/,testing/, etc.). - Include concrete good and bad examples with code blocks when applicable.
- Link to real files in the codebase that follow the convention in the "Real world examples" section.
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.