Loading...
Loading...
Found 39 Skills
Create and manage behavior specification wikis in Obsidian format. Use when creating specs, documenting features, or when user mentions "wiki", "spec", "feature", or "Obsidian".
Update the API reference documentation by downloading the latest OpenAPI spec from production and regenerating the Docusaurus API docs
Generate Word documents (.docx) from Markdown.
Keep README.md in sync with code changes (APIs, features).
Maintain project brain with architectural decisions in memory file.
Guide for creating comprehensive project setup README.md files. Use when users want to document dotfiles, development environments, libraries, frameworks, CLI tools, or any project requiring installation and setup instructions. Triggers on requests like "create a setup guide", "write installation docs", "document my project", or "make a comprehensive README".
Use this skill to create and publish changelog announcements for new features, improvements, or bug fixes. This skill handles the complete workflow - creating detailed changelog documentation pages, adding sidebar announcement cards, and ensuring everything follows project standards. Use when the user mentions adding changelog entries, documenting new features, creating release notes, or announcing product updates.
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.
Use when creating or developing, before writing code or implementation plans - refines rough ideas into fully-formed designs through collaborative questioning, alternative exploration, and incremental validation. Don't use during clear 'mechanical' processes
Update PRD based on design decisions and strategic changes made during conversations
Author RFC documents for proposed technical changes with clear problem framing, options, tradeoffs, and decision path. Use when proposal alignment and review sign-off are needed before implementation; do not use for post-decision implementation-only docs.
ADR management skill. Auto-invoked for generating architecture decisions, documenting design rationale, and maintaining the decision record log. Uses native read/write tools to scaffold and update ADR markdown files.