Total 52,056 skills, Documentation & Writing has 1488 skills
Showing 12 of 1488 skills
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.
Diagnose weak endings, rushed resolutions, and arbitrary conclusions. Use when stories build well but end disappointingly, when climax feels unearned, or when resolution doesn't complete character arcs.
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.
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).
Create a README.md file for the project
Explicitly update DESIGN.md with decisions from the current conversation. Use when you want to force a design document update.
Guide to Chinese Writing Skills for Generating High-Quality Weekly Newsletters, Blogs, and Tech News Articles
Writing Engine. Start with an opinion, and think it through as you write.
Execute Solana token trades - market orders, limit/pending orders, copy trading, and order management. Use when user wants to "buy tokens", "sell tokens", "place order", "cancel order", "check order status", "copy trade", "follow wallet", or execute any trading operation.
Review the README or a documentation page from several real reader points of view at once. Fans out one parallel reviewer per audience — Claude Code newcomer, power user, plugin/skill author, skeptical senior engineer, non-running decision-maker — each scoring it x/5 and naming concrete, line-level fixes. Use when asked to review, critique, grade, or "get to N/5" the README or any front-door doc, or to check how a doc reads for real users. Not for code review (use /code-review for that).
Systematically analyze existing media to extract transferable elements for new settings. Use when adapting TV, film, or games to fiction, translating tropes across genres, or transforming genre elements for new contexts.
Generates standalone Markdown reference documentation for any Qt/C++ source files — Qt Widgets classes, Qt Quick backends, Qt/C++ modules, plain C++ utilities, structs, free-function headers, and entry points like main.cpp. Use this skill to document any .h or .cpp file: Qt classes, plain C++ code, utility helpers, or application startup files. Triggers on: "document this class", "write docs for my C++", "document main.cpp", "C++ API docs", "document my Qt app", or whenever C++ or header files are provided and documentation is needed. Works with single files, pasted code, or entire project folders. DO NOT use if the user asks for QDoc format output.