api-reviewer
评审 API contract/接口契约(OpenAPI/AsyncAPI/GraphQL/gRPC/WebSocket/SSE/Webhook/SDK/文件格式/IPC-CLI)。用于在 PRD 之后、HLD/LLD/实现之前进行契约设计审查,检查一致性、完整性、兼容性、复用冲突与安全风险,输出准...
Discover Documentation skills, compare source repositories and read the instructions for each workflow.
评审 API contract/接口契约(OpenAPI/AsyncAPI/GraphQL/gRPC/WebSocket/SSE/Webhook/SDK/文件格式/IPC-CLI)。用于在 PRD 之后、HLD/LLD/实现之前进行契约设计审查,检查一致性、完整性、兼容性、复用冲突与安全风险,输出准...
用户旅程访谈专家。通过结构化访谈,将 BRD 中的业务需求转化为清晰、已对齐的用户旅程文档。 触发场景: - "帮我梳理用户旅程"、"用户流程访谈" - "BRD 写完了,接下来细化用例" - "对齐一下 use case"、"确认用户操作流程"...
评审 LLD、低层设计评审、详细设计审查。用于在实现前检查 LLD 是否承接 PRD/HLD/API Contract、遵循 Project Guardrails、覆盖必要模块并具备可实现性与可测试性。
撰写提示词、优化提示词、改写 Prompt、Prompt 优化。将模糊的想法转化为精确有效的 AI 提示词,支持 ChatGPT、Claude、Gemini、DeepSeek、豆包、智谱等多平台。
撰写高质量的高层技术设计文档(HLD),基于 PRD 和 API Contract 做出技术架构决策。适用于 PRD 和 API Contract 完成后需要进行系统架构设计、技术选型、或制定技术方案的场景。
写 PRD、写产品需求文档、PRD 模板、新功能需求。帮助撰写高质量的产品需求文档,支持多种类型:新功能(有UI/无UI)、第三方集成、功能重构、性能/安全优化。
创建 Skill、写 Skill、Skill 模板。帮助创建和优化 Claude Code Skills,遵循 Testany 公司规范。
Help text, error messages, and strings for R-DOS. Use when writing user-facing text, help content, error messages, or modal labels. Reference spec/help.txt and spec/strings/ for authentic Q-DOS II phrasing.
R-DOS development process. Use when planning features, creating documentation, tracking work with beads, or understanding the documentation system.
Rust best practices and overall approach for R-DOS development. Use when writing Rust code, implementing features, handling errors, or structuring code in the R-DOS codebase.
Release a new version of QDOS. Use when the user wants to ship, release, publish, or tag a new version. Handles version bumping, quality checks, tagging, pushing, and homebrew tap updates.
Plugin development for R-DOS. Use when creating new plugins, implementing Plugin trait, handling keys, or structuring plugin code. Reference spec/PLUGIN.md for complete specification.
UI components and rendering for R-DOS. Use when rendering modals, dialogs, lists, or any UI. CRITICAL - explains ModalFrame vs FullScreenView to prevent panics.
Interact with Canonical's Launchpad platform via the Launchpad API (api.launchpad.net) using the lp-api CLI tool. Use when working with Ubuntu/Debian packages, bugs, builds, people, projects, or any Launchpad A...
Implements high-performance streaming using System.IO.Pipelines in .NET. Use when building network protocols, parsing binary data, or processing large streams efficiently.
Navigates WPF Visual Tree and Logical Tree with VisualTreeHelper and LogicalTreeHelper patterns. Use when traversing elements, accessing template internals, or understanding event routing.
Guides decision-making for WPF control authoring including UserControl vs Control vs FrameworkElement selection. Use when creating new controls or evaluating Style/Template/Trigger alternatives.
Checks and clamps mouse coordinates within transformed image bounds in WPF. Use when implementing measurement tools or annotations that should only work inside Pan/Zoom/Rotate transformed images.
Implements parallel processing using Parallel, PLINQ, and ConcurrentCollections in .NET. Use when processing CPU-bound tasks in parallel or improving multi-core utilization.
Defines the basic solution structure for AvaloniaUI Desktop Applications using CustomControl. Use when creating new AvaloniaUI projects or designing stand-alone control styles with ControlTheme.
Implements asynchronous programming patterns using Task, ValueTask, and ConfigureAwait in .NET. Use when building non-blocking I/O operations or improving application responsiveness.
Provides CollectionView alternatives for AvaloniaUI using DataGridCollectionView and ReactiveUI. Use when filtering, sorting, or grouping collections in AvaloniaUI applications.
Binds enum values to WPF CommandParameter using x:Static markup extension. Use when passing enum types to commands or avoiding string-based command parameter errors.
Explains WPF content model hierarchy including ContentControl, ItemsControl, and Headered variants. Use when selecting base classes for custom controls or understanding content/items properties.
The default order uses GitHub repository stars from our indexed data. Stars belong to the source repository and may be shared by multiple skills. They indicate repository interest, not skill installs or an independent quality score.