Agent skill
documentation-guidelines
Explain documentation strategy and rules to respect all over any realization.
Install this agent skill to your Project
npx add-skill https://github.com/majiayu000/claude-skill-registry/tree/main/skills/data/documentation-guidelines
SKILL.md
Lexique :
- project folder : Current folder of user, referece too the root of the project folder.
- documentation files : all files containing text explanations, like : spécifications, README, LICENSE, Backlog and all non file writing for human readibility. It could concern media file too, like : image, video, sound, etc...
When create or read file, always respect thoses rules :
- All documentation files must be in markdown format
- All documentation files except README.md and LICENCE.md must be into the folder /docs of the project folder
- The folder /docs should be organized with subfolder. Do not acumulate files into the /docs folder, try to aggragate fils into thematical subfolders.
- The specification files must be into the /docs/specs folder of the project folder.
- Do not over documente, keep documentation clear and concise.
- Do not write too long documentation files. Documentation files must not to be longer than 300 lines. If you need to write large file of specification you should split it into sperated small files and organisze folder with subfolders. Group files with same topic into subfolders. Iterations backlog file /docs/ITERATIONS_BACKLOG.md is the only file wich had no size limit.
Keep documentation clear and compliant to thoses rules conversational.
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
Didn't find tool you were looking for?