Technical Writing

Markdown style patterns to use when writing documents.

Draft a Conventional Commits message in markdown when the user asks for a commit message/commit msg (e.g., "commit msg?", "commit message", "msg in md"). Use for any request to write or format a git commit message.

Load when working on documentation systems, README files, API docs, orimplementing documentation workflows. Contains best practices for treatingdocumentation as code with version control, automation, and CI/CD integration.

Use PMC (Project Manager Claude) CLI for workflow orchestration. Use this skill when running workflows, creating new projects, syncing docs with implementation, or managing project planning.

Kyle's R coding style guide combining tidyverse conventions with personal preferences. Use when writing or reviewing R code to ensure consistency with preferred style patterns.

Use when answering LangGraph questions. Prefer reading local project code/specs; fetch docs only if needed.

Research GitHub, GitLab, and Bitbucket repositories using DeepWiki MCP server. Use when exploringunfamiliar codebases, understanding project architecture, or asking questions about how a specificopen-source project works. Provides AI-powered repo analysis and RAG-based Q&A about source code.NOT for fetching library API docs (use fetching-library-docs instead) or local files.

Use when planning or implementing Vue 3 projects - helps architect component structure, plan feature implementation, and enforce TypeScript-first patterns with Composition API, defineModel for bindings, Testing Library for user-behavior tests, and MSW for API mocking. Especially useful in planning phase to guide proper patterns before writing code.

Builds type-safe database applications with Drizzle ORM including schema definition, queries, relations, and migrations. Use when working with databases in TypeScript, defining schemas, writing type-safe queries, or managing migrations.

Senior Technical Writer with 10+ years documenting complex systems. Use when creating/updating documentation, writing API docs, creating architecture diagrams (C4, Mermaid), generating changelogs, writing READMEs, or creating onboarding guides.

Comprehensive API design and development workflow that orchestrates API architecture, endpoint design, documentation generation, and integration patterns. Handles everything from RESTful API creation and GraphQL schema design to API gateway setup and version management.

Specialized workflow for transforming verbose natural language into semantic OCTAVE structures. REQUIRES octave-literacy to be loaded first. Use when refactoring documentation, generating knowledge artifacts, or compressing context. Triggers on: compress to octave, semantic compression, documentation refactoring.

Create and manage Jupyter notebooks for testing Adobe Edge Delivery Services (EDS) blocks interactively in the browser using the ipynb-viewer block. Interactive JavaScript execution, overlay previews with backdrop, direct ES6 imports. Use when creating notebooks, testing blocks with ipynb files in browser, generating overlay previews, or creating executable documentation.

Updates API documentation, governance docs, and creates Architecture Decision Records (ADRs)

NatSpec documentation standards and best practices for Solidity contracts. Use when documenting code or reviewing documentation quality.

Codex MCP tool reference. Supplemental parameter docs for codex tool (tuannvm/codex-mcp-server).

Use when creating or developing anything, before writing code or implementation plans - refines rough ideas into fully-formed designs through structured Socratic questioning, alternative exploration, and incremental validation

Improves the quality of images, especially screenshots, by enhancing resolution, sharpness, and clarity. Perfect for preparing images for presentations, documentation, or social media posts.

Documentation lookup using Context7 MCP server. Use when needing up-to-date documentation for any library, crate, framework, or API. Always use this for Rust crates, npm packages, Python libraries, or any external dependency documentation.

Guide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks.