Loading...
Loading...
Found 9 Skills
Guidelines for creating and modifying markdown files. Use when writing documentation, README files, or any markdown content.
Write Markdown that people actually read — READMEs, docs, PR bodies, issue bodies and comments, release notes, changelogs. Covers GitHub-flavored extras (alerts, collapsible sections, task lists, mermaid), prose that leads with the point instead of burying it, and a README skeleton.
Personal writing style preferences. Reference this skill when writing, translating, or editing content to ensure consistent style, punctuation, and formatting.
This skill should be used when the user asks to write, edit, review, or improve Markdown content (README, docs, changelog, guides), or needs Markdown formatting, syntax help, or advanced patterns (tables, callouts, task lists, mermaid, details/summary, footnotes).
Use this skill whenever creating or editing any markdown file. Do not wait for an explicit request — if a markdown file is being created or edited, this skill applies.
Creates detailed Product Requirements Documents in Markdown format. Use when writing PRDs, defining feature requirements, or creating specification documents for development teams.
Comprehensive markdown and Mermaid diagram writing skill. Use when creating any scientific document, report, analysis, or visualization. Establishes text-based diagrams as the default documentation standard with full style guides (markdown + mermaid), 24 diagram type references, and 9 document templates.
Write or rewrite the repo-root README.md.
How to work in a Writing Pipeline project (the `writing-pipeline` starter pack): a three-stage drafting flow, ideas → drafts → published. Read when the project has these folders, OR when asked to capture an idea, start or revise a draft, review a piece before it ships, or publish it. Carries the stage flow and review behaviors so that guidance does not live inside template bodies or folder descriptions. Complements the platform `open-knowledge` skill; does not replace it.