Total 52,228 skills, Documentation & Writing has 1491 skills
Showing 12 of 1491 skills
Official document writing assistant for Chinese government documents. Based on GB/T 9704-2012 standard. Triggers when: Writing Chinese official documents (公文), formatting documents according to national standards, reviewing document compliance, or creating notices, reports, requests, replies, letters, or minutes. Commands: - /gongwen notice <topic> - Write a notice (通知) - /gongwen report <topic> - Write a report (报告) - /gongwen request <topic> - Write a request (请示) - /gongwen reply <topic> - Write a reply (批复) - /gongwen letter <topic> - Write a letter (函) - /gongwen minutes <topic> - Write meeting minutes (纪要) - /gongwen check <document> - Check document compliance - /gongwen format - Show formatting rules Capabilities: 15 document types support, GB/T 9704-2012 compliance, hierarchy numbering rules, font and layout specifications, and document structure templates.
Long-form Web Novel Writing. Assists in creating long-form web novels from outline to full text, including management of worldviews, characters, and plot lines. Trigger methods: /story-long-write, /write-long-novel, /story, /web-novel, "Help me start a book" "Write an outline"
Manage multi-level novel revisions while preventing cascade problems. Use when editing novels, when changes at one level break things at others, when you need systematic change management for long-form fiction, or when revisions keep creating new problems.
Use when writing or editing novels, short stories, or any fiction manuscript. Trigger on: 'write fiction', 'edit my novel', 'developmental edit', 'line edit', 'character voice', 'plot hole', 'brainstorm', or fiction writing tasks.
Design multi-generational societal evolution for science fiction settings. Use when creating civilizations that diverge from baseline humanity, when exploring how environments shape cultures over generations, or when worldbuilding requires deep time development.
guidelines for creating, reviewing, updating, and searching ADK documentation - use when users ask about writing, maintaining, or auditing ADK bot docs
Create, update, or supersede architecture decision records under `architecture-decisions/`. Use when the user asks for ADR work or `spec-loop-plan-task` routes ADR writing.
Manage project changelog following Keep a Changelog format. Use when documenting releases, adding change entries, generating changelogs from commits, or maintaining version history.
Create a README.md file for the project
Create or update skills by generating, editing, or refining SKILL.md files in this repository. Use when authoring new skills or revising the structure, frontmatter, or guidance for existing ones.
Write a structured architecture decision document — an RFC / design doc / technical doc that records *why* a non-trivial technical choice was made, not just what was built. Follows a six-part method: contextualize for a newcomer, state the architecturally-relevant requirements, design components against them with static + dynamic diagrams, weigh every alternative by pros / cons / risks (each risk with impact, probability, mitigation, contingency), record the decision and how it was made, then conclude and communicate. Writes in the language of the request. Reach for it whenever someone is choosing between technical options or documenting one — "write an RFC", "design doc", "architecture decision", "ADR", "tradeoff analysis", "technical documentation of an implementation", "help me decide between X and Y" — even if they never say "RFC". Also fits the retrospective variant: documenting an implementation after the fact (lessons learned, version history).
Louis Rossmann's writing voice for general prose: testable-number density, high sentence-length variance, claim-then-proof structure, contractions, contempt shown through precision. Consult when writing in his voice.