technical-docs
0
skill-building
How to create Claude Code skill documents with YAML frontmatter, instructions, examples, and reference material
lawless-m
documentation
sorting
stars
current ordering strategy
query
all entries
refine the visible subset
technical-docs
0
local-dev-plan
Generate a local development environment plan for any stack. Use when user asks for local dev setup instructions, docker-compose configuration, or how to run a stack locally.
bnayae
documentation
technical-docs
0
rspress-api-docs
Generate API documentation from TypeScript source code for RSPress. Use when documenting package APIs, extracting types from source code, or creating function/class reference pages.
savvy-web
documentation
technical-docs
0
development-guidelines
チーム全体で統一された開発プロセスとコーディング規約を確立するための包括的なガイドとテンプレート。開発ガイドライン作成時、コード実装時に使用する。
yamato0811
documentation
technical-docs
0
sdlc-development
Guides implementation phase. Use when writing code, implementing features, or building functionality. Ensures code quality, testing, and documentation.
Jameera-Mahima
documentation
technical-docs
0
global-commenting
Write minimal, helpful code comments that explain why rather than what, prioritizing self-documenting code with clear structure and naming. Use this skill when adding comments to code, documenting complex logic, explaining non-obvious decisions or algorithms, writing function or class documentation, creating inline explanations for large sections of code, removing outdated or unhelpful comments, refactoring code to be more self-explanatory, or ensuring comments remain evergreen and relevant long-term. Use across all programming languages when deciding whether and how to comment code, including when writing or reviewing .js, .ts, .py, .java, .go, .rs, .rb, .php, .jsx, .tsx, .vue files or any other code files.
tlabs-xyz
documentation
technical-docs
0
writing-clojure-docstrings
Guidelines for writing effective Clojure docstrings with markdown formatting, wikilinks, code examples, and tables. Always use this skill when writing or reviewing docstrings in Clojure code, or when asked about docstring formatting and style. Triggers on (1) writing new functions/vars/namespaces with docstrings, (2) updating existing docstrings, (3) questions about docstring best practices, (4) reviewing code with docstrings.
Ramblurr
documentation
technical-docs
0
doc-updater
コード変更、API変更、新機能追加時にドキュメントを自動更新します。公開APIやインターフェースの変更、新クラス・関数・モジュールの追加、アーキテクチャの重要な変更、ユーザーからの明示的なドキュメント更新依頼時に起動します。プロジェクトのドキュメント標準に準拠した更新を提案します。
drillan
documentation
technical-docs
0
docs-as-code
Load when working on documentation systems, README files, API docs, or implementing documentation workflows. Contains best practices for treating documentation as code with version control, automation, and CI/CD integration.
chekos
documentation
technical-docs
0
repo-documenter
Provide repository-wide documentation guidelines under `docs/`. Use tool-based inspection first, and keep `README.md` and `docs/` in sync with the current state of the app.
timbuchinger
documentation
technical-docs
0
moqui-service-writer
This skill should be used when users need to create, validate, or modify Moqui framework services, entities, and queries. It provides comprehensive guidance for writing correct Moqui XML definitions, following framework patterns and conventions.
schue
documentation
technical-docs
0
keep-it-simple
Provides guidance and best practices for writing simple, understandable code that developers can easily maintain
Jacobgokul
documentation
technical-docs
0
tutorial-documentation
Use this skill when working on Skyline tutorials or tutorial tests.
ProteoWizard
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
JohnStrunk
documentation
technical-docs
0
ts-docstring
TSDoc documentation standards for TypeScript following tsdoc.org conventions. WHEN: Writing TSDoc comments, documenting TypeScript functions/classes/interfaces/types, generating docs with TypeDoc, improving existing TS documentation. WHEN NOT: JavaScript code (use js-docstring), Python (use python-docstring), PHP (use php-docstring), runtime logic without documentation needs.
LounisBou
documentation
technical-docs
0
docusaurus-documentation
Use when looking up information from the latest Docusaurus documentation at https://docusaurus.io/docs
mcclowes
documentation
technical-docs
0
doc-vault-skill
Auto-activating documentation cache with fresh API docs. Fetches and automatically consults cached documentation when user works with libraries/frameworks.
orakitine
documentation
technical-docs
0
ringwriting-plans
Creates comprehensive implementation plans with exact file paths, complete code examples, and verification steps for engineers with zero codebase context.
LerianStudio
documentation
technical-docs
0
doc-generator
Generate comprehensive documentation including API docs, comments, and README
yasun1
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
PoulpYBifle
documentation
technical-docs
0
rspress-page
Scaffold new RSPress documentation pages with proper structure and templates. Use when creating new docs pages, adding package documentation, writing guides, or setting up API reference pages.
savvy-web
documentation
technical-docs
0
global-commenting
Write self-documenting code with minimal, helpful comments that explain large sections of logic without cluttering the codebase. Use this skill when writing code comments, documenting complex logic, reviewing whether comments are needed, writing function documentation, explaining non-obvious code sections, ensuring code clarity through naming and structure, avoiding temporary or change-related comments, keeping comments evergreen and future-relevant, or deciding between adding comments versus refactoring for clarity. Apply this skill when writing or reviewing any code file to ensure comments add value without creating noise, and that code is primarily self-explanatory through clear naming and structure.
pdovhomilja
documentation
technical-docs
0
agent-handoff
Generate comprehensive handoff documentation optimized for AI agent takeover by analyzing project structure, design docs, and codebase
yarlson
documentation