Skip to content
cccskills
FreePublished on GitHub

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.

The English summary is being prepared. Showing the original description.

See how to install

Files included (1)

  • SKILL.md1.5 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

Based on the current conversation, create new or improve existing documentation files inside the docs/ folder.

Steps

  1. Identify conventions, patterns, or decisions discussed in the conversation that should be documented.
  2. 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.
  3. Read @docs/documentation-guidelines.md and 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
  1. Ask the user to confirm the target file path before writing.
  2. Update the AGENTS.md index with the new doc.

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.

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

Backend conventions and patterns. Use when working on API routes, dependency injection, or hexagonal architecture in the backend.

The English summary is being prepared. Showing the original description.

CodelyTV/agentic_programming-course38Updated Apr 21, 2026

Database conventions and patterns. Use when working on database schemas, migrations, or data modeling.

The English summary is being prepared. Showing the original description.

CodelyTV/agentic_programming-course38Updated Apr 21, 2026

Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, or applications.

The English summary is being prepared. Showing the original description.

CodelyTV/agentic_programming-course38Updated Apr 21, 2026

Manage the kanban board. List, read, and close GitHub issues.

The English summary is being prepared. Showing the original description.

CodelyTV/agentic_programming-course38Updated Apr 21, 2026

Navigate websites and query page content using Playwright CLI. Use this skill when the user asks to open a URL, extract data from a page, or check UI state.

The English summary is being prepared. Showing the original description.

CodelyTV/agentic_programming-course38Updated Apr 21, 2026

Execute queries on the Postgres database. Use this skill DIRECTLY whenever the user asks anything about database contents, counts, or data — do NOT read compose.yml or SQL migration files first.

The English summary is being prepared. Showing the original description.

CodelyTV/agentic_programming-course38Updated Apr 21, 2026

See all skills by CodelyTV

Report a problem with this skill