Total 52,846 skills, Documentation & Writing has 1498 skills
Showing 12 of 1498 skills
Scaffold and audit OSS documentation for open source projects. Use for "add OSS docs", "create README", "setup contributing", "add changelog", "prepare for open source", or "add AGENTS.md".
Document codebase as-is with thoughts directory for historical context
Create a 'how does X work' documentation file for a codebase component or concept. Use $ARGUMENTS as the doc topic if provided.
Creative writing skill for analyzing and critiquing story content. Use when the user requests feedback, critique, or analysis of their writing. Provides balanced feedback calibrated to intended audience.
Use this skill when generating AI-agent-friendly documentation for a git repo or directory, answering questions about a codebase from existing docs, or incrementally updating documentation after code changes. Triggers on codedocs:generate, codedocs:ask, codedocs:update, "document this codebase", "generate docs for this repo", "what does this project do", "update the docs after my changes", or any task requiring structured codebase documentation that serves AI agents, developers, and new team members.
Cognitive Atom: Plain (Bai). Rewrites any content to be fully understandable by a smart 12-year-old. It is structure-free — form follows content. Activate this function when the user uses phrases like "put it in plain language", "speak human", "explain this", "plain", or "grok".
General principles for structured content modeling that apply across CMSs, with Sanity-specific guidance. Use when designing content schemas, planning content architecture, or evaluating content reuse strategies.
Use when adding docstrings, creating API documentation, or building documentation sites. Invoke for OpenAPI/Swagger specs, JSDoc, doc portals, tutorials, user guides.
Capture solved problems as categorized documentation with YAML frontmatter for fast lookup
Writing effective code documentation - API docs, README files, inline comments, and technical guides. Use for documenting codebases, APIs, or writing developer guides.
Review documentation changes for compliance with the Metabase writing style guide. Use when reviewing pull requests, files, or diffs containing documentation markdown files.
Research topics and produce comprehensive written documentation. Synthesizes information into clear, well-structured, authoritative content pieces.