readme-writing
Guidelines for writing folder READMEs. Use when creating README.md files for directories.
Security Assessment
About readme-writing
The 'readme-writing' skill provides comprehensive guidelines for creating effective README.md files for directories within a project. Its primary purpose is to clarify the reasoning behind the existence of a folder and its contents, allowing users to understand the organizational structure and the context of the files without needing to delve into each file individually. By offering insights into the mental model and the intended use of the contents, this skill helps improve the overall documentation quality within a project, ensuring that developers can navigate and utilize the folder efficiently.
Key capabilities of this skill include establishing best practices for documenting folders, such as explaining the purpose and organizational logic, providing context for developers, and avoiding redundancy by not listing files or repeating information that is already apparent from the code. The guidelines emphasize the importance of scannability and brevity, suggesting that a few sentences or a short paragraph is typically sufficient to convey the necessary information. This skill is particularly focused on internal folder documentation, distinguishing itself from root project READMEs that may require installation and usage instructions.
Target users of this skill include software developers, technical writers, and project maintainers who are responsible for documenting their project's structure. By following these guidelines, users can ensure that their folder READMEs are informative, helpful, and conducive to a better understanding of the project's organization, ultimately enhancing collaboration and onboarding for new team members.
FAQ
What is the main purpose of the readme-writing skill?
The main purpose is to provide guidelines for creating effective README.md files that explain the purpose and organization of project directories.
Can this skill be used for root project READMEs?
No, this skill is specifically designed for internal folder documentation and does not cover root project README requirements such as installation and usage instructions.
What should be included in a good README according to the guidelines?
A good README should explain the 'why' behind the folder, its organizational logic, and provide helpful context without listing files or duplicating obvious information.
How long should a README be?
A README should be scannable; typically, a few sentences to a short paragraph is sufficient.
Who are the primary users of this skill?
The primary users are software developers, technical writers, and project maintainers responsible for documenting project structures.
Install readme-writing
Quick Setup:
- Copy the skill folder to
.claude/skills/ - Claude will automatically detect and use the skill
Repository
EpicenterHQ/epicenter