technical-docs
0
docs-standard
Standard for creating technical documentation in this repository.
FullFran
documentation
sorting
stars
current ordering strategy
query
all entries
refine the visible subset
technical-docs
0
update-docs
Update documentation after code changes. Use when API endpoints, database schema, backend/frontend structure, or block definitions have been modified.
so-ta
documentation
technical-docs
0
check-docs
Verify documentation quality - checks README.md, CLAUDE.md, and other docs for completeness and accuracy
whoabuddy
documentation
technical-docs
0
tech-design-doc
Generate detailed technical design documents including architecture, APIs, database schemas, and implementation specifications
dikini
documentation
technical-docs
0
phoenix-docs-sync
Syncs calculations documentation and JSDoc with actual behavior. Use after non-trivial changes to calculation modules.
nikhillinit
documentation
technical-docs
0
speclet-spec
Convert a draft document into an executable spec.json with trackable stories
danielcastro-dev
documentation
technical-docs
0
ruby-stdlib
This skill should be used when the user asks about "Ruby standard library", "stdlib", "FileUtils", "JSON", "CSV", "YAML", "Net::HTTP", "URI", "OpenStruct", "Struct", "Set", "Date", "Time", "Pathname", "StringIO", "Tempfile", "Logger", "OptionParser", or needs guidance on Ruby's built-in libraries.
bastos
documentation
technical-docs
0
django-conventions
Comprehensive Django best practices covering project structure, models (field choices, Meta options, managers, QuerySets, migrations), views (CBVs vs FBVs, generic views), Django REST Framework (serializers, ViewSets, permissions), forms, templates, security (CSRF, XSS, SQL injection), performance (N+1 queries, select_related, prefetch_related, caching), testing, and common anti-patterns. Essential reference for Django code reviews and development.
clostaunau
documentation
technical-docs
0
code-implementer
This skill should be used when the user asks to "implement code", "write feature", "create function", "develop component", "code the solution", or requests actual code implementation based on a design. Use for writing production code following specifications. Do NOT use for design decisions, testing, or debugging complex issues.
xkayo32
documentation
technical-docs
0
writing-plans
Use when design is complete and you need detailed implementation tasks for engineers with zero codebase context - creates comprehensive implementation plans with exact file paths, complete code examples, and verification steps assuming engineer has minimal domain knowledge
Jetaofgak
documentation
technical-docs
0
langgraph-docs
Use when answering LangGraph questions. Prefer reading local project code/specs; fetch docs only if needed.
rozwer
documentation
technical-docs
0
writing-plans
Use when design is complete and you need detailed implementation tasks for engineers with zero codebase context - creates comprehensive implementation plans with exact file paths, complete code examples, and verification steps assuming engineer has minimal domain knowledge
Ramblurr
documentation
technical-docs
0
codebase-understanding
自底向上分析代码库并生成层级化 README.md 文档树。从叶子目录开始分析，为每个目录生成包含文件、类、函数一句话描述的 README.md，逐层向上汇总形成完整的代码库文档体系。支持状态持久化和断点续传，适用于理解新项目、生成技术文档、分析代码结构等场景。当用户需要理解代码库结构、分析功能实现、生成代码文档时使用此技能。
yulong-me
documentation
technical-docs
0
update
End-of-session documentation updater. Updates DEVELOPMENT-PLAN.md checkboxes, adds PROGRESS.md session entries, updates GAME-DESIGN-DOCUMENT.md if design changed, syncs CLAUDE.md status, and keeps OS-specific versions (CLAUDE-Windows.md, mac-claude.md) in parity. Use when finishing a coding session or when the user says "update docs" or "end session".
Valorith
documentation
technical-docs
0
google-design-docs
Googleスタイルのデザインドキュメント（設計書）作成ガイド。コーディング前にソフトウェアの実装戦略と重要な設計判断を記録するための非公式文書を作成する。 使用タイミング: (1) 新機能やシステムの実装前に設計を明文化したい時 (2) 適切な設計について不確実性がある時 (3) シニアエンジニアのレビューが有益な時 (4) 設計が曖昧または議論の余地がある時 (5) セキュリティ・プライバシーの検討が必要な時 (6) レガシーシステムの高レベルドキュメントが必要な時 トリガーフレーズ: 「設計書」「デザインドキュメント」「design doc」「実装前の設計」「アーキテクチャ文書」
karak
documentation
technical-docs
0
sphinx-docs
Generates documentation using Sphinx and reStructuredText. Supports API docs, user guides, and architecture documentation. Use when creating project documentation, API references, or technical guides.
parthspatel
documentation
technical-docs
0
code-documentation
Generate comprehensive code documentation including docstrings, comments, and API documentation. Use when code lacks documentation, needs better explanations, or requires API docs. Focuses on clarity, completeness, and following language-specific documentation standards.
lexicalninja
documentation
technical-docs
0
gem-development
This skill should be used when the user asks about "gem development", "create a gem", "gemspec", "publish gem", "RubyGems", "bundler", "gem structure", "gem versioning", "semantic versioning", "gem testing", "gem documentation", or needs guidance on creating and publishing Ruby gems.
bastos
documentation
technical-docs
0
code-doc-generator
为 Python 项目仓库生成详细的技术说明文档。自顶向下介绍项目构建，按时间流程追踪数据流动，详解每个时间点的操作、输入输出和处理细节。用于用户需要深入理解代码流程、初始化过程、数据流、或任何需要详细代码分析的场景。
LakerBlock
documentation
technical-docs
0
docs-generate-readme
Generate Level 1 (README.md) user documentation from design docs. Use when creating or updating package README files for npm/GitHub.
savvy-web
documentation
technical-docs
0
doc-formatter
Format documentation with emojis, status bars, and versioning matrix. Use when creating or updating README files, documentation, specs, or any markdown files.
msftsean
documentation
technical-docs
0
explanation-layer
Keeps narrative framing in docs while keeping code comments structural and stable.
NkanyeziNgobese
documentation