docs▌

Consolidate redundant documentation while preserving 100% of valuable content.

Interactive demos render a Remotion composition inline in documentation pages using @remotion/player. They live in packages/docs/components/demos/.

Generates and formats changelog files for new releases with version-aware templates and highlight extraction. \n \n Handles three release types: stable minor versions, stable patches, and preview releases, each with distinct file update procedures \n Automatically processes raw markdown release notes by reformatting PR URLs to markdown links and removing contributor sections \n Generates concise 3–5 point highlight summaries for release announcements, prioritizing new features over bug fixes \n

Access current OpenAI developer documentation with MCP tools and model-selection guidance. \n \n Prioritizes the OpenAI Developer Docs MCP server for all queries; falls back to web search only on official OpenAI domains if MCP returns no results \n Includes reference files for model selection, GPT-5.4 upgrade planning, and prompting guidance; always verifies recommendations against live docs before answering \n Covers seven core OpenAI products: Apps SDK, Responses API, Chat Completions, Codex,

Fetch current Railway documentation to answer platform questions accurately. \n \n Provides LLM-optimized sources including full docs, templates, changelog, and blog posts accessible via .md file extensions \n Covers core Railway topics: projects, deployments, volumes, variables, CLI, and pricing \n Designed to be called before answering Railway questions from memory, ensuring responses reflect the latest documentation \n Supports direct doc.railway.com URL conversion by appending .md for markdo

Append plain text to the end of a Google Docs document. \n \n Requires a document ID and text string; inserts content at the end of the document body \n Write operation that should be confirmed with the user before execution \n For rich text formatting, use the raw batchUpdate API instead \n

Javadoc best practices for documenting Java types, methods, and members. \n \n Public and protected members require Javadoc comments; package-private and private members are encouraged, especially for complex code \n Use standard tags: @param for parameters, @return for return values, @throws for exceptions, @see for cross-references, and @since for version tracking \n First sentence serves as summary description and should end with a period; parameter descriptions start lowercase without period

GitHub Actions questions are easy to answer from stale memory. Use this skill to ground answers in official GitHub documentation and return the closest authoritative page instead of generic CI/CD advice.

Manage project documentation for Claude Code workflows including context files, READMEs, and agent instructions. This skill provides structured automation for maintaining accurate, up-to-date documentation that aligns with actual codebase structure and functionality. Use this skill when initializing new projects, updating existing documentation, or ensuring context files accurately reflect current code.

Create comprehensive API documentation with OpenAPI specifications and interactive documentation.