Create a new documentation file following project standards. Detects overlap with existing docs before creating.
The English summary is being prepared. Showing the original description.
See how to installReview the instructions the agent will receive before you install.
This skill activates for:
/create-docRead .claude/roles/documentalist.md — adopt this profile and follow all its rules.
If the subject is vague, ask:
reference, guide, architecture, or spec?MANDATORY before any creation.
# List all existing docs
Glob docs/**/*.md
# Read the titles and H2/H3 of each file
# Compare with the requested subject
If an existing doc already covers the subject:
/update-docsIf partial overlap:
Apply the template from PERSONA.md:
---
title: <Title>
scope: reference | guide | architecture | spec
related:
- src/path/to/source.ts
- docs/RELATED-DOC.md
last-updated: YYYY-MM-DD
---
Writing rules:
| Location | Convention |
|---|---|
docs/ top-level | SCREAMING-KEBAB.md (e.g., MCP-TOOLS-REFERENCE.md) |
| Subdirectory | kebab-case.md (e.g., docs/mcp/architecture.md) |
Run /docs-index to regenerate docs/INDEX.md with the new file.
| Forbidden | Do Instead |
|---|---|
| Duplicate existing content | Link to the canonical source |
| Doc > 800 words | Split into multiple files |
| Sections unrelated to the title | Create a separate doc |
| Prose when a table suffices | Use a table |
| Mixing French and English | Everything in English |
No reviews yet. Tell others what you thought.
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.
Guide for creating optimized Claude Code agents. Use to design a new specialized agent, a swarm sub-agent, or a multi-agent workflow. Follows the Skill → Agent (preloaded skills) → Skill orchestration pattern.
The English summary is being prepared. Showing the original description.
Anti-overengineering guide based on YAGNI. Use before adding an architectural pattern, during code review, or to challenge an overly complex implementation.
The English summary is being prepared. Showing the original description.
Clean Architecture (Uncle Bob) guide for this project. Use when creating modules, entities, use cases, presenters, controllers, gateways, guards, services. Contains tactical patterns and structure conventions.
The English summary is being prepared. Showing the original description.
Audit documentation for duplication, staleness, language issues, and verbosity. Read-only — produces an actionable report.
The English summary is being prepared. Showing the original description.
Local auto-review of modified code (no GitLab/GitHub). Runs 5 sequential audits and generates a local report. Ideal for validating code before creating a MR/PR.
The English summary is being prepared. Showing the original description.
Clean Code (Robert C. Martin) guide to produce and challenge code that is readable, durable, simple, and consistent. Covers naming, functions, comments, smells, and refactor heuristics. Complements `/solid` (SOLID principles) and `/anti-overengineering` (YAGNI/KISS). Activate during the REFACTOR phase of the TDD cycle and during implementation self-review.
The English summary is being prepared. Showing the original description.