All Skills

OpenHarmony/KaihongOS C/C++ 编程规范。当 Claude 需要为 OpenHarmony、KaihongOS 移植项目编写或审查 C/C++ 代码时使用。涵盖：(1) 代码格式化（clang-format 配置），(2) 命名规范，(3) GN 构建配置，(4) 文档注释规范，(5) 权限配置，(6) 线程同步。

Use this when the user asks about performance, slowness, optimization, or wants to make code more efficient. Focus on hot paths, unnecessary work, and algorithmic complexity.

Resume work from a previous session using a handoff document. Use when starting a new session and a handoff.md exists, when the user says "resume", "pick up where we left off", or "read handoff", or when continuing work started in a previous Claude Code session.

Generate a complete project index with per-module README files for efficient code navigation. Use when starting work on a new project or after major restructuring. Run once per project.

Visualize phase logs as HTML reports.

# OHOS Permission Skill ## 概述 OpenHarmony/KaihongOS 特有的权限配置技术。涵盖 DSoftBus Session 权限、AccessToken 处理、配置文件格式规范等关键知识点。 **适用场景**: - rmw_dsoftbus ROS2 中间件开发 - DSoftBus 分布式软总线应用 - Native 应用权限配置 - 跨设备通信调试 **验证状态**: ✅ 2026-01-19 rk3588s KaihongOS API 11 真机验证通过 --- ## 快速开始 (3 步配置) ```bash # 1. 准备配置文件

Use this to design a nice UI in single html as inspiration & UI exploration.

Monitor Nx Cloud CI pipeline status and handle self-healing fixes automatically. Use when user says "watch CI", "monitor pipeline", "check CI status", "fix CI failures", or "self-heal CI". Requires Nx Cloud connection. Do NOT use for local task execution (use nx-run-tasks) or general CI debugging outside Nx Cloud.

Analyze competitors with feature comparison matrices, positioning analysis, and strategic implications. Use when researching a competitor, comparing product capabilities, assessing competitive positioning, or preparing a competitive brief for product strategy.

Use this for SQL queries, database schema design, ETL pipelines, data transformations (pandas/Spark), and data validation.

Initialize prompt-vault logging environment for the current project.

Generate or update CODEMAP.yaml - a semantic map of code locations for LLM navigation

Use this skill when you need to configure, create, or troubleshoot Claude Code hooks. This includes setting up PreToolUse hooks, PostToolUse hooks, UserPromptSubmit hooks, debugging hook failures, or any automation within Claude Code. Examples include "I want to run tests before every file edit", "My hook isn't firing", "1 out of 2 hooks ran", or "How do I create a hook that formats JSON output with jq?"

Use this for mobile app development (iOS/Android), cross-platform frameworks (Flutter, React Native), and mobile-specific UI/UX patterns.

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes

Clean Architecture audit for Go services. Use when reviewing layered architecture, dependency rules, or gRPC/usecase/repository patterns. Ensures proper separation of concerns and dependency inversion.

Use when working with agent teams on multi-step development tasks, to coordinate teammates effectively using commands and review agents

Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation

DDD 端到端交付流程。DDD 理論基礎（戰略設計、戰術設計、CQRS）→ Event Storming 領域探索 → SA 領域分析 → SD 戰術設計 → 實作規劃。關鍵字: ddd, domain driven design, 領域驅動, bounded context, aggregate, event storming, 事件風暴, sa, sd, 系統分析, 系統設計, implementation plan, 實作規劃, cqrs, 戰略設計, 戰術設計, 限界上下文, 聚合, 聚合根, 領域事件, 通用語言, ubiquitous language, context mapping, 上下文映射

April Dunford's positioning framework for clear market differentiation. Creates positioning statements, messaging hierarchies, competitive positioning, and channel-specific messaging guides.

Systematic codebase scanning for features and evidence-based feature-to-benefit translation. Extracts what a project does from its code and translates it into what users gain. Use when generating README features tables, auditing feature coverage, or building benefit-driven documentation.

Validates documentation quality and freshness — checks for broken links, stale content, llms.txt sync, image issues, heading hierarchy, and badge URLs. Runs locally or in CI. Use to catch documentation decay before it reaches users.

Use when a project spans multiple phases with review gates between them — architecture then implementation then integration, for example

Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always