technical-docs
0
pages-explorer-tree
Complete implementation guide for the DocsSidebar v2 (React Complex Tree + Convex + Liveblocks + AI).
raythurnvoid
documentation
sorting
stars
current ordering strategy
query
all entries
refine the visible subset
technical-docs
0
read-guides
Instructions for checking the available guides in the ai4space repository and reading them.
LunCoSim
documentation
technical-docs
0
document-python-component
Write or upgrade conventional Python docstrings for public modules, classes, functions, methods, and properties. Docstrings must be user-facing, mkdocstrings-friendly, include runnable examples, and must not repeat type hints.
NightingaleV
documentation
technical-docs
0
documentation-standards
How user-facing and internal documentation should be written and maintained.
amattas
documentation
technical-docs
0
docs-internal
Docs Internal Agent. 아키텍처 문서, 온보딩 가이드 작성을 담당합니다.
shaul1991
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
JKKN-Institutions
documentation
technical-docs
0
global-commenting
Write self-documenting code with minimal, evergreen comments that explain complex logic without documenting changes or temporary fixes. Use this skill when adding comments to any code file. When deciding whether code needs a comment or should be made more self-explanatory. When writing comments for complex algorithms or business logic. When tempted to add comments about recent changes, fixes, or TODOs. When reviewing existing comments for relevance and accuracy.
mshafei721
documentation
technical-docs
0
documentation
코드를 문서화합니다. "문서 작성", "주석 추가", "document" 요청 시 사용합니다.
jhl-labs
documentation
technical-docs
0
onboarding-c3
Creates C3 architecture documentation from scratch using staged Socratic discovery. Use when the user asks to "adopt C3", "onboard me to architecture", "scaffold C3 docs", "init C3", "set up architecture docs", or starts C3 documentation for a new project. Implements 3-stage workflow: Inventory → Details → Finalize.
lagz0ne
documentation
technical-docs
0
feature-doc-elaborate
Produce a feature/component documentation that adheres to repo standards.
JohnLudlow
documentation
technical-docs
0
code-documentation-generator
Эксперт по документации кода. Используй для JSDoc, docstrings, комментариев и автогенерации документации.
dengineproblem
documentation
technical-docs
0
generate-spec
Generate a specification file from user input/requirements. Use when user says "generate spec", "create spec", "write spec", "spec from requirements", or provides feature requirements and asks to create a spec. (user)
teliha
documentation
technical-docs
0
cursor-development-rules
Provides comprehensive development rules and guidelines for Cursor project development. Use when working on Cursor projects, setting up development environments, or implementing coding standards.
small-java-world
documentation
technical-docs
0
technical-writing
Apply rigorous technical writing standards when creating architecture documentation, system descriptions, component descriptions, API documentation, or any technical specification text. Use when writing descriptions for systems, actors, externals, modules, components, relationships, or interfaces.
EvanLavender13
documentation
technical-docs
0
docs-expert
Co-author and QA documentation such as READMEs, guides, and runbooks. Use when writing or auditing docs (not PRDs/specs).
jscraik
documentation
technical-docs
0
global-commenting
Write meaningful code comments that explain WHY rather than WHAT, focusing on business logic, non-obvious solutions, workarounds, and complex algorithms while keeping code self-documenting. Use this skill when adding comments to explain rationale, documenting complex business logic, explaining workarounds or temporary solutions, describing performance optimizations, writing function documentation (JSDoc, docstrings, XML docs), or reviewing code for appropriate commenting. Apply when working on any code file that contains logic requiring explanation, public API functions, complex algorithms, security-critical code, or architectural decisions. This skill ensures comments explain rationale not implementation (WHY not WHAT), self-documenting code through clear naming (refactor unclear code instead of commenting), concise and evergreen comments (no who/when dated comments - Git tracks this), links to external resources for context, proper function documentation format (JSDoc for TS/JS, docstrings for Python, XML d
TheophilusChinomona
documentation
technical-docs
0
writing-documentation
技術ドキュメント、機能仕様書、ビジネスコミュニケーション資料を作成します。セットアップガイド、ユーザーマニュアル、要件定義書、ステークホルダー向けレポート、インシデント報告など、あらゆるドキュメント作成をカバーします。
sekka
documentation