opencode-plugin-dev
OpenCode plugin development guidance including structure, events, tools, patterns, and best practices
OpenCode plugin development guidance including structure, events, tools, patterns, and best practices
Fetches official documentation for external libraries and frameworks (React, Next.js, Prisma, FastAPI, Express, Tailwind, MongoDB, etc.) with 60-90% token savings via content-type filtering. Use this skill when implementing features using library APIs, debugging library-specific errors, troubleshooting configuration issues, installing or setting up frameworks, integrating third-party packages, upgrading between library versions, or looking up correct API patterns and best practices. Triggers automatically during coding work - fetch docs before writing library code to get correct patterns, not after guessing wrong.
Comprehensive frontend development guide covering HTML, CSS, JavaScript, TypeScript, React, Vue, Angular, and modern web technologies. Use when working on frontend development, web applications, or UI/UX implementation.
This skill should be used when the user asks to "create DocC documentation", "add documentation comments", "write API docs", "set up DocC catalog", "host documentation on GitHub Pages", "document Swift code", "write /// comments", "create tutorials", "generate documentation", "build documentation", "DocC を作成", "ドキュメントコメントを追加", "API ドキュメントを書く", "DocC カタログを設定", "GitHub Pages でホスト", "Swift コードをドキュメント化", "/// コメントを書く", "チュートリアルを作成", "ドキュメントを生成", or needs guidance on DocC catalogs, documentation comments, symbol documentation, articles, tutorials, or documentation hosting for iOS 17+/macOS 14+ Swift projects.
Fetch Expo documentation via llms.txt for up-to-date React Native development references
Fetch React Native documentation via llms.txt for up-to-date framework references
This skill should be used when the user asks to "search docs", "look up documentation", "find docs for [library]", "get documentation for [package]", or when working with a library and needing up-to-date API reference. Uses the context7 MCP server to retrieve current documentation and code examples.
Technical writing excellence - documentation, API references, tutorials, and guides that users actually understand. Clear, accurate, useful.
Generador automático de documentación - API docs, README, guías de usuario y documentación técnica
Explores internal documentation (brain repos, Notion) for context
Technical documentation specialist - create docs, API references, user guides for technical and non-technical audiences
Esta skill debe usarse cuando el usuario pide "documentar un patrón", "documentar un problema", "documentar una decisión", "documentar guías", "documentar la sesión", "crear documentación de", o quiere capturar conocimiento técnico de la sesión usando plantillas estructuradas.
This skill should be used when the user mentions "Taro" in any technical context, asks about "Taro API", "Taro components", "Taro configuration", "Taro development", "Taro project", "mini program with Taro", "WeChat mini program", uses Taro methods (like "Taro.request", "Taro.navigateTo"), or discusses multi-platform development with Taro framework. Provides comprehensive Taro framework documentation including APIs, components, configuration, and development guides.
Technical writing, API docs, and documentation best practices
Create epic-specific documentation skill with external reference docs. MUST BE USED for caching external docs. Fetches URLs, caches full content, uses documentation-engineer to generate cohesive summaries, and creates auto-activating skill. Use when starting work on epic that requires external documentation context (API docs, tool guides, reference materials), or when user mentions "cache docs", "external docs", "API documentation", URLs for docs, documentation needs, reference materials, knowledge caching, or epic context documentation.
Fetch up-to-date library documentation directly into context to prevent hallucinated APIs and outdated code examples. Use when user says "use docs", "fetch docs for [library]", "check [library] docs", or asks about a library's API, methods, or usage patterns and current documentation would be helpful. Also use proactively when generating code for libraries where version-specific accuracy matters.
Technical writing frameworks for clear, maintainable documentation
Queries Context7 library documentation via Python CLI. Use when resolving library IDs, fetching API references, code examples, or conceptual guides.
Guide for creating API client packages from OpenAPI specs using the api_client brick in app_api (project)
列出 Storybook manifests 中的全部组件/文档条目(等价于 list-all-documentation),用于组件发现、盘点与测试覆盖率梳理。
Fetch LLM-optimized documentation for tRPC, the end-to-end typesafe API framework.
When you need check documentation about Ruby classes, modules, and methods use this skill to get full details. Avoid check source code or use `ruby -e` for documentation unless absolutely necessary.
A demo skill that helps with documentation