Total 43,935 skills, Documentation & Writing has 1297 skills
Showing 12 of 1297 skills
Make surgical edits to specific sections while maintaining voice cohesion across the essay
Governance-focused README with fixed structure and output contract. Use for asset governance, audit, or standardized first-impression docs. For process-driven creation (templates by project type) use crafting-effective-readmes.
Produces concise, clear documentation by applying Elements of Style principles. Use when writing or improving any technical documentation (READMEs, guides, API docs, architecture docs). Not for code comments.
Diagnose flat dialogue, same-voice characters, and lack of subtext. Use when conversations feel wooden, characters sound alike, or dialogue only does one thing at a time.
Casual but professional tone for team communication. Uses company-specific terminology with scannable format.
Handle structured co-authoring of professional documentation. Use for proposals, technical specs, and RFCs. Use proactively when a collaborative drafting process (Gathering -> Refinement -> Testing) is needed. Examples: - user: "Draft a technical RFC for the new API" -> follow Stage 1 context gathering - user: "Refine the introduction of this proposal" -> use iterative surgical edits - user: "Test if this document is clear for readers" -> run reader testing workflow
Expert blueprint for desktop platforms (Windows/Linux/macOS) covering keyboard/mouse controls, settings menus, window management (fullscreen, resolution), keybind remapping, and Steam integration. Use when targeting PC platforms or implementing desktop-specific features. Keywords desktop, Windows, Linux, macOS, settings, keybinds, ConfigFile, DisplayServer, Steam, fullscreen.
This skill provides comprehensive support for the writing process from ideation through revision. Use this skill when helping users write essays, articles, or creative pieces through interactive collaboration. The skill supports co-evolving outline and prose, voice-based input processing, multiple writing styles, and connection to the user's PKM system for enriched content.
Create Obsidian-compatible Mermaid diagrams. Prefer square layouts (TB + subgraph LR), avoid markdown in labels. Use when creating flowcharts, sequence diagrams, or any Mermaid diagrams in markdown files.
Rewrites text to be clearer, simpler, and more engaging using Scott Adams' writing principles and persuasive techniques. Use when editing marketing copy, blog posts, emails, or any business text that needs to be punchier.
Use when building scenes or planning chapter content - provides scene-sequel framework, tension management, and beat-based structure for engaging scenes
Use when writing documentation, guides, API references, or technical content for developers - enforces clarity, conciseness, and authenticity while avoiding AI writing patterns that signal inauthenticity