Technical Writing
5624 skills in Documentation > Technical Writing
add-neon-docs
Use this skill when the user asks to add documentation, add docs, add references, or install documentation about Neon. Adds Neon best practices reference links to project AI documentation (CLAUDE.md, AGENTS.md, or Cursor rules). Does not install packages or modify code.
testing-anti-patterns
Use when writing or changing tests, adding mocks, or tempted to add test-only methods to production code - prevents testing mock behavior, production pollution with test-only methods, and mocking without understanding dependencies
zai-cli
Z.AI CLI providing:- Vision: image/video analysis, OCR, UI-to-code, error diagnosis (GLM-4.6V)- Search: real-time web search with domain/recency filtering- Reader: web page to markdown extraction- Repo: GitHub code search and reading via ZRead- Tools: MCP tool discovery and raw calls- Code: TypeScript tool chainingUse for visual content analysis, web search, page reading, or GitHub exploration. Requires Z_AI_API_KEY.
content-writer
Writing content across different platforms and styles. This skill should be used when creating blog posts, LinkedIn posts, X/Twitter threads, technical documentation, or other written content. It intelligently selects the appropriate writing style based on the platform, audience, and content type, then applies that style consistently throughout the piece.
prompt-engineer
Use this skill when creating, improving, or optimizing prompts for Claude. Applies Anthropic's best practices for prompt engineering including clarity, structure, consistency, hallucination reduction, and security. Useful when users request help with writing prompts, improving existing prompts, reducing errors, increasing consistency, or implementing specific techniques like chain-of-thought, multishot prompting, or XML structuring.
blog-writer
帮助用户按照 astro-koharu 博客的规范创建新博文。自动生成正确的 frontmatter 结构、选择合适的分类路径,并提供 Markdown 内容框架建议。使用场景:写一篇博文、创建新文章、写文章、写博客、new post、create blog post。
markdown-formatter
Format and clean up markdown documents following best practices
scottink-writer
Write in Scott's authentic voice - British, conversational, self-deprecating, code-first. Use when writing blog posts, technical content, or documentation.
blog-post-creator
Create new blog posts with proper frontmatter, structure, and ScottInk voice. Use when writing blog posts or starting technical articles.
content-linter
Lint content for spelling errors, en-GB compliance, and writing quality. Use when checking markdown files before publication.
documentation-authoring
Create or augment skills and documentation. Use when writing new skills, updating existing skills, or modifying project documentation like AGENTS.md.
using-elixir-skills
Use when writing Elixir, Phoenix, or OTP code - routes to the correct thinking skill before any code is written
fact-check
This skill should be used when the user asks to "verify claims", "fact check", "validate documentation", "check sources", or needs verification of external source references. Provides patterns for systematic fact verification using Context7 and WebSearch.
composewebview-documentation
Manages MkDocs documentation site and API references for ComposeWebView. Use when creating, updating, or building documentation, adding guides, or generating API docs. Handles mkdocs serve, build, and validation.
context7-usage
This skill should be used when the user asks to "check documentation", "latest API", "library docs", "context7", or needs up-to-date library documentation. Provides Context7 MCP usage patterns.
elixir-thinking
Use when writing Elixir code. Contains paradigm-shifting insights about processes, polymorphism, and the BEAM runtime that differ from OOP thinking.
otp-thinking
Use when writing OTP code in Elixir. Contains insights about GenServer bottlenecks, supervision patterns, ETS caching, and choosing between OTP abstractions.
ecto-thinking
Use when writing Ecto code. Contains insights about Contexts, DDD patterns, schemas, changesets, and database gotchas from José Valim.
technical-documentation
This skill should be used when the user asks to "write documentation", "create README", "API docs", "design document", "specification", "user guide", or needs documentation guidance. Provides comprehensive documentation patterns for developers, teams, and end-users in both English and Japanese.
phoenix-thinking
Use when writing Phoenix, LiveView, or Plug code. Contains insights about LiveView lifecycle, Scopes, PubSub, and gotchas from Chris McCord.