home/categories/technical-docs
category focus

Tech Docs

API references and manuals.

2137 مهارةall categories
sorting
stars
current ordering strategy
query
all entries
refine the visible subset
technical-docs
6

writing-skills

Use when creating or updating SKILL.md documentation - Explains how and why to create a skill.

dave1010
dave1010
documentation
open
technical-docs
6

latex-overleaf

Comprehensive LaTeX documentation from Overleaf Learn tutorials

enuno
enuno
documentation
open
technical-docs
6

writing-specs

Use when creating feature specifications after brainstorming - generates lean spec documents that reference constitutions heavily, link to external docs instead of embedding examples, and focus on WHAT not HOW (implementation plans handled separately)

arittr
arittr
documentation
open
technical-docs
5

technical-design-doc

Generates clear technical design documents with architecture, trade-offs, and rollout plans.

bostonaholic
bostonaholic
documentation
open
technical-docs
5

technical-writing-editor

Technical documentation expert for clear, concise, user-friendly documentation and tutorials

sandraschi
sandraschi
documentation
open
technical-docs
5

technical-writing

Technical writing best practices including documentation structure, clear writing principles, API documentation, tutorials, changelogs, and markdown formatting. Use when writing documentation, creating READMEs, documenting APIs, or writing tutorials.

webdevtodayjason
webdevtodayjason
documentation
open
technical-docs
5

thematic-doc-generator

Generate comprehensive, publication-quality technical manuals with thematic storytelling using multi-agent orchestration. Use when user asks for themed documentation, narrative technical guides, memorable training materials, or mentions themes like Victorian, steampunk, art deco, medieval, or nautical combined with technical topics. Triggers on phrases like "create themed manual", "documentation with storytelling", or requests to make docs "more engaging" or "memorable".

delorenj
delorenj
documentation
open
technical-docs
5

absurdist-readme-writer

Toolkit for creating an entertainingly stupid README that manages to give off Tim & Eric, Steve Brule vibes while maintaining a level of technical acumen that is expected of a modern open source project. This skill applies when users request a silly or absurd README.

delorenj
delorenj
documentation
open
technical-docs
5

llm-doc-gen

LLM-powered documentation generation for narrative architecture docs, tutorials, and developer guides. Uses AI consultation to create contextual, human-readable documentation from code analysis and spec data.

tylerburleigh
tylerburleigh
documentation
open
technical-docs
5

documentation-tutorial

Build hands-on, code-first tutorials from any primary source - technical documentation, codebases, APIs, tools, or other complex material. Extract real examples, working code, and concrete scenarios. Create tutorials using markdown (text-heavy summaries) or React artifacts (complex interactive workflows). Keywords - tutorial, codebase, API, hands-on, code-first, copy-paste, interactive, real examples, primary source

WarrenZhu050413
WarrenZhu050413
documentation
open
technical-docs
5

sdd-render

Render JSON specs to human-readable markdown with AI-enhanced insights, visualizations, and progressive disclosure

tylerburleigh
tylerburleigh
documentation
open
technical-docs
5

context7

Fetch up-to-date library documentation via Context7 API. Use PROACTIVELY when: (1) Working with ANY external library (React, Next.js, Supabase, etc.) (2) User asks about library APIs, patterns, or best practices (3) Implementing features that rely on third-party packages (4) Debugging library-specific issues (5) Need current documentation beyond training data cutoff Always prefer this over guessing library APIs or using outdated knowledge.

clawdbot
clawdbot
documentation
open
technical-docs
5

deepwiki

Query the DeepWiki MCP server for GitHub repository documentation, wiki structure, and AI-powered questions.

clawdbot
clawdbot
documentation
open
technical-docs
5

inline-documentation

Use when writing code - ensure complete JSDoc, docstrings, and inline comments assuming documentation will be generated from code

troykelly
troykelly
documentation
open
technical-docs
5

api-documentation

Use when API code changes (routes, endpoints, schemas). Enforces Swagger/OpenAPI sync. Pauses work if documentation has drifted, triggering documentation-audit skill.

troykelly
troykelly
documentation
open
technical-docs
5

documentation

Use for WRITING documentation with ready-to-use code templates (C# XML docs, TypeScript JSDoc, API docs, README patterns). Best for implementing actual documentation, adding code comments, and creating docs from scratch. NOT for documentation planning (use documentation instead).

CongDon1207
CongDon1207
documentation
open
technical-docs
5

rust-architect

Use when designing or architecting Rust applications, creating comprehensive project documentation, planning async/await patterns, defining domain models with ownership strategies, structuring multi-crate workspaces, or preparing handoff documentation for Director/Implementor AI collaboration

nanlong
nanlong
documentation
open
technical-docs
5

review-docs

ドキュメントとコードの乖離を監査。APIエンドポイント、スキーマ、設定ファイルとドキュメントを比較し、不整合をレポート。定期的なドキュメントヘルスチェックに使用。

k35o
k35o
documentation
open
technical-docs
5

doc-navigator

Efficiently navigate codebase documentation during Research phase. Use instead of Grep/Glob for finding architectural decisions, feature specs, and technical docs. Maps topics to doc locations for fast context retrieval. If codebase lacks documentation structure, provides patterns to establish one.

georgekhananaev
georgekhananaev
documentation
open
technical-docs
5

creating-skills

Guide for creating Claude Code skill documents with YAML frontmatter, instructions, examples, and reference implementations

lawless-m
lawless-m
documentation
open
technical-docs
5

api-documentation

API 文档生成工具。适用于任何后端技术栈的 API 接口文档生成和维护,确保前后端接口规范统一。

ChuDiRen
ChuDiRen
documentation
open
technical-docs
5

tasks-documentation

Use for WRITING documentation with ready-to-use code templates (C# XML docs, TypeScript JSDoc, API docs, README patterns). Best for implementing actual documentation, adding code comments, and creating docs from scratch. NOT for documentation planning (use documentation instead).

CongDon1207
CongDon1207
documentation
open
technical-docs
5

golang

Expert Go developer guide. Use when writing, debugging, or reviewing Go code.

jaeyeom
jaeyeom
documentation
open
technical-docs
5

logging-implementation

Manage implementation logs in _docs/templates/ with consistent format. Use when starting project work, completing implementations, or when user mentions 実装ログ/implementation log.

camoneart
camoneart
documentation
open
Previous
Page 60 / 90
Next