Browse Skills

Release Notes Generator analyzes git history and code diffs since the previous release to produce user-facing release notes in the project's established format. Use it when drafting or preparing release notes for a new version of the Obsidian plugin.

Backend to Frontend Handoff Docs produces a structured API handoff document for frontend developers when backend work is complete. Use it to document endpoints, DTOs, validation rules, business logic, and integration notes without backend Q&A.

C4 Architecture generates C4 model diagrams in Mermaid syntax for documenting software architecture at context, container, component, and deployment levels. Use it when you need to visualize system structure or communicate architecture to technical and non-technical audiences.

Crafting Effective READMEs helps write or improve README files by matching templates and guidance to the audience and project type. Use it when creating, adding, updating, or reviewing project documentation.

Difficult Workplace Conversations provides a structured preparation-delivery-followup framework for handling workplace conflicts, performance discussions, and challenging feedback. Use it to prepare, deliver, and follow up on tough conversations effectively.

Frontend to Backend Requirements documents frontend data needs for backend developers. Use it to communicate what data and actions a UI needs without dictating API structure.

Humanizer removes signs of AI-generated writing from text to make it sound more natural and human-written. Use it when editing or reviewing text that seems AI-generated, based on Wikipedia's guide to signs of AI writing.

Helps write and maintain documentation for the Carbon manufacturing platform (ERP+MES) using its Fumadocs site. Guides authoring in the house style with real MDX components and source-grounded verification.

Author and edit the Carbon documentation site, including editorial Guide chapters and Reference entity pages. Follows a grounded-in-source workflow with flow-based architecture and build verification.

Surveys how best-in-class ERPs implement features and produces a structured findings file. Use before designing ERP-domain features like accounting, inventory, or manufacturing.

Guides feature design by researching competitors, surfacing open questions, and interviewing stakeholders before writing the spec. Use for new modules, data model changes, or changes across 3+ files.

Guides feature design and spec writing by researching competitors, making design decisions, and resolving open questions before writing the spec document. Use for new features, modules, data model changes, or cross-module changes.