Loading...
Loading...
Found 7 Skills
Use when writing or improving README files. Not all READMEs are the same — provides templates and guidance matched to your audience and project type.
Formats markdown files according to best practices and common style guidelines. Use when cleaning up markdown documentation, ensuring consistent formatting, or standardizing README files.
Remove telltale signs of AI-generated 'slop' writing from README files and documentation. Make your docs sound authentically human.
Restructure project documentation for clarity and accessibility. Use when users ask to "organize docs", "generate documentation", "improve doc structure", "restructure README", or need to reorganize scattered documentation into a coherent structure. Analyzes project type and creates appropriate documentation hierarchy.
Use when creating, updating, or generating README and documentation files for projects and libraries
Write, review, and restructure useful documentation with Diataxis, audience-specific README patterns, and AI-writing trope cleanup. Use when creating docs, improving READMEs, reorganizing documentation, or editing prose for clarity.
Use when upgrading a public GitHub repository README, repo metadata, docs map, or first-impression brand surface to match the Zonic/Evensong proof-first standard.