Documentation & Writing for Claude Code

Design system skills: component specs, design tokens, naming conventions, spacing and grid systems, accessibility standards, and documentation.

Connects Claude to Feishu/Lark for collaboration, messaging, and document management across team workflows.

Retrieve up-to-date documentation for software libraries, frameworks, and components via the Context7 API. This skill should be used when looking up documentation for any programming library or framework, finding code examples for specific APIs or features, verifying correct usage of library functions, or obtaining current information about library APIs that may have changed since training.

Convert documents and files to Markdown using markitdown. Use when converting PDF, Word (.docx), PowerPoint (.pptx), Excel (.xlsx, .xls), HTML, CSV, JSON, XML, images (with EXIF/OCR), audio (with transcription), ZIP archives, YouTube URLs, or EPubs to Markdown format for LLM processing or text analysis.

Use this skill when the user wants to read or search their Monologue notes through the Monologue Notes REST API. It covers authentication with the MONOLOGUE_API_KEY environment variable, safe token handling, listing notes, fetching a single note, pagination, filters, and error handling. The API is read-only and should be accessed with direct HTTP requests such as curl or any equivalent REST client.

Generate beautiful code snippet images using ray.so. This skill should be used when the user asks to create a code image, code screenshot, code snippet image, or wants to make their code look pretty for sharing. Saves images locally to the current working directory or a user-specified path.

Connect Claude Code to Outline for document search, reading, creation, and management

Russian text quality — ~1,044 rules for typography, info-style, editorial, UX writing, business correspondence, and AI-text cleanup

Essential Elixir and Phoenix LiveView development guide with enforced skills, hooks, and patterns for idiomatic code

Skill: Spectrum 2 component documentation on-demand. Fetches S2 design guidelines, component options, and usage patterns without loading a persistent MCP server.

Turn uploaded VoiceDrop voice memos (the jianshuo.dev/files R2 inbox) into WeChat article drafts — pull the unprocessed recordings, transcribe, and mine articles from each.

Prompt-native interactive HTML docs. Open-source community implementation of Jesse Pollak's bdocs idea.

Essential skills for everyday development: beginner-friendly explanations (baby-education), comprehensive README creation (readme-expert), LLM prompt optimization (prompt-engineering), AI-to-human doc transformation (humanize-docs), technical spec creation (quick-spec), pre-deployment QA checklisting (pre-deploy-checklist), and developer progress logging (been-there-done-that).

Corezoid BPM platform skills, MCP server, docs, and samples for Claude Code.

Review markdown documents with an interactive TUI and let Claude address feedback automatically.

Knowledge engineer — architecture docs, ADRs, API specs, system diagrams, onboarding

Write an Architecture Decision Record — document what was decided, why, what alternatives were considered, and what trade-offs were accepted. Use when asked to "write an ADR", "document this decision", or "why did we choose X".

Maintain per-repo and cross-repo changelogs — append structured entries after agent work. Use when asked to "log this change", "update changelog", "what changed", "change history".

Map the system architecture — read the codebase, identify services and connections, output a C4-level architecture map as Mermaid diagrams with component descriptions. Use when asked to "map the architecture", "system diagram", "how does this work", or "architecture overview".

Generate onboarding documentation — what this project does, how to set up locally, where things live, key decisions, how to deploy. Written for day-one engineers who know nothing. Use when asked for "onboarding docs", "new engineer guide", "how to get started", or "developer setup".

Generate a polished HTML presentation page and Obsidian Canvas for big releases — new products, takeovers, major migrations. Non-technical audience. Use when asked to "present this", "release announcement", "show what we built", or "stakeholder update".

Documentation reconnaissance for takeover — find all docs, assess accuracy, freshness, coverage, and discoverability, and identify critical knowledge gaps. Use when asked "what docs exist", "documentation assessment", or "knowledge gaps".

Render agent findings as a styled HTML report in the browser. Use when asked for "full report", "detailed report", "show in browser", or when CLI output exceeds the 40-line budget.

Internal legal controls review — approval workflows, doc governance

Draft compliance policies required by a framework

Contract & Policy Drafter — NDA, MSA, employment agreements, SLAs, vendor contracts

Draft a contract or policy document from a description

Survey existing contracts and policy documents

|

|

|

Corporate Governance Advisor — board resolutions, cap table, equity plan docs

Draft board resolutions and corporate consent documents

Draft equity plan documents and option grant agreements

Draft regulatory response letters and regulator comms

Produce a system design doc — components, data flow, decisions made, tradeoffs, failure modes. Not a list of options. An actual design with calls made. Use when asked for "system design for", "architect this", "how should we build", or "design the backend".

Privacy & ToS Drafter — GDPR-compliant privacy policies, ToS, cookie policies, DPAs

Draft GDPR-compliant privacy policy for the product

Draft Terms of Service for the product