Loading...
Loading...
Found 1,415 Skills
Reviews and proofreads blog posts, articles, documentation, communications, emails, and any other write-ups to improve conciseness, legibility, clarity, and tone. Fixes typos, grammar issues, redundancies, run-on sentences, and punctuation errors. Use when the user asks to proofread, review, edit, or improve a piece of writing, or when they share text and ask for feedback, corrections, or a revised version.
Provides templates, standards, and best practices for writing clear, comprehensive technical documentation
Guidelines for creating and modifying markdown files in WooCommerce. Use when writing documentation, README files, or any markdown content.
Narrative templates for git history documentation. Used by /git:code-story command.
Generate comprehensive service decommission documentation
Run /check-docs, then fix the highest priority documentation issue. Creates one fix per invocation. Invoke again for next issue. Use /log-doc-issues to create issues without fixing.
Build comprehensive ARCHITECTURE.md files for any repository following matklad's canonical guidelines. This skill should be used when creating codebase documentation that serves as a map for developers and AI agents, auditing existing repos for architectural understanding, or when users ask to 'document the architecture', 'create an architecture.md', or 'map this codebase'. Produces bird's eye views, ASCII/Mermaid diagrams, codemaps, invariants, and layer boundaries.
TDD applied to documentation - create production-ready skills. Use when authoring new skills. Includes writing style guidelines for clear prose.
Create comprehensive planning documentation for a native Android app that integrates with an existing web-based SaaS platform. Use when building a mobile companion app for any SaaS — ERP, CRM, POS, logistics, healthcare, fintech, etc. Generates 7 production-ready planning documents: PRD, SRS, SDS, API Contract, User Journeys, Testing Strategy, and Release Plan.
Write like a human, not a language model. Avoid AI-tell vocabulary, formulaic structures, and hollow emphasis. Apply to ALL written output including prose, documentation, comments, and communication. Use when drafting prose, documentation, comments, or any written output that should sound human.
Creates task-oriented technical documentation with progressive disclosure. Use when writing READMEs, API docs, architecture docs, or markdown documentation.
Add and update the documentation website for Syncpack. Use when making user-facing changes to the codebase.