Complete skill guide for AI agents to write proper Odoo 18 code. This master file references detailed guides for each topic including models, fields, decorators, views, performance optimization, controllers, and development best practices. Use this skill when writing, reviewing, or refactoring Odoo 18 code to ensure proper ORM patterns, API usage, and performance optimization.
General documentation standards for README, AsciiDoc, and technical documentation
Write prosaic, narrative-style documentation for Lean 4 libraries. Use when creating README files, user guides, tutorials, or comprehensive library documentation.
Generate a library-specific documentation/source reference skill
Fetches up-to-date, version-aware library documentation from the Context7 MCP server before working on a project.
Documentation standards. Apply when completing full feature development, introducing new architecture patterns, or adding new public APIs.
Comprehensive Ruby on Rails v8.1 development guide with detailed documentation for Active Record, controllers, views, routing, testing, jobs, mailers, and more. Use when working on Rails applications, building Rails features, debugging Rails code, writing migrations, setting up associations, configuring Rails apps, or answering questions about Rails best practices and patterns.
Add Google-style docstrings to modules. Use for documentation requests.
Generate MkDocs documentation sites with Material theme, mkdocstrings for API docs, and versioning. Use when setting up or extending project documentation.
Maintain and update architecture documentation in docs/architecture/. Uses tool-based inspection first, falling back to CLI only when needed.
Add new pages to docs.json navigation structure. Updates navigation groups based on user journey (Guides, API Reference, Recipes, etc.). Use when the user asks to add a page to navigation, update docs.json, add to nav, or include a new page in the sidebar.
Generate and maintain comprehensive documentation including Doxygen comments, progress reports, session notes, and API docs for Orpheus SDK.
技术文档撰写专家代理，将复杂代码库转化为清晰文档。当用户需要以下帮助时使用：(1) 编写 README (2) API 文档 (3) 架构文档 (4) 用户指南 (5) 变更日志 (6) 注释和 JSDoc。触发词包括：「写文档」「README」「API 文档」「使用说明」「注释」等文档相关请求。
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
Generates comprehensive book structures for Docusaurus with proper hierarchy, navigation, and SEO. Creates chapter outlines, sidebar configurations, and ensures consistent structure across the book.
プロジェクトで使用しているアーキテクチャの実装ベストプラクティスを調査し、 docs/best-practices.md にドキュメント化する。技術スタックを自動検出し、 スタック別のベストプラクティス（コード例・アンチパターン）を出力する。 「ベストプラクティスをまとめて」「実装パターンを調べて」「コーディングガイドを作成」 「アーキテクチャの使い方を整理」などの依頼時に発火。
Outline extension implementing protocol for documentation domain
プロジェクトで使用しているアーキテクチャの実装ベストプラクティスを調査し、docs/best-practices.mdにドキュメント化する。技術スタックを自動検出し、スタック別のベストプラクティス（コード例・アンチパターン）を出力。「ベストプラクティスをまとめて」「実装パターンを調べて」「コーディングガイドを作成」「アーキテクチャの使い方を整理」などの依頼時に使用。
Write PHP DocBlocks following PSR-5 and PSR-19 PHPDoc standards. WHEN: Writing DocBlocks for PHP classes/methods/functions/properties, documenting @param/@return/@throws, type annotations in PHPDoc. WHEN NOT: Python docstrings (use python-docstring), JavaScript (use js-docstring), TypeScript (use ts-docstring).
Require comprehensive WHY/WHEN/HOW documentation for all functions. Apply when writing functions, classes, or complex logic to explain purpose, usage context, and implementation approach.
Download Swagger/OpenAPI specification file from a URL. Use phrases like "Download swagger file", "Fetch OpenAPI spec", "Get API documentation", etc.
Generate Level 2 (repository docs) from design docs. Use when creating comprehensive topic-based documentation for developers.
